{"version":"2.1.314","anchor":"compliance-gate-for-hipaapolicy-changed","canonical_anchor":"compliance-gate-for-hipaapolicy-changed","heading":"Changed reasons and checks for HIPAA-restricted accounts","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/compliance-gate-for-hipaapolicy-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Changed reasons and checks for HIPAA-restricted accounts\n\nA policy check no longer gives diskless or hipaa as reasons, and a separate feature now also requires HIPAA and zdr to be unset\n\n**Unclear.** Which feature the second check controls, and so what HIPAA or zdr accounts lose, is not stated.\n\n**What**\n\nClaude Code has a check that can block something for policy reasons. It no longer reports \"diskless\" or \"hipaa\" as the reason. In the HIPAA case it now reports \"policy_not_loaded\" when a certain condition holds.\n\nA separate check for a feature now also requires that the account is marked neither HIPAA nor zdr.\n\n**Why**\n\nThe reason you see when policy blocks something may read differently.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}