Skip to main content

Compare user and team spend in Analytics

Enterprise Tier

The User and Team filters on the Analytics page (/usage) accept more than one selection at a time, so people or teams can be compared side by side. The chart, the table, and the CSV export all follow the selection.

Persona: Platform operator working in the Admin Console.

Estimated time: 5 to 10 minutes once the comparison set is known.

Outcomes​

By the end of this guide:

  • Several users or teams are selected in Analytics, and the chip shows either a name or a count such as 2 users.
  • Side-by-side spend is visible on the chart (one bar color per user or team), or a deliberate Group choice is preserved.
  • Narrowing combinations (user within a team), No team assigned, shareable filter URLs, and the 50-selection limit are understood.

Prerequisites​

  • Administrator access to the Admin Console: typically the super_admin or billing_admin role.
  • Enough usage in the chosen time range for the people or teams being compared.

Step 1: filter by several users or teams​

  1. Open Usage → Analytics in the Admin Console.
  2. Open the User (or Team) filter and tick the people or teams to compare. The list stays open during selection, and the selections stay visible at the top even while searching.
  3. Confirm the chip: it shows the name when one is selected, or a count like 2 users when more are selected.
  4. Confirm that the chart, the table, and Download CSV all follow the selection.

Multi-select User filter on Analytics

Multi-select Team filter on Analytics

Step 2: compare them on the chart​

  • As soon as a second user or team is picked, the chart automatically switches to one bar color per user (or per team). That is usually the right view for a comparison.
  • This only happens when no grouping has been chosen explicitly. Once something is selected in the Group control (including No grouping), that choice sticks and is never overridden.
  • With several users selected and No grouping, the chart shows the individual API keys instead, and each key is labeled with its owner (for example Ada · prod-key), which identifies which key belongs to whom.
  • Clicking a user's bar in the chart, or their row in the table, focuses on just that person.

Two users compared on the Analytics cost chart

Step 3: combine filters and share the view​

  • User and team filters combine by narrowing: selecting Ada plus the Security team shows Ada's usage within the Security team. If she is not in it, the result is empty. That is expected.
  • To see one person compared against their teammates, filter by the team and group by User.
  • No team assigned is available in the Team filter for usage from people who are not in any team, and it can be combined with real teams.
  • Filters are part of the page URL, so a link can be shared and the recipient sees the same selection (names are resolved on their side based on their permissions).
  • Up to 50 users or teams can be selected; past that, the picker requires removing one before another is added.

Where to go next

Catch spend drift before the invoice does

Use multi-select compare as part of a regular usage review.

Split the AI bill across the teams that caused it

Export the filtered user or team selection for finance.

Set a budget and track spend against it

Turn the baselines read here into budgets.