> 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/helmutco/projects/filter.md).

# Filter

### User-specific filter:

Displays the user-specific saved filters and allows you to select and remove them as well as to save a current configured filter.

![Saved Filter](/files/M8oTmVFfOnGeJAfLmyOC)

### Filter Bubble:

A filter bubble can be created by clicking on a metadata entry in the project overview or by clicking on a metadata entry in the hidden overlay. By clicking on the filter bubble itself, a dialog opens to edit it (see Figure below). By default, the filters for group, category and template are active and set to ALL. If the group filter bubble is edited and a group is selected via the dialog that opens, only the categories belonging to the selected group can be selected via the category filter bubble. The same applies to the template filter bubble. If a filter bubble has been edited, it is possible to reset the filter bubble to ALL using the displayed minus sign.

![Define Filter](/files/D15xKn6Tt5b9RAky5QK3)

### Add Filter:

The Edit filter button adds another filter bubble to the current selected filters. Note: When using the filter “Filepath” in context of a Windows based path in the database for particular assets, it is mandatory to only use the condition “IS” for that case. Windows paths in the database are a signal for wrong or at least non desired workflows since a proper path mapping would force unix paths in the database. If your workflow requires windows paths in the database this is the limited possibility to search for an asset by “Filepath”.


---

# 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/helmutco/projects/filter.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.