The project admin settings hub
Project Administrators can view ADO Pilot subscription status from the project admin hub. All configuration happens at adopilot.dev.
Last updated
The ADO Pilot settings hub is a read-only page under your Azure DevOps project administration that shows whether reviews are active for the organization, how many subscriptions are running, and a link to the adopilot.dev dashboard. Configuration tasks — adding projects, rotating credentials, viewing auth-failure reports — happen at the dashboard, not in the hub.
Who can open the hub
The hub requires Azure DevOps Project Administrator permissions. If you open it without that role, the hub renders an unauthorized message:
You need Project Administrator permissions to view ADO Pilot status.
Contact your project administrator for help.
This is an Azure DevOps permission, not an ADO Pilot one. If you need access, ask the person who installed the extension or another Project Administrator for elevation in your organization's permissions settings.
Opening the hub
- From your Azure DevOps project, click Project settings in the bottom-left navigation.
- In the project settings sidebar, click the top-level ADO Pilot entry. It appears as its own item in the sidebar — it is not nested under "Extensions".
The hub opens in the project settings content area. While it loads it shows "Loading ADO Pilot settings...".
What the hub shows
When loaded successfully, the hub renders four sections.
Status badge
A pill in the top-left of the page that reads either Active or Not configured.
- Active appears when the backend has at least one service-hook subscription running for the organization. The hub also shows the line "AI code reviews are enabled for this organization."
- Not configured appears when the extension is installed but no subscriptions exist yet. The hub shows the line "ADO Pilot is installed, but no subscriptions are active. Complete onboarding at adopilot.dev to enable reviews."
The badge reflects subscription state at the time the page loaded. Refresh the page to re-check.
Legacy subscription warning
If any subscriptions in the organization were provisioned by older versions of the extension (pre-v0.1.8, when the extension itself created subscriptions), a warning banner appears:
N legacy subscription(s) detected. Re-authenticate at adopilot.dev to migrate them.
The "adopilot.dev" link opens the dashboard. Re-authenticating from the dashboard rotates the affected subscriptions to the current backend-owned format. Until you migrate, the legacy subscriptions continue to fire reviews, but they are not visible to dashboard tools that operate on the new format (auth-failure reports, drift detection).
Subscription statistics
When the status is Active, the hub shows two counters:
| Counter | What it counts |
|---|---|
| Projects subscribed | Distinct Azure DevOps projects in this organization that have at least one ADO Pilot subscription. |
| Active subscriptions | Total service-hook subscriptions across all projects in the organization. |
A project can have more than one subscription (one per supported event type), so "Active subscriptions" is normally larger than "Projects subscribed". If "Projects subscribed" is zero but "Active subscriptions" is non-zero, the hub displays an em-dash for the project count — this state is rare and usually means the project list in the extension's stored settings is stale. Re-run onboarding from the dashboard to refresh it.
Manage at adopilot.dev
A primary link labelled Manage at adopilot.dev opens https://adopilot.dev/dashboard in a new tab. A short paragraph below it reads:
Subscriptions are managed by ADO Pilot's onboarding flow. To add projects, regenerate webhook credentials, or view auth-failure reports, use the adopilot.dev dashboard.
Both occurrences of "adopilot.dev" in this section are clickable.
Why configuration lives at adopilot.dev
The extension does not hold the personal access token (PAT) used to provision subscriptions, and it does not hold any backend API key. Subscription provisioning, PAT rotation, webhook credential regeneration, and auth-failure reporting all happen at the dashboard:
- Add a project to reviews: dashboard → Projects → Add project.
- Rotate the PAT: dashboard → Connections → Re-authenticate.
- Regenerate webhook credentials: dashboard → Connections → Regenerate.
- View auth-failure reports: dashboard → Health → Auth failures.
- Cancel the subscription: dashboard → Billing → Cancel.
The hub is intentionally narrow. Anything beyond "is it active and how much is running" lives at the dashboard so the same tooling works whether or not the extension is installed.
If the hub shows an error
If status loading fails, the hub renders an error banner with the underlying message and a Retry button. Retrying re-runs the status check. Common causes:
- A transient Azure DevOps Extension Data Service outage.
- The PAT used by the backend has expired and the backend cannot enumerate subscriptions for the organization.
If retrying does not help, open the adopilot.dev dashboard. The dashboard works independently of the hub.