Choose public URL, secret-link token, org invite, or client-side passphrase encryption.
gno.sh ships four visibility modes.
A public URL anyone can read while the publication is active and unrestricted. Good for open research notes, client-facing overviews, and anything you’d otherwise post on a blog.
URL shape:
https://gno.sh/share/<owner>/<slug>When the imported artifact carries a valid public-agent manifest, this same space also serves llms.txt, manifest.json, and exact Markdown evidence URLs. These routes are derived only from the declared public projection; gno.sh does not guess or expose other note paths.
A long, unguessable token appended to the URL. Readers with the token open the page; anyone without it gets a 404. You can rotate the token at any time (old links stop working), revoke access entirely, or expire in 24 hours.
Every image request checks the secret token again and is never cached, so rotating or revoking the link also stops the images.
URL shape:
https://gno.sh/secret/<token>Readers must sign in and pass the share’s access checks. Personal shares allow the owner by default; organization shares use membership and access settings. Review the intended audience in Studio. Being able to read an organization share does not by itself grant permission to publish, change access, or delete it.
Invite-only shares publish note text, but they cannot show bundled images yet. Use an invite without images, a secret link, or an encrypted share when local images must appear.
URL shape:
https://gno.sh/private/<slug>Export an encrypted artifact from local GNO with a passphrase you choose, then upload it to gno.sh. Note contents remain encrypted on gno.sh servers; routing, encryption parameters, and the opaque note-ID roster remain outside the ciphertext. Readers enter the passphrase in their browser to decrypt and read.
gno.sh cannot decrypt note contents or recover a lost passphrase. Store it yourself. Switching into or out of encrypted access requires a fresh local export in that mode; gno.sh cannot convert an existing share.
To update an encrypted share, export a fresh encrypted artifact from local GNO and upload it again. Hosted republish does not rebuild encrypted shares from source.
Bundled images stay inside the ciphertext. Only the reader’s browser decrypts them, after the passphrase is entered, and it discards the decrypted images when the reader leaves the page.
URL shape:
https://gno.sh/locked/<token>