Codebase settings
Controls how Watchtower scans your test source for spec files: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 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.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.
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.