The Model Catalog solves this by giving admins a single place to control exactly which models are available, who can use them, and where — whether that's the model picker in home chat or custom agents built by your team.
You might need the Model Catalog when:
You want to limit access to expensive frontier models to a specific team, like your AI Committee
Your organization is phasing out a model but one team needs to keep using it during the transition
You want to prevent new custom agents from being built on outdated or unapproved models
Your IT team manages API keys centrally and you need to verify which models actually work through your current keys
This guide will show you how to block models, grant exceptions, and verify model availability, so you can roll out AI access on your organization's terms.
Before you begin
You must have an admin role in your elvex organization
At least one AI provider must be connected as the Model Catalog only lists models available through your connected API keys
If you plan to grant exceptions by group, make sure those groups already exist under Admin → Company → Groups
Understanding the Model Catalog
Navigate to Admin → AI → Model Catalog. You'll see a table listing every model available through your organization's connected API keys. The summary line at the top shows your totals, for example "112 models available · 0 blocked."
Each row represents one model and includes:
Column | What it controls |
Model | The model's display name and its model ID (for example, |
Provider | The AI provider the model belongs to (Anthropic, OpenAI, etc.) |
Elvex Agent | Whether the model appears in the model picker in home chat |
Custom Agents | Whether the model can be used by custom agents — both existing agents and new ones |
Test | A button that verifies the model works through your connected API key |
Except for | Who keeps access when you've blocked the model |
The two access columns are independent. Blocking a model for the Elvex Agent removes it from the home-chat model picker but leaves it available to custom agents, and vice versa. This lets you, for example, keep a powerful model out of everyday chat while still allowing a purpose-built agent to use it.
All changes in the Model Catalog save automatically — there's no save button, and changes take effect immediately.
About "Unavailable" models
Some models show Unavailable in the Elvex Agent column with no checkbox. This means the elvex team hasn't approved that model for the elvex agent, so it can't be enabled for home chat regardless of your settings. Hover over the label to see the reason. Unavailable models can still be enabled for Custom Agents, and they don't count toward your blocked total.
How to block a model from the home-chat model picker
Use this when you want to stop users from selecting a model in home chat, without affecting custom agents.
Navigate to Admin → AI → Model Catalog to see your full model list
Use the Search models field to find the model by name or model ID — for example, typing "opus" narrows the list to matching models
Uncheck the box in the Elvex Agent column on that model's row — the model is immediately removed from the home-chat model picker for all users
Note that the Custom Agents column stays checked, so existing and new custom agents can continue using the model
Once a model is blocked in either column, its Except for cell changes from "—" to a No one dropdown, which you can use to grant exceptions (see below).
How to block a model from custom agents
Use this when you want to prevent a model from being used by any custom agent — including agents that already exist.
Navigate to Admin → AI → Model Catalog
Find the model using search or the Provider filter
Uncheck the box in the Custom Agents column on that model's row
Blocking a model for Custom Agents prevents new agents from being built on it and affects existing agents that use it. If existing agents use a model you block, you'll be asked to reassign those agents to a different model of your choice, so they keep working.
Warning: Blocking a model for Custom Agents affects everywhere those agents run — chat, Slack and Teams, scheduled runs, and the API — for anyone not listed under Except for.
How to block many models at once
Use this when you want to restrict an entire family or provider of models — for example, blocking all Opus-class models to control costs.
Navigate to Admin → AI → Model Catalog
Filter the list using the Search models field or the Provider dropdown so only the models you want to block are shown
Click Block all in the header of the column you want to restrict (Elvex Agent or Custom Agents)
Review the confirmation dialog, which states exactly how many models will be blocked — for example, "Block 5 models for custom agents?"
Click the confirmation button to apply the block — every affected row's Except for cell changes to No one
Important: Block all only affects the models currently shown in the list. If you've searched for "opus" and see 5 of 112 models, only those 5 are blocked — not the entire catalog. Clear your filters first if you intend to block everything.
To restore access in bulk, use Allow all on the same filtered list.
How to grant exceptions to a blocked model
Blocking a model doesn't have to be all-or-nothing. Exceptions let specific people keep access — useful when one team needs a restricted model for a sanctioned project, or when you're phasing a model out gradually.
Block the model in one or both columns, so its Except for cell shows No one
Click No one to open the exceptions panel below the row — it reads "Blocked for the elvex agent — except for:" (or "…and custom agents" if blocked in both columns)
Add exceptions in either field:
Roles — select a standard elvex role or one of your custom roles
Groups and people — select a group (for example, "AI Committee") or individual people
The dropdown updates to show who's exempt — for example, "1 group"
There's one exception list per model. If a model is blocked in both columns, the same list of roles, groups, and people keeps access in both places.
How to test that a model works
If your IT team manages your API keys — for example, in the OpenAI Platform — a model can appear in your catalog even if your key doesn't actually have access to it. The Test button lets you confirm before your users find out the hard way.
Find the model in the Model Catalog
Click Test on its row
Check the result that appears under the button — for example, "Works · 1447 ms" confirms the model responds through your connected key
How the blocked count works
The summary line counts blocks, not models. Each column you block a model in counts once. For example:
Claude Opus 5.5 blocked for the Elvex Agent = 1 block
5 Opus models blocked for Custom Agents = 5 blocks
Total: 6 blocked, even though only 5 models are affected
Models marked Unavailable don't count toward the total.
What your users see
Home chat: Blocked models simply don't appear in the model picker for users without an exception. Users with an exception see and select the model as normal.
Custom agents: New agents can't be built on blocked models. Existing agents on a blocked model stop working for users without an exception — across chat, Slack and Teams, scheduled runs, and the API — until they're reassigned to an allowed model.
Common questions
What's the difference between blocking for the Elvex Agent and for Custom Agents?
The Elvex Agent column controls the model picker in home chat — the direct conversation users have with elvex. The Custom Agents column controls which models your team's custom agents can be built on and run with. Block in the first column to simplify everyday chat choices; block in the second to enforce standards on what your organization builds.
Do changes really apply immediately?
Yes. Every change saves automatically and takes effect right away — there's no save button and no undo. To reverse a change, re-check the box or use Allow all on the filtered list.
Can I restrict models for just one team instead of the whole organization?
Blocks apply organization-wide, but exceptions give you per-team control in practice: block the model for everyone, then add the team that needs access as a group under Except for.
Why does a model show "Unavailable" for the Elvex Agent?
The elvex team hasn't approved that model for the elvex agent. Hover over the label for the specific reason. You can still enable it for Custom Agents.
What happens if I block a model that existing custom agents are using?
You'll be prompted to reassign those agents to a model you choose, so they continue working. Until reassigned, those agents stop working for anyone without an exception — everywhere they run.