# Remove user from entity confirmation modal

When an admin removes a user from an entity, a confirmation modal now appears showing which other entities the user belongs to. This replaces the previous basic browser confirmation dialog that provided no context about the user's other memberships.

## Problem

Previously, removing a user from an entity (or deleting an individual registration) showed only a plain browser confirm with no additional context. Admins had no way of knowing whether the user belonged to other entities, or whether this was their only one. This made it difficult to understand the impact of the action.

## How it works

* When an admin clicks "Remove" on a user within an entity, or "Delete" on an individual registration, a modal dialog appears instead of a plain browser confirm.
* The modal title shows the user's name and the entity they will be removed from.
* If the user belongs to other entities, the modal lists those entities with links so the admin can review them before confirming.
* If the user is not part of any other entities, a warning is displayed alerting the admin that the user will no longer belong to any entity after removal. The user account itself is preserved and can be added to another entity in the future.
* The admin can confirm the removal or cancel.

## Where it appears

* **Applicants index page (multi-user entities)**: The "Remove from \[type]" option appears in the dropdown menu for nested user rows, replacing the "Delete User" action.
* **Applicants index page (individual entities)**: The "Delete \[type]" dropdown option now opens the confirmation modal instead of a plain browser confirm.
* **Entity Users tab**: The existing "Remove" button now triggers the confirmation modal instead of a basic browser confirm.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tahua.io/product-news/2026/april/remove_user_from_entity_confirmation_modal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.