# Remove User From App

div
div
Client SDK
div
Backend API
div
Mobile approve
div
SSO
div
Sub-journey
> Removes a user from the application


## Description

This step is used to remove a user from the application. It can be used in account removal flows, user privacy requests, or administrative user cleanup.

The user context for the step may be provided implicitly by the journey if the user is already authenticated; otherwise, a user identifier must be specified in the step configuration. The user can be located by any supported identifier (for example, email, phone number, username, external user ID, or a [custom identifier](/guides/user/manage_user_schema), if configured for B2C users in your tenant). If the user is found, the step deletes the user profile.

If the step is successfully completed, the journey continues. If it fails, the journey proceeds according to the configured failure behavior.

## Configuration

div
| Field | Description |
|  --- | --- |
| **User auth state** | Indicates if the user has authenticated in this journey. If the user is authenticated (default), the user context is provided implicitly by the journey. If not, a user identifier must be configured. |
| **Identifiers** | Only configured if the journey doesn't authenticate the user before invoking this step. Can be an external user ID, email, phone number, username, or a [custom identifier](/guides/user/manage_user_schema), if configured for B2C users in your tenant. |
| **Identifier value** | User identifier, specified as an expression. |
| **Error output variable** | Name of the variable that stores any errors returned by the step. |
| **Failure behavior** | Determines the behavior in case of failure: proceed to a failure branch of the control flow (default) or abort the journey. |


Journey event data
This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see [Additional data reporting](/guides/orchestration/getting-started/event_reporting).

## Example

Suppose a signed-in user requests account deletion. After confirming the request (for example, using a step that performs strong authentication), you can use **Remove User From App** to remove the user from the application.

If the step succeeds, you can proceed to a [Display information](/guides/orchestration/journeys/display_information) step to confirm the deletion.