From b4c816f4a499199b6a72969eb39ba8619fe886d1 Mon Sep 17 00:00:00 2001 From: Lukas Wagner Date: Tue, 14 Nov 2023 13:59:58 +0100 Subject: [PATCH] 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 --- notifications.adoc | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/notifications.adoc b/notifications.adoc index c7bdc5a..74447e5 100644 --- 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/`. Matchers use -a seperate namespace in the ACL tree: `/mapping/notification/matchers/`. +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`