Share and publish
Access is managed in the dashboard, never over MCP: the MCP server has no share, publish or delete tool, so an agent cannot widen access to what it writes. Artifacts start private, visible only to their owner.
Open the share dialog
Section titled “Open the share dialog”In the library, open the row menu (⋯) on an artifact you own and choose Share…. The dialog has two halves: people who can read the artifact, and general access.
Invite a person
Section titled “Invite a person”- Type the email address of an existing account on the same instance and press Invite.
- The address appears in the list as Can view, alongside Owner for you.
- Remove access with the × on that row, and the account stops being able to read the artifact.
The dashboard shows the server’s own answer, so the common refusals read literally as:
| Message | Meaning |
|---|---|
| No user with that email address has an account here. | The address is not registered on this instance |
| You cannot share an artifact with your own account. | You are already the owner |
| That account can already read this artifact. | A grant already exists for that account |
Invitees find the artifact under Shared with me in their own library, with the owner’s email on the row. Their row menu offers Open only: nobody but the owner shares or deletes.
Publish a public link
Section titled “Publish a public link”Under General access, the two states are Only people invited (the default) and Anyone with the link.
- Choose Anyone with the link. The link is created and its URL is shown once, with Copy URL.
- Share that URL. It opens the current revision without an account, marked
noindexso it is not listed by search engines. - Choose Only people invited again to revoke it. Anyone opening the old URL then gets the not-found page.
The URL is shown once because only a SHA-256 of its token is stored: the raw link cannot be recovered from the database. If you lost it, use Reset link:
- Resetting asks first: “Reset the link? The current URL stops working for everyone who has it.”
- Confirming creates a new URL and revokes the previous one in the same action, so the old link dies for everyone holding it.
Links do not expire on their own, and a public link always serves the artifact’s current revision, not the revision that was current when the link was created. To stop sharing entirely, revoke the link or delete the artifact.
What a visitor gets
Section titled “What a visitor gets”| Kind | Public view |
|---|---|
| HTML | The page in the same sandbox as the owner viewer, without the bar |
| Markdown | The rendered document read-only: no editor, no comments, no bar |
A public link is read-only by construction. Visitors cannot comment, edit, see revision history or learn who else has access.
Embedding
Section titled “Embedding”/artifact/<artifactId>?embed=1 drops the viewer bar when you want the artifact alone, which is what
the OpenCode desktop integration uses for its artifact tabs. It needs a signed-in owner or invitee;
public links are already just the artifact.
Delete an artifact
Section titled “Delete an artifact”The row menu’s Delete… opens a confirmation that explains the consequences and requires two presses (Delete artifact, then Confirm delete). Deleting removes the artifact for everyone: the viewer, every invitation and every public link stop resolving at once, and copies already opened elsewhere are not recalled. It cannot be undone.