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

# User Displayname Condition

With the help of the User Displayname Condition it is possible to use all or part of the display name of the user who is executing the stream as a condition for further actions. For example, if you want to make the behaviour of the stream dependent on whether the user has a certain display name, you would enter the display name or parts of the display name for which the behaviour should change in this node. Here the way can be defined. For example, if the node is to be successful when it comes to a specific user, "is" would be used as the condition. "Is\_not" would be used if the node should fail for a specific user. This makes it possible to decide precisely whether the behaviour should apply to a user or not. The user display name condition can be queried in every stream.


---

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