[DOCS] Model config docs omit "Org default" and "Role default" labels in `/model` picker
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/model-config
Section/Topic
"Restrict model selection" and "Default model selection" — coverage of admin-set organization and role default models.
Current Documentation
The page currently explains two admin-side restrictions:
"Enterprise administrators can useavailableModelsin managed or policy settings to restrict which models users can select. Entries match a model family such assonnet, a version prefix such asclaude-sonnet-4-5, or a full model ID such asclaude-sonnet-4-5-20250929."
"Organization admins restrict which models members can run by disabling individual models in the Claude Console. Use this Console toggle instead ofavailableModelswhen your members authenticate through the Anthropic API and you want one org-wide switch without deploying settings files. This restriction is delivered with the account's entitlements when Claude Code authenticates, separate from anyavailableModelslist in settings, and the server enforces the same restriction independently when a session is created. Requires Claude Code v2.1.187 or later."
The page does not mention organization- or role-default models that admins can pin so members see "Org default" or "Role default" in /model until they pick something themselves.
What's Wrong or Missing?
Starting in v2.1.196, organization admins can set a default model for the entire org (or a specific role) from the org console. Claude Code exposes that choice in the /model picker as a row labeled "Org default" (or "Role default" when the default is scoped to a role) so members can pick it explicitly without having to remember the model ID. The page describes restriction (availableModels, per-model disable) but does not document this admin-set default or the picker labels a user sees when no personal default has been chosen.
Suggested Improvement
Add a new subsection under "Restrict model selection" titled "Set an organization or role default model" that explains:
- Admins set the default from the org console.
- When a user has not picked a model themselves, the
/modelpicker shows a row labeled "Org default" (or "Role default" when the default is role-scoped). - The docs should clarify how this admin default interacts with user-selected models and settings-level model preferences, without requiring users to know the underlying model ID.
- Mention the behavior alongside the existing v2.1.187+ org-level disable paragraph so admins can see both halves of model policy.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/model-config | Primary location for org- and role-default model behavior |
| https://code.claude.com/docs/en/settings | Cross-reference for /model picker behavior and per-user model overrides |
| https://code.claude.com/docs/en/admin-setup | Cross-reference for admin console actions on model policy |
Total scope: 3 pages affected.
Claude Code v2.1.196 added the org/role default model labels in /model. The docs only cover restriction (availableModels, per-model disable), not the complementary "set a default" path admins use today.