> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/security-governance/emergency-access/remove-users-emergency-access-assignments.md).

# Remove users' emergency access assignments

This article describes how to remove a user's Cerby Emergency Access assignment.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners** and **Super Admins**
* Supported using the Cerby web app
  {% endhint %}

As a workspace **Owner** or **Super Admin**, you can remove a user's emergency access assignment at any time.

## Remove users' emergency access assignments

To remove an assignment, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select **Workspace Configuration** from the left navigation drawer. The **Workspace Configuration** page is displayed.
3. Select the **Emergency Access** tab. The **Emergency Access** tab is displayed with your current list of assigned users.
4. Locate the assigned user in the list.
5. Click the **Remove** button for that user. A success message is displayed confirming that the assignment is removed and access is revoked.

{% hint style="danger" %}
**IMPORTANT:** Removing an assignment immediately revokes the user's registered security keys and ends any active emergency access session. This action cannot be undone. To use emergency access again, you must assign the user again and register a new security key.
{% endhint %}

{% hint style="warning" %}
If an assigned user is deactivated or deleted through your identity provider's SCIM integration, Cerby automatically removes their emergency access assignment. If an assigned user leaves through another method, use the steps above to remove their assignment manually. See [Explore Cerby Emergency Access](/setup-and-admin/security-governance/emergency-access/explore-emergency-access.md) for details on what automatic revocation does.
{% endhint %}

Now you are done.

## Related articles

**Setup guides:**

* [Explore Cerby Emergency Access](/setup-and-admin/security-governance/emergency-access/explore-emergency-access.md)
* [Assign users to emergency access](/setup-and-admin/security-governance/emergency-access/assign-users-to-emergency-access.md)
* [Terminate emergency access sessions](/setup-and-admin/security-governance/emergency-access/terminate-emergency-access-sessions.md)

**Troubleshooting:**

* [Troubleshooting: Emergency Access issues](https://help.cerby.com/tips-and-troubleshooting/troubleshooting/workspace-access/troubleshooting-emergency-access-issues)


---

# 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://help.cerby.com/setup-and-admin/security-governance/emergency-access/remove-users-emergency-access-assignments.md?ask=<question>&goal=<user_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.