> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.7.0/helmut4-components/streamdesigner/layout/variables.md).

# Variables

Opens a dialog for managing variables. In contrast to the variables that are managed via the Preferences menu, the variables managed here can also be controlled via streams, i.e. they can be created, changed or deleted via stream. They can also be used globally within each stream. There are three different action nodes available for this.

<figure><img src="/files/cu5uSX86Owy81wDxcNlt" alt=""><figcaption></figcaption></figure>

#### New Variable:

Opens a dialog with which it is possible to add new variables. Opens a dialog with which it is possible to add new variables. The character length of each key and value is limited to 255 characters.

<figure><img src="/files/BuQAyVDWvsb8egOsvjfH" alt=""><figcaption><p>New Variables Dialog</p></figcaption></figure>

#### Protected:

This toggle switch enables a variable to be protected globally. A protected variable cannot be changed via a stream, i.e. neither edited nor deleted.


---

# 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.de/helmut4-releases/v4.7.0/helmut4-components/streamdesigner/layout/variables.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.