Publishing and public windows¶
Every ability in Glassy is available to every account. Publishing is the one exception — and it is the only place where free and paid differ for a reason other than capacity.
Why publishing is the gate¶
A public window serves your content from our domain. That makes us the host of something the whole internet can read, which is a different liability from storing your private notes. The paid requirement is an accountability anchor, not a feature wall: a public page needs a real payer behind it, and that one rule is what keeps Glassy from becoming free anonymous hosting.
The enforcement is a single check — canShareIPublic — and it is the same check in the API, the UI, and
the sync apply path.
What a public window is¶
- A note, canvas, or document presented as a standalone page at
#/w/:slug/:id. - A chrome-free single-artifact handoff at
#/present/:kind/:id(kinds:note,canvas,document). - Readable without the app shell; comments and collaboration stay in the workspace.
Who can publish¶
| Surface | Can publish |
|---|---|
| Free account | No |
| Pro | Yes |
| Clear | Yes |
| Your own appliance | Yes — the owner's own domain, no quota, no gate |
On an appliance, allowPublicShare is always true: it is your server and your liability. The gate is a
cloud multi-tenancy protection, the same way storage quotas are.
Publishing and unpublishing¶
- Open the note, canvas, or document.
- Choose Share → Public window.
- Set the slug, then publish. The link is live immediately.
- Unpublish at any time. The public URL stops resolving; the artifact itself is untouched.
If a membership lapses, existing public windows stop being editable as public surfaces — the content is never deleted, and nothing private becomes public.
What publishing does not do¶
- It does not change who can read your private notes. A public window is a deliberate, single artifact.
- It does not bypass the storage quota or sync caps.
- It does not give an agent permission to publish on its own. Agent writes still pass the review loop.
Related¶
- Public Window — the feature surface and presentation routes
- Sync limits and caps — what a plan actually changes
- Agent review and approvals — the gate in front of agent writes