Understand retention and deletion boundaries
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that snapshots and policies support governance review but do not automatically delete employee data.
Where to go Admin Area → Human Resources → Retention & Archives
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
Before you start
- Access to Admin Area → Human Resources → Retention & Archives.
- The Human Resource Management: Settings capability or administrator access.
- The correct employee, record, period or evidence reference before making a change.
Follow these steps
- Go to Admin Area → Human Resources → Retention & Archives.
- Verify the employee, period, queue, batch, register or record reference shown on the page.
- Use the visible search, filter, tab, status or register control named by this guide.
- Go to the matching record and review its current status, warnings, dates and linked evidence before taking another action.
- Use only the action visible for your capability and the record’s current state.
- Reopen the same record or register and verify the result and audit/activity entry.
Fields and options
Governance areaSelect the implemented HR data area covered by the policy, snapshot or review.
Review frequencyQuarterly, six-monthly and annual review frequencies are available for policies.
Archive jobA generated snapshot is a protected governance export, not an automatic deletion operation.
Decision and reasonReviews and void actions require a clear status or reason for the audit trail.
What the module checks
- The menu and data shown are permission-aware.
- Read-only dashboards and health pages do not repair or alter data unless a separate repair action is deliberately used.
- Counts and status labels come from module-owned tables and should be verified against the underlying register.
- Protected payroll, identity, bank, right-to-work and access data may be hidden without the appropriate capability.
What happens next
The result remains available from Admin Area → Human Resources → Retention & Archives. Confirm its identifier, status, linked employee or period, dates and audit/activity record before relying on it operationally.
Troubleshooting
- If the menu or action is missing, confirm the module is active and your HRM capability is assigned.
- If validation fails, correct the exact field named in the message; do not bypass the rule in another workspace.
- If a downstream email or automation does not run, check the related delivery/audit log and the host application cron or mail configuration.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: retention governanceaudit
Related guides
Was this guide useful?Your response is stored only in this browser.