The idea
An audit trail should explain who performed a significant action, what changed and whether it succeeded. It is not the same as verbose application debugging. Useful audit events support accountability while avoiding unnecessary capture of sensitive payloads.
Design choice
Choose important event types such as permission changes and data exports. Protect the trail from casual editing and define who can read it. Include stable references rather than copying secrets or full documents into each event.
Worked example
An access change records the actor, target role, requested scope, time and outcome. The event references the approval record without reproducing its confidential attachments.
Before you ship
- Define high-value audit events
- Exclude secrets from event payloads
- Test access to the audit trail
Examples are illustrative. Adapt the checks to your own environment.