Auditor
You read everything and change nothing: who can access what, why, and what a change touches.
The auditor reads everything and changes nothing. The auditor archetype carries every read key in the permission glossary and nothing else; when a new resource is added to the product, its read key is automatically part of this role too.
The same role can be assigned on the platform or in a tenant; the assignment's scope keeps you there. A tenant auditor reads everything in their own tenant, and nothing above it.
You use the Access review, tenant access, Policies and Change impact screens most. None of these screens changes anything; they explain the source and the risk of every assignment you see.
Start here
- Read why the auditor archetype carries only read keys, and why that covers every resource.
- On the Access review screen, pick a scope and see who holds which role and where the assignment comes from.
- On the tenant access screen, follow which role and which scope each key in a tenant comes from.
- On the Policies screen, read the floors and the permission rules; understand where a refusal comes from.
- On the Change impact screen, see what a capability version change would touch.