Audit Log

An audit log is a baseline regulatory requirement for any platform processing personal data under GDPR, and is doubly important for Meander given that it handles health-adjacent information, next-of-kin data, and encrypted assignments containing sensitive personal details. Without a credible audit trail, organizations cannot satisfy accountability obligations or respond to data-subject requests with confidence. Beyond compliance, the audit log directly supports the source doc's promise that every Global Admin support-access session is logged in the org's audit trail. This is what makes time-bounded support access politically acceptable to tenants - they can verify after the fact exactly what Norse staff did during the window. It also enables incident investigation, dispute resolution, and internal governance reviews without manual log scraping.

Implementation uses the audit_logs table scoped by organization_id, with the Audit Service writing entries from across the platform via a small, stable API. Writes are append-only - entries are never updated or deleted by application code - to preserve evidentiary value. The Audit Log Page in the admin portal provides filtering by actor, resource type, action, and time range, plus pagination for large result sets. Hooks must be placed at every privileged action: user lifecycle changes, role assignments, feature-toggle flips, support-access grant/revoke, expense approvals, and authentication events emitted by the Authentication Module. The audit module must remain decoupled from the auth module's internals - it consumes events through a stable contract rather than reading auth tables directly.