From 8c2d72affef21fd9c210c7fff1b91b5a7debdfd5 Mon Sep 17 00:00:00 2001 From: "gcp-cherry-pick-bot[bot]" <98988430+gcp-cherry-pick-bot[bot]@users.noreply.github.com> Date: Sun, 22 Jun 2025 00:58:35 +0200 Subject: [PATCH] website/docs: fix egregious maintenance fail (cherry-pick #15176) (#15180) website/docs: fix egregious maintenance fail (#15176) fix egregious maintenance fail Co-authored-by: Tana M Berry Co-authored-by: Tana M Berry --- website/docs/sys-mgmt/events/notifications.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/website/docs/sys-mgmt/events/notifications.md b/website/docs/sys-mgmt/events/notifications.md index 93dc8f605f..035e1709b8 100644 --- a/website/docs/sys-mgmt/events/notifications.md +++ b/website/docs/sys-mgmt/events/notifications.md @@ -8,9 +8,7 @@ To prevent infinite loops (events created by policies which are attached to a No ## Filtering Events -Starting with authentik 0.15, you can create notification rules, which can alert you based on the creation of certain events. - -Filtering is done by using the Policy Engine. You can do simple filtering using the "Event Matcher Policy" type. +An authentik administrator can create notification rules based on the creation of specified events. Filtering is done by using the Policy Engine. You can do simple filtering using the "Event Matcher Policy" type. ![](./event_matcher.png)