Share in the artifact view opens one dialog that answers the whole question of who and what can reach your work.
The artifact link
At the top is the artifact's URL, with a copy button, and one line stating the boundary plainly:
Only team members can open this link.
So the link is safe to paste into a team channel, and it is not a public link. Someone outside the team who opens it sees a wall, and can request access from there. For a wider audience, publish the artifact.
Invite people to team
Adds a person to the team the artifact belongs to, by email address, at a role you choose: Viewer, Editor, or Admin. They receive an email invitation.
A team is the unit of access, not the artifact. Anyone in a team can open every artifact in it. There is no way to give someone one artifact and not the rest.
That has three practical consequences:
- Keep private work in a team of its own, with nobody else in it. Your personal team is exactly that until you invite someone.
- Before inviting anyone, look at what else is in the team. An invitation is to all of it.
- To share one artifact with a different group, make a team for them and duplicate the artifact into it. That copy then has its own life — changes on one do not reach the other.
See Team roles.
Invite an agent
Creates a secure, one-time connection link for an AI agent, so you can bring an agent in deliberately rather than waiting for it to hand you something.
You give it:
- A name. This identifies the agent in your access list and on every change it makes, so pick something you will recognise later.
- Capabilities. Read, Write, Share, Publish, as checkboxes. All four are ticked by default, so untick what the agent does not need. A good conservative default is Read and Write.
The dialog states the rule that matters: agents act under your account and do not use a team seat.
Then copy what it gives you and hand it over. Creating the link does not connect anything: the dialog shows a one-time connection link and a ready-made prompt, and you paste one of them into your agent. It appears in your access list once it redeems the link.
Capabilities are fixed at invite time. There is no way to edit what an agent holds afterwards. To change them, remove the agent and invite it again with the capabilities you want. See Revoke an agent.
See Invite an agent.
Manage access
The roster: everyone and everything with access to this team, in one list.
People, with their role in a dropdown you can change, and a remove button. The team owner shows as Owner and cannot be changed here.
Agents, each with its name, an Agent tag, and its capabilities spelled out (read · write · share · publish), with a remove button that revokes it. Revocation takes effect on the agent's next request. See Revoke an agent.
Note the asymmetry: a person's role is a dropdown you can change; an agent's capabilities are not. They are fixed when the agent is invited. To change them, remove the agent and invite it again.
Two rules worth knowing
Agents get capabilities from a human, at consent. Not from a link, not by asking. An agent never petitions the team for more access. If it needs more, it says so to its human, and the human changes it here.
Access is team-shaped today. Both invitations put someone into the team. Per-artifact access for a single person is not a separate control yet.
Coming soon
- Anyone with the link: a public read-only link for people outside the team
- Passcodes and link expiry, so a forwarded link stops working
- The published state and its update count, shown in this dialog
FAQ
Can I share one artifact without giving access to the whole team? No. Access is team-wide: whoever you invite sees every artifact in that team. For a single artifact, either publish it, export it, or create a separate team and duplicate the artifact there.
Does an agent take up a seat? No. Agents act under the account of the human who invited them.
How do I take access away? Manage access, then the remove button on that person or agent.
Can I change an agent's capabilities? Not directly. Remove it and invite it again with the capabilities you want — that is the only route today.
What happens if someone outside the team opens the link? They see a wall, and can request access from it. See Request access to a private artifact.
Is the artifact link secret? It is team-scoped, so it only works for people already in the team. It is not a capability by itself.