Skip to main content
Browse all guides
All guides

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, and tenant settings).

Permission matrix

CapabilityRead-OnlyUserAdmin
View Actions and StepsYesYesYes
View Runs and run historyYesYesYes
Create, edit, duplicate, or delete ActionsNoYesYes
Add, edit, or delete StepsNoYesYes
Publish or enable/disable an ActionNoYesYes
Import ActionsNoYesYes
Create, edit, or delete SkillsNoYesYes
Start a run (execute an Action)NoYesYes
Delete, archive, or reprocess RunsNoYesYes
Manage tenant users and rolesNoNoYes
Manage apps and tenant settingsNoNoYes
View and export the Audit LogNoNoYes

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 by the browser.

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.