> 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.6.0/helmut4-components/streamdesigner/nodes/conditions/user.md).

# User

A user condition always refers to the information available about a user executing a stream. This means, for example, that the name of the user or his group membership can be made a condition for the further course of the stream.

#### Example:

If there are streams that are configured to always be executed via the local client (autoimport), a different decision can be made in the stream depending on the user. For example, if the user is called "Lee", the user name condition can be used to query whether Lee is the one executing the stream or not. If this is the case, the further course of the stream can change due to the fact that the condition is true.


---

# 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.6.0/helmut4-components/streamdesigner/nodes/conditions/user.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.