# Delete Device

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


## Description

This step permanently deletes a device associated with a user. The next time the user accesses your application from this device, it will appear as new.

Only the Device entity is removed while linked device cryptographic keys and authenticators remain active. Since the Device is a logical record representing the endpoint in the system, removing it doesn't invalidate the cryptographic bindings or affect the authenticator's ability to function on the physical device by default.

You can optionally configure the step to also delete device-bound authenticators (mobile biometrics and PIN) linked to this device via `registering_device` and device cryptographic keys (unless associated with a different user).

Important
Device deletion is permanent. Deleting a device cannot be undone. To temporarily suspend a device, use the [Suspend Device](/guides/orchestration/journeys/suspend_device) step instead.

## 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. |
| **Device source** | Specifies a device. Defines whether to obtain the device ID from the journey context or specify it explicitly for this step. For more, see [Device context](/guides/orchestration/concepts/devices). |
| **Delete bound authenticators** | When enabled, also deletes device-bound authenticators (mobile biometrics and PIN) linked to this device. Disabled by default. |
| **Error output variable** | Name of the variable that stores any errors returned by the action |
| **Failure behavior** | Determines the behavior in case of failure, which either aborts the journey (default) or proceeds to a failure branch of the control flow. |


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).