Skip to content

Give an external auditor time-boxed, read-only access

An external auditor gets two things: the External Auditor role, which is read-only everywhere, and an auditor grant, which time-boxes that role: without an active grant the role opens nothing (see No standing access for how this is being switched on). Grants are managed on Security & Risk → Compliance → Auditor access (the Auditor Access Grants page).

Who can do what

Task Roles
Create the auditor’s user account Identity Admin, Tenant Owner, Super Admin
Assign the External Auditor role Super Admin
Issue, list and revoke auditor grants Compliance Officer, CISO, Super Admin

Identity Admin and Tenant Owner cannot issue grants. An auditor cannot issue a grant to themselves.

1. Create the auditor’s account

There is no invitation tied to a grant; the auditor needs a normal user account first.

  1. Identity & Access → Directory → New Identity, and fill in the auditor’s details. A temporary password is shown once; send it to the auditor through a channel you trust.
  2. Open the user, click Manage Roles and, in Manage Platform Roles, give them External Auditor. Only a Super Admin can assign this role.

The account must be Active to receive a grant.

2. Issue a grant

  1. On Auditor Access Grants, click Issue grant.
  2. External auditor: choose the auditor (active External Auditors in your organisation are listed).
  3. Scopes: tick at least one.
Scope What it unlocks
Audit View The Auditor Portal summary
Report Export Evidence-pack history, generating evidence packs, and the SOC 2 evidence pack
Compliance Report The AI agent inventory report
Audit Export Decision-trace exports (JSON, PDF, bundle); evidence packs need it alongside Report Export

For a typical engagement tick all four.

  1. Access window: 1 hour, 8 hours, 24 hours (default), 7 days, 30 days or 90 days. 90 days is the maximum.
  2. Reason (optional): for example the engagement name.
  3. Click Issue grant. The grant appears with status Active.

There is no edit: to extend or change scopes, issue a new grant. Nobody is notified when a grant is issued, so tell the auditor yourself.

3. What the auditor sees

The auditor works from Security & Risk → Compliance → Auditor portal: open SoD violations, active certifications, recent identity and audit events, framework posture, and links to Evidence Packs, the Compliance Hub, the Audit Log, SoD Violations and Certifications. The portal is view-only.

The External Auditor role is read-only throughout the product. When the engagement ends, revoke the grant (or let it expire) and remove the External Auditor role or deactivate the account, so the account holds nothing it no longer needs.

No standing access

An auditor acts only inside an active grant, on every page and API the role can open, checked on the server:

  • No active grant: the External Auditor role is taken off the auditor’s session within a few minutes of the grant ending (revocation or expiry), and off Iris in Slack on their next message. They keep only what any signed-in user has, plus any other role you gave them.
  • Outside the grant’s scopes: an export the grant does not cover is refused on that request. The auditor sees Active auditor grant required — ask a compliance officer to issue a time-boxed grant. or Your auditor grant does not include ….

This is being switched on in two phases. In the first (warn) phase nothing is taken away; each time it would have been, AUDITOR_GRANT_ENFORCEMENT is recorded with an outcome starting would_. Review those events, then enforcement is switched on and the outcomes read auditor_role_suspended or denied. The Auditor Portal summary, evidence-pack and SOC 2 downloads, and the AI inventory report already refuse an auditor without the right grant in both phases.

4. Revoke or let it expire

  • Revoke: click Revoke on an Active row. Exports stop on the auditor’s next request, and the role’s other views within a few minutes. There is no confirmation step, and a revoked grant cannot be reinstated.
  • Expiry: the grant stops working the moment its window ends and shows Expired. A daily job records the expiry and notifies the person who issued it (not the auditor). The auditor’s account stays active.

5. Check the audit trail

Event When
AUDITOR_GRANT_ISSUED Grant issued (auditor, scopes, expiry and reason)
AUDITOR_GRANT_REVOKED Grant revoked
AUDITOR_GRANT_EXPIRED Expiry recorded by the daily job
AUDITOR_PORTAL_VIEWED Auditor opened the portal (at most once every 5 minutes)
EVIDENCE_PACK_GENERATED An evidence pack was generated
AUDITOR_GRANT_ENFORCEMENT The grant check refused (or, in the warn phase, would have refused) the auditor, or their grant became active again

Filter for these in the audit trail.

© AtmanID · Privacy