> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/berichte/benutzerdefinierte-filter.md).

# Custom filters

Custom filters can — as the name suggests — be created by the user.

They are then available in various places in the system, e.g. in the custom reports, in the year in review and in various other statistical evaluations.

A custom filter restricts a result set of a report to what is declared in the filter.\
For example, we can apply the "Automotive" filter to an annual revenue report and see how much revenue our company made in the automotive sector.

### Use cases for custom filters

#### Filter "Food-Branche"

A "Food-Branche" filter could include only our customers from the food sector with all their customer accounts and jobs.

![](/files/c524208333a07d416e433521cbaf4d123a90ec47)

#### Filter "Reiskosten"

If you create a travel-expenses job for each customer, you can create a custom filter that considers all customers and all customer accounts, but only evaluates the jobs named "Reisekosten" of all customers.

#### Filter "Retainergeschäft"

If you maintain two customer accounts for your customers — one for project business and the other for retainers, i.e. fee-based business with, for example, annual contracts — you can create a custom filter that includes all customers but only the retainer customer accounts with their jobs.

#### Filter "Team Media Production"

Does your company have teams and assign customers to them? Then it makes sense to create a custom filter for each team and assign the team's customers with all their customer accounts and jobs to the filter. 

## Define project types with custom filters

Custom filters are also suitable for defining certain project types. 

{% hint style="info" %}
**Examples:**\
\
Digital projects\
Print projects\
Events\
\
\
Studio projects\
Workshop projects
{% endhint %}

You can learn how such project types are defined and used in this video:

{% embed url="<https://www.loom.com/share/af1c44fe739143148120324c56cf4b5d?sid=e4471755-459b-4d71-a3ce-37195356d91b>" %}


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/berichte/benutzerdefinierte-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.