> 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/collections/managing-access-to-your-collections/update-a-team-s-role-in-a-collection.md).

# Update a team's role in a collection

This article describes how to update a team’s role in a collection.

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

* Workspace **Owners**, **Super Admins**, **Admins**, **Users**, and **Guest Users**
* Collection **Owners**
* Supported using the Cerby web app and mobile app. For the mobile app instructions, read the article [Update a team’s role on a collection using the Cerby mobile app](https://help.cerby.com/cerby-mobile-app/collections/managing-access-to-your-collections/update-a-team-s-role-on-a-collection)
  {% endhint %}

As a collection **Owner**, you can update a team’s role in a collection. This action also updates team members' roles for the items in the collection.

To update a team’s role in a collection, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select the **Collections** option from the left menu. The **Collections** page is displayed.
3. Click the **Settings** icon of the corresponding collection card. The collection details page is displayed with the **General** tab activated.
4. Activate the **Teams** tab. The **Teams** table is displayed with the list of teams that have shared access to the collection.
5. Select the option from the **Cerby role** drop-down menu that corresponds to the new role for the team:
   * **Owner:** Team members can share access to the collection, manage the item settings, and perform the actions of a **Collaborator**.
   * **Collaborator:** Team members can only log in to accounts, view secrets, and download the secret attachments.

A success message box is displayed.

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/collections/managing-access-to-your-collections/update-a-team-s-role-in-a-collection.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.