The job of this console
Publish retention for each family, place a hold when legal asks, and understand what purge will touch before it runs. Coordinate with jobs that actually execute purge.
Retention schedules, purge windows, and compliance holds for operational records.
Scroll to Flowcharts. Scenario: Set a retention schedule.
Keep, hold, purge
Data retention is the schedule of keep windows, purge eligibility, and compliance holds for operational records. A hold freezes purge; it does not freeze the live business record from legitimate edits.
/admin/data-retention
Org flag dataRetentionEnabled
HR Admin · Org Admin
Publish retention for each family, place a hold when legal asks, and understand what purge will touch before it runs. Coordinate with jobs that actually execute purge.
Administrators with compliance duty. Employees never set their own retention. Developers do not add ad-hoc deletes that bypass these windows.
Open a family, set the window, save, place or lift a hold, then confirm scheduled jobs. Spot-check audit after a purge window elapses.
A litigation hold. GDPR-style deletion request that still must respect a hold. After a new module starts writing records with no schedule. Year-end policy review.
Pick an entity family, set the window, then save.
flowchart TD
A[Open Data retention] --> B[Select a schedule]
B --> C[Set window / hold]
C --> D[Save]
D --> E[Jobs honor schedule]
E --> F[Audit the change]
Retention is policy over existing source tables. It does not introduce a parallel archive of business truth.