The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
English Spanish (Colombia)
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.
To create a new ACL you can either import ACLs which were exported from another system or create a complete new one.
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.
ACLs
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.
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.
Create a new ACL by submitting the form data. After creating the ACL, you will be able to add configuration items in edit mode.
Overwrite existing entities
Filter for Calendars
Filter for Notifications
Filter for notifications
Agent preferences tooltip
This message will be shown on the agent preferences screen as a tooltip for this notification.
Recipients
Send to all group members (agents only)
Also send if the user is currently out of office.
These are the possible methods that can be used to send this notification to each of the recipients. Please select at least one method below.