Projects

What this is

Projects are named groupings within a workspace. They let you slice a workspace’s tests by product area, system boundary, or team — for example, Core APIs, Checkout, or Mobile backend. A test belongs to at most one project; runs, secrets, and access controls flow from the workspace and are inherited by all projects inside it.

Projects are an organisational layer: they do not change how tests run or what regions are available.

Projects sit below workspaces and above tests in the account hierarchy: account → workspace → project → test. Project access, secrets, and runs all flow down from the parent workspace. See Account overview & active runs for the full four-layer model and role table.

Where to find it

Click Projects in the left navigation sidebar. The route is /projects. The page is scoped to the workspace currently selected in the top-bar workspace scope switcher — you must have a workspace selected to see or create projects.

Projects list

The Project directory section lists every project in the active workspace, one per row.

Each row contains:

Element	What it does
Project name	Click the name to edit it inline (if you have edit rights). Press Enter or click away to save; press Escape to cancel.
Project ID	A truncated stable identifier shown below the name — hover for the full value.
View tests	A quick link that opens the Tests list filtered to this project.
Actions menu (three-dot icon)	Contains Settings (opens Project detail) and Delete… (opens the delete confirmation dialog). Visible only if you have edit or delete rights.

How to view tests for a project

Open Projects in the left nav.
Find the project row.
Click View tests — the Tests list opens pre-filtered to that project.

Create a project

Workspace editors and admins can create projects using the Create project button in the page header.

How to create a project

Ensure a workspace is selected in the top-bar scope switcher.
Click Create project in the page header. A dialog opens.
Enter a Name for the project (up to 200 characters). Use something descriptive, such as Core APIs or Mobile backend.
Click Create. The dialog closes and the new project appears in the list.

Rename a project

Project names can be updated inline from the list, or from the Project detail page.

How to rename a project (inline)

In the Project directory, click the project name text.
The name becomes an editable field. Type the new name.
Press Enter or click outside the field to save.
If the rename fails (e.g. a network error), an error message appears next to the field and the previous name is preserved.

Delete a project

Deleting a project is a soft-delete — the project is removed from the directory and no longer usable, but historical run data is not purged from the database. If the project still has tests, the API returns a conflict error unless you choose to force-delete tests along with the project.

How to delete a project

Open the Actions menu (three-dot icon) on the project row.
Click Delete…. A confirmation dialog opens.
In the Project name field, type the exact project name to unlock the delete buttons.
Choose one of two actions:
- Delete — soft-deletes the project. Fails with a 409 error if tests still exist in the project. The error message suggests using “Delete including tests” instead.
- Delete including tests — force-deletes the project and all its tests in a single operation. Use this only when you intend to remove the tests permanently.
Click the chosen button. The dialog closes and the project is removed from the list.

Project detail

The Project detail page is opened from the Actions menu → Settings or by navigating to /projects/<project-id>.

The page is organised into four sections:

Identity

Shows the stable identifiers for the project — project ID, workspace ID, and account ID — along with your current access level (viewer, editor, or admin).

Launch control

Two quick-action buttons:

Tests in this project — opens the Tests list pre-filtered to this project.
Workspace settings — opens the Workspace detail page for the parent workspace.

Access

Explains how access is inherited. Project roles (viewer, editor, admin) flow down from workspace and account-level team grants — there is no separate per-project permission assignment. The section lists team grants that target the parent workspace so you can see which teams have access to this project.

To change access, go to Account → Teams or Workspace settings.

Danger zone (admin/owner only)

If you have delete rights, a Delete project… button appears in a red-bordered section at the bottom. It opens the same confirmation dialog as the list-row delete action.

Assign tests to a project

Tests are assigned to a project at test creation time, or by editing an existing test’s configuration.

Assign during test creation

Open Tests → New test (or New Vario test).
In the test configuration, look for the Project field.
Select the project from the dropdown. Tests created without a project assignment are unassigned — they appear in the Tests list under “No project” and are accessible regardless of project filter.

Reassign an existing test

Open the test’s detail page → Configuration tab.
Find the Project field and change the selection.
Save the configuration.

Tips & gotchas

No workspace, no projects. The Projects page requires a workspace to be selected in the top-bar scope switcher. If the scope is “All workspaces” the page shows no data.
Rename is instant. Inline rename saves on blur or Enter — there is no Cancel in the inline flow (only Escape before blurring). If you make a mistake, click the name again and retype.
Delete vs force-delete. Attempting to delete a project with existing tests results in a 409 conflict. Either delete the tests first, or use Delete including tests to remove everything at once.
Access is inherited. Projects do not have their own member list. Team and workspace grants control who can see, edit, or delete a project.

Account overview & active runs — the full account → workspace → project → test hierarchy explained.
Tests — create and configure — how to create tests and assign them to a project.
Workspaces — manage workspaces and their settings.
Teams — configure team-based access that flows down to projects.
Navigating the console — the shell, sidebar, and workspace scope switcher.