> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/administration/security/removing-a-user.md).

# Removing a user

Before removing a user from your organization, check what accounts they had connected to avoid losing emails or access to shared channels.

## Do you need to take action?

**If the departing user never connected any accounts** - no personal email, no shared accounts - remove them immediately with no data loss.

**If the departing user connected a personal work email** (like `jessica@conferencebadge.com`), their emails will disappear from shared conversations once removed. See [Backup emails](/docs/administration/security/removing-a-user/backup-emails.md) to preserve them before proceeding.

**If the departing user connected shared accounts** - team inboxes (info@, support@), a WhatsApp number, SMS line, or social page - those accounts must be transferred to another user before removal. The path differs by account type: email accounts can be re-connected by the new owner, while WhatsApp, SMS, and social pages need a backend transfer by Missive support so message history is preserved. See [Transferring ownership](/docs/administration/security/removing-a-user/transferring-ownership.md).

If the departing user has both a personal email and shared accounts connected, handle both before removing them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://missiveapp.com/docs/administration/security/removing-a-user.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.