LMS Audit and Timeline Storage

Summary

Source-backed audit/timeline persistence, actor, and tenant-scope reference.

Audience

Engineering, QA, support, architecture, security, product, and governance reviewers.

Reference Content

Audit and timeline are separate persisted evidence objects rather than TenantEntity subclasses. Both have generated identifiers, numeric tenant scope, logical entity type/identifier, actor fallback, occurrence time, and optional serialized context. Timeline additionally carries entry type and description.

Both mappings define tenant-plus-occurrence indexes and the same global filter pattern as tenant domain objects. API reads order newest first and apply a bounded limit. Correlation is handled at request level but is not a dedicated mapped property on these evidence objects.

No retention, archival, immutability, redaction, tamper-evidence, export governance, or delete policy was found. Optional serialized details may contain business context; payloads are not reproduced here.

Source References

• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/training-service/Infrastructure/Persistence.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs

Related Articles

• LMS database documentation
• LMS technical documentation

See Also

• Schema reference
• Database testing guide

Keywords

• LMS database
• Training persistence
• Source-backed model

Revision Information

• Status: Draft
• Last reviewed: 2026-07-17
• Review cycle: Quarterly