New message explains when a feature stays disabled for the rest of a session after a restricted-policy org signed in
A 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.
This 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.