{"version":"2.1.314","anchor":"org-config-gate-now-probed-at-login-sign-in-can-be-refused","canonical_anchor":"org-config-gate-now-probed-at-login-sign-in-can-be-refused","heading":"Signing in can be refused or warned when your organization's settings cannot be checked","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/org-config-gate-now-probed-at-login-sign-in-can-be-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Signing in can be refused or warned when your organization's settings cannot be checked\n\nAfter sign-in, Claude Code checks your organization's settings and may refuse the sign-in or warn you if they cannot be loaded\n\n**What**\n\nAfter you sign in, Claude Code now asks the server for your organization's policies and settings. If those settings cannot be loaded, one of two things happens, depending on a setting the server sends:\n\n- the sign-in is refused and the new login token is cancelled\n\n- the sign-in goes through with a warning: \"Signed in. Claude Code couldn't verify your organization's settings yet\"\n\nA login token is the key Claude Code uses to act for your account. When a token is cancelled this way, the message says Anthropic reported it revoked and that it was not shown. Creating a long-lived token with the setup-token command is handled the same way, so its token can also be withheld.\n\n**Why**\n\nIf you belong to an organization with managed settings, a sign-in or a setup token may be blocked or held back when those settings cannot be fetched. Signing in again later may then succeed.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}