Understand soft deletion and record retention

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Remove supported records without breaking historic operational links.

What this guide helps you do

Remove supported records without breaking historic operational links. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Go to the exact record.
2. Verify it is not needed for an active assignment or workflow.
3. Use Delete.
4. Verify the action.
5. Check it no longer appears in normal active lists while linked history remains intact.

Fields and options

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules and limits

• The controller accepts only supported entity names.
• Deletion is implemented as soft deletion for supported records.
• Do not delete a record merely to correct a status; use the workflow action instead.

Check it worked

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Errors and rejected actions

• Permission denied means the role lacks Delete.
• Unsupported entity or missing record is rejected.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Related guides