Summary
As an organizer, I want all changes logged in an audit trail, so that I can track who changed what and when
Blocked by: story-001-multi-organization-support
Acceptance Criteria
1. Logging
- Automatic Logging: All significant actions (event changes, order modifications, team changes, settings changes) are automatically logged with actor, timestamp, affected entity, and description.
- System Actions: System-triggered actions (e.g., automatic reservation expiration, scheduled tasks) are also logged.
2. Viewing
- Browse Logs: Organizers can browse the audit log filtered by event, entity type, time range, or actor. Logs are scoped to the organization.
Test Plan
Tier 1 — Acceptance Tests
- AC1: User actions are logged with actor, timestamp, entity, and description
- AC2: System actions are logged with "System" as actor
- AC3: Browse and filter audit logs by event, entity type, time range, or actor
Tier 2 — Edge Cases
- Audit log entries persist for deleted entities
- Distinguish system actor vs user actor in filters
- Filter with no results shows empty state message
- Audit log immutability (no edit or delete)
📄 Full spec: spec/elixir-phoenix-migration/10-product/stories/story-032-audit-logging.md
Summary
As an organizer, I want all changes logged in an audit trail, so that I can track who changed what and when
Blocked by: story-001-multi-organization-support
Acceptance Criteria
1. Logging
2. Viewing
Test Plan
Tier 1 — Acceptance Tests
Tier 2 — Edge Cases
📄 Full spec:
spec/elixir-phoenix-migration/10-product/stories/story-032-audit-logging.md