# Suspend to Archive Movement

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="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2F648o25un2zNb8S71XchT%2Funknown.png?alt=media&#x26;token=97f50bb9-4f11-4ffe-ac84-3bf846c2e3ec" 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="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FaBPtWz8h5UuN2sVUDkFc%2Funknown.png?alt=media&#x26;token=572dc5c3-4c6d-4918-84ec-c90d35f6f4e6" 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="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FVKNxZ7ABrdjGuI3EsLW2%2Funknown.png?alt=media&#x26;token=55219a4f-69b2-4239-a32b-0f27150c0492" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FB2kDmBEt3vFdTqgvs4qZ%2Funknown.png?alt=media&#x26;token=8225a3bc-924b-4b31-bb45-4c6d809499ac" 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="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FV3W4UbuqF68iSXL2A6SX%2Funknown.png?alt=media&#x26;token=422e8132-0129-4292-92ca-0846ea5261aa" 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="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FHGG14XUjQ8sfrZdWoXYQ%2Funknown.png?alt=media&#x26;token=26b704da-9f68-41be-abea-c2a79c911198" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3609793515-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOkb5tnBpg4wioRhBnTB%2Fuploads%2FQHfuzHjUHI8wln9tWHjY%2Funknown.png?alt=media&#x26;token=5f06de57-1344-40a5-bcd4-187625ce0455" 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