Removing a participant from active work depends on whether their historical records must be preserved. Equip supports deletion only when the person has no associated records that must be kept. Otherwise, use discharge/inactivation workflows or request support review.
đ How It Works
If a person can be deleted and you have permission, the profile shows a delete option.
If the person has associated records that must be preserved, Equip shows Request Deletion instead of allowing direct deletion.
Discharging or inactivating keeps the personâs historical information while removing them from active workflows as appropriate.
Deletion is permanent and removes associated data when allowed.
â Benefits
Protects records that must remain available for reporting, history, authorizations, forms, goals, documents, or compliance workflows.
Helps teams avoid deleting someone who should instead be marked inactive or discharged.
Clarifies why the delete button may not be available.
đĄ Best Practices
Use direct deletion only for true duplicates or test records with no required history.
Use discharge or inactivation when the participant is no longer active but history should remain available.
Use Request Deletion when Equip blocks deletion because preserved records exist.
Do not delete a participant only to remove them from active lists; use the proper inactive/discharge workflow instead.
â FAQs
Why do I see Request Deletion instead of Delete?
The person has associated records that must be preserved, so Equip blocks direct deletion and routes the request to support.
When should I discharge or inactivate someone?
Use discharge or inactivation when the person is no longer active but their historical records should remain available.
Can deleted participant data be recovered?
Deletion is permanent. Only delete when you are sure the record does not need to be preserved.
Related Articles
Participant Management