{"version":"2.1.314","anchor":"login-now-checks-the-organizations-config-before-saving-a-s","canonical_anchor":"login-now-checks-the-organizations-config-before-saving-a-s","heading":"claude auth login checks your organization's settings before saving a sign-in","tier":"notice","area":"Auth","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/login-now-checks-the-organizations-config-before-saving-a-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### claude auth login checks your organization's settings before saving a sign-in\n\nclaude auth login now checks a new sign-in against your organization's settings and exits with an error if it is refused\n\n**Unclear.** Nothing says what makes an organization refuse a sign-in, or whether it requires an organization policy to be set up.\n\n**What**\n\nWhen you sign in with `claude auth login`, Claude Code now checks the new sign-in against your organization's settings before saving it. This applies to both the browser sign-in and the refresh-token sign-in.\n\n- If your organization refuses the sign-in, Claude Code prints the reason and exits with status 1. The exit reason is `cli_auth_login_org_config_refused`.\n\n- If the check cannot be completed, the sign-in is still saved. Claude Code tells you it will check again the next time it starts.\n\nBefore, login saved your credentials straight away after checking the token.\n\n**Why**\n\nIf you belong to a managed organization, you can now be stopped when you sign in, not only later when Claude Code starts. Scripts that run `claude auth login` should be ready for it to exit with status 1.\n\n- Area: Auth\n- Names: `claude auth login`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}