Team usage overview
The top panel summarizes the period — Active users, Tokens burnt, Output tokens, and Spend (or Net spend), each compared with the previous period — with a chart of tokens over time by person. A Most active card highlights who used the project most.People table
Search the table, or sort it by any column:
A person who uses several agents appears once when their identities are mapped to the same organization member. See Principal mapping.
A person’s page
Select a person to open their page. It is labeled User, API key, or Unattributed, and a source picker narrows it to one agent.- Summary: spend, tokens, sessions, commits, and pull requests merged.
- Funding: one card per source they use.
- For a subscription, each allowance window — for example 5-hour and 7-day — shows how much is used, when it resets, and whether they are on pace, running fast, or at the cap.
- Prepaid credits show their balance.
- Metered sources are marked as having no allowance: they pay list price with no cap.
- When a person uses more than one account for a source, each account gets its own tab.
- Models and Providers: their usage by model and by provider. Select one to narrow the page to it.
- What they reach for: the skills they invoked in the last 30 days, with invocations, sessions, and share.
- Sessions: their sessions, linked to session replay.
Allowance windows come from the plan usage your agents report: Claude Code’s status line and Codex’s hooks, captured when Terma is installed with the CLI. A person who runs an agent without the CLI shows unobserved windows, and the Overview shows a funding gap banner. See Funding and cost views.