> 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

As the name suggests, custom filters can be created by users.

They are then available in various places in the system, for example, in custom reports, the annual review, and various other statistical analyses.

A custom filter narrows a report's results to the criteria specified in the filter.\
For example, we can apply the "Automotive" filter to an annual revenue report to see how much revenue our company generated in the automotive sector.

### Examples of how to use custom filters

#### The "Food Industry" filter

A "Food Industry" filter could include only our customers in the food industry, along with all their customer accounts and jobs.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M1s-YLjRvto_aqnBgqG%2F-M1s0qRq0lVwsWjPsPXm%2FBildschirmfoto%202020-03-08%20um%2009.41.55.png?alt=media\&token=aae686aa-7e94-4b70-babf-b4a577df0375)

#### The "Travel Expenses" filter

If you create a travel expenses job for each customer, you can create a custom filter that includes all customers and customer accounts but only analyzes the jobs named "Travel Expenses" for each customer.

#### The "Retainer Business" filter

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

#### The "Team Media Production" filter

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

## Define job types with custom filters

Custom filters are also useful for defining specific job types.&#x20;

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

This video explains how to define and use job types like these:

{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/berichte/benutzerdefinierte-filter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
