Use case

Report without handing out logins

Somebody needs the numbers and does not need an account. The usual answers, a screenshot in a deck or a seat for a person who will sign in twice, are both worse than a link.

The situation

Once a month you rebuild the same slide. It is out of date before the meeting, nobody can click into it, and the one question anybody asks is the one the screenshot does not answer.

Giving them an account solves that and creates a different problem: an extra person with access to settings, who signs in twice and then asks you to email it anyway.

How it is done

1. Create a shared link. Name it for the audience, "Board deck" or "Client: Acme", because that name is the heading they see. You can keep up to twenty per site, so each audience gets its own and can be revoked separately.

2. Send it. No account, no sign-up, and no JavaScript: the page renders on the server, so it works with scripts off and on a bad connection.

3. Put a password on anything you would mind being forwarded. Without one, the security is that the token is unguessable, which is genuinely enough for most uses and not for all of them.

4. Let the digest do the monthly email. A summary that arrives on its own is read more often than a dashboard somebody has to remember to open.

5. Annotate. A chart that explains its own spikes stops the meeting where somebody asks what happened in week 12.

Where this stops

Aggregates only. A shared link shows the site's numbers. It cannot reach individual visitors, settings, or anything about the account.

A link is a secret, not a person. Anyone it is forwarded to has exactly the access you gave. If you need to remove one reader without disturbing the others, that is a member, not a link. See giving someone access.

It is one site. There is no combined view across several, so somebody who needs three sites gets three links.