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>
This commit is contained in:
Lukas Wagner 2023-11-14 13:59:58 +01:00 committed by Thomas Lamprecht
parent 7b293b5d9a
commit b4c816f4a4

View File

@ -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>`.
In order to modify/view the configuration for notification targets,
the `Mapping.Modify/Mapping.Audit` permissions are required for the
`/mapping/notifications` ACL node.
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.
Testing a target requires `Mapping.Use`, `Mapping.Audit` or `Mapping.Modify`
permissions on `/mapping/notifications`