{"version":"2.1.287","anchor":"managed-settings-denial-message-for-model-checks","canonical_anchor":"managed-settings-denial-message-for-model-checks","heading":"Claude Code explains when managed settings block a model","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/managed-settings-denial-message-for-model-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude Code explains when managed settings block a model\n\nA new message says when a model was skipped for a check, fallback or upgrade because managed settings do not allow it\n\n**Unclear.** Where this message is shown is not stated.\n\n**What**\n\nManaged settings are settings an administrator installs centrally. Claude Code now has a message saying a model was skipped for a check, a fallback or an upgrade because managed settings do not allow it as spelled. The reasons it gives:\n\n- no enforced `availableModels` entry matches the model\n\n- the model is named in `deniedModels`\n\n- the managed settings failed to load\n\n**Why**\n\nAdministrators and users get an explanation when a managed model policy blocks a model, instead of the model silently not being used.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}