Access Roles
Last updated on November 20, 2026
Every member of a TofuPilot organization holds exactly one role, and that role applies across the whole organization. Roles set what a member can do. Access groups layer on top to scope which stations, test data and members a Viewer or an Operator sees.
Changing a member's role requires the Admin or Owner role.
The five roles
| Role | What it is for |
|---|---|
| Owner | Everything an Admin can do, plus SSO, SCIM and deleting the organization. One per organization. |
| Admin | Manages members, access groups, integrations, billing, organization settings and all test data. |
| Developer | Builds the test setup: procedures, stations, deployments, workflows and test data. Uses the connected integrations but cannot connect them or manage members. |
| Viewer | Reads runs, units, parts and analytics in the dashboard without changing anything. Restricted to their access groups unless an Admin or Owner gives them the whole organization. |
| Operator | Runs tests from the Operator UI at the bench and never sees the dashboard. |
The permissions tables below list every action role by role.
Owner
Each organization has exactly one Owner. Owners can do everything an Admin can, plus SSO and SCIM configuration. To delete the organization, contact support@tofupilot.com.
Admin
Admins invite and remove members, change roles, create and delete access groups, and manage test data such as procedures, stations, deployments, and runs.
Admins also manage billing and edit the organization's name, slug, logo and serial number format. They cannot configure SSO and SCIM. Those actions are reserved for the Owner.
Developer
Developers create and update procedures, stations, deployments, parts, units, batches, and other test data. They see every access group's stations, so they can work across production lines without restriction.
Developers cannot manage members, access groups, billing, or SSO.
Viewer
Viewers browse runs, units, parts, and analytics read-only, without being able to create or modify anything. They do not see billing, workflows, alert rules or the connected integrations.
What a Viewer sees depends on their access group assignment. A new Viewer starts with the organization's access for new members, which is no access by default.
- A Viewer with access to the whole organization sees every station, every run, and every member with their email address.
- A Viewer restricted to access groups sees only their access groups' stations, the runs those stations produced and the units, parts, batches and analytics that come from them, and the members of their access groups, without email addresses. Adding a Viewer to an access group restricts them, and only an Admin or Owner gives back the whole organization: deleting their group leaves them restricted, with nothing to see.
This is the role to give a supplier or a contract manufacturer. See access groups.
Operator
Operators land on /operator on sign-in and never see the dashboard. They see their own profile, the stations they belong to (always group-scoped), and basic organization context. They do not see a member list, peer profiles, runs, procedures, API activity, or billing.
Test data is produced through the station API key, not the operator's account. When an operator presses Run in the Operator UI, the run is attributed as operated_by: the dashboard forwards the operator's email to the CLI, and the CLI stamps it on runs.create. Operators without a TofuPilot account can still be attributed: operated_by also accepts a free-text name (from a procedure prompt, a run.operated_by binding, or Python code), recorded as a declared name without an account link. CLI-only runs and kiosk-mode mounts with no signed-in user and no declared name stay unattributed.
Permissions
A ✓ means the role can perform the action. An empty cell means it cannot.
Test data
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View runs, units, batches, parts and revisions | ✓ | ✓ | ✓ | ✓⁴ | |
| Create, edit and delete runs, units, batches, parts and revisions | ✓ | ✓ | ✓ |
Operators produce runs through the station API key, not through their own account.
⁴ For a Viewer restricted to access groups (a new Viewer is, by default), only the runs produced by their groups' stations, and the units, batches, parts and revisions that come from them. Runs uploaded without a station are not included.
Procedures and deployments
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View procedures | ✓ | ✓ | ✓ | ✓⁶ | |
| Create, edit and delete procedures | ✓ | ✓ | ✓ | ||
| View repositories and deployments | ✓ | ✓ | ✓ | ✓⁶ | |
| Link a repository to a procedure | ✓ | ✓ | ✓ | ||
| Deploy, promote to production, and delete deployments | ✓ | ✓ | ✓ | ||
| View environment variables (Secrets as digests only) | ✓ | ✓ | ✓ | ✓⁶ | |
| Create, edit and delete Config environment variables outside production | ✓ | ✓ | ✓ | ||
| Manage Secret, station and production environment variables | ✓ | ✓ |
⁶ For a Viewer restricted to access groups (a new Viewer is, by default), only the procedures linked to their groups' stations or run on them, their deployments, and the environment variables of those procedures, of their groups' stations and of the organization.
Stations
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View stations | ✓ | ✓ | ✓ | ✓¹ | ✓² |
| Create, edit and delete stations | ✓ | ✓ | ✓³ | ||
| Manage station API keys and link stations to procedures | ✓ | ✓ | ✓³ |
¹ All stations for a Viewer with access to the whole organization. For a Viewer restricted to access groups (a new Viewer is, by default), only their groups' stations. ² Only their access groups' stations. ³ Removing a station from its access group, or moving it to another, needs Admin or Owner: the access group decides who may deploy to the station (see access groups and suppliers). A Developer assigned to access groups creates stations inside one of them, and pushes builds and links procedures only to their groups' stations.
Workflows, analytics and alerts
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View workflows | ✓ | ✓ | ✓ | ||
| Create, edit and delete workflows | ✓ | ✓ | ✓ | ||
| View alerts | ✓ | ✓ | ✓ | ✓⁷ | |
| View alert rules | ✓ | ✓ | ✓ | ||
| Acknowledge alerts, and create, edit and delete alert rules | ✓ | ✓ | ✓ | ||
| View API activity | ✓ | ✓ | ✓ | ||
| View and export the audit log | ✓ | ✓ |
⁷ For a Viewer restricted to access groups (a new Viewer is, by default), only the alerts on their groups' stations.
Integrations
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View connected integrations (GitHub, GitLab, Bitbucket, Odoo, InvenTree, Linear) | ✓ | ✓ | ✓ | ||
| Use a connected integration: link a repository, deploy, build a workflow | ✓ | ✓ | ✓ | ||
| Connect, change or remove an integration | ✓ | ✓ |
Members and organization
| Action | Owner | Admin | Developer | Viewer | Operator |
|---|---|---|---|---|---|
| View members | ✓ | ✓ | ✓ | ✓⁵ | ✓⁸ |
| Invite and remove members, and change their role | ✓ | ✓ | |||
| View pending invitations | ✓ | ✓ | |||
| View access groups | ✓ | ✓ | ✓ | ✓⁵ | |
| Create, edit and delete access groups | ✓ | ✓ | |||
| View organization settings | ✓ | ✓ | ✓ | ✓ | ✓ |
| Edit organization settings | ✓ | ✓ | |||
| Delete the organization | ✓ |
⁵ For a Viewer restricted to access groups (a new Viewer is, by default), only their access groups and the members of those groups, without email addresses. ⁸ Only their own profile.
Roles vs access groups
Access groups sit on an orthogonal layer to roles, so the two combine when you decide what someone sees.
- Owners, Admins, and Developers see every station.
- A new Viewer gets the organization's access for new members (no access by default). Once assigned to an access group, a Viewer stays group-scoped (stations, procedures, test data and members) until an Admin or Owner restores the whole organization.
- Operators are always group-scoped, and see no stations until they are assigned to an access group.
Changing a role
Admins and Owners can change a role at any time, and the change applies immediately. For the full walkthrough, see Managing members.
How is this guide?
Access
Learn how to manage who can sign in to your TofuPilot organization, what they can do, and how they authenticate across users, access groups, and stations.
Access Groups
Learn how to scope TofuPilot stations, test data and members with access groups, so a supplier or production line sees only its own results.