Project
A project groups test specs and test reports within a workspace. You can create unlimited projects per workspace.
Project settings
The project settings page has the following tabs:
| Tab | Description |
|---|---|
| General | Edit name, description, and visibility (public / private) |
| Members | Manage project members and send invitations |
| MCP tokens | Manage project-scoped MCP access tokens |
| Webhooks | Configure webhook notifications for test report completion |
| Dictionary | Manage reusable test data values (see Test spec) |
Visibility
| Setting | Who can access |
|---|---|
| Private (default) | Explicit project members only |
| Public | All members of the workspace |
Project roles
| Role | Permissions |
|---|---|
| Owner | Full control, including member management |
| Editor | Create / edit / delete specs, cases, and reports; manage MCP tokens and webhooks |
| Viewer | Read-only |
Workspace Owners and Editors inherit project-level edit permissions across all projects.
Users invited to a project who are not already workspace members are automatically added to the workspace as Guests, giving them access only to that project.
Deletion
A project can be deleted by workspace Owners, workspace Editors, and project Owners. A project that contains test specs cannot be deleted. Remove all specs before deleting the project.
MCP Tokens
MCP access tokens are project-scoped shared assets. Project Owners and Editors can create and manage tokens. Because tokens belong to the project—not to any individual—CI/CD pipelines never depend on a single person's account.
Token capabilities:
- Token rotation — regenerate a token with a configurable grace period (0–90 days) so old and new tokens overlap during the transition
- Scheduled rotation — automatically rotate tokens on a fixed interval (1–365 days) at a specified UTC time
- Token scopes — restrict each token to specific MCP tools (allowlist)
- Rotation webhook — notify an external system (CI/CD, Secrets Manager) when a token is rotated; the new plain token value is delivered in the webhook payload
Webhooks
Webhooks send a POST notification to an external URL when a test report is completed. Webhook configurations (URL and optional custom HTTP headers) are managed per project and can be assigned to multiple test specs.