> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/seats-and-licenses.md).

# Seats and Licenses

See how many of the AI assistant seats you pay for went unused, what those seats cost each month, and how your Claude Code seats split by plan tier.

Revenium shows how many of the AI assistant seats you pay for went unused, and what those unused seats cost each month. For Claude Code it also breaks seats down by plan tier and raises an **Inactive seats** finding with the monthly amount you could recover.

Seat figures appear for Claude Code, Cursor, Gemini and Codex once you enter the seats you pay for. Claude Cowork has no seats of its own: your Claude Code seat plan covers it.

## Add the seats you pay for

Seat figures need a seat plan: the tiers you pay for, how many seats each tier has, and the price per seat. A team admin saves it.

* **Claude Code:** open **Intelligence > AI Assistants > Claude Code** and choose the **Seats & plan** tab. Select **Add a seat plan**, or **Edit plan** if one is already saved. Use **Add tier** for each tier you pay for, set its seats and price per seat, and save. Prices start at Anthropic's published pricing, so edit them to match your contract. One plan covers Claude Code and Claude Cowork.
* **Cursor, Gemini and Codex:** open the assistant's tab, choose **Subscription Overview**, and enter your seat allocations under **Subscription Settings**.

## Claude Code: unused seats, tiers and the Inactive seats finding

The **Seats & plan** tab shows your **Seat bill**, your **Seats**, how many are **Active** and how many are **Inactive**, with the monthly cost of the inactive seats you could recover. A seat counts as active when its person used Claude Code or Claude Cowork in the last 30 days; someone who used both counts once. The **Seats by tier** table lists each tier with its seats, its price per seat and its monthly seat bill.

When more people were active than the plan has seats, **Active** shows both counts, such as "39 active, 37 seats", in place of a percentage. The summary at the top of the dashboard also gives both counts. Check that the seats in your plan match the seats you pay for.

When you have inactive seats, the **Overview** tab adds an **Inactive seats** finding to **What to change**. It states the monthly amount you could recover and suggests reassigning or dropping those seats at renewal. **Open Seats & plan** takes you to the detail.

The plan records how many seats each tier has, not who holds them. Revenium therefore prices the recoverable amount at the average seat cost across all tiers and does not name a seat holder. Before you remove a seat, check who holds it in your Anthropic account.

For the rest of the tab, see [Claude Code Dashboard](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-claude-code/claude-code.md).

## Claude Enterprise seat fees and usage

With Claude Enterprise, seat fees and usage come from two places. Seat fees come from the seat plan you enter on the **Seats & plan** tab. Usage comes from your Claude Enterprise connection. See [Provider Integrations](https://docs.revenium.io/integrations/provider-integrations.md) to connect it.

## Cursor, Gemini and Codex: the Seat Overview card

On each of these assistants, the **Seat Overview** card on the **Subscription Overview** tab shows how many of your seats are active and how many are inactive. Once a price per seat is saved, it also shows what the inactive seats cost each month. Until you enter your seats, the card asks you to add a subscription plan.

## Check that every seat is sending usage

For a provider that bills you per seat, once Revenium knows the seat count, the **Spend by provider** tab under **Providers** shows two counts side by side: the people sending coding assistant usage to Revenium, and the seats on your invoice or assigned in your plan. Revenium does not divide one by the other, because the two counts come from different sources. When fewer people send usage than you expect, check that they have finished setup for that assistant. See [AI Assistants](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend.md) for each assistant's setup page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/seats-and-licenses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
