> 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/share-an-account.md).

# Share an account

This article describes how to share an account with other workspace users and teams.

{% 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. For the Cerby mobile app, read the article [Share an account using the Cerby mobile app](https://help.cerby.com/cerby-mobile-app/accounts/managing-access-to-your-accounts/share-an-account)
  {% endhint %}

To share an account with other workspace users and teams 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 **Share account** icon that appears when hovering over the corresponding account card. A drop-down list is displayed.
3. Select the **Share item** option. The **Share Access** dialog box is displayed.\
   **TIP:** You can also access the **Share Access** dialog box by completing the following steps:
4. Click the corresponding account card. The account details page is displayed.
5. Click the **Share** button located at the top right. A drop-down list is displayed.
6. Select the **Share item** option. The **Share Access** dialog box is displayed.
7. Enter a user's or team's name in the search bar. The users or teams that match the name are displayed on a list automatically.
8. Select the corresponding user or team from the list. The user or team is listed in the **Members and Teams** section.
9. Repeat steps 4 and 5 to select multiple users or teams.
10. Select the corresponding user or team role on the account from the **Role** drop-down list:

    * **Owner:** Users and teams can share accounts, manage access and account configuration, and view passwords through the user interface (UI) and API responses.
    * **Collaborator:** Users and teams can only view passwords through API responses for account login with Cerby; viewing passwords through the UI is restricted.

    **NOTE:** When you select a user with the **Login-only** role, they are listed in the **Login-Only** section. You can only select the **Collaborator** role for them.
11. Customize the message to send when you share the collection in the **Message** field.
12. Click the **Confirm** button. The dialog box closes, and a success message box is displayed.

Now you are done.

{% hint style="info" %}
**NOTE:** For some apps, Cerby automatically creates or links the recipient's own account on that app in the background after you share access. No additional action is needed from you or the person you shared with.
{% endhint %}


---

# 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/share-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.