> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-administration/user-management/remove-or-suspend-a-user.md).
# Removing or Suspending Users
Org Administrators can **suspend** (temporarily disable) or **delete** (permanently remove) users when team membership changes.
Suspension preserves the account record so you can reactivate it later; deletion erases the account and audit trail forever.
> **Tip:** Always suspend first if you think the user might return—reactivation is one click, while deletion requires recreating the account from scratch.
***
### Suspend or Delete a User
1. Sign in with an **administrator** account.
2. Navigate to **Admin › Users**.
3. Locate the user you want to modify.
4. **Delete User** – click the trash-can icon to erase the account permanently.
5. **Suspend / Activate** – click **Activate/De-activate** to toggle the account’s status.
6. Confirm the action by clicking **OK** in the dialog.
***
### What Happens Next?
| Action | Result | Can Be Reversed? |
| ----------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| **Suspend** | User cannot log in; data and permissions remain intact. | **Yes** – click **Activate** to restore access. |
| **Delete** | User account is removed from ARM; historical records remain in audit logs but cannot be reassigned. | **No** – must create a new account if needed again. |
***
### Best Practices
* **Suspend first** if unsure—reactivation is easier than re-creating roles, labels, and permissions.
* **Reassign approvals** or scheduled tasks before deleting a user to avoid orphaned work.
* Periodically review **Admin › Users** for suspended accounts you can delete to stay within license limits.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-administration/user-management/remove-or-suspend-a-user.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
