Administration
Roles
The four built-in roles and what each one can do.
Every member of a Prodgator organization has a role. Roles are ordered: < < < . Each role can do everything the roles below it can.
What each role can do
| Area | reader | operator | editor | admin |
|---|---|---|---|---|
| Dashboard, Pipelines, Gates, run details, Notifications | Yes | Yes | Yes | Yes |
| Your own profile, notification and preference settings | Yes | Yes | Yes | Yes |
| Failures and Activity pages | Yes | Yes | Yes | |
| Cancel and re-run runs, re-run one job | Yes | Yes | Yes | |
| Security, Analytics, SPACE, Compliance and Exports pages | Yes | Yes | ||
| Approve or reject deployments, roll back | Yes | Yes | ||
| Dismiss security alerts | Yes | Yes | ||
| Run compliance evaluations | Yes | Yes | ||
| Manage custom adapters and processing rules | Yes | Yes | ||
| Admin Console: organization, members, roles, invitations, identity, billing, integrations, notifications and webhooks, API keys, AI, audit log | Yes | |||
| Turn compliance policies on or off, set enforcement modes, create break-glass overrides | Yes | |||
| Override a deployment decision made by a Block compliance policy | Yes | |||
| Override a release policy (when the organization allows it) and change that setting | Yes |
Some pages also depend on your plan. For example, Security needs the Team plan, Compliance and SPACE need the Business plan, and the audit log needs Enterprise. See Plans and features.