> 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/partners/host-guest/share-an-account-via-a-host-guest-partnership.md).
# Share an account via a host-guest partnership
This article describes how to share access to your accounts with a guest workspace via a host-guest partnership.
{% hint style="info" %}
**Who can use this feature?**
* **Partnership Owners**
* Available to Cerby Automate
* Only supported using the Cerby web app
{% endhint %}
As a **Partnership Owner** from the host workspace, you can share access to your accounts with a guest workspace via a host-guest partnership.
By default, the only user in the guest workspace who receives shared access to your accounts is the guest workspace **Admin**, and you can assign them the **Collaborator** or **Manager** role. With the **Manager** role, they can request access to these accounts for other guest workspace members. For more information, read the article [Request access to an account shared via a host-guest partnership](/cerby-web-app/partners/host-guest/request-access-to-an-account-shared-via-a-host-guest-partnership.md).
{% hint style="danger" %}
**IMPORTANT:** You can only share via a host-guest partnership the accounts to which you have the **Owner** role.
{% endhint %}
To share an account via a host-guest partnership, you must complete the following steps:
1. Log in to your corresponding [Cerby](https://app.cerby.com/) workspace.
2. Select the **Partners** option from the left navigation drawer. The **Partners** page is displayed.
3. Select your partner from the list in the **Your partners** section. The partner details are displayed on the main panel.
4. Click the **Share accounts** button. The **Share accounts** wizard is displayed on the **Select Accounts and Roles** page with a list of accounts, as shown in **Figure 1**.
Figure 1. Select Accounts and Roles page of the Share accounts wizard
5. Select the accounts you want to share from the list in the **Accounts** section.
6. Select the role to assign on the accounts:
7. **Collaborator:** With this role, guest workspace members can only log in to the shared accounts.
8. **Manager:** With this role, guest workspace members can log in to the shared accounts and request access to these accounts for other members.
**NOTE:** By selecting the **Manager** option, this role is assigned only to the guest workspace **Admin**. Then, they can request access to accounts for other guest workspace members. For more information, read the article [Request access to an account shared via a host-guest partnership](/cerby-web-app/partners/host-guest/request-access-to-an-account-shared-via-a-host-guest-partnership.md).
7. Click the **Finish** button. The wizard closes, and a success message box is displayed.
---
# 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/partners/host-guest/share-an-account-via-a-host-guest-partnership.md?ask=&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.
