> 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/projektverwaltung-1/projekte/projekteinstellungen/projekteinstellungen-benachrichtigungen.md).

# Job settings: notifications

In the "Settings" tab of a job, under "Notifications" it can be configured under which circumstances the project manager of a job should be notified about budget overruns in that job.

In the "General" tab there is a user selection field "Responsible". This field indicates who is currently leading this job. This user may receive notifications.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M85Ut1pseEnTadxNrRd%2F-M85V3dIzS2b4wdkurJt%2FBildschirmfoto%202020-05-24%20um%2013.44.00.png?alt=media\&token=3bc60fa9-2ea9-45f2-8a0c-1fc357b60363)

The checkboxes can indicate whether an overrun should lead to a notification at all.

{% hint style="info" %}
For some jobs - e.g. internal ones - no budget frame is stored at all. These jobs are then always overrun, so a notification would not be useful.
{% endhint %}

With the percent selection field you can specify from when a job should notify the project manager.

#### Remaining budget of functions

An example of a remaining budget of a function would be e.g. "Graphic design". Here we have defined a calculated or planned budget of 10 h at 70,- EUR; if more than 8 h have been incurred, in the example shown above we would receive a warning for the graphic design budget of this job, because now less than 20% remaining budget remains.

## View all overrun jobs

In the main menu under Reports > Overrun Budgets all job overruns can be viewed:

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-M3-p_rLmka9nDzciTof%2F-M3-pf-Gn2j0qwZH6q0M%2FBildschirmfoto%202020-03-22%20um%2012.57.42.png?alt=media\&token=6a7a1e29-4f24-4252-844d-1beceae29cb1)

### Filter by project manager and by latest events

This list can show either all projects or the projects of a specific user for administrators. For non-administrators it only shows their own projects.

With the filter "Show only overruns from the last 24 h" only jobs are shown where events in the last 24 h led to an overrun.

## Notifications by e-mail

Provided the user has not disabled their e-mail notifications, Die Agenturverwaltung sends an e-mail to the person entered here with a list of the overrun jobs.

{% hint style="info" %}
**Attention**: The list in this e-mail only includes jobs where an overrun occurred within the last 24 hours. Jobs that were overrun earlier are not listed again here.
{% endhint %}


---

# 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/projektverwaltung-1/projekte/projekteinstellungen/projekteinstellungen-benachrichtigungen.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.
