Skip to main content

Scopes & Permissions

Qumo Deploy uses a two-tiered authorization system: Scopes (enforced at the token/API key level) and Permissions (enforced at the IAM role level).
Source of truth: This page is the canonical reference for all API key scope strings and IAM permission names.

API Key Scopes

Scopes define the maximum set of actions a specific API key is allowed to perform, regardless of the principal’s IAM permissions.
Scope vs. Permission: Even if a key has the * scope, it cannot perform an action unless the associated principal (User or Bot) has the required IAM Permission.

IAM Permissions

Permissions are granular actions that can be grouped into IAM Roles. They are typically scoped to either a Tenant or a Project.

Tenant-level Permissions

Project-level Permissions