Source string Read only

50/500
Context English State
To delete an ACL:
Click on an ACL in the list of ACLs.
Set the *Validity* option to *invalid* or *invalid-temporarily*.
Click on the *Save* button. A new *Delete Invalid ACL* button will appear in the left sidebar.
Click on the *Delete Invalid ACL* button.
Click on the *Delete* button in the confirmation screen.
ACLs are written into ``ZZZACL.pm`` file in Perl format. Without deploying, all ACLs are still in this cache file even if they are deleted or the *Validity* option is set to *invalid* or *invalid-temporarily*. Don't forget to deploy all ACLs after modifications!
To deploy all ACLs:
Click on the *Deploy ACLs* button in the left sidebar.
New or modified ACLs have to deploy in order to make affect the behavior of the system. Setting the *Validity* option to *valid* just indicates, which ACLs should be deployed.
To export all ACLs:
Click on the *Export ACLs* button in the left sidebar.
Choose a location in your computer to save the ``Export_ACL.yml`` file.
To import ACLs:
Click on the *Overwrite existing ACLs?* checkbox, if you would like to overwrite the existing ACLs.
Click on the *Import ACL configuration(s)* button.
Deploy the imported ACLs with *Deploy ACLs* button.
If several ACLs are added to the system, use the filter box to find a particular ACL by just typing the name to filter.
Changing the name of this object should be done with care, the check only provides verification for certain settings and ignores things where the name can't be verified. Some examples are dashboard filters, access control lists (ACLs), and processes (sequence flow actions) to name a few. Documentation of your setup is key to surviving a name change.
ACL Settings
Description
Like comment, but longer text can be added here.
Stop after match
ACLs are evaluated in alphabetical order. This setting disables the evaluation of the subsequent ACLs.
Edit ACL Structure
The ACL definition can be split into two big parts, *Match settings* and *Change settings*. In the matching sections the ACLs contain attributes that has to be met in order to use the ACL. If the attributes defined in the ACL do not match with the attributes that are sent, then the ACL does not take any affect, but any other match ACL will. The change sections contain the rules to reduce the possible options for a ticket.
Match settings
``Properties``
This section contains matching options that can be changed on the fly. For example on a ticket creation time the data of the ticket changes dynamically as the agent sets the information. If an ACL is set to match a ticket attribute then only when the matching attribute is selected the ACL will be active and might reduce other ticket attributes, but as soon as another value is selected the ACL will not take any affect.
``PropertiesDatabase``
This section is similar to ``Properties`` but does not take changes in ticket attributes that are not saved into the database, this means that changing an attribute without submit will not make any effect. This section is not use for ticket creation screens (as tickets are not yet created in the database).

Loading…

User avatar None

New source string

OTRS 7 / Administration ManualEnglish

New source string 9 months ago
Browse all component changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Labels
No labels currently set.
Flags
read-only
Source string location
../../content/processes-automation/access-control-lists.rst:82
Source string age
9 months ago
Translation file
string