> 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.1/helmut4-components/helmutio/metadata.md).

# Metadata

The Metadata menu is used to manage metadata. It is divided into a sidebar menu, a list view, and a hidden overlay. Entries are unique and can not be created multiple times with the same name. Metadata can be created, edited and deleted, as well as assigned to sets. Metadata entries can be used in IO to assign them to sets and thus to profiles. A profile, in turn, will be assigned to one or more groups.

![Sidebar Menu](/files/sOW94Jz7oGB4MwrNhwEa)

### All Tab:

Displays all metadata entries created in the system.

### Metadata Set Tab:

Displays all metadata sets created in the system and filters the metadata entries displayed in the list view when selecting a set. To add a metadata set click on the “Add Metadata Set Button” on the top right and define a name for that set. This Button appears in the Metadata tab of HIO, HCO and HHK. It is not available in HFX.

![Add Metadata Set + Add Metadata Button](/files/nLVaUyxaOQuz1VnorkHB)

For more information see: [Metadata](/helmut4-releases/v4.6.1/helmut4-components/helmutfx/metadata.md)


---

# 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.1/helmut4-components/helmutio/metadata.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.