Here you can upload a configuration file to import ACLs to your system. The file needs to be in .yml format as exported by the ACL editor module.

Changes to the ACLs here only affect the behavior of the system, if you deploy the ACL data afterwards. By deploying the ACL data, the newly made changes will be written to the configuration.

Please note: This table represents the execution order of the ACLs. If you need to change the order in which ACLs are executed, please change the names of the affected ACLs.

Edit ACL %s

Match settings

Set up matching criteria for this ACL. Use 'Properties' to match the current screen or 'PropertiesDatabase' to match attributes of the current ticket that are in the database.

Set up what you want to change if the criteria match. Keep in mind that 'Possible' is a white list, 'PossibleNot' a black list.

Check the official %sdocumentation%s.

Stop after match

Create a new ACL by submitting the form data. After creating the ACL, you will be able to add configuration items in edit mode.

Calendar Overview

Here you can upload a configuration file to import a calendar to your system. The file needs to be in .yml format as exported by calendar management module.

Overwrite existing entities

Filter for Calendars

Depending on the group field, the system will allow users the access to the calendar according to their permission level.

Read only: users can see and export all appointments in the calendar.

Move into: users can modify appointments in the calendar, but without changing the calendar selection.

Create: users can create and delete appointments in the calendar.

Read/write: users can manage the calendar itself.

Permission group