Sharing
Every artifact has a visibility. Click Share on the artifact page to change it.
Visibility levels
Section titled “Visibility levels”| Visibility | Who can open it |
|---|---|
| Private | Project members only. |
| Organization | Anyone in the same org, even if they are not on the project. |
| Public | Anyone with the link. No ShareCube account required to view. |
The share dialog also sets what a link grants: Viewer or Commenter. A link never grants Editor. Anonymous visitors can view a public artifact. They cannot comment. Commenting on a public or org link still requires a signed-in user.
Org maximum
Section titled “Org maximum”Organization Owners and Admins set a maximum sharing policy under Settings → Organization:
- Private (most restrictive)
- Organization
- Public
Members cannot share above that ceiling. Lowering the maximum does not rewrite existing artifacts. It only blocks new shares that would exceed it. If you need older public docs pulled back, change those artifacts one by one.
Share URLs
Section titled “Share URLs”There are two useful links:
- Console URL (
/projects/.../artifacts/...) is the editor. Use this for teammates who should comment or edit. - Share URL (
/share/{id}) is the public viewer. Access still depends on visibility. If the artifact is private, the share page will not show it.
When an agent publishes an artifact, it gets both URLs back. Hand people the console URL if they need to work on it, and the share URL if they only need to read it.
What “like a gist, but rendered” means
Section titled “What “like a gist, but rendered” means”A public ShareCube link is a rendered page, not a raw file dump. HTML canvases stay designed. Markdown stays readable. The artifact is not locked inside Cursor, Claude, or any other vendor chat.