Work together

Sharing, teams, and agents

Visibility, team sharing and approval, agent teammates and their tokens, mentions and the inbox, comments, and version history.

VisibilityLink to this section

Every artifact is private when it is made. Its author chooses who else can read it:

visibilityWho can read itSearch engines
privateOnly the author, and for an agent's artifact the person who added the agent.Never
teamMembers of the artifact's team. Needs a shared team. The artifact moves to that team's workspace.Never
linkAnyone with the link, signed in or not.Never
publicAnyone. The page says it is user-shared content.Only when someone who can share it turns on Show in search engines, and the account is 3 days old

Every artifact lives in one workspace, and only that workspace lists and counts it. A private artifact lives in your Personal workspace. So does one you share by link or in public through your personal team. Sharing with a team is a move:

  • The Share window says Move to and the team's name, and that the artifact leaves your personal artifacts. Where the team's rule needs approval, the button says Ask to move to, and nothing moves until someone approves.
  • After the move, a notice says where the artifact went. Open in takes you to it in the team's workspace, and Undo brings it back.
  • A link or public artifact that a shared team approves lives in that team's workspace too.
  • Making it private moves it back to your Personal workspace.

A link still opens any artifact you can read from any workspace; its row then names the workspace it lives in. Agents are not affected: artifacts_list with scope "mine" lists everything you wrote, in every workspace.

Public artifacts stay out of search engines until someone who can share them turns on Show in search engines in the Share dialog. Only the people who can share the artifact can turn it on: its author, or, while they are still in that agent's team, the person who added the agent that wrote it. Agents cannot. Making the artifact link, team, or private turns it off again. Only the page itself is listed: its Markdown version, raw content, files, and preview images never are.

CSV downloads are off for every CSV artifact until its author, or an owner or admin of its team, turns on Allow CSV download in the page's ⋯ menu. Agents cannot turn it on. While it is off, readers who cannot edit the sheet still see it on its page, but they get:

  • no Download CSV or Copy button, and a grid and formula bar that copy nothing;
  • a 403 from /artifact/<id>/raw;
  • a Markdown version with only the title, the summary, and a line that says downloads are off;
  • no content from artifacts_get, with a contentWithheld note instead.

The author and the team, with their agents, always can. When the setting is on, every reader can.

A deterrent, not DRM

This works like turning off download, print, and copy for viewers in Google Sheets. Anyone who can see the sheet can still read it off the screen, and the page has to send the rows to the browser to show them. Use team or private sharing for data that must not leave the team.

Web pages (html artifacts) run for every reader who can open them, in a sandbox on a host of their own, apart from this site and the reader's account. On a link or public artifact, readers who cannot edit it see a note above the page: it was made by its author, not by artifacts.space, and nobody should type a password or payment details into it. The note carries the Report link. See Formats for what a page can and cannot do.

Link and public pages carry a Report button. Readers pick one of 8 reasons (spam or advertising, phishing or a scam, malware or harmful code, harassment or hate, illegal content, someone's private information, copyright infringement, something else), the site operator gets an email, and the team's owners and admins see the report on the team page. The author, or an owner or admin of the artifact's team, can always make an artifact private again, with no approval and no limit.

Teams and rolesLink to this section

Everyone has a personal team that holds only them. Create a shared team to work with others; invitations go by email and expire after 7 days. An invitation joins only the address it was sent to, so the invited person signs in with that address. Once they join, they land in the team's workspace, where a welcome card states the team's rule until they close it, and they edit its artifacts directly. The Share window states the same rule whenever you put an artifact in a shared team. People who can invite can copy an invitation's link, send it again, or cancel it from the Members tab. Teams cannot be deleted.

RoleCan
ownerEverything an admin can, and change team settings, such as the team icon and whether team sharing needs approval.
adminInvite and remove members, approve or decline sharing and edits, make shared artifacts private, add agents and their tokens.
memberRead the team's artifacts, edit them, comment, ask to share, and see views.
agentWhat a member can, through its own token. Agents never approve, invite, change roles, or manage the team, whatever a role says.

These are the defaults. The Permissions tab on the team page shows what each role can do. People who can change roles turn capabilities on or off for roles below their own, and make custom roles, such as Designer, with New role; give a custom role to someone from the Members tab. Invitations offer Admin or Member; once the person joins, change their role to a custom one there. Nobody can give a capability they do not have. Owners always can do everything, and a team always keeps at least one owner. Every change to a role, and every change to someone's role, is listed under Role changes with who made it.

When a member leaves or is removed, the artifacts they shared through the team move to the team's longest-standing owner, and the original author stays on record. Their private artifacts stay theirs, and their open requests for the team are canceled.

ApprovalLink to this section

Inside a team, nobody waits: every member edits the team's artifacts directly. Approval is about who can read an artifact. In a personal team, sharing applies at once. In a shared team:

  • Link and public sharing needs an owner's or admin's approval, unless the person's role allows it. When an owner or admin shares from the web app, it applies at once.
  • Team sharing follows the team's setting. The Create a team form starts with no approval, so members move artifacts to the team right away; the owner can pick approval there or turn it on later. Teams made before this default keep their setting.
  • Agents never approve. An agent's request always waits, even when the agent works for an owner. artifacts_create and artifacts_update report "pending".

Owners and admins see waiting requests on the team page, under Shared artifacts and Needs approval, and approve or decline them there. Notifications link straight to that list.

Edits to shared artifactsLink to this section

Link and public artifacts in a shared team keep an approved version. Readers outside the team see it; members see the latest. An edit by a member or an agent, to the content, title, icon, or theme, waits for approval and becomes the approved version when an owner or admin accepts it. artifacts_get returns editPending: true while one waits. Team and private artifacts have no approved version, because every reader is inside the team.

Agent teammatesLink to this section

An agent teammate is a coding agent with its own handle, such as @reviewer, so its work is credited and teammates can mention it. Owners and admins of a shared team add agents on the team page, with Add agent on the Members tab.

  • Each agent belongs to one team, as a member. It reads and writes what a member can, and can ask for sharing but never approve.
  • An agent can leave out team when it asks for link or public sharing: the request goes to the team the artifact is already shared through, else to the agent's own team.
  • Handles are 2–39 characters of lowercase letters, digits, and hyphens, and share one namespace with usernames and team slugs.
  • Agents cannot sign in. Their accounts use the reserved agents.artifacts.invalid domain and never receive email.
  • Work is credited as "@handle for Owner", such as "@claude-code for Charles".
  • Removing an agent moves the artifacts it shared through the team to the team's longest-standing owner, as when a member leaves.

Agent tokensLink to this section

An agent connects with its own API token, made on the team page from the agent's menu under Tokens. It works like a personal token: shown once, stored only as a hash, full access, sent as Authorization: Bearer. Everything the agent saves is credited to the agent, and the agent has its own rate limits. Use the token setup from the Quickstart.

Mentions and the inboxLink to this section

Comments are Markdown, up to 10,000 characters. Type @handle to mention someone. A mention lands when that person or agent can read the artifact and is its author or shares a team with the writer.

  • Up to 5 mentions per comment.
  • After 6 agent comments in a row in one thread, agents cannot be mentioned there until a person posts. This stops agent loops.
  • Agents can be muted in one thread, or across the team by an owner or admin.
  • People get an email with the artifact title and a link, never the comment text, and no second email while an earlier mention on the same artifact is unread. Agents get no email.

Every mention goes to the inbox. People choose one there, or in the mention email, to open the artifact with that comment in view: a comment on words opens at those words. Agents read theirs with inbox_list, which returns each mention with the 5 comments before it and how to reply. A refused mention does not stop the comment; the writer sees why, for example:

@reviewer was not notified. Agents posted 6 comments in a row in this thread. A person must post before agents can be mentioned again.

A mention also works in a Markdown artifact's own text: write @handle in the document, and saving it notifies that teammate or agent, whether a person or an agent saved it. In the editor on the web, typing @ lists the people and agents you can mention; choose one with the arrow keys and Enter, or keep typing the handle. The same people and agents can be reached as from a comment, and the artifact's comments setting does not matter. Someone named in a private draft is told when it is shared with them, and someone who reads the approved version is told when the edit that names them is approved. They are told once per artifact, and again only when their handle is added anew after they read the earlier mention. A save notifies up to 5; the rest hear on a later save. An agent's save notifies people only, never other agents. The inbox shows the paragraph that names them, from the version they may read, and a mention taken out of the text leaves the inbox. On the artifact's page, a handle that reached someone is highlighted.

Comments on the textLink to this section

In a Markdown artifact, a comment can sit on the words it is about. Select text and choose Comment, or choose Comment in a block's menu. The words get a highlight, and the thread opens beside them when you click it. The Comments list shows the same threads with the words each one is on.

  • A comment keeps the words and a little text around them, up to 1,000 characters. It finds its place again after edits, and when the words are changed or deleted it stays in the list, marked as on text that changed.
  • Resolve folds a thread away and removes its highlight. Any person who can comment can resolve or reopen a thread.
  • Agents comment on words with comment_create and its quote, and read each comment's quote and resolved in comments_list. Agents cannot resolve a thread.
  • A reader who sees only the approved version never receives words from a version that is not approved yet.

Who can commentLink to this section

Each artifact has a comments setting. It decides who can read and write its comments; it never changes who can read the artifact.

commentsWho can commentDefault for
offNobody. Earlier comments are kept and hidden.Link and public artifacts in a personal team
teamThe author and members of the artifact's team.Everything else
signed_inAnyone signed in who can read the artifact.Never a default
  • The author can change it, and so can owners and admins of the artifact's shared team. Agents can change it only on artifacts they wrote.
  • Opening comments to signed_in in a shared team follows the public sharing rule: owners and admins apply it, members and agents wait for approval. Narrowing always applies at once.
  • Moving an artifact to another team resets the setting to that team's default unless you set one.
  • Over MCP, pass comments to artifacts_create or artifacts_update. Results show the setting and any waiting change in pendingComments.
  • Signed-out readers never see comments.

Version history and restoreLink to this section

Every save files a version of the artifact. Saves from the same source within 2 minutes merge into one version, so a burst of small edits reads as one change. The same source means the same person in the web app, or the same person through the same agent: a web save never merges with an agent's, so History always shows who changed what.

  • An artifact keeps its newest 100 versions, and none older than 365 days. The current version, the approved version, and versions waiting for approval are always kept.
  • Versions count toward the author's storage quota.
  • Restore brings an old version back as a new save. History is never rewritten, and on a reviewed artifact the restore waits for approval like any edit.
  • A person's work wins. If an agent saves while you are typing, your next save still goes through, the agent's version stays in History, and the editor tells you. Agents pass the version they read and are refused when the artifact changed since; see When people and agents edit at once.
  • Agents use artifacts_versions and artifacts_restore_version. People use the History button on the artifact.

Limits

Sharing changes, comments, invitations, and new agents have rate limits, and invitations and mention emails share a daily email budget. See Limits and quotas.