> For the complete documentation index, see [llms.txt](https://help.cymmetri.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cymmetri.io/identity-hub/managing-users-and-groups/delete-users.md).

# Delete Users

In user lifecycle management, the transition of a user's status from Suspended to Archived initiates a critical de-provisioning sequence. This process is designed to ensure that all user entitlements are permanently revoked from target applications, a final action controlled by a configurable flag.

**User Creation and Initial Status**: The process begins with a user being created in the system, with their initial status set to Active.

<figure><img src="/files/9BdT4MbkdyM0aQI3rG2e" alt=""><figcaption></figcaption></figure>

**Suspension Initiation**: An administrator initiates the suspension of a user by selecting the "Delete User" option. This action changes the user's status to Suspended, thereby revoking their login privileges while retaining their account information.

<figure><img src="/files/bjVlYTWPngukUwUN3rfs" alt=""><figcaption></figcaption></figure>

**Movement to Suspended List**: The user's profile is then moved to the Suspended Users list, allowing administrators to differentiate between active and temporarily disabled accounts.

<figure><img src="/files/Q5txB7e9cgfIbzkFe4HL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/L7WFHiRZhridukMu9yl8" alt=""><figcaption></figcaption></figure>

**Log Verification**: The administrator can verify this status change by reviewing the system logs. The logs will record the status transition from "ACTIVE" to "DELETE." This log entry also provides a clear record of the user's application status, indicating if any associated applications were also de-provisioned at this stage.

<figure><img src="/files/WXR1zDeo1jrkTJXBwzc4" alt=""><figcaption></figcaption></figure>

**Forced Deletion**: Should the administrator require immediate, permanent de-provisioning, the "FORCE DELETE" option can be used. This action bypasses the standard suspended state and triggers the final de-provisioning call immediately, ensuring that all entitlements are permanently removed.

<figure><img src="/files/VGBgKhzlsE293VwNTc39" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/AIcJpGwOLmnCN0BofsZy" alt=""><figcaption></figcaption></figure>

**Final Validation**: To confirm the user's complete de-provisioning, the administrator can once again validate the status in the system logs. The logs will confirm the final deletion and provide a complete audit trail of the user's lifecycle, from creation to final de-provisioning.