major surgery

website/docs/sys-mgmt/events/event-actions.md

@@ -1,5 +1,5 @@
 ---
-Title: Event actions
+title: Event actions
 ---
 
 Whenever any of the following actions occur, an event is created. Actions are used to define [Notification Rules](notifications.md).

website/docs/sys-mgmt/events/logging-events.md

@@ -1,5 +1,7 @@
 ---
-Title: Logging events
+title: Logging events
 ---
 
 shshhs
+
+## mmoo--

website/docs/sys-mgmt/events/notifications.md

@@ -16,9 +16,13 @@ To receive notifications about events, follow this workflow:
 2. [Create a policy](#create-a-policy)
 3. [Create a notification rule, and bind the policy to the rule](#create-a-notification-rule)
 
-## Create a policy
+## 1. Create a notification transport
 
-First you need to create a policy, either the **Event Matcher** policy or a custom Expression policy.
+
+
+## 2. Create a policy
+
+First you need to create a policy (either the **Event Matcher** policy or a custom Expression policy) that defines which events will trigger a notification.
 
 ### **Event Matcher** policy
 
@@ -39,9 +43,15 @@ if "event" not in request.context:
 return ip_address(request.context["event"].client_ip) in ip_network('192.0.2.0/24')
 ```
 
-## Create a notification rule
+## 3. Create a notification rule and bind it to the policy
 
-After you've created the policies to match the events you want, create a **"**Notification Rule\*\*.
+After you've created the policies to match the events you want, create a notification rule.
+
+1. Log in as an administrator, open the authentik Admin interface, and navigate to **Event > Notification Rules**.
+
+2. Click **Create** to add a new notification rule, or click the **Edit** icon next to an existing rule to modify it.
+
+3. Define the ------------, and then
 
 You have to select which group the generated notification should be sent to. If left empty, the rule will be disabled.
 
@@ -49,7 +59,11 @@ You have to select which group the generated notification should be sent to. If
 Be aware that policies are executed even when no group is selected.
 :::
 
-You also have to select which transports should be used to send the notification.
+You also have to select which [transports](./transports.md) 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](../../install-config/install/docker-compose.mdx#email-configuration-optional-but-recommended).
 
-Starting with authentik 2022.6, a new default transport will be created. This is because notifications are no longer created by default, they are now a transport method instead. This allows for better customization of the notification before it is created.
+4. Click **Create**.
+
+
+
+

website/docs/sys-mgmt/events/transports.md

@@ -4,7 +4,7 @@ title: Transports
 
 To receive notifications about events, you will need to [create](#create-a-transport) a transport object, then create a notification rule and a policy. For details on this workflow refer to
 
-## Transport types
+## Transport modes
 
 Notifications can be sent to users via multiple mediums, or _transports_:
 
@@ -54,4 +54,9 @@ This sends a request using the Slack-specific format. This is also compatible wi
 
 ## Create a transport
 
-dfvfd
+1. Log in as an administrator, open the authentik Admin interface, and navigate to **Event > Notification Transports**.
+
+2. Click **Create** to add a new transport, or click the **Edit** icon next to an existing transport to modify it.
+
+3. Define the **Name** and **Mode** for the transport, enter required configuration settings, and then click **Create**.
+