Usage answers two questions: how widely AI coding tools have been taken up across your organization, and which vendor accounts your developers are signing in with.
What’s on the page
Sub-tabs
Account Usage is always available. Adoption is enabled per organization: where your organization has it, both sub-tabs appear and Adoption opens by default; otherwise the page is Account Usage alone. Asking for
?tab=adoption renders the report either way, so it can be previewed before it is switched on.
An older link using ?tab=usage or ?tab=policy-enforcement still works and the address is corrected once you arrive.
Adoption — headline figures
Adoption — charts and tables
Adoption by Team carries: Team, Total users, Active users, Adoption rate, Inactive users, Avg. adoption and Change — the last two headed with the window you picked, as Avg. adoption (8 wks). Ten teams to a page, sortable from the headers, with a column picker, and columns you can resize and drag into a different order.
What each Adoption by Team column means:
Group rows by switches the table between Team and Manager, and the column picker, Choose columns, adds Tokens — the team’s tokens across the window. Each row’s arrow opens its people. Weekly Adoption by Team shades each week darker where a larger share of the team was active, and a team’s row also reads select a team to see its people.
Selecting a team opens its people in place of the table — twenty-five to a page, with their own search, an Activity filter, and an All teams breadcrumb to return. The address carries the team as
?department=<team>.
The Adoption exports carry up to 1,000 rows. Where your filters match more, the file holds the first 1,000 in your current sort order and the table says so beside its title: N more teams did not fit the export, or N more people did not fit the export. Narrowing the window, the department, the manager or the band brings it under the cap.
Adoption by Team is built from your directory. Without the Okta sync it shows Team Breakdown Needs the Okta Sync, a Connect Okta control and a Send instructions to IT control. Weekly Adoption by Team empties out with it; the headline figures, the Adoption Funnel and Weekly Active Users by agent are unaffected and continue to report.
Account Usage
Which vendor accounts your developers are actually signed into, listed by when each was first seen in the range.
The tab filters by plan (All plans, listed as tool · plan) and by domain (All domains), and searches on Search email, organization ID or user…. The time range applies, and the list holds the accounts first seen inside it; with none, it reads No accounts first seen in this period.
A notice above the table reads Personal account usage detected with a count — 3 accounts across 3 people in Claude Code, Codex and Cursor — and selecting it filters the table to them. Those rows carry a Personal badge, meaning the account is a personal one signed in on a managed device.