# Profiles

Profiles are used to define all relevant links between workflows, metadata, user groups, and rendering codes. Here it is determined which user group is allowed to see and execute the corresponding profile, which metadata is transferred when the job is executed and which render nodes from the pool can take over the job. It is divided into a sidebar menu, a list view, and a hidden overlay.

The Profile menu in HK provides almost the same functionality as the profile menu in IO.

For more information see:

{% content-ref url="/pages/4F0dtAKBm4XsOuOS6tXt" %}
[Profiles](/helmut4-releases/v4.6.0/helmut4-components/helmutio/profiles.md)
{% endcontent-ref %}

The major differences are considered in the section below.


---

# Agent Instructions: 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:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/helmuthk/profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.