{"version":"2.1.314","anchor":"policy-limits-fallback-returns-deny-all-when-a-condition-hol","canonical_anchor":"policy-limits-fallback-returns-deny-all-when-a-condition-hol","heading":"A policy limit can now block everything instead of staying off","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/policy-limits-fallback-returns-deny-all-when-a-condition-hol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### A policy limit can now block everything instead of staying off\n\nUnder one condition, a policy limit that used to be off whenever unset now resolves to blocking everything\n\n**Unclear.** Nothing says which setting this is or what condition turns it into deny_all.\n\n**What**\n\nClaude Code reads policy limits, meaning restrictions an organization can place on what it is allowed to do. For one of them, an unset or switched-off value used to always mean \"off\". Now, when a further check passes, that same value means \"deny_all\", which blocks everything that limit covers.\n\n**Why**\n\nA restriction that used to stay off by default can now apply under some condition. Some features could then be blocked for those users.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}