Share and Export
Review the exact artifact revision, its linked evidence, and any bespoke content before publication. A saved edit or accepted internal review does not by itself update what a buyer receives. See Review and Approve.
Share a tracked link
In a Project's Buyer links controls, choose the recipient and revision policy before Create link. The two policies have different correction behavior:
- Pinned — keeps the published revision. A correction uses a replacement link; deliberately send that link to the recipient when the corrected work is ready.
- Current — follows the published channel. Editing the internal artifact does not advance it; publishing a correction is a separate decision.
- Recipient context — inspect the recorded revision, activity, and affected content. An internal review decision is not evidence that a recipient has opened the corrected work.
Manage published links in Shared or the Project. Review the changed content before using Publish correction, and inspect the publication result. Linked-claim checks and access controls do not certify every bespoke statement; the team still reviews the final buyer-facing work.
Check native file availability
Native import and export are still being qualified. Confirm support for the exact format and workflow before promising PowerPoint, Word, Excel, or PDF delivery. A visible export or re-import control does not establish fidelity or a supported round trip for the buyer's file.
Where file output is available, inspect the saved revision, operation result, and any reported format losses, then open and review the actual file before sending it. A downloaded copy does not change when the internal artifact or a shared channel is updated.
Which to use
- Pinned link — when the buyer should keep a specific published revision.
- Current link — when the buyer should follow deliberate updates to a published channel.
- File — when the buyer requires it and the exact output has been confirmed and reviewed. Arrange a separate handoff for later corrections.