{"version":"2.1.273","anchor":"new-session-wide-lock-message-for-restricted-policy-orgs","canonical_anchor":"new-session-wide-lock-message-for-restricted-policy-orgs","heading":"New session-wide lock message for restricted-policy orgs","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-session-wide-lock-message-for-restricted-policy-orgs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New session-wide lock message for restricted-policy orgs\n\nNew message explains when a feature stays disabled for the rest of a session after a restricted-policy org signed in\n\n**What**\n\nA new message has been added alongside the existing \"disabled by your organization's policy\" message. It explains that once a session has seen a sign-in from an organization with a restricted policy, a feature stays disabled for the rest of that session, even if you later sign in with a different account.\n\n**Why**\n\nThis clarifies a behavior that could otherwise be confusing: switching accounts mid-session doesn't necessarily re-enable a feature that a restricted-policy organization's sign-in had turned off, and now Claude Code tells you why.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}