Configure LLMs in the Model Hub

Configure which models are available in your Glean deployment and choose the models used in Glean Agents and Glean Assistant workflows.

To exclude models or restrict them to specific departments, see Exclude or restrict models.

For the list of supported models, availability by hosting environment, and pricing, see Supported LLMs.

Configure models in the Model Hub

You can configure models using either Glean Universal Model Key or Customer Key (BYOK).

note

Self‑hosted AWS deployments can use Gemini through Vertex AI. Self‑hosted GCP deployments cannot use models hosted on AWS, for example, Bedrock.

Glean Universal Model Key

With Glean Universal Model Key, Glean manages model configuration and provisioning for you. However, you can still configure which models are available in your deployment:

1. Go to Admin console → Platform → LLMs.
2. On the Models page, use the search bar, capability filter, or scroll to find the model you want to include.
3. Select the three-dot menu (...) next to the model creator, then click Manage models.
4. For the model you want to include, toggle the model on.
5. Click Save to apply your changes. This includes the model across Glean, including Assistant and Agents.

The Models page for Glean Universal Model Key shows per-model toggles grouped by creator. This differs from the Customer Key experience, which uses hosting provider-based configuration.

Customer Key

With Customer Key, you can configure which models are available in your deployment. The Models page for Customer Key shows per-model toggles grouped by hosting provider.

note

For Customer Key deployments, model defaults for image generation models can use a different provider. All other models must use defaults from the same provider.

To configure which models are available in your deployment:

1. Go to Admin console → Platform → LLMs.
2. Click Add LLM.
3. Select a hosting provider and follow the configuration steps:

1. Ensure that the Assistant is configured.
2. In your Azure Portal, go to Keys and Endpoints, add the Key and Endpoint you want to use with Glean.
3. (Optional) If you have not configured the Assistant, select models for Assistant.
   • For each selected model, add the deployment name configured on Azure.
4. Select models for use in Glean.
   • For each selected model, add the deployment name configured on Azure.
5. Validate the connection.
6. Click Save.
7. To remove a model, uncheck it, validate, and save.

1. Enter your preferred region.
2. (Optional) If you have not configured the Assistant, select models for Assistant.
3. Select models for Agents.
4. Validate the connection.
5. Click Save.
6. To remove a model, uncheck it, validate, and save.

1. (Optional) If you have not configured the Assistant, select models for Assistant.
2. Select models for Agents.
3. Ensure selected models are enabled in Google Model Garden.
4. Validate the connection.
5. Click Save.
6. To remove a model, uncheck it, validate, and save.

1. Enter your API key to be used with Glean from the OpenAI Portal.
2. (Optional) If you have not configured the Assistant, select models for Assistant.
3. Select models for Agents.
4. Validate the connection.
5. Click Save.
6. To remove a model, uncheck it, validate, and save.

Select models for workflows

Only models enabled for the Agents appear in the agent builder. Similarly, only models enabled for the Assistant are available when users select models in Glean.

See Exclude or restrict models for more information on how to exclude or restrict models.

Set default model for an agent

In the agent builder, open Settings (gear icon) → Select Model.

Set per‑step model

In the canvas, select a step and choose a model for that step.

Best practices

• Start with a balanced default model for most tasks and upgrade select workflows to higher‑tier models when you need stronger reasoning.
• Where possible, keep model families consistent across multi‑step workflows for predictable quality and cost.
• For Customer Keys: Align with your enterprise provider contracts and control data routing with cloud restrictions.

See also

• For the list of supported models, availability, and pricing, see Supported LLMs.
• To exclude models or restrict them to specific departments, see Exclude or restrict models.
• To learn how Glean handles model deprecation, including notification timelines, migration paths, and tools needed for assistants and agents, see Model deprecation.
• To learn how users can select a model in Glean Assistant, see Model choice.
• To resolve errors when connecting to your LLM provider, see Troubleshoot LLM provider errors.