Source string Read only

type: Content of: <section><section><itemizedlist><listitem><para>
Context English State
ACLs can be directly entered into the <filename>Kernel/</filename> file. However this is not any more recommended as OTRS comes now with a GUI <link linkend="adminarea-groups">Access Control Lists</link> in the Admin panel that allows to save the ACLs in the Database as the first step and then deploy them into a file when they are ready.
This chapter has some ACL examples which will walk you through the process of defining ACL definitions, and a reference of all possible important ACL settings.
The default user 'root@localhost' is not affected by the Ticket ACLs
The ACL definition can be split into two big parts, 'Matching' and 'Change'. In the matching sections the ACLs contains attributes that has to be met in order to use the ACL. If the attributes defined in the ACL does 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 contains the rules to reduce the possible options for a ticket.
Matching Sections
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.
This section is similar to <literal>Properties</literal> 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).
Change Sections
Possible section resets the data to be reduce to only the elements that are set in this section.
Elements in PossibleAdd section add missing elements that were reduced in other ACLs. PossibleAdd is only used in together with other ACLs that have Possible or PossibleNot sections.
This section is used to remove specific elements from the current data. It could be used stand alone or together with other ACLs with a Possible or PossibleAdd sections.
In order to make the development of ACLs easier and more powerful there is a set of so called modifiers for the attributes on each section. This modifiers are explained below:
This modifier is used to negate a value for example: '[Not]2 low' in this case talking about ticket priorities will be the same as to have: '1 very low', '3 normal', '4 high', '5 very high'.
It is use to define a regular expression for matching several values, for example '[RegExp]low' talking about priorities is the same as '1 very low', '2 low'.
It is very similar to [RegExp] but it is case insensitive.
Negated regular expressions for example '[NotRegExp]low' talking about priorities is the same as '3 normal', '4 high', '5 very high'.
It is very similar to [NotRegExp] but it is case insensitive.
The following examples are shown in both ways graphical and text based.


User avatar None

New source string

OTRS 6 / Administration ManualEnglish

New source string a year ago
Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks



English English
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <section><section><itemizedlist><listitem><para>
Source string location
String age
a year ago
Source string age
a year ago
Translation file
i18n/doc-admin.pot, string 783