Use cases

Keep clients in the loop

Your client should see the work as it moves, not a status deck once a week. Send them the document you are actually working in, and they follow along as it changes.

From Share on a document, create a guest link. Anyone with it can open the document without signing up, as a viewer or as a commenter; a guest link never grants editing. Your client clicks it and sees the current version, every time.

When the engagement ends, or the link went somewhere it should not have, revoke it and it stops working.

Let them answer on the line

A commenter link lets the client leave comments on the exact text they are about: a question on a requirement, a yes on a decision. You reply in the same thread and resolve it when it is settled, so the agreement stays attached to the spec instead of an email chain.

The work updates itself

The link shows the document, not a copy of it. When you, a teammate or your agent changes the spec in the repository, the client sees the change the next time they look. There is nothing to export and nothing to forget to send.

Publish what is final

For something meant for anyone, a changelog, a guide, a proposal, publish the document as a public page. It stays readable by anyone and, like a link, always shows the current version.

When they should edit

To let a client edit, add them by address as an editor instead. They sign in, their edits merge into the document like yours, and the document reaches their machine in their Shared Vault if they use the desktop app.