AI-generated notes can contain sensitive customer context even when no recording is available. Audit who reads, changes, exports, and shares them without copying the note content into another unrestricted log.
Note auditing observes consequential access
An access audit records actions against a protected resource so authorised reviewers can investigate inappropriate use or operational disputes. For generated customer notes, useful events include view, edit, export, share, delete, and permission changes.
In a proposed event model, retain actor identity, resource reference, tenant, action, permission decision, time, and relevant request context. Protect the audit store from ordinary note editors and define who may inspect it.
The audit is not the access control itself. A system that logs unauthorised disclosure after returning the note has still failed. Enforce permission before delivery and use the audit to verify and investigate that boundary.
Investigate a fictional unexpected export
A manager finds that a customer note appeared in an external spreadsheet. The audit can show whether an authorised export occurred, who initiated it, and which record scope was requested. It should not require searching raw note text in application logs.
If a broad dashboard view loads many notes at once, decide whether that counts as individual resource access and how evidence is represented. A single page-view event may be insufficient to establish which content was delivered.
| Staff action | Audit evidence |
|---|---|
| Open permitted note | Actor, resource, and allowed decision |
| Attempt cross-tenant read | Denied request without content disclosure |
| Edit generated summary | Before/after version references and actor |
| Bulk export | Scope, permission, and export job reference |
| Share controlled link | Recipient policy and link lifecycle event |
Test the audit under ordinary staff roles and denied requests. Verify that logging failures are visible and do not silently remove evidence from the paths most likely to need review.
Make audits reviewable rather than merely large
Define suspicious patterns and an accountable reviewer. Examples can include unusual bulk exports or repeated denied resource access, but context matters. A legitimate queue migration can resemble anomalous volume unless planned activity is recorded.
Detailed access events increase storage and can themselves reveal staff and customer relationships. Minimise content, restrict access, and establish retention through the actual policy. Avoid treating the audit store as a second copy of every note.
This audit design is proposed. The HVAC case study documents authenticated staff workflows without claiming this exact audit feature. Read dashboard role design.
Generated-note audit FAQ
Are generated notes less sensitive than transcripts?
Not necessarily. They can preserve identifying or consequential information from the call.
Should note content be copied into each audit event?
Prefer controlled version references and minimal metadata unless a defined requirement justifies more.
Does an access log prove permission was correct?
No. Test the policy decision and actual content delivery as well as the existence of the log.