{"version":"2.1.232","anchor":"enterprise-policy-files-validate-identity-matching-much-more","canonical_anchor":"enterprise-policy-files-validate-identity-matching-much-more","heading":"Enterprise policy files validate identity matching much more strictly","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/enterprise-policy-files-validate-identity-matching-much-more","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Enterprise policy files validate identity matching much more strictly\n\nEnterprise policies now reject blank groups and normalize email domains before matching.\n\n**What**\n\nManaged configuration now rejects blank entries in a policy's group list, an empty group list, and an empty or whitespace-only email domain, as well as domains containing `@`, whitespace or commas. Email domains are trimmed, stripped of a leading `@` and lowercased before being matched, so casing and stray characters no longer silently break a policy. The admin group list rejects empty strings for the same reason.\n\n**Details**\n\n- The `desktop` block is no longer checked against a fixed schema and now accepts any record.\n\n**Evidence**\n\n`match.email_domain is blank after normalization`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}