Audit activity
Review recorded changes and actions without overstating what the audit trail proves.
Recorded events
The application has an audit-log collection for selected actions. Records can include an organization, actor, role, action, target, timestamp, and optional before-and-after context. The audit view should be used to investigate recorded activity within the viewer's authorized organization.
Administration
Return to the wider administrative workflow.
Organization context
Understand how workspace identity affects access to records.
Integrity boundary
The audit model rejects updates and deletes through its normal Mongoose model operations, including resaving an existing document. That is an application-level append-only control. It is not a blockchain, cryptographic signature chain, external write-once store, or proof that a database administrator cannot alter records. This guide also does not claim that every action or failed access attempt is logged.
Correlate audit entries with the relevant record, user, organization, and operational logs. Escalate suspected incidents through the organization's approved response process; a single audit entry is not a complete forensic record.