Helpdesk Audit and Timeline Storage

Audience

Developers, database engineers, security, QA and support.

Summary

TicketAuditLog and TicketTimeline are separate activity entities rather than TenantEntity subclasses.

Reference Content

Both carry explicit tenant identity and occurred time, tenant/time indexes and global tenant filters with super-administrator bypass. Audit stores entity type/identity, action, actor and optional JSON details. Timeline stores entity type/identity, entry type, actor, description and optional JSON metadata.

Activity helpers default a missing actor to system and serialize supplied details. No database relationship links activity rows to canonical entities, and no immutability or retention mechanism is configured.

Requires confirmation

Audit immutability, actor trust, retention, tamper evidence, redaction and privileged query authorization require confirmation.

Source References

• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Audit storage, timeline storage, JSON metadata, tenant filter.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20