> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/de/web-interface/administration/configuration/notifications.md).

# Benachrichtigungen

Konfigurieren Sie E-Mail-Benachrichtigungen in Devolutions Server basierend auf Benutzeraktivitäten; dafür sind mindestens ein Abonnent und ein Abonnement erforderlich, damit die Funktion ordnungsgemä

{% hint style="info" %}
Die Funktion [E-Mail](/server/de/web-interface/administration/configuration/server-settings/general/email.md) muss aktiviert und ordnungsgemäß konfiguriert sein, damit die ***Benachrichtigungen*** funktionieren.
{% endhint %}

Mit Devolutions Server ist es möglich, mithilfe der Funktion ***Benachrichtigungen*** E-Mail-Benachrichtigungen basierend auf Benutzeraktivitäten zu erhalten.

Damit die Benachrichtigung funktioniert, müssen mindestens ein [Abonnent](/server/de/web-interface/administration/configuration/notifications/subscribers.md) und ein [Abonnement](/server/de/web-interface/administration/configuration/notifications/subscriptions.md) erstellt werden. Es ist auch möglich, Abonnenten in [Abonnentengruppen](/server/de/web-interface/administration/configuration/notifications/subscriber-groups.md) zusammenzufassen, um Benachrichtigungen an eine Gruppe von Abonnenten zu senden.


---

# 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://docs.devolutions.net/server/de/web-interface/administration/configuration/notifications.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.