Adoption Analytics
The Adoption page (Operations → Adoption) answers a simple question for engineering leadership: out of everyone provisioned to use AI tools, how many actually are?
Active Users
Active Users counts distinct human identities with at least one session in the selected time window, out of the number of provisioned users (active personal access token holders, falling back to all-time unique session identities if no PATs exist yet). This count only includes human identities — sessions from anonymous agent identities (anon:*, used when a request can't be tied to a specific developer) are excluded from the numerator, so agent traffic specifically can't inflate the ratio above 100%. (The ratio can still exceed 100% for other reasons — see Adoption Rate below.)
Agent activity in the same window isn't hidden — it's shown as a separate sub-label (N agents) below the Active Users count, so you can see automated usage without it inflating the human adoption number.
Adoption Rate
Active Users divided by provisioned users, as a percentage. An org-wide headcount override can be set in Settings → Organization if the provisioned-user count (PAT holders) undercounts real headcount — for example, when some developers authenticate via OIDC without ever issuing a PAT.
New Adopters and Churned
- New Adopters — developers whose first-ever session falls inside the selected window.
- Churned — developers who had sessions in the prior window of equal length but none in the current window.
Adoption by Team
The team breakdown table rolls up active users, sessions, and cost per OIDC group, using the same team assignment used for cost and policy attribution elsewhere in the product.
See also
- Sessions — per-session detail behind the Active Users count
- Productivity — PR-level AI adoption (a different, code-review-based adoption metric)