> For the complete documentation index, see [llms.txt](https://docs.uify.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uify.io/data-management/secrets.md).

# Secrets

For sensitive connection details that you don't want to expose to other users, we allow you to specify secrets. Secrets are not exposed after their initial creation but can be used by any user when filling out the data source configuration. The secrets are stored and inserted in the backend and never touch the frontend. 

## Creating and modifying secrets

You can maintain your secrets in the workspace settings. You can find the settings by clicking on the dropdown next to the workspace name and then on "Settings". Here you will find a section **Security Settings** that includes the subsection **Secrets**.

<figure><img src="https://1582137130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkTYtq8XZyg79paoHbd93%2Fuploads%2FYR2eNtl5YF6juU8wvPcJ%2FScreenshot%202023-03-28%20at%2019.48.52.png?alt=media&amp;token=ebad580c-b8d5-47e4-9220-7359bfb067d1" alt=""><figcaption></figcaption></figure>

You can create a new secret by clicking on "**Create new secret**". There you can specify a **name** and a **value**. After creation the only the name and the timestamps of its creation and last update are available. You can **delete** the secret via the context menu and **edit** it. When you want to update the value of your secret, the current value is not exposed, i.e. you can only add a new one. The name of the secret is immutable.

## Using your secrets

When you want to connect a data source, some configuration details can be filled in using your previously specified secrets. The secret is available in any input that has `{{` at the end of its field. Clicking on it opens up a dropdown from which the secret can be selected.

<figure><img src="https://1582137130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkTYtq8XZyg79paoHbd93%2Fuploads%2FeZFEEFWxDewk8Aqtxup7%2FScreenshot%202023-03-28%20at%2019.56.54.png?alt=media&amp;token=fc633356-842a-4913-8314-9c23adb23d52" alt=""><figcaption></figcaption></figure>

&#x20;Additionally, we allow you to insert the secret manually by typing `{{secrets.<name-of-my-secret>}}` where `<name-of-my-secret>` is the name of your secret.


---

# 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://docs.uify.io/data-management/secrets.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.