Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Scoped Auditor Access: How Room-Only Grants Work
Short answer
A scoped grant is the access an auditor receives when you accept them for an engagement: read access to that one evidence room, created by the acceptance itself, recorded with the match, visible in the room's grants and access log, and revocable at any time. The auditor cannot see your other rooms or your account. Scoping is what lets you file complete, unredacted evidence — the auditor gets everything the audit needs and nothing it does not.
What is a scoped grant?
A scoped grant is a room-level access right on AI Audit Exchange, created when an auditee accepts an auditor for an engagement. It gives that auditor read access to that room only — its artifacts, manifest and question thread. The room page lists its grants with the auditor's firm name, and every access is recorded in the room's access log; a grant can be revoked, which ends the auditor's access to the room.
Access created by acceptance, not by sharing
In weaker workflows, access is something you hand over: a password, a shared folder, an email full of attachments. Each handover is unrecorded, unbounded and hard to take back. The Exchange inverts that: access is a consequence of a recorded event — your acceptance of an auditor for a specific engagement. Before acceptance, the auditor has nothing. At acceptance, the grant exists, scoped to the room, attached to the match. After the engagement, revocation ends it just as cleanly. The chain from brief to response to acceptance to grant is one record, which is what makes the question 'who could see this evidence, and when?' answerable at all.
Read access to one room: the exact boundary
The grant's boundary has three edges, each deliberate. Room edge: this room only — a second room, even for the same client and period family, requires its own engagement and grant. Action edge: read access — the auditor examines artifacts, works the manifest and raises questions; they do not edit your evidence, which is immutable from intake in any case. Account edge: nothing outside the room — no billing, no other engagements, no profile beyond what the room's work needs. When an auditor works several of your rooms, they hold several grants, each visible separately on its room.
Visibility: grants and the access log
A control you cannot inspect is a control you are trusting blindly, so the room shows its own access state. The room page lists its grants alongside the auditor's firm, and the room carries an access log of who accessed it. Review both at three moments: at acceptance, to confirm the grant is exactly the one you intended; mid-engagement, as a routine check that access matches the work; and at close-out, when grants are ended or deliberately renewed. That review habit is cheap — minutes — and it converts access control from a setup task into a maintained fact.
Why scoping changes what you can file
The quiet benefit of scoping is completeness. Teams sharing evidence through open channels self-censor: the sensitive artifact is left out 'for now', and the auditor's picture develops holes exactly where the sensitivity was — which is usually where the examination matters most. A room-only, read-only, revocable, logged grant removes the reason to censor. File the complete set, as it was produced, sealed at intake. The auditor sees everything for this engagement and nothing beyond it; your other periods, clients and matters stay exactly as private as they were. Completeness and confidentiality stop trading against each other.
Revocation and succession
Grants end two ways: deliberately, by revocation, or well — there is only the deliberate way, and that is the design. When an engagement concludes, revoke. When an auditor must be replaced mid-engagement, revoke their grant and accept the successor on the same room; the evidence, manifest and question history persist, so the successor inherits context instead of restarting discovery. Revocation ends access to the room; it does not delete the record of the match or the work done under it. The step-by-step is in how to revoke auditor access and the handover pattern in handing over to a new auditor.
Scoping as an independence control
Scoping protects the auditor as much as the auditee. An examiner who can wander a client's whole account carries knowledge they cannot un-know into every judgement; an examiner bounded to one room's record can honestly say their findings rest on that record. Regulators and courts think about independence exactly this way — as boundaries maintained, not intentions professed. When you describe your audit arrangements, the scoped grant is the sentence that does the work: access created by acceptance, bounded to one room, read-only, logged, revocable. Structure, again, beats assurance.
Five actions to take
- Grant access only through acceptance — never share credentials, folders or evidence outside the room.
- Confirm at acceptance that the grant names this room and this auditor, and nothing more.
- Review the room's grants and access log at acceptance, mid-engagement and close-out.
- File complete evidence under the protection of the scope — do not self-censor the set.
- Revoke at close-out or on any change of auditor, and re-grant deliberately to a successor.
Worked example
A fictional home-services platform, Desert Rose Home Systems, runs two rooms: a CPPA room for 2028 and an SB 1119 rehearsal room for 2027. It accepts one auditor for the CPPA engagement. The grant list on the CPPA room shows exactly one grant, to that auditor's firm; the rehearsal room shows none, and the auditor confirms he cannot see it — the boundary is tested in the first week, politely, by both sides.
Mid-engagement the access log shows the auditor's reads tracking his sampling plan: manifest first, then 16 artifacts across three sessions. At close-out the grant is revoked in the same sitting as the manifest export. When the next cycle's auditor is accepted a year later, she receives her own grant and can see, in the room, the record of the prior engagement — without ever having had access before her acceptance.
Frequently asked questions
What exactly can a granted auditor do in the room?
Read: examine artifacts, work from the manifest, verify hashes, and raise questions in the room's thread. They cannot edit evidence — artifacts are immutable from intake — and they have no access beyond the room.
Can one auditor hold grants on several rooms?
Yes, one grant per engagement. An auditor serving several of your rooms, or several clients, holds a separate scoped grant for each room, each independently revocable.
Is the auditor's access logged?
Yes. The room keeps an access log, and the room page lists its active grants with the auditor's firm name, so access is inspectable at any time.
Does revoking a grant delete the audit record?
No. Revocation ends access. The room, its evidence, the match record, questions and answers all persist under the room's retention setting.
Why not just give the auditor an account login?
Because a login is unbounded and unrecorded. A scoped grant is created by a recorded acceptance, bounded to one room, read-only, logged and revocable — every property an audit's access control should have.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Write an AI Audit Engagement Brief That Gets Good Responses · Next: How to Revoke an Auditor's Access to an Evidence Room
SB 1119 vs CPPA Audits: What Actually Differs · When Are California AI Audits Due? The 2028–2029 Dates · Running a 10-Year Retention Programme for AI Audit Records