> 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/update-a-team-s-role-on-an-account.md).

# Update a team's role on an account

This article describes how to update the role of other teams on your accounts.

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

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

As an account **Owner** or **Manager**, you can update a team's role on your account. The new role must be equal to or below your own, and as a **Manager**, you cannot change the role of a team that is already an **Owner** or **Manager**.

To update a team's role on an account using the Cerby web app, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Click the corresponding account card. The account details page is displayed.
3. Select the **Teams** tab.
4. Select the option from the **Cerby role** drop-down menu that corresponds to the new role to assign:

   * **Owner:** Teams can share accounts, manage access and account configuration, and view passwords through the user interface (UI) and API responses.
   * **Manager:** Teams can log in to the account and share it with other users and teams, but they can't manage the account configuration or remove access. Viewing passwords through the UI is restricted.
   * **Collaborator:** Teams can only view passwords through API responses for account login with Cerby; viewing passwords through the UI is restricted.

   A success message 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/update-a-team-s-role-on-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.