Members and roles
Last updated 12 November 2026
An account’s members are its people and its Agents, and each member’s role decides what they, and every key that acts as them, may do. Owners and admins invite people to an organization, change roles and remove people; Agents are in Agents.
People and Agents
Members in the console lists an account’s people and Agents, each with its role. Each member has a subject, its id in the account: a person’s user id, or agent.<agent id> for an Agent.
- A person signs in with GitHub or Google and joins an organization by invitation.
- An Agent is a member that is not a person: an identity of one account, for a program, a CI job or a coding agent. It never signs in; it acts only through its own API keys, with the role you give it, and it may have a budget of its own. Its home region is chosen when it is created and never changes. Owners and admins create Agents, in a personal account or an organization (see How an Agent is authorized).
Deleting an Agent, on its page under Members (Delete Agent, in the console only), revokes its keys and every token they minted. The account keeps its databases, and the name is free for a new Agent.
Roles
Every member has one role: member, admin or owner, with the same permissions in the console, the CLI and the API. A role gives people and Agents the same permissions, except three that only people use: whatever its role, an Agent creates no Agents and no keys, and changes no member’s role or name.
| A member with this role may | member | admin | owner |
|---|---|---|---|
| Read the account, its regions, members, databases, streams and Machines | Yes | Yes | Yes |
| Create and delete databases | Yes | Yes | Yes |
| Create and delete streams | Yes | Yes | Yes |
| Create, change, sleep and delete Machines, and set their secrets | Yes | Yes | Yes |
| Reach a Machine’s private ports, run commands in it and use its files | Yes | Yes | Yes |
| List and revoke their own keys, and, for a person, create them | Yes | Yes | Yes |
| Publish a database for anonymous reads, or take it private | No | Yes | Yes |
| Publish a stream for anonymous reads, or take it private | No | Yes | Yes |
| Make a Machine’s port public | No | Yes | Yes |
| Read the account’s usage | No | Yes | Yes |
| Change members’ roles and rename Agents (people only) | No | Yes | Yes |
| Create Agents (people only) | No | Yes | Yes |
| List and revoke other members’ keys, and, for a person, create keys for Agents | No | Yes | Yes |
| Set and change budgets | No | Yes | Yes |
| Buy credit | No | No | Yes |
- Owners and admins invite people and remove them. Only an owner grants
owner, and only an owner removes an owner or changes their role. - Every account keeps at least one person as owner. An Agent may be an owner, but never counts as that person.
- A key acts with its member’s current role, read again on every request, so a role change applies to the next request of every key the member holds.
To change a role in the console, open Members, choose the member, and pick the role beside their name. In a personal account, your own role stays owner; your Agents’ roles change. Each operation’s capability is listed in the Management API reference.
tonbo member list
tonbo member update release-bot --role admincurl -sS https://api.tonbo.dev/v1/members \
-H "Authorization: Bearer $TONBO_API_KEY"
curl -sS -X PATCH https://api.tonbo.dev/v1/members/agent.<agent id> \
-H "Authorization: Bearer $TONBO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"role":"admin"}'Invite a person
An owner or admin of an organization invites a person in the console, on Members: choose Invite person, enter their email and a role (Member or Admin), and choose Create link. The CLI and the API have no invitation step.
- Tonbo sends no email. The console shows the link once: send it to the person yourself.
- The link works once, for 7 days, for a person who signs in with exactly that email. If it is lost, invite the address again; the earlier link stops working.
- The person opens the link, or finds the invitation at the top of any console page once signed in, and accepts it. To make them an owner, change their role after they join.
- Invitations not yet accepted are listed under the members, where you can revoke them.
When someone leaves
A person leaves an organization on its Settings page (Leave organization), or an owner or admin removes them on their page under Members (Remove from the organization). Both are in the console only. At that moment:
- every key of theirs that acts as them in the organization is revoked, so re-joining never brings one back;
- their login reaches the organization no more, from its next exchange;
- everything they created stays with the organization, including the Agents they created and those Agents’ keys.
An organization keeps at least one person as owner, so its last owner cannot leave: make someone else an owner first. Give the programs and jobs that must outlive one person’s membership a key that acts as an Agent, not one of a person (see Keys act as a member).
Keys act as a member
An API key belongs to one account and acts as one member of it, you or an Agent, with that member’s current role and whatever narrowing the key has. Any member creates keys that act as themselves; owners and admins also create keys for Agents whose role is no higher than their own. Nobody creates a key that acts as another person, and owners and admins list and revoke every key of the account.
- A key that acts as you is sent as it is, or exchanged for a short-lived token. It is revoked when you leave the account.
- A key that acts as an Agent is always exchanged for a token first (see How an Agent authenticates).
Your tonbo login is not a key: it is you on one computer, in every account you belong to, so never hand it to an Agent or a CI job. Creating, narrowing, exchanging and rotating keys are in API keys and tokens.
Limits
- An invitation link works once, for 7 days.