Crux uses roles to decide who can do what. There are two levels: roles at the organization level and roles inside each workspace.
capabilities × roles
roleViewerread-only access
Viewer
Member
Admin
View suites, cases & runs
Create & edit tests
Manage members
Webhooks & project tokens
Workspace settings & branding
Workspace roles
These control day-to-day testing work.
Admin — full control inside the workspace. Can create, edit, and delete projects, test suites, test cases, and runs; manage members; set up automation, webhooks, and branding; and create the project token used to connect automated tests. (This is the “operator” role — the person who runs the workspace.)
Member — can do the everyday testing work: view, create, and edit test suites, test cases, runs, comments, and attachments. Cannot manage members, webhooks, project tokens, or workspace settings.
Viewer — read-only. Can browse everything (suites, cases, runs, results, comments, attachments) but cannot create or change anything.
Organization roles
These control company-wide settings and billing.
Owner — the highest level of control over the whole company: company settings, all members, billing, and every workspace. An owner is automatically an admin of every workspace in the company.
Admin — like the owner across workspaces and members, but cannot remove or demote the owner and does not manage billing.
Billing admin — can manage the subscription and payment details only. Cannot touch workspaces, projects, or test data.
Member — no company-wide powers; their access depends on the workspace role they're given.