> 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/cerby-web-app/accounts/managing-access-to-your-accounts/remove-a-user-s-access-to-an-account.md).

# Remove a user's access to an account

This article describes how to remove a user’s access to an account granted through an account, team, collection, or business hub.

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

* Workspace **Owners**, **Super** **Admins**, **Admins**, **Users**, and **Guest Users**
* Account **Owners**
* Supported using the Cerby web app and mobile app
  {% endhint %}

As an account **Owner**, you can remove a user directly from the account if their access was granted through the account itself. However, if the access was granted through a team, collection, or business hub, you must be the **Owner** of those items to remove the user’s access to the account.

To remove a user’s access to an account, you must follow the next steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Click the corresponding account card. The account details page is displayed with the **General** tab activated.
3. Activate the **Users** tab. The **User Overview** section is displayed with a table of users who have shared access to the account.
   * If the user has direct access to the account:
     1. Click the **More options** (...) icon next to the user’s details. A menu is displayed.
     2. Select the **Remove from account** option. The **Remove access** dialog box is displayed.
     3. Click the **Remove access** button. A success message box is displayed, and the user is removed from the account.
   * Access through other items:
     1. Click the **More options** (...) icon next to the user’s details. A menu is displayed.
     2. Click the **Go to teams**, **Go to collections**, or **Go to business hubs** option.
        * If you have the **Owner** role, the team, collection, or business hub details page is displayed. You can remove the user’s access to the account directly from that page.
        * If you don’t have the **Owner** role, an error page is displayed.

Now you are done.

<figure><img src="https://2432765489-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5ttyhSeCwMoE7UPFgC6%2Fuploads%2Fgit-blob-00612b16109bbacedc24946d7a41c1b254f3b92e%2FAD_4nXfYQQcBG4Wj_bYtBJoBe8Vg0x4Xc5KZt8Y_gqUaIIYXoMevHpc5k94x0Lo7RlihDb2fQ8BbieRV7hM35se-4ITS4VH8Ss2-ALMoJthKI3EpPo49OzlXxpOFSINywpiTsMmSS-dVFg.png?alt=media" alt="A blue light on a black backgroundDescription automatically generated"><figcaption></figcaption></figure>


---

# 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/cerby-web-app/accounts/managing-access-to-your-accounts/remove-a-user-s-access-to-an-account.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.
