Share a whole project by link, not one email at a time

Sharing a single captured email already worked. It stopped working well the moment the thing under review was a flow rather than a message — a signup sequence, an invoice run, a password reset in four languages. Nobody wants seven links in an email to a client.

A share can now cover a whole project. One link, read-only, no account at the other end.

Two modes, because two audiences

A link is created in one of two modes, and the difference is not cosmetic.

Preview is for the person approving the work. The rendered message, and nothing else.

Developer is for the person fixing it, and exposes tabs you choose from: the HTML source, the plain-text part, the raw message, the headers, the spam analysis, the attachments. Each tab is opt-in per link. The rendered preview is always shown; everything else is a decision you make when you create the link, and you can change it afterwards without minting a new one.

The point of the split is that a link is a grant of access, and a grant should be the size of the job. A client approving a template has no reason to be handed your raw headers.

The controls

A link can carry a password. It can be given an expiry date. It can be revoked outright. It can allow or forbid downloading attachments. It has its own locale, so a French client reads a French page whatever language you work in. On Pro and above it carries your own branding rather than ours.

Every link records when it was last viewed and how many times, which is the quiet feature that turns out to matter most: "has the client actually opened it" is a question people otherwise ask in Slack for three days.

Creating, updating and revoking a link are all recorded in the activity journal, as is notifying someone about it. Share links are the one part of a project that reaches outside the organization, so they are the part with the most complete trail.

Revoked is not gone

A revoked or expired link stops working immediately, and the row stays for thirty days before it is pruned. It remains listed in the manage view the whole time.

This is deliberate. A link that vanishes the instant it is revoked leaves you unable to answer "what was that URL the agency had, and when did we cut it off" — which is precisely the question you get asked. The link is dead; the record of it is not.

What it does not do

A share link is read-only, and it is scoped to what you shared: a project link never exposes another project, and an email link never exposes the project around it. There is no reply, no send, no way back into the account. Reviewers do not take up a seat, which is the whole reason this exists — sign-off should not require procurement.

If you are wiring review into a pipeline rather than sending links by hand, the API reference covers creating and revoking shares programmatically.