How ACL Evaluation Works
ACLs are evaluated: table-level first, then field-level, then record-level. Multiple matching ACLs — access is granted if any permit. One missing table-level ACL and no downstream ACL will save you.
The Wildcard Problem
A '' ACL (table='', field=’*’) is convenient and dangerous. It applies to everything. Audit for wildcards and replace with scoped rules.
Roles vs ACLs
Roles are who. ACLs are what. A common mistake: over-granting admin role ‘just to test’ and forgetting. Build roles that map to real personas and assign ACLs to those roles.
Regulated Environments
SOX, HIPAA, GDPR — all require ACL documentation. Export ACL definitions quarterly. Tag sensitive fields. Build Data Certification processes around them.
Testing ACLs
Impersonate a user with the expected role set. Walk through their tasks. Any ‘number does not match’ or silent-missing-data means an ACL gap, not a bug.