Pick the right kind of handoff.

Share a read-only link

Use a file’s sharing tools to create an expiring read-only link. Choose an appropriate expiry and send the link only to the intended audience. Anyone with an active link may view the shared content, so avoid putting it in a public channel by accident.

Revoke the link when the review is finished. Revocation stops future link access but cannot remove a screenshot or downloaded copy. Trashing the file revokes current public links; restoring it does not restore those links.

Work with a team

Assign team access using the file tools. Owner, editor, and viewer roles determine what the backend allows. Use component comments for specific feedback and resolve a thread after addressing it. Review team membership when someone’s role changes.

Choose an export

• PNG: a convenient image for a document or conversation.
• SVG or PDF: a scalable or document-oriented output; inspect labels and fonts in the receiving tool.
• Source or Markdown: a technical handoff that can sit beside documentation.
• Editable project backup: retain project editing data for a separate import. Inspect the contents before distributing it.

Keep documentation near the code

The GitHub / docs tool can download Markdown or explicitly commit to a repository you select. Repository write access is separate from GitHub sign-in. Check the target repository, branch, and path before confirming a commit.