Audit Log
Feature Detail
Description
The Audit Log feature records a tamper-evident, chronological trail of all significant actions performed within the Meander platform — including user logins, data modifications, role changes, export operations, and administrative actions. Each log entry captures who performed the action, what was changed, when it occurred, and from which context (organization, IP, device). The log is queryable and filterable by date range, user, action type, and organization, supporting both operational review and compliance auditing.
User Flow
Analysis
Audit logging is a non-negotiable compliance requirement for organizations handling personal data under GDPR and for recipients of Bufdir public funding, who are subject to inspection and accountability obligations. Without an audit log, Meander cannot credibly offer data processing agreements (DPAs) to customer organizations or pass due-diligence reviews by their legal and IT departments. Beyond compliance, the audit log provides critical forensic capability: when a dispute arises over who approved an expense, deleted a contact record, or changed a user's role, the log is the authoritative source of truth. This protects both Norse Digital Products and its customers from liability and reputational risk.
All write operations across the API layer emit audit events via a centralized AuditLogService that inserts records into the audit_logs table (users, organizations foreign keys) within the same database transaction as the business operation — ensuring no action succeeds without a corresponding log entry. Log entries are append-only; no update or delete operations are permitted on this table at the application layer (enforced by the absence of DELETE/UPDATE routes and a database-level policy). The admin portal provides a paginated, filterable Audit Log Page using server-side rendering with cursor-based pagination for performance on large datasets. Log export (CSV/JSON) is available for Org Admins scoped to their organization and for Global Admins across all orgs. Log retention policy (e.g., 24 months) is configurable per organization.
Components (112)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.