{"version":"2.1.251","anchor":"blocked-features-now-name-the-compliance-policy-behind-the-b","canonical_anchor":"blocked-features-now-name-the-compliance-policy-behind-the-b","heading":"Blocked features now name the compliance policy behind the block","tier":"notice","area":"Policy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/blocked-features-now-name-the-compliance-policy-behind-the-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Blocked features now name the compliance policy behind the block\n\nFeatures blocked by org policy now name the compliance policy, currently only HIPAA.\n\n**What**\n\nWhen your organization's policy blocks a feature like Artifacts or Remote Control, the message now names the compliance policy responsible, for example \"not available for your organization due to its compliance policy (HIPAA)\", instead of a generic policy notice. HIPAA is the only policy name this build recognizes.\n\n**Details**\n\n- The policy name comes from flags reported by the server, not from local settings.\n- Falls back to the previous generic wording when no recognized policy flag is present.\n\n**Evidence**\n\n`not available for your organization due to its compliance policy`\n\n- Area: Policy\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}