Dominion Shield reads every ACL, role, group and before-query rule on the tables you track, counts each active person once, and splits the answer into people with unrestricted access and people whose access depends on the record.
The whole table on one screen
Four cards answer "who can create, read, write and delete", split into unrestricted and conditional. Below them every role meets every operation, coloured by how access is decided.
Try it: select a big number to see how it adds up, or any cell to see who it covers and why.
Every person behind the numbers
Reviewers see who sits inside each count, how they got the role, and what changed since the last run. Filter by operation, tier or role; the counts above still cover everyone.
| Person | Access via | Create | Read | Write | Delete | Since last run |
|---|
Why can this person do that?
Before-query rules first, then every ACL the person's roles reach, in order. Compare two people side by side, or pick a record to see the answer for that record.
Risks a security lead can act on
Read-only checks on the latest analysis and on recent ACL changes: broad exposure against the table's threshold, ACLs that changed in the drift window, and read access that list views can't filter.
A flag reaches the person who can answer it
Anyone with access to the portal can flag a cell. The review goes to the first match below, and the confirmation names who got it, so people can see routing working.
Choose what it may track, and when it runs
One Settings record holds the allowed tables, the weekly analysis time, retention and the fallback reviewer. A tracked table outside the allowed list can't be saved.
Three roles, three levels of detail
Grant them through groups. Each role contains the one before it, and new viewers get a nine-step guided tour of the Heatmap on their first visit.
Viewers
x_blui2_dshield.viewer- Managers and service owners
- Cards, role grid and tier counts
- Flag a cell for review
Reviewers
x_blui2_dshield.reviewer- Role owners and access reviewers
- Names in Explorer, deciding ACLs
- Evaluate a user, work assigned reviews
Admins
x_blui2_dshield.admin- The team that runs the app
- Settings, tracked tables, routing and risk rules
- Security detections, approve explanations
What it won't claim
An access tool is only useful if you can trust it. These are the places it tells you it doesn't know.
See it on your own tables
We'll point it at your most sensitive tables, run the first analysis, and walk through the results with your platform and security leads.