Review and share a project asset
Preview an asset, publish an intentional public link, and revoke it when sharing should end.
A project asset can be reviewed inside Forge and, for supported kinds, published to a public share link. Use this when someone needs to read a specific deliverable without navigating the whole project.
For Northgate ESD Packaging, you might share an approved buyer-guide draft for review. Publishing that share link is different from installing the content into Northgate's website or sending an email campaign.
Review before sharing
- Select the correct account.
- Open Projects and the intended project.
- Use Search assets to locate the asset.
- Expand its row and inspect the preview or content.
- Read the project context and confirm the material is ready for its intended audience.
Check names, technical claims, links, and any personal or internal information. A public link is suitable only for material you intend its recipients to access outside the authenticated project.
For Northgate's FAQ, confirm that dimensions and ordering instructions agree with the approved source. Remove internal review notes from the shareable body if those notes are not intended for the reader.
Understand the preview
HTML and email previews show the asset in a restricted preview environment. Scripts do not run there. A static preview is useful for reading and visual review, but it does not establish that an interactive component works after installation on a live website.
Text assets can support readable document sharing. Code and image assets have different handling from publishable document kinds. Do not assume every asset type will offer the same Publish control.
The inline content copy action copies the stored content for placement or reuse. It does not perform the placement. If you copy HTML into a website or email into another tool, review the result in that destination before treating the job as complete.
Publish a public link
- Confirm that the asset is a supported shareable kind: HTML, Email, or Text.
- Choose Publish if your role permits it.
- Read any publication error before proceeding.
- Choose Copy link once the asset is published.
- Open the copied link to verify that the intended asset is displayed.
- Share the link through your approved communication process.
The public route uses a generated token. Treat the link as access to the published material: recipients do not need access to the full private project to read that shared page.
Publication does not itself send a message to anyone. The useful outcome is a verified share page ready for the intended recipient, with the correct content and no accidental internal material.
Revoke sharing
- Return to the same asset in its project.
- Choose Unpublish.
- Check that the old public link is no longer available.
Unpublishing makes the old URL return an unavailable page. Republishing creates a fresh token, so the previously revoked URL stays inactive. If you need to share again, copy and verify the new link rather than distributing the old one.
Revocation stops access through that Forge link. It cannot remove a copy a recipient already saved, so review the content before the first publication rather than relying on unpublishing as the review step.
Troubleshooting
If Publish is missing, check the asset kind and your permissions. If copying fails, the interface offers a fallback for recovering the link. If the preview differs from the final website, inspect the destination's styles and behavior; the project preview is not a complete website test.
If someone reports an unavailable link, check whether the asset was unpublished or republished. Confirm the current link before sending another copy. The task is complete when the intended page is accessible, or when a deliberate revocation has been verified.