Organization roles and permissions

An organization has four roles. They decide who can run tests, who can manage people and settings, and who can only look. This page is the detailed permission map; for how to invite people and change their roles, see How to invite team members.

The four roles

Owner — full control, including deleting the org. Exactly one per org, set when the org is created.
Admin — runs the org day-to-day: members, settings, billing, schedules, tests. Can’t delete the org or override another admin.
Member — does the testing work: create, edit, and run tests.
Viewer — read-only. Sees tests and reports, changes nothing.

What each role can do

Capability	Owner	Admin	Member	Viewer
View tests and reports	✓	✓	✓	✓
Create, edit, run tests	✓	✓	✓	—
Manage schedules	✓	✓	—	—
Invite and manage members	✓	✓	—	—
Edit org settings	✓	✓	—	—
Manage billing / plan	✓	✓	—	—
Delete the organization	✓	—	—	—

A member can run the suite and write tests but can’t set up schedules or touch org settings — that’s the line between doing the work and administering the org.

Rules when changing roles

Roles are assigned at invite time and changed from Settings → Members. A few rules the app enforces:

The Owner role can’t be assigned through invites or the role dropdown — there’s only ever one, set at org creation.
You can’t change the owner’s role.
An admin can’t change another admin’s role — only the owner can.
You can’t change your own role — ask another admin or the owner.

Personal vs. team organizations

Every account gets a personal workspace — a one-seat org you can’t invite anyone into. Roles only come into play in an org with more than one member — any multi-seat plan (Starter and up) supports them, with Team adding the seat count for larger groups; see Plan tier limits and How to invite team members.

How to invite team members — sending invites, seats, removing members
Plan tier limits — seats and team features by tier
Security model — how org isolation is enforced