Roles and permissions

Every member of an organization has one of four roles: Owner, Admin, Editor or Viewer. The role applies to every project in that organization. Someone in several organizations can have a different role in each.

Role	In short
Viewer	Reads everything in the organization’s projects: test cases, plans, schedules, runs, session replays, logs, findings, Self-driving’s Inbox, activity and map, and settings, variable values included. Changes nothing, starts nothing and spends no credits.
Editor	Everything a Viewer can do. Also creates projects, writes and runs tests, asks the assistant, manages environments, credentials, variables, schedules and API keys, sets up and steers Self-driving, and starts explorations.
Admin	Everything an Editor can do. Also deletes projects, renames the organization, sets its allowed email domains, invites and removes members, and manages the plan and billing.
Owner	Everything. Only an Owner can make someone else an Owner, or change or remove another Owner. Whoever creates the organization is its first Owner.

Testmode enforces these rules on its servers, not only in the app’s buttons.

Action	Viewer	Editor	Admin	Owner
See test cases, plans, schedules, runs, explorations and project settings	Yes	Yes	Yes	Yes
See session replays and console and network logs	Yes	Yes	Yes	Yes
See variable values	Yes	Yes	Yes	Yes
See findings, the Inbox, Self-driving’s activity and the map	Yes	Yes	Yes	Yes
See the plan and credits left	Yes	Yes	Yes	Yes
Read the conversations about Inbox items	Yes	Yes	Yes	Yes
Send the assistant messages (each costs credits)	No	Yes	Yes	Yes
Watch the live browser during a run	No	Yes	Yes	Yes
Create projects and change project settings	No	Yes	Yes	Yes
Create, edit and delete test cases, test plans and schedules	No	Yes	Yes	Yes
Create, edit and delete environments, credentials and variables	No	Yes	Yes	Yes
Start and cancel runs	No	Yes	Yes	Yes
Start, stop and delete explorations, and add their suggestions to the suite	No	Yes	Yes	Yes
Turn Self-driving on or off and change its settings and goal	No	Yes	Yes	Yes
Act on Inbox items: answer, apply, confirm, dismiss	No	Yes	Yes	Yes
Undo Self-driving’s changes, stop its reviews and investigations	No	Yes	Yes	Yes
Triage, file and resolve findings	No	Yes	Yes	Yes
Add, edit and delete notes; rank journeys; remove screens from the map	No	Yes	Yes	Yes
Pause and resume testing	No	Yes	Yes	Yes
Connect and disconnect Slack	No	Yes	Yes	Yes
Create and revoke API keys	No	Yes	Yes	Yes
Delete projects	No	No	Yes	Yes
Rename the organization and set its allowed email domains	No	No	Yes	Yes
Invite members, resend and cancel invitations	No	No	Yes	Yes
Change members’ roles and remove members (not Owners)	No	No	Yes	Yes
Make someone an Owner, change or remove an Owner	No	No	No	Yes
Open the Billing tab: choose or change the plan, cancel, invoices	No	No	Yes	Yes

Good to know:

• Nobody ever sees a stored password. Credential passwords can be replaced, never read back, by any role.
• Your own role is changed by another Owner or Admin, never by you. The organization’s last Owner can’t be demoted or removed while other members remain.
• API keys follow their creator. A key works only while the member who created it is still an Editor, Admin or Owner. Removing that member, or making them a Viewer, stops their keys for good.
• AI apps connected over MCP act as the member who connected them, with that member’s role in each project. See Connect an AI agent over MCP.
• A role change shows up at once. The app of someone whose role changed, or who was removed, catches up the next time they return to its tab or it is refused something, and says what changed.

• Viewer for people who read results: product managers, support, stakeholders who get the report emails.
• Editor for people who write and run tests, and for anyone setting up CI with an API key.
• Admin for team leads who manage people and billing.
• Owner for the account’s accountable owners. Keep at least two, so the organization never depends on one person.