Skip to main content

Exit Approval and History Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

ExitRequestAuditLog records compatibility exit actions separately from the request. It provides action history but is not a proven immutable compliance ledger.

History relationship​

The source model uses identifiers for request, subject and actor. Public documentation does not expose identifier formats or stored values.

Recorded operations​

Source-backed controller paths add history for request creation, approval, rejection, rollback and access revocation. Timestamps and actor metadata support an operational chronology.

Limitations​

  • Database-enforced immutability was not found.
  • Retention, legal hold and redaction policy were not found.
  • History is local to compatibility HR Operations and is not unified with Recruitment, Employee, Asset or Notification audit stores.
  • A history row proves an application write, not that downstream systems completed their work.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • Models/ExitRequest.cs
  • Models/ExitRequestAuditLog.cs
  • Controllers/HrOperationsController.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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