{"version":"2.1.283","anchor":"model-default-attributed-to-organization-when-managed-policy","canonical_anchor":"model-default-attributed-to-organization-when-managed-policy","heading":"Default model replaced by an organisation deny policy gets its own managed_deny source","tier":"notice","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/model-default-attributed-to-organization-when-managed-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Default model replaced by an organisation deny policy gets its own managed_deny source\n\nWhen an organisation's managed policy denies your default model, the replacement is now tagged managed_deny and still labelled Set by your organization\n\n**Unclear.** It is not clear whether the on-screen label reads any differently than it did before.\n\n**What**\n\nAn organisation can use a managed policy, settings an administrator controls, to allow only certain models. When your usual default model is not allowed, Claude Code picks another one.\n\n- That replacement is now tagged with a new source, `managed_deny`. Before, it was counted as an `entitlement` fallback.\n\n- The model picker shows \" \u00b7 Set by your organization\" for `managed_deny`, the same label as the enforced and entitlement sources.\n\n- Usage reporting now records it as `managed_deny_default` instead of `entitlement_default`.\n\n**Why**\n\nWhat you see is the same: a model chosen because of your organisation's policy is marked \"Set by your organization\". Behind the scenes, a model swapped out by an organisation deny policy can now be told apart from one set by your plan's entitlements.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}