> ## Documentation Index
> Fetch the complete documentation index at: https://docs.watchtower.systems/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> Everything under Configuration: codebase scanning, repository connections, notifications, and account preferences.

Most of Watchtower's setup lives in one place. Open **Configuration** from **Project Settings** in the sidebar. It's split into three tabs: **Codebase**, **CI / Repos**, and **Watchman**.

## Codebase settings

Controls how Watchtower scans your test source for spec files:

| Setting                  | What it does                                                                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tests directory**      | The path inside your repository that contains your specs. Watchtower auto-detects this from your Playwright config when possible.                       |
| **Spec file extensions** | Which file extensions count as tests (e.g. `.spec.ts`, `.test.ts`). The first one listed is used when Watchtower generates new spec files.              |
| **Folder depth**         | How many path segments turn into a folder in Test Center. For example, a depth of 1 turns `tests/checkout/foo.spec.ts` into a single `checkout` folder. |

### Environments

Add the environments your team tests against (staging, production, etc.) under **Codebase → Environments**. Each one has a name, a display label, and a color, and click **Add environment** to add more. Once configured, environments appear as a filter in the top bar and as a picker when you run Patrol.

### Execution

If your workspace runs tests locally rather than dispatching them to CI, the **Execution** section lets you choose which framework(s) Patrol should support (**Both**, **Playwright only**, or **Cypress only**) and set the exact command used to run each one, including an `${env}` placeholder for the selected environment. This section isn't shown on hosted deployments that dispatch runs to CI instead.

### Notifications

Under **Codebase → Notifications**, turn on **Email release notifications** to get emailed about Patrol results:

* **Notify the repository owner**: include the repo's owner automatically.
* **Additional recipients**: add extra email addresses.
* **Send when**: every run, or only when the result isn't GO.
* **On NO-GO**: whether a NO-GO result should block release or just warn.

## Repository connections

The **CI / Repos** tab is where you connect GitHub repositories, choose your test source, and manage existing connections. See [Connecting a Repository](/v0.5.0/guides/connecting-a-repository) for the full walkthrough.

## Watchman settings

The **Watchman** tab shows whether AI analysis is enabled for your workspace, and lets you choose where Watchman posts its review. See [Watchman](/v0.5.0/watchman).

## Account preferences

Open **Preferences** from your profile menu (or visit the standalone Preferences page) to set:

* **Default view**: which view Watchtower opens to (Test Center, Dashboard, Patrol, Compare, Reports, Watchman, or Trash).
* **Default environment**: the environment selected by default, or **All environments**.
* **UI density**: **Comfortable** or **Compact**.

Click **Save preferences** to apply your changes.

<Note>
  Profile details like your name, email, and avatar are managed through **Manage account** in the profile menu, which opens your account's own profile settings rather than a Watchtower-specific form.
</Note>