From d1d18c299a5b1de98ae8cfd07458a609a0d986d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Norman=20J=C3=A4ckel?= Date: Fri, 5 Feb 2021 12:34:14 +0100 Subject: [PATCH] Added permission.yml. --- docs/permission.yml | 57 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 docs/permission.yml diff --git a/docs/permission.yml b/docs/permission.yml new file mode 100644 index 000000000..46b9234be --- /dev/null +++ b/docs/permission.yml @@ -0,0 +1,57 @@ +--- +# To get a permission string you have to combine the top level string +# with one of the strings in the lower levels. Permissions are e. g. +# agenda_item.can_manage or agenda_item.can_see. + +# The permissions are hierarchical. Users with agenda_item.can_manage do have +# implicitly agenda_item.can_see_internal and agenda_item.can_see. + +agenda_item: + can_manage: + can_see_internal: + can_see: +list_of_speakers: + can_manage: + can_see: + can_be_speaker: + can_see: +meeting: + can_manage_settings: + can_manage_logos_and_fonts: + can_see_frontpage: + can_see_autopilot: + can_see_livestream: + can_see_history: +projector: + can_manage: + can_see: +tag: + can_manage: +motion: + can_manage: + can_manage_metadata: + can_see: + can_manage_polls: + can_see: + can_see_internal: + can_see: + can_create: + can_see: + can_create_amendments: + can_see: + can_support: + can_see: +assignment: + can_manage: + can_nominate_other: + can_see: + can_nominate_self: + can_see: +mediafile: + can_manage: + can_see: +user: + can_manage: + can_see_extra_data: + can_see: + can_change_own_password: