> 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/log-in-to-accounts-shared-via-a-host-guest-partnership.md).
# Log in to accounts shared via a host-guest partnership
This article describes how to log in to the accounts you shared with a guest workspace via a host-guest partnership.
{% hint style="info" %}
**Who can use this feature?**
* Workspace **Users**
* Available to Cerby Automate
* Supported using the Cerby web app, browser extension, and mobile app
{% endhint %}
All guest workspace members with shared access to accounts from the host workspace can log in to these accounts through Cerby, regardless of their role (**Collaborator** or **Manager**).
Access the accounts as you normally would via the account cards in the dashboard of the Cerby web app, browser extension, and mobile app.
In the Cerby web app dashboard, the accounts shared via a host-guest partnership are displayed on the **All accounts** page with the initial letter of the workspace name beside the app logo, as shown in **Figure 1**.
Figure 4. Account cards in the Cerby web app dashboard of a host or guest workspace
---
# 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/log-in-to-accounts-shared-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.
