You decide which repositories ADO Pilot reviews. The **Dashboard → Repositories** page is where you manage this day to day — it lists every repository ADO Pilot knows about and lets you enable or disable each one individually. You also make an initial selection in the onboarding wizard the first time you connect an Azure DevOps organization.

## Managing repositories from the dashboard

1. Open the customer dashboard at `https://app.adopilot.dev` and sign in.
2. Select **Repositories** from the sidebar.
3. Browse the project/repository tree and select the repository you want to change.
4. Turn the **Enabled** toggle on or off for that repository.

Only Admins can change the toggle; Members and Viewers see a read-only view. If a repository or project you expect is missing from the tree — for example, one your team just created in Azure DevOps — click **Refresh from Azure DevOps** to discover it.

{% callout type="info" title="Newly discovered projects may need a resync" %}
Refreshing can turn up a project ADO Pilot has never seen before. When it does, click **Resync** on the **Integration** page (`Dashboard → Settings → Integration`) so a service hook gets created for it — otherwise its pull requests won't trigger a review yet.
{% /callout %}

## Selecting repositories during onboarding

The onboarding wizard runs the first time you sign in after installing ADO Pilot from the Azure DevOps Marketplace, and it's where you make your initial repository selection.

1. Open the customer dashboard at `https://app.adopilot.dev`.
2. Sign in with the Microsoft account that owns the Azure DevOps organization.
3. From the dashboard, start (or resume) the onboarding wizard.
4. Step through to the **Configure repositories** step.
5. Under **Configure monitored repositories**, check the repositories you want ADO Pilot to monitor.
6. Click **Continue** and complete the remaining wizard steps.

The wizard's granularity is the Azure DevOps **project**, not the individual repository: saving it creates one service hook for each project that contains at least one repository you selected, and every repository in that project — including ones you left unchecked — becomes subject to review under the organization's default settings. To keep a specific repository out of review inside an otherwise-enabled project, disable it individually from the **Repositories** page described above.

## How enablement interacts with the hierarchy

Repository enablement is a scalar field — the most-specific scope wins. See [Org, project, and repo settings hierarchy](settings-hierarchy.md) for the full merge rules.

- If you set `enabled: true` at the **organization** level, every repository is monitored by default. You can still opt individual repositories out at the repository level.
- If you set `enabled: false` at a specific repository, that repository is skipped even if the organization default is `true`.
- If you set `enabled: false` at the **organization** level, ADO Pilot reviews nothing — even repositories that have `enabled: true` set — because the organization scope is resolved first and short-circuits before any project- or repo-level value is consulted.

Disabling a repository doesn't stop Azure DevOps from sending its pull request events — the service hook is scoped to the whole project, not the individual repository — so ADO Pilot still receives the event. The review pipeline checks the repository's effective setting first and stops before any review work begins.

A repository that is disabled never costs review credits (RC), no matter how many PRs are opened against it.

## Adding a new repository later

When your team creates a new repository in Azure DevOps:

- If the repository lands in a project ADO Pilot already monitors, it's reviewed automatically — the project's existing service hook covers it, and it inherits the organization's default `enabled` setting.
- If the repository is in a brand-new project, it isn't reviewed yet. Click **Refresh from Azure DevOps** on the **Repositories** page to discover the project, then click **Resync** on the **Integration** page so a service hook gets created for it.

{% callout type="tip" title="Decide org-wide before per-repo" %}
For most teams, the simplest setup is to leave organization-level `enabled: true`, set sensible default branch filters and exclusions at the organization level, and only override at the repository level for unusual cases (experimental repos, vendor mirrors, archive-only repos).
{% /callout %}

## Disabling a repository

To stop reviewing a repository:

1. Open the customer dashboard at `https://app.adopilot.dev` and go to **Repositories**.
2. Select the repository in the tree.
3. Turn off the **Enabled** toggle.

Open PRs that were already in flight finish their current review. New PRs and pushes are ignored.