Control which models people use
Set the default model and limit which models Claude Code, Codex, and Cursor can run, for the whole organization or one team.
The Models page sets two things for each coding agent: which model new sessions start on, and which models people are allowed to run. You set an organization baseline, then override it for specific teams. The Tokenize desktop app applies the rules on each person's computer.
Who can do this: Admins. Everyone else sees a read-only view of the models their organization allows them to run.
How the page is laid out
Go to Models. There is one card per agent: Claude Code and Codex. Each card has:
- Default model: the model new sessions start on. Choose Provider default to let the agent pick its own model.
- Limit models: when on, devices can run only the models you allow. When off, devices can run any model for that agent.
- A list of models, each with an on/off switch, shown when Limit models is on. A model is allowed when its switch is on.
When Limit models is on, the default has to be one of the allowed models.
Admins also see a Cursor card when a Cursor Team Admin API key is saved. It works differently. See Limit Cursor models.
Set the organization baseline
- Go to Models. Make sure the scope picker at the top right says Organization.
- On each agent's card, choose a Default model.
- Turn Limit models on if you want to restrict models. Then turn each model's switch on or off.
- Click Save changes. To undo edits you haven't saved, click Discard.
Organization settings apply to every team unless a team overrides them.
Override a team
- In the scope picker, choose the team. Teams come from your directory. See SSO and directory sync.
- Change the Default model or the allowed models. Anything you change shows an Override badge.
- Click Save changes.
A team without its own setting inherits from its parent team, then from the organization. Limit models can only be turned on or off at the organization level. On a team, it shows as Limited or Open.
To remove all of a team's overrides, choose the team and click Reset to organization, then Save changes.
Limit Cursor models
The Cursor card switches models off in your Cursor team's model access policy. Cursor applies the policy itself, so it doesn't depend on the Tokenize desktop app. The card has no Default model row.
Before you start, you need:
- A Cursor Team Admin API key saved in Tokenize. See Connect Cursor.
- Model access controls on your Cursor team, which come with Cursor's Enterprise plan.
- A custom model policy saved in Cursor under Team Settings → Models.
To limit models:
- Go to Models. Make sure the scope picker says Organization.
- On the Cursor card, turn Limit models on. The card lists your Cursor team's models.
- Turn off the switch for each model your team shouldn't run.
- Click Save changes. You'll see "Saved. Tokenize updates your Cursor team within a few minutes."
Keep these points in mind:
- One policy for the whole team. With a team selected, the card says "Cursor has one model policy for your whole Cursor team, so change it under Organization."
- Off in Cursor. A model an admin switched off in Cursor itself shows an Off in Cursor badge and can't be changed here. Tokenize only switches back on the models it switched off.
- Turning Limit models off switches back on every model Tokenize switched off.
- Organization Groups. Cursor's Organization Groups can still allow more models for some people.
- Same list as Tasks. The card edits the same list as the Block the most expensive models in Cursor task on the Tasks page. A change on either page shows on the other.
The line at the top of the card says whether Tokenize can apply your changes. When it can, it reads "Tokenize applies changes to your Cursor team within a few minutes of saving, including to models Cursor adds later." For the other messages, see Troubleshooting below.
When changes take effect
These timings are for Claude Code and Codex. Cursor changes are applied in your Cursor team within a few minutes of saving.
Changes reach devices in about 15 minutes. Once a device has the new rules:
- Claude Code: sessions already open keep their old settings. Start a new session to pick up the change.
- Codex Desktop: quit and reopen the app. Closing the window isn't enough, because Codex keeps running in the background.
- Codex CLI: each new command picks up the change.
People who don't have the Tokenize desktop app installed aren't affected. See Install on your computer.
Troubleshooting
"Team scopes are unavailable — listing teams needs usage access, which your role does not have." Your role can edit models but can't read the team list. You can still edit the organization baseline. Ask an admin to add usage access to your role.
"Someone else saved this policy — it was reloaded and your changes re-applied; review and retry." Another admin saved while you were editing. Check the page, then click Save changes again.
"Tokenize is checking your Cursor admin key. Changes you save apply once the check passes." Wait a few minutes and reload the page. What you save is kept.
"Cursor didn't answer the last check. Tokenize tries again within a few minutes." Nothing to do. Your saved list applies once Cursor answers.
"Add a Cursor admin key on the Providers page so Tokenize can apply this." The Cursor key was removed while models were still blocked. Add a Team Admin API key, or turn Limit models off. See Connect Cursor.
"Your Cursor team doesn't have model access controls, which come with Cursor's Enterprise plan. Tokenize keeps what you save and applies it if your team gets them." Model limits need Cursor Enterprise.
"Your Cursor admin key can't manage models. In Cursor, create a key with the models permission (or full admin), then save it on the Providers page." Replace the Team Admin API key with one that has that permission. See Connect Cursor.
"Your Cursor team uses Cursor's default model settings. In Cursor, open Team Settings → Models and save a custom model policy. Tokenize doesn't make that switch itself, because it can change which models are on." Save a custom model policy in Cursor. Tokenize applies your list after that.
A model's name followed by "Cursor refused a change." Cursor rejected the change for that model. Any detail Cursor gave follows the message. Change that model in Cursor instead.
"Couldn't load your Cursor model settings." Click Retry.
A team can't choose Provider default. A team can only choose Provider default if neither the organization nor a parent team has chosen a default model.