Sharing your library

Route: Library → Share

Flip one toggle and your library gets a public URL. Anyone you send it to opens it in a browser — no account, nothing to install — and sees the real thing: your tokens, live component previews, your Do/Don't rules.

https://app.tostada-ui.app/s/kR3nQ7xLm2vB8pT4wZ9aD

A cloud feature: it needs a signed-in account and an organisation, because there has to be a library on the server for the link to point at.

What the link shows

The same read-only Developer view the app already has. Tokens with copyable var(--…) names, layout principles, components with live previews and their usage rules.

What the link does not show

Your edit history is excluded. Every change Tostada records carries the email address of the person who made it, so publishing the history would publish who on your team was working on what, and when. The link never includes it — not hidden in the interface, genuinely absent from what the server sends.

Nothing else identifying travels either: no organisation name, no member list, no internal identifiers, no other library.

Sharing versus inviting

Two different things, and the difference matters more than it looks:

If a developer on your team needs the code side — the variables, the rules, the export bundle — invite them as a reader (Settings → Members). It's free, it doesn't expire, and it won't break the day someone resets a link.

The share link is for the people you can't invite.

Turning it off

Per library — reopen Share and switch off. The URL stops working immediately. Switching back on restores the same address.

Reset link — issues a new address and kills the old one at once. Use it when a link has travelled further than you intended.

For the whole organisation — Settings → Sharing → Allow public sharing. Admins only. Turning it off dead-ends every link in the org straight away, whatever each library's own setting says. Turning it back on restores them.

All of this is enforced by the database, not by the interface. A revoked link returns nothing to anybody, including someone who saved the URL.

What a recipient cannot tell

Every dead link looks identical: revoked, never existed, or switched off org-wide all give the same "this link is no longer active". That's deliberate — otherwise a stranger could use the difference to work out whether a given address was ever real.

Good practice

• Treat the URL as the secret. It's unguessable (21 random characters), but anyone who has it can view the library. It's a link, not a password.
• Reset after a public paste. If a link ends up somewhere you didn't intend, reset it — it takes one click and the old address dies instantly.
• Prefer reader seats for anyone who stays. They're free, and they keep working.