Role Permissions

Overview

Role permissions implement RBAC (role-based access control). Roles determine what a user can:

• view (projects, results, settings)
• create/edit (endpoints, tests, configurations)
• execute (runs, schedules, CI triggers)
• administer (users, roles, system settings)

Default roles (typical)

Your deployment may include roles similar to these:

| Role | Typical use | Notes | | --- | --- | --- | | Admin | Platform administration | Full access to users, settings, and projects | | Contributor/Tester | Build and run tests | Can create/edit tests in assigned projects | | Environment manager | Manage environments | Focused on environment setup and maintenance | | Reader | View-only | Read-only access to results and reports | | Reviewer | Approvals | Reviews workflows/changes (where applicable) |

How to assign roles safely

1. Start with least privilege.
2. Grant access per responsibility (builders vs operators vs viewers).
3. Review role assignments periodically (quarterly is a good default).

Best practices

• Keep admin membership small and monitored.
• Use dedicated roles for automation tokens and CI (see Public API).
• Pair RBAC with auditability (see Audit logs).

Related articles

• User policies
• User management