Statuses
Statuses represent the outcome or state of a test run result, session, or scope item. Admins define statuses at the workspace level and control which parts of the system each status applies to.
Who can manage statuses?
The Statuses page is located at Settings → Statuses and is accessible to Tenant Admins and Project Admins.
| Action | Who can access |
|---|---|
| View the Statuses page | Tenant Admin, Project Admin |
| Create a status | Tenant Admin, Project Admin |
| Edit a status | Tenant Admin, Project Admin |
| Delete a status | Tenant Admin, Project Admin |
| Enable or disable a status | Tenant Admin, Project Admin |
| Assign a status to projects | Tenant Admin, Project Admin |
How statuses work
Each status has a unique system name that is set at creation and cannot be changed. Statuses carry meaning — you pick one outcome, Success, Failure or Neutral, and separately say whether the status counts as a completed result — and each status can be limited to the parts of the platform it makes sense in.
Statuses can be global (applied to all projects automatically) or assigned to individual projects. Disabled statuses are hidden from users but remain in the system for historical data integrity.
Managing Statuses
Create, edit, delete, and enable or disable statuses from Settings → Statuses.
Status Properties
Understand every status field — system name, name, aliases, icon and colour, outcome, and display order.
Scope Availability
Control which parts of the platform each status appears in — Test runs, Explorations, and Automation.
Project Assignment
Apply a status to all projects automatically, or restrict it to a specific set of projects.