{"version":"2.1.227","anchor":"switching-models-checks-your-organization-s-entitlement-firs","canonical_anchor":"switching-models-checks-your-organization-s-entitlement-firs","heading":"Switching models checks your organization's entitlement first","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/switching-models-checks-your-organization-s-entitlement-firs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Switching models checks your organization's entitlement first\n\nSwitching models now checks your organization's entitlement live and refuses if it can't confirm.\n\n**What**\n\nChoosing a model now forces a server-side entitlement check instead of trusting cached access. If the check denies the model or cannot be completed, the switch is refused with the organization-restriction message rather than silently proceeding.\n\n**Details**\n\n- Failures are recorded against `model_switch` with the reason `denied_by_entitlement` or `entitlement_probe_failed`.\n- A successful switch prunes models you are no longer entitled to out of the saved `modelAccessCache`.\n\n**Evidence**\n\n`denied_by_entitlement`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}