Roles and what they can do
Five roles, and where the lines are drawn.
- •Viewer — read-only. Sees agents, executions, reports and the approval queue; decides nothing and exports nothing.
- •Member — day-to-day work. Uses chat, runs agents, creates and exports reports, cancels runs.
- •Manager — builds and operates. Creates and deploys agents, manages connections, and approves high-risk actions.
- •Admin — everything except ownership transfer and deletion.
- •Owner — everything.
team
- Sarah Mensah sarah@example.com Owner
- Tom Alvarez tom@example.com Manager
- Priya Raman priya@example.com Viewer
An agent acts for the person who asked. A viewer asking for a deletion is refused for the same reason they cannot delete it by hand.
The line that surprises people
Reading and changing are separated, and the split falls in the middle of the member role rather than at the edge of it.
- •A tool that only reads needs
chat.use, which a member has. - •A tool that changes anything needs
tool.execute, which starts at manager.
So a member can ask an agent "how many orders came in today" and get an answer, then ask it to update one of those orders and be refused — same person, same agent, same conversation. That is working as intended, and the refusal names tool.execute so the trace says which side of the line it fell on.
If you want someone doing day-to-day work who can also let an agent write, that person is a manager, not a member.
Two more worth knowing
Reviewing and authorising are separate. Seeing the approval queue is a viewer permission; deciding on it starts at manager.
An agent cannot lend you authority. It acts on behalf of the person using it, so a viewer talking to an agent that can create customers still cannot create a customer. This is the property that makes it safe to give an agent a powerful tool: the tool is only as reachable as the person asking.
Roles are a starting point
The five are seeded per workspace rather than hardcoded, so an owner can clone one and adjust it.
Ranks are what stop the ladder being climbed from below. You cannot assign a role at or above your own, and you cannot change the role of somebody who outranks you — including demoting them, which would otherwise be the same escalation taking the long way round. The owner role is not assignable at all; it moves through ownership transfer.