> 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/vaults/view-the-vaults-to-which-you-have-shared-access.md).
# View the vaults to which you have shared access
This article describes how you can view the vaults to which all users have access.
{% hint style="info" %}
**Who can use this feature?**
* Workspace **Owners**, **Super Admins**, **Admins**, and **Users**
* Only supported using the Cerby web app
{% endhint %}
All users in a workspace can view the vaults to which they have shared access, no matter their workspace role. This article describes how to view the vaults to which you have shared access.
To view the vaults to which you have shared access, you must complete the following steps:
1. Log in to your [Cerby](https://app.cerby.com/) workspace using the Cerby web app.
2. Click your user profile located at the top right of the Cerby dashboard. A drop-down list is displayed.
3. Select the **My Profile** option. The **My Profile** page is displayed.
4. Activate the **Security** tab. A table with a list of vaults to which you have access is displayed in the **Vaults** section, as shown in **Figure 1**.
Figure 1. Vaults section in the Security tab of the My profile page
---
# 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/vaults/view-the-vaults-to-which-you-have-shared-access.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.
