> 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/edit-a-secret-item.md).

# Edit a secret item

This article describes how to edit the secret items you have added or that you were granted shared access as Owner in Cerby.

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

* Workspace **Owners**, **Super Admins**, **Admins**, and **Users**
* Secret item **Owners**
  {% endhint %}

To edit a secret item (WiFi, SSH keys, database, server, and custom item), you must complete the following steps using the Cerby web app:

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 card or the **Settings** icon for the corresponding secret item. The secret details page\*\*\*\* is displayed with the **Settings** tab activated.
4. Click the **Edit** icon of the corresponding field to make it editable.
5. Enter the new value in the field.
6. Click the **Done** icon to save your changes. A success message box is displayed.
7. Repeat steps 4 to 6 as necessary for each field.

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/edit-a-secret-item.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.