Who Can Do What
Three separate answers decide every permission in Trinity. A person's platform role applies on every agent. Their access is set agent by agent. Their relationship to an agent says whom the agent works for, writes to and waits on. This page maps all three, plus what API keys can reach.
Trinity Roles & Permissions Explained: Platform Roles, Agent Access, and Approval Relationships
Nov 2026
Each layer is set separately and answers a different question. What someone can do on a given agent is the three combined: an admin can sit on an agent's roster as a plain viewer, and a Workspace-only user can be the person an agent works for.
1. Platform Roles
Roles stack: admin > creator > operator > user. Each role gets everything below it, and the same checks apply in the UI, the REST API and MCP.
| Action | External clientVerified email, no account | userWorkspace only | operatorRuns shared agents | creatorBuilds and owns agents | adminRuns the platform |
|---|---|---|---|---|---|
| Working with agents | |||||
| Chat with an agent | Yes, with a conditionVerified email | YesShared | YesShared | YesOwn + shared | YesAll |
| Answer asks addressed to themWorkspace Inbox | Yes | Yes | Yes | Yes | Yes |
| Open the operator UIDashboard, agent pages, Operations, Settings | No | No | Yes | Yes | Yes |
| Run tasks and add schedules | No | No | YesShared | YesOwn + shared | YesAll |
| Building agents | |||||
| Create agentsCreator quota: 10 by default | No | No | No | YesQuota | YesUnlimited |
| Install a system from a manifest | No | No | No | Yes | Yes |
| Configure, share and delete an agent | No | No | No | YesOwn | YesAll |
| Through the API and MCP | |||||
Call the operator API and MCP toolsA user gets 403 workspace_only | No | No | Yes | Yes | Yes |
| Create a personal API keyFrom a signed-in session; a key can't create a key | No | No | Yes | Yes | Yes |
| Call admin-only endpoints with a personal key | No | No | No | No | Yes |
| Running the platform | |||||
| Manage users, roles and the email whitelistSigned-in session; not their own role | No | No | No | No | Yes |
| Platform settings, agent quotas, skill sources | No | No | No | No | Yes |
| Read other people's chats with an agent | No | No | No | No | Yes |
| Human-only grantsOps and portal keys, large retention deletions, usage sharing | No | No | No | No | Yes, with a conditionIn person; no API key |
How someone gets a role. The first admin is created at setup. Anyone else who signs in by email gets the role on their whitelist entry, which defaults to user. An admin changes anyone else's role in Settings → Access → User Management. Lowering a role also lowers the whitelist entry, so signing in again can't bring the old role back. See Roles and Permissions.
An external client signs in but gets no account. They prove an email with a code, and Slack proves it automatically. On a Restricted agent the owner approves that email once. See Access Control.
2. Access to One Agent
A shared person can use an agent but can't control it. An admin can do everything an owner can, on every agent.
| On this agent | OwnerCreated it | Shared personAdded in Settings › People | AdminEvery agent | Not sharedEveryone else |
|---|---|---|---|---|
| Using it | ||||
| Open it and chat with it | Yes | Yes | Yes | No |
Run its tasksNeeds the operator role | Yes | Yes | Yes | No |
Start and stop the agentNeeds the operator role | Yes | Yes | Yes | No |
| Read chat history | Yes, with a conditionOwn chats | Yes, with a conditionOwn chats | YesEveryone's | No |
| See runs and task history | Yes | Yes, with a conditionOnly the ones they started | Yes | No |
FilesCredential files: .env, .mcp.json, keys, certificates | Yes | Yes, with a conditionNo credential files | Yes | No |
| Container log and activity timeline | Yes | No | Yes | No |
Add a scheduleNeeds the operator role | Yes | Yes | Yes | No |
| Edit or delete a schedule | Yes, with a conditionOnes they created | Yes, with a conditionOnes they created | Yes | No |
| Controlling it | ||||
| Enable, disable or run a schedule now | Yes | No | Yes | No |
| Change settingsAutonomy, resources, timeout, guardrails. Never with the agent's own key | Yes | No | Yes | No |
| Manage credentials | Yes | No | Yes | No |
| Share itPeople, external clients, channels, public links | Yes | No | Yes | No |
| Delete itNobody can delete the system agent | Yes | No | Yes | No |
Sharing does not create an account. A shared email signs in to the Workspace with an emailed code. Whether that person also gets the operator UI is their platform role.
Unprompted messages. The agent can always message its owner. Anyone else must first have the proactive-messaging toggle turned on in Settings › People.
The agent is held to the person it is working for. During a shared person's turn the agent's file tools reach only what that person could open, it gets no shell, and it can't set up standing work for them. See Agent Sharing.
3. Relationships to an Agent
A relationship records who a person is to an agent, not their job title. The Primary is the person the agent works for. Approvers sign off on gated work. Collaborators and Viewers follow along.
| Relationship | PrimaryThe person the agent works for | ApproverSigns off on gated work | CollaboratorWorks alongside the agent | ViewerFollows without deciding |
|---|---|---|---|---|
| How the agent addresses themMessages, reports, asks, voice notes | to: primary | to: approver | No value of its own | to: viewer |
| Approves gated skills | YesBy default | Yes, with a conditionIf the gate names approvers | No | No |
Approves a gate that names a canon rolerole:<id> | Yes, with a conditionIf they hold that role | Yes, with a conditionIf they hold that role | No | No |
| Receives credential asksThe agent asks for a secret in the chat | Yes | No | No | No |
| Gives access to the agent | No. Only sharing gives access. Assigning someone in Settings › People also shares the agent with them; a person who is assigned but not shared shows a warning and a Share with them button. | |||
| Where it is set | Settings › People → People this agent serves, on instances licensed for it. Non-admins see the section read-only. | |||
| When nobody is assigned | The agent's owner stands in for the Primary. Anything addressed to approver or viewer is refused until someone fills that role. | |||
Assigning people needs an entitlement. Without it there is no People this agent serves section, the owner is the Primary, and approver and viewer are refused. Gates that name the primary contact work on every instance.
An approver must also be able to open the agent. An approval card goes only to people in the role who own the agent, have it shared with them or are admins. See Approvals and Skills and Playbooks.
"Operator" is never a relationship. to: operatorgoes to the instance's operators as a group, with no single person named.
Three Rules People Get Wrong
Assigned is not the same as allowed in
A relationship tells the agent who someone is. Only sharing gives access. If an approver can't open the agent, a gated request is refused with approver_cannot_open_agent. The fix is to share the agent with them.
A role is not the same as a human
An agent's key acts with its owner's role, but it never passes an admin check. Granting power needs a person: roles and new keys need a signed-in browser session, and an agent's settings refuse the agent's own key, so an agent can't raise its own limits.
The layers mix freely
A Workspace-only usercan be an agent's Primary and approve its gated work without ever seeing the operator UI. Raising someone's platform role doesn't change their relationship to any agent, and the reverse holds too.
4. Agents and API Keys
Every API key belongs to a person and can do at most what that person can. Only a browser session, a personal key and the system agent can pass an admin check.
| Caller | ReachesWhat the key can touch | Admin-only endpointsCan it pass an admin check? | Created byWho can mint it |
|---|---|---|---|
Personal keyuser | Everything the owner's role allows, except writes that take a signed-in session | Yes, with a conditionIf the owner is an admin | Any operator or above, for themselves |
Agent's own keyagent | Its own agent, the agents it may call, the agents it spawned | No | The platform, when the agent is created |
System agentsystem | The platform's own agent; skips agent permission checks | Yes | The platform |
Connectorconnector | One agent's exposed skills and chat | No | The agent's owner |
Portal delegateportal_delegate | One route: starts a Workspace session for an end user | No | An admin, in person |
Ops, read-onlyops | Fleet health, telemetry, roster, executions, usage | Yes, with a conditionThose reads only | An admin, in the browser |
Ops, writesops_write | Reset a circuit breaker; start, stop an agent; terminate a run | Yes, with a conditionThose four only | An admin, in the browser |
Grants that need a person refuse every key.Changing roles, adding whitelist entries and creating keys take a signed-in session; an admin's own key is refused too.
An ops key follows its owner. It stops working when the admin who created it is demoted or suspended, so create it under a service account. See Authentication → MCP key scopes.