> 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-team-access-to-an-account.md).

# Remove team access to an account

This article describes how to remove team access to an account.

{% 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 team access to your accounts.

To remove team access to an account, you must complete the following steps using the Cerby web app:

1. Log in to your corresponding [Cerby](https://app.cerby.com/) workspace.
2. Click the **Settings** (<img src="https://2432765489-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5ttyhSeCwMoE7UPFgC6%2Fuploads%2Fgit-blob-26551c02fe8069bd79d74e8c7d238d9a68d75555%2Funnamed_51.png?alt=media" alt="" data-size="line">) icon of the corresponding account card. The account details page is displayed with the **Settings** tab activated.
3. Activate the **Teams** tab. The **Teams** section is displayed with a table of teams who have shared access to the account.
4. Click the **More options** (...) icon of the corresponding team. A drop-down list is displayed.
5. Select the **Remove team** option. The **Remove access?** dialog box is displayed.
6. Click the **Remove access** button. The dialog box closes, and a success message box is displayed.

Now you are done.


---

# 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-team-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.
