Roles and Permissions
Every user who belongs to a tenant has a tenant role that controls what they can do inside that tenant. Tenant roles are assigned from Tenant Admin > Users and are independent of a user's global role (such as Global Admin).
Studio has three tenant roles:
- Read-Only — can view Actions, Steps, and Runs, but cannot change anything or start a run.
- User — can view and edit Actions and Steps, and can start runs.
- Admin — everything a User can do, plus tenant administration (managing users, apps, AI Models, data table schemas, API endpoints, mailboxes, and tenant settings).
Permission matrix
| Capability | Read-Only | User | Admin |
|---|---|---|---|
| View Actions and Steps | Yes | Yes | Yes |
| View Runs and run history | Yes | Yes | Yes |
| View Data Tables and their rows | Yes | Yes | Yes |
| View and download Data Files, including zip downloads of selected files and folders | Yes | Yes | Yes |
| View mailboxes and the emails they received | Yes | Yes | Yes |
| View the AI Models available to the tenant (global models and tenant models) | Yes | Yes | Yes |
| Ask Shepherd questions (with attached files) and get previews | Yes | Yes | Yes |
| Create, edit, duplicate, or delete Actions | No | Yes | Yes |
| Add, edit, or delete Steps | No | Yes | Yes |
| Publish or enable/disable an Action | No | Yes | Yes |
| Import Actions | No | Yes | Yes |
| Create, edit, or delete Skills | No | Yes | Yes |
| Start a run (execute an Action) | No | Yes | Yes |
| Delete, archive, or reprocess Runs | No | Yes | Yes |
| Create or edit test datasets and run evaluations | No | Yes | Yes |
| Add, edit, or delete Data Table rows | No | Yes | Yes |
| Upload, create, edit, move, rename, or delete Data Files and folders | No | Yes | Yes |
| Re-trigger or archive received emails | No | Yes | Yes |
| Manage tenant users and roles | No | No | Yes |
| Manage apps and tenant settings | No | No | Yes |
| View Variables and Secret names, also through Shepherd | No | No | Yes |
| Choose the Human Task email sender and send test emails | No | No | Yes |
| Create, change, delete, or import Data Table schemas | No | No | Yes |
| Create, edit, or delete API Endpoints and API keys | No | No | Yes |
| Create, edit, delete, import, or export mailboxes | No | No | Yes |
| Add, edit, delete, test, import, or export tenant AI Models and their deployments | No | No | Yes |
| View and export the Audit Log | No | No | Yes |
| Mark an Action free of charge or set its fixed credits or credit bounds per run | No | No | No |
Action pricing — free-of-charge, fixed credits and credit bounds per run — is reserved for Global Admins. No tenant role can change it, and it is not carried over when an Action is duplicated or imported. Free-of-charge applies to every version of the Action. Fixed prices and credit bounds apply only to the Action version a Global Admin set them for, so runs of a version edited afterwards are billed by usage until a Global Admin confirms the pricing again.
Shepherd follows your role
Shepherd acts as you. Whatever your role, you can ask it questions and get previews, but applying a preview needs the same role as making that change yourself in Studio:
- Read-Only members get answers and previews but cannot apply any change.
- Users can apply changes to Actions, start runs, archive Runs, run evaluations, and let Shepherd test tools and input types.
- Only Admins can apply previews that create or change Apps, Data Table schemas, API Endpoints, or mailboxes.
- Only Admins can have Shepherd read the tenant's Variables and Secret names, the same as the Variables & Secrets page. Shepherd never sees Secret values.
When your role does not allow a change, Shepherd says so and tells you who can apply it.
About Read-Only access
Read-Only is intended for stakeholders who need visibility into automations without the ability to change or trigger them — for example auditors, analysts, or business reviewers.
A Read-Only user sees the same Actions and Runs as other tenant members, but the editing and execution controls are hidden or disabled. The restriction is enforced by the Studio backend, so Read-Only access cannot be bypassed from the browser or through Shepherd.
Read-Only does not include access to the Audit Log, which is Admin-only. An auditor who needs to review or export the change history themselves must be given the Admin role; otherwise a Tenant Admin produces the export for them.
Changing a user's role
Tenant Admins change a user's role from Tenant Admin > Users by selecting a new role in the user's role dropdown. New tenant members default to the User role.