Set budgets

Set a monthly AI budget for your organization and each team, and have Tokenize apply it as spend limits in Claude, ChatGPT, and Cursor.

A budget sets how much each person can spend on AI each month. You set it for the organization and for each team on Budgets. Tokenize then writes each person's limit to the AI tools they use, so the tool stops them when they reach it.

Who can do this: Admins set the organization budget, set any team's budget, choose team owners, and change Settings → Budgets. Managers can open and set budgets for the teams in their reporting line. Everyone else sees their own budget. See Roles and permissions.

Before you start

Budgets need at least one enterprise key that can set spend limits:

KeyWhere to add it
Claude AnalyticsConnect Anthropic
OpenAI AnalyticsConnect OpenAI
Cursor Team Admin APIConnect Cursor

Without one, every Budgets page says "Budgets need an enterprise key" and lists each key with its state: Connected, Not connected, Key not working, Needs spend limit access, Limits turned off, or Not billed in USD. Admins see Connect a key, which opens Settings → Providers.

If Cursor is your only key and your Cursor team has per-person spend limits turned off, the page says "Budgets are off while Cursor limits are off". Turn the limits on in Cursor, and budgets come back by themselves within about 15 minutes.

Budgets set Claude limits in US dollars only. If your Claude organization bills in another currency, Claude limits aren't read or changed. If Claude is your only key, the page says "Budgets don't support your Claude currency yet". If you have other keys, Settings → Providers shows it on the Billing currency line of your Claude Analytics key. Contact your Tokenize account team to set it up.

Teams come from your directory. If Budgets says "No teams to show", an admin needs to set up directory sync.

Each team's Owner comes from the reporting lines in your directory. It's usually the person on the team who manages most of it. When no one on the team does, the manager above the team's leads can own it. In that team's People table, their badge names their own team, for example "Lead · on Finance". Someone deprovisioned in your directory never owns a team. A team with no owner is looked after by the owner of the nearest team above it, who can see it, fund it, and answer its requests.

Choose a team's owner

If your directory gives a team the wrong owner, or none, an admin can choose one. This changes the owner for budgets only. It doesn't change anyone's manager.

  1. Open the team's page on Budgets. The Owner line shows who owns the team and either "From directory" or "Chosen by an admin".
  2. Click Change, search for the person, and click Save.

The new owner gets the team's requests and alerts and can manage its budget. Their managers can open the team too. An owner chosen from outside the team doesn't get the team's leftover pool on their own limit, but they can still give it out.

To go back to the directory's owner, click Change, then Reset to directory. If the person you chose leaves, the page says, for example, "sam@example.com left, so the directory's owner applies."

How budgets fit together

  • Organization budget. A Per person amount that is every team's default and maximum. It also applies to people who aren't on a team. An optional Overage pool is shared by the top-level teams.
  • Team budget. A team uses the rate of the team above it unless you set its own Per person amount. A team can't go above the team it sits in. A team's total counts each person at their own rate, plus its pool, so a sub-team on a lower rate lowers its parent's total.
  • Overage pool. Extra money a team owner gives to people or sub-teams. Whatever a pool doesn't give out goes to the team owner's own limit when the owner is on that team. When the owner isn't on the team, or the team has no owner, only what's given out to people can be spent. Set budget then shows what's left, for example "Not given out yet: $800. Give it to people to make it spendable."

Budgets count calendar months in UTC.

Set the organization budget

  1. Go to Budgets and click Set budget.
  2. Enter Per person and, if you want one, Overage pool.
  3. Click Save. Tokenize shows who the change affects, for example "This sets a new limit for 12 people (Claude 8 · Cursor 4)." It also warns when people are already at or over their new limit: "Saving stops them."
  4. Click Confirm and save.

To remove the organization budget, leave both fields empty. A $0 pool on its own is refused: "A $0 overage pool needs a per-person rate. Leave both fields empty for no org budget."

Set a team budget

  1. On Budgets, pick the team in the team list on the left, or click its row in the table.
  2. Click Set budget at the top of the team page.
  3. Enter Per person. Leave it empty to use the default the popover shows, such as "Defaults to $500 from Engineering."
  4. For a top-level team, you can also set Overage pool. The popover shows the team total before you save.
  5. Click Save.

If the save would lower a limit below what people have already spent, you'll see "3 people are already at or over this limit. Saving stops them." Click Save anyway to go ahead.

If the amounts break a rule, a warning explains why and Save stays disabled. For example:

  • "Can't be more than Engineering's $500.00 per person."
  • "That puts Platform at $12,000.00, over Engineering's $10,000.00 total."
  • "Only $2,000.00 left in the org's overage pool."
  • "Overage pool can't go below the $1,500.00 already given out."

Give out overage

  • To a person: on their team's page, click Set overage on their row in People. The amount is added to their limit.
  • To a sub-team: click Set overage on the sub-team's row in Sub-teams, or open the sub-team's page and click Set overage at the top. The amount becomes that sub-team's pool. For a sub-team with no owner, the popover says only what it gives out to its people can be spent.

The popover shows how much of the pool is left. You can't give out more than it holds: "Only $400 left in Engineering's pool." You also can't cut a sub-team's pool below what it has already given out, for example "Platform's overage pool can't go below the $300.00 it already gave out."

What you see after saving

The popover first says "Saved. Updating limits…" while Tokenize writes the new limits to each tool. You can close it. Then it shows the result:

MessageWhat it means
"Saved. Limits updated."Every tool took the new limits.
"Saved."No one's limit changed.
"Saved. Limits updated, but some aren't enforced."Every limit was written, but Cursor applies a higher team default or group limit to some people. See below.
"Saved. Some limits didn't update."Check the line for each tool below the message.
"Saved, but a tool refused the new limit. Check its key's permissions in Settings."Replace the key in Settings → Providers with one that can change limits.
"Saved, but limits didn't update."The tool couldn't be reached. Tokenize tries again.
"Saved. Couldn't confirm the limits updated. Check them before trying again."Look at the limits in the tool's admin console before saving again.

Below the message there's one line per tool, such as "Cursor: updated" or "Cursor: didn't update. Turn on per-person spend limits in Cursor, and limits update within 15 minutes." If only some of a tool's limits went through, the line says so, for example "Cursor: some limits didn't update. We'll retry on the next sync." "3 people have no account that takes a spend limit, so none was set." means Tokenize couldn't match them to an account in any of these tools. The budget itself is always saved.

Cursor holds each person to the highest of their own limit, their team's default limit, and their group limits. When someone's share of the budget is under one of those, Tokenize still writes it, but Cursor doesn't enforce it. The save result says so, for example "3 people's budgets aren't enforced: Cursor applies a higher team default or group limit. Lower it in Cursor to enforce the budget." Lower the team default or group limit in Cursor's admin settings.

How limits reach each tool

Tokenize matches each person to their accounts by email. In Settings → Budgets, under Spending limits, an admin chooses how a person's budget is shared between their tools:

  • Split evenly: each tool gets an equal share. This is the default.
  • Follow usage: once a day, unused budget moves to the tools they use. The total stays the same.

Cursor limits are whole dollars. ChatGPT limits use your workspace's billing unit, credits or dollars. Tokenize rounds down, so a limit never goes over the budget. Someone can be stopped a little under their budget and still show as out of budget.

Claude and ChatGPT limits reset on the 1st (UTC). Cursor limits reset on your Cursor billing date.

What spend counts

A budget covers only the tools where Tokenize can set a per-person limit: Claude Enterprise, ChatGPT Enterprise (including Codex), and Cursor, through a key that can set limits. Spend anywhere else, such as OpenAI Platform or OpenRouter, doesn't count against budgets.

Someone with no Claude, ChatGPT, or Cursor account that takes a spend limit has no budget. Their row shows their spend as "$9 · No limit", and they don't count toward their team's budget or spend.

Read the Budgets pages

The top of each page shows a ring and Budget, Spent, Remaining (or Over by), Forecast, Teams out of budget (or People out of budget on a team with no sub-teams), and Spare budget, the budget teams are on pace to leave unspent. In the first days of the month there is no forecast yet: Forecast and Spare budget show "—" with "Too early in the month". Hover a team's or person's usage to see it split by tool. A person's breakdown also shows any amount approved for this month only, such as "includes $20 for October". "Cursor limit above budget, not enforced" means Cursor applies a higher team default or group limit to that person. On a team, it counts the people, such as "2 people: Cursor limit above budget, not enforced". See Ask for more budget.

On a team with no budget yet, each person's usage reads like "$34 · No budget set", so you can see what people spend before you pick a budget.

If you open a team page you can't see, it says "You don't have access to this team". If the team was renamed or removed, it says "Team not found". Click Back to budgets to return. If the page says "Couldn't load this team", click Try again.

The team list on the left marks teams that have reached or are close to their budget. Notes call out efficient teams close to their budget, where more budget is likely well spent, and teams where coaching may help more.

On the Overview page, the Budget card shows the company's month and the five teams most likely to run out. Click Manage budgets to open Budgets.

See budget activity

Click Activity at the top of Budgets to open a feed of everything that changed: requests for more and their answers, budget and overage changes, team owner changes, and changes to Settings → Budgets. Each line names who did what, for example "Dana raised Platform's per-person budget from $400 to $500", "Dana approved $100 for Sam for October from Engineering's pool", or "Dana made Sam the owner of Compliance, replacing Ada". Changes to the organization budget use your organization's name, for example "Dana lowered Acme's overage pool from $26,000 to $25,000", and carry a badge with that name instead of a team. A request's note or decline reason is shown under its line. When an approval for this month ends, or a request is answered in Claude or ChatGPT instead, the feed says so.

Who can see this: Admins see every team. Managers see the teams they own. Everyone else gets "You don't have access to this activity".

Use the Team list in the top right to pick one team or All teams. Click a person's name to see only their activity, and click the name again at the top to show everyone. Click Load more at the bottom for older events. Before anything has happened, the page says "No budget activity yet".

Export budgets to CSV

Admins can download every team's budget as a CSV file. At the top of Budgets, click the More actions button (⋯) and choose Export CSV. The file is named budgets-<date>.csv. The first row, (org default), is the organization budget. Then there is one row per team, parents before their sub-teams, with these columns:

ColumnWhat it holds
teamThe team's full path, such as Engineering/Platform
owner_emailThe team owner's email
peopleHow many people are on the team
per_person_budget_usdThe team's own Per person amount, empty when it uses its parent's
inherited_per_person_usdThe Per person amount of the team above it, which it uses when it has none of its own
overage_pool_usdThe team's Overage pool
pool_given_out_usdHow much of the pool is already given out
team_total_usdThe team's total
spent_this_month_usdWhat the team has spent this month

If the download fails, the page says "Couldn't download the budgets. Try again."

Settings → Budgets

At the top of Budgets, click the More actions button (⋯) and choose Settings, or go to Settings → Budgets. Only admins can open it. Besides Spending limits, it has:

  • Requests for more: turn Let people ask for more on or off. Requests go to the person's nearest team lead, who approves them for this month only or from now on. See Ask for more budget.
  • Manager alerts and People alerts: choose who hears about budgets, at what share, and by Slack or email. A Slack preview shows the messages. See Alerts.