Exclude or restrict models
You can exclude or restrict large language models (LLMs) to determine which models are available for Glean Assistant and Glean Agents, and who can use them.
When you exclude a model:
- The model becomes unavailable for selection in the agent builder, Glean Assistant, or both, depending on your configuration.
- Any agents or steps within an agent that were using the excluded model automatically switch to the default model.
- Auto stops routing to the model. If you exclude every recommended model in a task category, the Models page shows that Auto is degraded. See Resolve Auto mode warnings.
Exclude models based on your organization's key type
Glean supports two types of keys: Glean Universal Model Key and Customer Key (BYOK). Depending on the type of key your organization uses, the steps to exclude models and what you can exclude are different.
For both key types, you can exclude individual models with separate controls for Assistant and Agents.
Glean Universal Model Key
You can turn off individual models and control whether they're available for Assistant, Agents, or across Glean.
To block a model across Glean:
- Go to Admin console → Models.
- On the Models page, use the search bar, capability filter, or scroll to find the model you want to block.
- For the model you want to block, toggle the model off.
- Click Save to apply your changes. This blocks the model across Glean.
Open models, such as GLM 5.2 and Nemotron 3 Ultra, don't have individual toggles. You turn them on or off by creator region in the Other open models section. See Manage open models by region.
To keep new models off until you review them, turn on the New Model Review Period. See Review new models before they launch.
Customer Key (BYOK)
If your organization uses a Customer Key (BYOK), here's how to block models so that your Glean doesn't use them:
- Go to Admin console → Models.
- Click Add LLM.
- Select a LLM hosting provider.
- In the Select all models that can be used in agents section, clear the checkbox next to the model you want to exclude.
- Validate the connection.
- Click Save. This blocks the model across Glean.
Block a model for Assistant or agents only
These blocklists work the same way for both key types. Blocking a model here affects only the surface you choose and is independent of whether the model is available across Glean.
To block a model for Assistant only:
- Go to Admin console → Assistant → Settings.
- Navigate to the Blocked models in assistant section, then click Manage the blocklist.
- Search for models to add or remove from the blocklist.
- Click Save to apply your changes. This blocks the model for Assistant only.
To block a model for Agents only:
- Go to Admin console → Agents → Setup.
- Navigate to the Blocked models in agents section, then click Manage the blocklist.
- Search for models to add or remove from the blocklist.
- Click Save to apply your changes. This blocks the model for Agents only.
Hide all premium models from model pickers
If your organization uses a Glean Universal Model Key, you can remove all premium models from the model pickers in Glean Assistant and the agent builder. This may help your organization save costs related to using premium models.
To view a list of premium models, see the Premium tier under Supported models in LLMs.
Premium models have a $ Premium tag next to their names. This tag helps you identify premium models that incur higher costs so you can be mindful about which models you exclude.
Here are the steps to hide all premium models from the model pickers:
- Go to Admin console → Models.
- Click Advanced settings.
- Toggle off the Show premium models in model pickers switch.
This immediately hides premium models from Assistant model choice and the agent builder. Users can no longer manually select a premium model in those model pickers, and any premium models Glean launches in the future are hidden from the pickers as well.
Toggle on the Show premium models in model pickers switch to show premium models in the pickers again.
This toggle only controls the model pickers in Assistant model choice and the agent builder. It doesn't block premium models everywhere in Glean. Auto can still route to a premium model for certain use cases, such as artifact generation. To reduce premium model usage in Auto, assign the Economy policy, which prioritizes token-efficient models, or set usage limits.
To turn off a premium model completely across Glean, exclude it on the Models page. See Glean Universal Model Key for the steps.
Restrict model access by department
You can restrict any model to one or more departments so that only members of those departments can use it. This works for both Glean Universal Model Key and Customer Key deployments and applies wherever the model is used, including Glean Assistant and Glean Agents.
By default, Glean doesn't restrict models by department. If you don't select any departments for a model, everyone can use it. Department restrictions layer on top of the existing model controls. You still have to turn the model on (Glean Universal Model Key) or configure it (Customer Key) before the restriction takes effect.
Default models can't have department or IdP-group restrictions.
If you restrict all recommended models in a category to certain departments, users outside those departments don't have a recommended model for that category, and the Models page shows that Auto is degraded for some users.
Glean determines department membership from your synced people data. To learn how to populate the Department field for your users, see Sync people data.
To restrict a model to specific departments:
- Glean Universal Model Key
- Customer Key (BYOK)
- Go to Admin console → Models.
- Make sure the model is turned on.
- In the Access column for that model, open the selector and choose one or more departments. Leave the selector empty to keep the model available to everyone.
- Click Save to apply your changes.
- Go to Admin console → Models.
- Click Add LLM, select the hosting provider, and continue to the model selection step.
- Make sure the model is selected.
- In the Access column for that model, open the selector and choose one or more departments. Leave the selector empty to keep the model available to everyone.
- Click Save to apply your changes.
The Access column shows All users when a model isn't restricted, or the configured departments and groups otherwise. Hover the access details to see the full list.
Restrict model access by team
You can restrict an eligible model, including premium models, to one or more teams. Glean uses the group memberships synced from your identity provider to determine who can access the model. For supported identity providers and group sync behavior, see Group-based permissions.
Prerequisites
Before you restrict a model to an IdP group, complete the following prerequisites:
- Configure the identity connector that supplies your groups and complete an identity crawl.
- Configure the group datasource. Go to Admin console → Users & permissions → User roles → Default Member permissions → User group permissions, select the identity provider that supplies your groups, then click Save changes. You don't need to add a group-to-role mapping. See Make IdP groups available in Glean.
Creating a group in your identity provider isn't enough. Groups don't appear in the Access selector until you complete these prerequisites.
To restrict a model to specific teams:
- Glean Universal Model Key
- Customer Key (BYOK)
- Go to Admin console → Models.
- Make sure the model is turned on.
- In the Access column for that model, open the selector and choose one or more team.
- Click Save to apply your changes.
- Go to Admin console → Models.
- Click Add LLM, select the hosting provider, and continue to the model selection step.
- Make sure the model is selected.
- In the Access column for that model, open the selector and choose one or more teams.
- Click Save to apply your changes.
Users who aren't members of a selected group can't select or invoke the model in Glean Assistant or the agent builder.
You can configure department and team allow-lists on the same model. A user can use the model if they belong to at least one selected department or IdP group. If the model has no department or group restrictions, it's available to everyone who can otherwise use it.
Glean applies group membership changes after the next identity sync and model access refresh. If you add or remove a user from a group, the change may not be reflected immediately.
See also
- Review new models before they launch — keep new models off until you enable them or the review period ends
- Restrict feature access by user or group — limit advanced Assistant features to named users and IdP groups
- Group-based permissions — sync IdP groups and use them as principals across Glean
- Sync people data — populate the Department field used for department restrictions