> 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/secrets/managing-your-secrets/view-a-secret.md).

# View a secret

This article describes how to view the secrets you have added or that you were granted shared access in Cerby.

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

* Workspace **Owners**, **Super Admins**, **Admins**, and **Users**
* Secret **Owners** and **Collaborators**
* Available in the Cerby web app, mobile, and web extension
  {% endhint %}

All users with shared access to a secret, regardless of their workspace role, can view its details.

Additionally, as mentioned in the article [Add a secret](/cerby-web-app/secrets/managing-your-secrets/add-a-secret.md), you can configure an identity challenge to view a secret. In this case, all users with shared access, including **Owners**, must confirm their identity to view a secret.

To view a secret using the Cerby web app, you must complete the following steps:

1. Log in to your corresponding [Cerby](https://app.cerby.com/) workspace.
2. Select the **Secrets** option from the left navigation drawer. The **Secrets** page is displayed.
3. Click the secret card or the **View** icon from the corresponding secret card. The **Secret** dialog box is displayed with the content of the secret and the attachments.\
   **NOTE:** If an identity challenge is configured, the **Confirm your identity to continue** dialog box is displayed. To confirm your identity, use one of [Cerby's multi-factor authentication methods](https://help.cerby.com/tips-and-troubleshooting/best-practices/set-up-your-identity-with-cerby-s-mfa-methods).
4. Click the **View** button next to the **Secret** field to show the secret content.

Now 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/secrets/managing-your-secrets/view-a-secret.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.