The Deleted Records page (Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/admin/deleted-records) gives platform administrators visibility into all soft-deleted records across the HR, Governance, Forms, and Housing modules, with the ability to restore or permanently delete each record.
Overview
The page is double-gated: the route requiresadmin.deleted_records.manage, and the component wraps its content in a RequirePermission for the same permission. Records are loaded via useDeletedRecords with optional entity-type filtering. The page is tabbed by module: All, HR, Governance, Forms, and Housing. Each tab shows a DeletedRecordsTable with the filtered soft-deleted records. Tab labels show a badge with the count of records in each module. The Restore and Permanent Delete actions open confirmation dialogs (RestoreRecordDialog, PermanentDeleteDialog) before executing the respective mutations.
Who it’s for
Requires permissionadmin.deleted_records.manage.
Before you start
- You must hold
admin.deleted_records.manage. - Confirm with your team before permanently deleting any record — this action cannot be undone.
Steps
Open Deleted Records
Navigate to
/admin/deleted-records. The All tab is active by default showing all soft-deleted records.Filter by module
Click a module tab (HR, Governance, Forms, Housing) to narrow the list to records from that module.
Restore a record
Locate the record in the table and click Restore. Confirm the action in the
RestoreRecordDialog dialog.Key concepts
Soft delete vs. permanent delete
Soft delete vs. permanent delete
Records soft-deleted in the platform have their
deleted_at timestamp set but remain in the database. This page exposes both the restore path (clear deleted_at) and permanent deletion (remove from the database entirely).Module tabs and entity configs
Module tabs and entity configs
Module-to-entity mapping is defined in
DELETED_ENTITY_CONFIGS. Each config entry specifies the database table and module key, which drives both the tab count badges and the record filtering.Related
Platform Foundation
Platform Foundation overview.
Governance & parity
Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/platform.tsx
- src/platform/admin/pages/DeletedRecordsPage.tsx
- src/platform/admin/hooks/useDeletedRecords.ts