Skip to main content
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. 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.
The Adoption Funnel marks a target line at 50% of seats.

Account Access refusals

Blocked attempts are not reported here. They live on the Account Access policy’s own page, under Policies → Usage → Account Access, where opening a policy shows its refusals alongside its configuration. There you get a summary of refusals across the range, the refusals themselves one row each, and the policy’s settings. An attempt row carries when it happened, the tool, the Unbound user whose key was used, the account that was refused with its email and organization ID, its plan, the device, and the reason. Opening a row adds that account’s email domain and the sign-in method. Refusal reasons are: Organization not approved · Domain not allowed · Plan not allowed · Policy from another org · Policy check failed

Filters and controls

Adoption

What you can do

Messages you may see