# Configurations

> Manage reusable configuration groups and their values — the building blocks for matrix-based test planning.

**Configurations** are reusable, project-scoped building blocks that describe the axes of variation you want to track across your tests — for example, "Browser" (with values `Chrome`, `Firefox`, `Safari`) or "Operating System" (with values `Windows`, `macOS`, `Linux`).

Each configuration is organized as a **group** (the axis) that contains one or more ordered **values** (the options). Groups and values belong to a single project and are shared across all test planning in that project.

A configuration describes where a whole run executes, and each combination of its values creates a run. Data that changes what a case checks belongs to the case as a parameter, which multiplies the run cases inside each run instead. A configuration value can also fill a `${name}` placeholder that the case has no parameter for. See [Parameterized test cases](https://docs.probara.net/en/guides/parameterized-test-cases/#configurations-and-parameters).

## Reaching the screen

Open a project, then click **Configurations** in the TESTS section of the project sidebar. The URL is `/projects/:projectId/configurations`.

## The configurations list

The screen shows all configuration groups for the project. Each group displays its name and the ordered list of values it contains. If a group has no values yet, an explicit "No values yet" message appears in its row so the gap is never silent.

Search is not offered in v1. The group list is paginated, so projects with many configuration groups can page through them in batches.

## Creating a group

1. Click **New group** (visible to members and above; viewers see a read-only list).
2. Enter a **Name** for the group — for example, `Browser` or `Operating System`.
3. Click **Create group**.

**Name rules**: group names must be unique within the project. If the name is already in use, an inline "This name is already in use" error appears on the name field and the dialog stays open.

## Editing a group

Click the **Edit group** action (pencil icon) on the group row to open the edit dialog. Change the name and click **Save changes**.

The same uniqueness rule applies on edit: if you rename a group to a name already used by another group in the project, the dialog stays open with an inline error.

## Deleting a group

Click the **Delete group** action (trash icon) on the group row. A confirmation dialog names the group and warns that all its values will be permanently removed. Click **Delete** to confirm, or **Cancel** to return without changes.

Deleting a group permanently removes the group and all its values. This action cannot be undone from the UI.

## Adding a value to a group

1. Click **Add value** on the group row.
2. Enter a **Name** for the value — for example, `Chrome`.
3. Click **Add value** in the dialog.

Values are appended to the end of the group's ordered list.

**Name rules**: value names must be unique within their group. If the name is already in use in that group, an inline "This name is already in use in this group" error appears and the dialog stays open.

## Editing a value

Click the **Edit value** action on the value row. Change the name and click **Save changes**. The same uniqueness rule applies within the group.

## Deleting a value

Click the **Delete value** action on the value row. A confirmation dialog names the value. Click **Delete** to confirm, or **Cancel** to return without changes. Deletion is permanent.

## Permissions

| Action                 | Viewer | Member |
| ---------------------- | ------ | ------ |
| View groups and values | Yes    | Yes    |
| Create a group         | No     | Yes    |
| Edit a group           | No     | Yes    |
| Delete a group         | No     | Yes    |
| Add a value            | No     | Yes    |
| Edit a value           | No     | Yes    |
| Delete a value         | No     | Yes    |

## Coming soon: Test Plan matrix

Configurations are the foundation for the upcoming **Test Plan** feature. When test plans ship, a plan will automatically generate one test run per combination of configuration values — so a plan with a `Browser` group (Chrome, Firefox) and an `OS` group (Windows, macOS) would produce four runs. Setting up your configuration groups now means your projects will be ready when test planning becomes available.