notifications: change to simplified ACL structure.

For now, we use a less deeply nested structure. We can always extend
it if we need to.

Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>

diff --git a/notifications.adoc b/notifications.adoc
index c7bdc5aa11763a8617e593e283813106b8f15a07..74447e5d13c553d176aae4c43bdaedb9ab7db689 100644 (file)
--- a/notifications.adoc
+++ b/notifications.adoc
@@ -309,11 +309,9 @@ content, they will be transformed into plain text format during this process.
 Permissions
 -----------
 
-For every target, there exists a corresponding ACL path
-`/mapping/notification/targets/<name>`. Matchers use
-a seperate namespace in the ACL tree: `/mapping/notification/matchers/<name>`.
-
-To test a target, a user must have the `Mapping.Use` permission on the corresponding
-node in the ACL tree.
-`Mapping.Modify` and `Mapping.Audit` are needed to read/modify the
-configuration of a target or matcher.
+In order to modify/view the configuration for notification targets,
+the `Mapping.Modify/Mapping.Audit` permissions are required for the
+`/mapping/notifications` ACL node.
+
+Testing a target requires `Mapping.Use`, `Mapping.Audit` or `Mapping.Modify`
+permissions on `/mapping/notifications`