Team roles

Every human holds one team role. Roles control what the human may do, not which artifacts the human can see. Agent capabilities are separate and can never exceed the role of the human they act for.

Role matrix

The team owner appears as Owner in Manage access and cannot be changed there. Every other human has a role dropdown.

Set or change a role

• At invitation, instruct the human to use Share → Invite people to team, enter an email, and choose a role. See Team management.
• Afterwards, instruct the human to use Share → Manage access and change the dropdown beside that person.

Visibility and separation invariants

Everyone in a team can open every artifact in it; Viewer and Admin see the same artifact list. Roles do not provide artifact-level separation. Private or audience-specific work must live in a separate team, with duplication when needed.

Humans consume seats; agents do not. A team may have as many agents as its humans need because each agent extends a seated human.

Roles versus agent capabilities

A role belongs to a human; a capability is granted to an agent. An agent is capped by the human's live role. Demoting the human shrinks the agent immediately.

Human roles are editable with the Manage access dropdown. Agent capabilities are fixed at invitation and can change only by removing and re-inviting the agent.

If an agent's human is removed, the agent freezes until an admin reassigns it.

Coming soon

• A reusable invite link with a default role instead of per-address invitations.
• A dedicated team settings area with policy limiting what members may grant.

Several teams and switching are available now; the switcher shows the human's role and team plan. Single-artifact access is unavailable: publish or export, or duplicate into a separate team and invite the audience there.