This repository has been archived on 2024-05-31. You can view files and clone it, but cannot push or open issues or pull requests.
authentik/website/docs/events/notifications.md

36 lines
1.4 KiB
Markdown
Raw Normal View History

---
title: Notifications
---
:::note
To prevent infinite loops (events created by policies which are attached to a Notification rule), **any events created by a policy which is attached to any Notification Trigger do not trigger notifications.**
:::
## Filtering Events
Starting with authentik 0.15, you can create notification triggers, which can alert you based on the creation of certain events.
2021-01-13 09:28:02 +00:00
Filtering is done by using the Policy Engine. You can do simple filtering using the "Event Matcher Policy" type.
![](./event_matcher.png)
2021-01-13 09:28:02 +00:00
An event has to match all configured fields, otherwise the trigger will not activate.
2021-01-13 09:28:02 +00:00
To match events with an "Expression Policy", you can write code like so:
```python
if "event" not in request.context:
return False
return ip_address(request.context["evnet"].client_ip) in ip_network('192.0.2.0/24')
```
## Selecting who gets notified
2021-01-13 09:28:02 +00:00
After you've created the policies to match the events you want, create a "Notification Trigger".
You have to select which group the generated notification should be sent to. If left empty, the trigger will be disabled.
2021-01-13 09:28:02 +00:00
You also have to select which transports should be used to send the notification.
A transport with the name "default-email-transport" is created by default. This transport will use the [global email configuration](../installation/docker-compose#email-configuration-optional-but-recommended).