Content is never in both homes. Adopting standalone content into a workspace removes its team shares. From then on, everyone in the workspace sees it.
Workspace content
You share a workspace, not single items. Everyone in a workspace sees all of it: files, tables, folders, tasks, outputs, jobs, history and the trash. Team shares never apply to workspace content. Who’s in a workspace:- The owner side. The personal owner, or the owning team’s owner and admins, are admins. Every other member of the owning team is an editor. This access is live and never listed.
- Guests. Everyone you add or invite is a guest, as an editor or a viewer. A guest reaches only the workspaces they are added to.
WORKSPACE_AUTHORITY. See Workspaces.
An agent key limited to a workspace never shares. A read or write key cannot add or remove people or set a public link: it is refused with KEY_ACCESS_LIMITED when its person could.
Sharing has no per-item setting. A write that sends audience is refused with 400 INVALID_FIELD (INVALID_INPUT over MCP) and this message: “Sharing is by workspace now: everyone in a workspace sees all of it. Keep private work in a separate workspace.” A member add or role change that sends membership is refused the same way: “Everyone added to a workspace is a viewer or an editor; set role.”
Public access to one file
To send one file to someone with no account, an editor turns on its public link:visibility is private (members only, the default for every new, adopted or forked file) or link. It is never public (400 INVALID_VISIBILITY). Set it with PATCH /v0/artifacts/:id { visibility }, the MCP tools artifact_patch and artifact_share_policy, or the Public link chip on the file in the dashboard. Publish first, then patch: workspace creation still omits visibility.
A change of visibility alone needs no why. A why you send is recorded. The workspace history reads “Gave public access to” or “Removed public access to”.
Anyone with the URL reads the file through direct reads only: its metadata, content, the /s/ page (HTML, markdown and JSON), its versions, diffs, table rows, and the MCP reads. Earlier versions are readable too, so prune them first (rip artifact prune-versions <id>) if they shouldn’t be. Outsiders never find the file through listings, search, sitemaps or the public listing, and never see its workspace or folder. A file in the trash, or in a deleted folder or workspace, answers them 403.
An outsider who forks a public file gets a standalone copy in their own account; the workspace is untouched.
Standalone content
Team shares
Share an existing artifact with a team you belong to:rip artifact publish --team <slug>, or file the artifact into a team folder. Every member of a team it is shared to can read it and gets collaborator rights: new versions, metadata edits, moves, visibility changes, fork, and sharing to other teams they belong to. Deleting the artifact and deleting a version stay owner-only.
Visibility
Every standalone artifact carries avisibility field that controls anonymous read access:
Set visibility at publish time (
--visibility on rip artifact publish, visibility on POST /v0/artifacts) or change it later (rip artifact patch <id> --visibility private, PATCH /v0/artifacts/:id, or the MCP tool artifact_share_policy).
Visibility grants read access only. Publishing a new version always needs an authenticated caller who can change the artifact: the owner or a member of a team it is shared to.
Reading artifacts
Read endpoints accept optional authentication:GET /v0/artifacts/:id— MetadataGET /v0/artifacts/:id/content— Raw contentGET /v0/artifacts/:id/versions— Version historyGET /v0/versions/:vid/content— Specific version content