{"version":"2.1.304","anchor":"org-config-gate-sessions-can-be-refused-when-required-org-s","canonical_anchor":"org-config-gate-sessions-can-be-refused-when-required-org-s","heading":"Sessions can be refused when your organization's settings fail to load","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/org-config-gate-sessions-can-be-refused-when-required-org-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sessions can be refused when your organization's settings fail to load\n\nClaude Code can now refuse to start a session when your organization's required settings can't be loaded\n\n**Unclear.** Which accounts and plans the server applies this check to is not known.\n\n**What**\n\nOrganizations can set rules and limits for Claude Code that it fetches at startup. Claude Code now has a check that looks at whether those fetches worked and decides one of these:\n\n- pass\n\n- pass using a stored earlier result\n\n- pass because the account is exempt\n\n- blocked\n\n- refused\n\nWhen blocked, Claude Code shows a message such as \"Claude Code couldn't load your organization's settings, which it requires before a session can start.\" In the interactive screen you get a blocked screen with a retry option. Headless runs, where Claude Code runs without its interactive screen, exit with the message.\n\nThe check is controlled by a setting Claude Code reads from the server. That setting can give a time limit, a share of accounts, which plans it covers, and a grace period in hours.\n\n**Why**\n\nFor team and enterprise accounts where it applies, a failure to load organization settings can now stop a session from starting at all, rather than letting it run without them.\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"}