Projects
A project owns its test cases, test runs and cycles. Everything else you configure — fields, templates, statuses, workflows, environments, tags — is shared across the whole workspace. Each project also carries its own answer to two questions: who can open it, and what role they get inside it.
Two ways to see projects
- Projects (in the sidebar) — one full-width list of every project you can open, active and completed together, with scope pills, search and a Display panel that decides layout, grouping, ordering and columns. Pin, edit and complete a project from its row menu. See Browsing Projects.
- Settings → Projects — one administrative list of every project in the workspace, with a status filter, sorting, per-row actions and the full-page editor behind them. See All Projects (Admin).
Access is a default plus exceptions
There is no membership list. Every project has a default that applies to the whole workspace — each person’s own Role, or one role handed to everybody — and a short list of exceptions naming the people and groups treated differently. Someone with no exception is not missing from the project; they are on the default, like everyone else. See Project Access.
The one case that looks like a bug and is not. On a project set to “their own workspace role”, a user who has no Role assigned has nothing to inherit — so the project does not appear for them at all. Give them a Role, or set the project to hand one role to everyone.
Active and completed
Completing a project is a reversible status change, not a deletion: it leaves the project switcher and stops being offered for new runs, and every test case, run, result and attachment stays exactly where it is. Reopening it is one menu click. Deleting is the opposite — permanent, unrecoverable, and gated behind typing the project’s exact name.
Who can manage projects
All five project capabilities are workspace-level, so they follow Access Level rather than a Role:
| Action | Who can do it |
|---|---|
| Open the projects you have access to | Anyone in the workspace, subject to the project’s default and exceptions |
| See Settings → Projects | Project Admin or Tenant Admin |
| Create and edit projects — from the Projects page or the sidebar, without going through Settings | Project Admin or Tenant Admin |
| Set a project’s access default and exceptions | Project Admin or Tenant Admin |
| Delete a project | Project Admin or Tenant Admin |
A custom Role cannot grant these. Adding View Projects to a custom Role does not let a Regular User open Settings → Projects — the page still refuses. These capabilities are answered by the Access Level.
Browsing Projects
The workspace project list — scope pills, search, the Display panel, pinning, and completing with Undo.
All Projects (Admin)
One admin list with a Status filter, row actions, the plan’s project limit, and the delete confirmation.
Create a Project
The one editor for new and existing projects — Project, Access and Exceptions panels behind one save bar, and the four ways in.
Project Access
The default everyone gets, the exceptions that override it, and how to read the outcome sentence.