Audit Log Store
Component Detail
Data Layer
medium complexity
backend
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Append-only persistence layer for audit events with indexes optimized for tenant-scoped queries by actor, action type, target, and timestamp. Guarantees immutability of recorded entries.
audit-log-store
Sources & reasoning
Audit Log is explicitly required by line 193 to back the time-bounded Global Admin support-access mechanism, and is taxonomy-mandated at line 380. GDPR accountability for the sensitive data Meander handles makes it MVP-critical, aligning with admin-security being part of the Admin Web Portal MVP scope (lines 244-247).
-
docs/source/likeperson.md · line 380Audit Log | Audit Log Page [ui] | Audit Service [service] | Audit Log Store [data]
-
docs/source/likeperson.md · line 193Every support-access session is logged in the org's audit trail.
Responsibilities
- Persist audit event records in append-only storage
- Maintain indexes for efficient filtering by org, actor, action type, and time
- Reject any update or delete operations on existing entries
- Support paginated retrieval ordered by timestamp
- Enforce tenant isolation at the storage query layer
Interfaces
insertEvent(event): AuditEventId
findEvents(orgId, filters, pagination): AuditEventPage
findEventById(orgId, eventId): AuditEvent
Related Data Entities (1)
Data entities managed by this component