Cursor
Inventory the Cursor team: who holds a seat, who has actually used it, what each person's AI usage costs per billable request, and which models, repositories and billing groups the team's policy allows.
Members
The team roster — every member with role and removal state, including people who have been removed but still appear on the account.
Daily Usage
One row per member per day: lines suggested and accepted, tab and agent activity, request counts, and the model each person leaned on.
Usage Events
One row per billable request with its model, token counts and cents — the line-item detail behind the invoice, and the only place billable request units are counted correctly.
Spend
Per-member spend for the current billing cycle alongside each person's configured limit, so overspend is visible before the invoice is.
Audit Logs
Admin activity: sign-ins, membership changes, role changes and settings changes, with the IP each came from.
Billing Groups
Billing groups with their spend for the current cycle, including Cursor's reserved catch-all group for members who belong to none.
Billing Group Members
The member-to-group edge list, keeping former members so past spend can still be attributed to whoever incurred it.
Repository Blocklists
Which repositories and paths are withheld from Cursor's AI features — the record of what the team has decided not to send to a model.
Model Access Policy
Whether the team restricts models at all, and what a newly released model or provider defaults to before anyone reviews it.
Model Providers
Each model provider and whether the team has it enabled.
Models
Every model the policy names, whether it is enabled, and the parameter values configured for it.