GN-72 KeyCloak-Roles in Architecture Documentation added
diff --git a/src/main/asciidoc/architectureDocumentation/auth_n_auth_architectureDocumentation.adoc b/src/main/asciidoc/architectureDocumentation/auth_n_auth_architectureDocumentation.adoc
index 71bb66c..7abfa88 100644
--- a/src/main/asciidoc/architectureDocumentation/auth_n_auth_architectureDocumentation.adoc
+++ b/src/main/asciidoc/architectureDocumentation/auth_n_auth_architectureDocumentation.adoc
@@ -813,10 +813,12 @@
- planning-access
- feedin-management-access
- planned-policies-access
+- planned-policies-normaluser
+- planned-policies-superuser
-. Configuring elogbook-superuser role. Hit elogbook-superuser or press `Edit`
+. Configuring a superuser role. Under Roles, hit on a superuser(elogbook-superuser or planned-policies-superuser) or press `Edit`
.. Switch `Composite Roles` to on.
-.. Add the Realm Role 'elogbook-normaluser' from the `Available Roles`
+.. Add the Realm Role 'elogbook-normaluser' or 'planned-policies-normaluser' correspondingly from the `Available Roles`
.. Select from the `Client Roles` Dropdown-List 'realm-management' and add the role 'view-users'.
.Elogbook superuser composite role
@@ -846,6 +848,10 @@
- elogbook-normaluser = standard user in the elogbook-app
- elogbook-superuser = admin user in the elogbook-app
+... User right in the distinct modul Planned Grid Measures (`planned-policies-access` required of course):
+- planned-policies-normaluser = standard user in the plannedGridMeasures-app
+- planned-policies-superuser = admin user in the plannedGridMeasures-app
+
... Access rights to the specific modul:
- elogbook-access
- planning-access
@@ -862,8 +868,8 @@
[start=8]
. Add an admin user. (Mandatory) +
-Same procedure like adding a User (see 7.) but with the role 'elogbook-superuser' instead of
-'elogbook-normaluser'.
+Same procedure like adding a User (see 7.) but with the role 'elogbook-superuser' or 'planned-policies-superuser' instead of
+'elogbook-normaluser' or 'planned-policies-normaluser' correspondingly.
IMPORTANT: We use this admin account (username & password) also to configure the backend. +
See "Configuration of the backend",
