> For the complete documentation index, see [llms.txt](https://docs.helmut.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.cloud/high5/spaces-in-high5/secrets-store.md).

# Secrets Store

The Secrets Store enables users to store value. A user can choose if a value needs to be concealed or not.

A secret remains unrevealed during stream execution. To read and use a secret in a stream, the node "*Get Secret*" should be used.

## Create a secret

Go to the Space where your secret will be needed. Navigate to the "*Secrets Store"* in the menu on the left side. A list of all secrets available in this Space appears.

* Click on the button "*+ Create secret*" in the upper right quarter of the UI
* Assign a unique name to your secret
* Fill in a value
* Click on the padlock-icon to close it and conceal the value, if needed
* Click on "*Create*" to finish the process and create the secret

The secret is now visible in the list, and when chosen, the value is concealed by asterisks.

<figure><img src="/files/G23h10iECf0wHCK8xzq0" alt=""><figcaption><p>Use the padlock icon to conceal the value in lists and logs</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.cloud/high5/spaces-in-high5/secrets-store.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.