{"version":"2.1.304","anchor":"login-blocked-messages-when-managed-settings-policy-cannot-b","canonical_anchor":"login-blocked-messages-when-managed-settings-policy-cannot-b","heading":"Clearer messages when sign-in is blocked by your organization's managed settings","tier":"notice","area":"Auth","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/login-blocked-messages-when-managed-settings-policy-cannot-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Clearer messages when sign-in is blocked by your organization's managed settings\n\nA sign-in refused because managed settings could not be satisfied now says whether it was revoked or must be revoked by an admin\n\n**What**\n\nManaged settings are rules an organization's administrator puts on a machine to control how Claude Code may be used. The messages shown when a sign-in is refused because this policy could not be satisfied or verified now come in two versions:\n\n- Revoked: the refused sign-in has already been cancelled.\n\n- Possibly still valid: the sign-in may still work, and the message asks you to have an admin revoke it, especially on a shared device.\n\n**Why**\n\nIf you work under managed settings, the message now tells you whether you need to do anything after a blocked sign-in. On a shared machine, it tells you to have an admin cancel the leftover sign-in so nobody else can use it.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}