Skip to main content
Model Management gives your organization control over which AI models your team can access in Scout Studio. Admins enable models by provider, choose an org-wide default, and keep agents restricted to approved, cost-effective options. These settings apply org-wide and govern which models appear everywhere models are used — including the agent editor.
The Settings > Models page showing a Default chat model dropdown above a provider list with enabled counts

​
Where to Find It

In Scout Studio, open Settings in the left sidebar, then choose Models.
These settings apply org-wide, and only org admins can enable, disable, or change defaults. If you don’t see editable controls, ask your org admin to make the change.

​
Enabling Models

Models are grouped by provider. Each provider row shows how many of its models are enabled versus the total available (for example, OpenAI 3/10).
1

Open Models settings

Navigate to Settings → Models.
2

Expand a provider

Click a provider to reveal its individual models.
3

Toggle on the models you want

Switch on each model you want available to your team.
To narrow the list, filter by type using the All, Completion, and Image tabs, or search by model name or provider. Enabled models become usable in agents right away.

​
Setting a Default Model

The org default is pre-selected for new chats unless an agent overrides it. A cost-efficient model is recommended for the default so everyday usage stays predictable.
1

Open Models settings

Navigate to Settings → Models.
2

Open the default dropdown

Under Default chat model, open the dropdown.
3

Pick your org default

Choose the model to use as the organization default.
The chosen model pre-fills new chats and serves as the starting option in the agent editor.

​
How It Affects Agents

The agent editor’s model picker only shows enabled models, with the org default pre-selected. Creators can still choose any other enabled option. This lets you:
  • Restrict agents to vetted, approved models
  • Keep costs predictable by limiting the available choices
  • Set an efficient default while keeping powerful models available for specific needs
  • Adjust models on existing agents individually or in bulk

​
Disabling a Model

When you disable a model that’s used by agents or workflows, Scout shows how many items are affected and requires you to choose a replacement before the model can be disabled. Affected agents continue running until a replacement is applied.
The disable-model confirmation modal with a replacement model picker and a count of affected items
You have two replacement options:

Replace all with

Apply a single replacement model to every affected item, then click Replace & disable.

Review individually

Open a table to assign a different replacement per item, then click Disable.
Choosing Review individually opens a table listing each affected item with its own replacement dropdown, so you can map different models per agent before disabling.
The per-item review table listing affected agents, each with its own replacement model dropdown
Confirm your replacements before closing the dialog. The model is only disabled once a replacement has been applied to the affected items.

​
Troubleshooting

IssueLikely causeSolution
Model not appearing in agent editorNot enabled for the orgGo to Settings → Models and toggle it on
Cannot change settingsNot an org adminAsk your org admin to make the change
Default model not pre-selectedBrowser cacheHard refresh (Cmd+Shift+R / Ctrl+Shift+R)
Agent using the wrong model after a changeAgent has a pinned model overrideOpen the agent editor and update the model directly

​
Next Steps

API Keys

Create and manage credentials to authenticate your Scout integrations.

Agents Overview

Build agents that use your approved models in the agent editor.