{"version":"2.1.314","anchor":"login-flow-checks-org-config-and-reloads-org-documents","canonical_anchor":"login-flow-checks-org-config-and-reloads-org-documents","heading":"Sign-in now checks your organization's configuration and reloads its settings","tier":"notice","area":"Auth","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/login-flow-checks-org-config-and-reloads-org-documents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Sign-in now checks your organization's configuration and reloads its settings\n\nSign-in can now be refused by organization policy, including in `claude setup-token`, and organization settings are reloaded right after sign-in\n\n**Unclear.** It is not clear what turns this organisation check on or which accounts it applies to.\n\n**What**\n\nWhen you sign in with your Claude account through the browser (the OAuth sign-in flow), Claude Code now checks your organization's configuration before it saves the new credentials. Your organization's policy can therefore refuse a sign-in.\n\n- A refused sign-in revokes the token that was just issued, so it can no longer be used, and the error is shown to you.\n\n- `claude setup-token`, the command that creates a long-lived sign-in token, now ends when the sign-in is refused. Its sign-in screen gained an `onOrgConfigRefused` callback (a step that runs when this happens) next to the existing `onAccountOnHold`, and the command exits with an `org_config_refused` status.\n\n- The onboarding, login and session-resume dialogs now reload your organization's documents and settings after sign-in, through the new `onOrgDocumentsReload` and `onSettingsReload` callbacks and an `orgConfigGateFollows` option.\n\n- The error shown when `--bg` (start a session as a background agent) is combined with bypass-permissions mode now tells you when your user settings are not being read.\n\n**Why**\n\nIf you work under an organization that manages Claude Code, signing in or creating a token can now fail because of that organization's policy, and the failure is reported instead of the token being kept. Organization-managed settings are reloaded as part of signing in.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}