Source string Read only

Context English State
It is recommended to always use English words for names.
Names can be translated into other languages with custom translation files. For more information, see the *Custom Translation File* chapter in the developer manual.
If you have an LDAP directory with your customer user data, you can use it as the customer user back end. The example below shows the configuration of a LDAP customer user back end.
To activate and configure the LDAP back end:
Remove the comments (``#`` characters) from the beginning of the lines.
If additional customer user attributes are stored in your LDAP directory, such as a manager name, a mobile phone number, or a department, this information can be displayed in OTRS.
To display additional customer user attributes from LDAP directory:
Expand the ``Map`` array in ``Kernel/`` with the entries for these attributes.
Multiple Customer User Back Ends
If you want to use more than one customer user data source, the ``CustomerUser`` configuration parameter should be expanded with a number, like ``CustomerUser1`` and ``CustomerUser2``.
The following configuration example shows usage of both a database and an LDAP customer user back end.
It is possible to integrate up to 10 different customer back ends. Use the :doc:`customer-users` screen to view or edit (assuming write access is enabled) all customer user data.
Customer User Data in Dynamic Fields
Sometimes it can be useful to also store customer user data directly in dynamic fields of a ticket, for example to create special statistics on this data.
The dynamic field values are set, when a ticket is created or when the customer user of a ticket is changed. The values of the dynamic fields are taken from the customer user data. This works for all back ends, but is especially useful for LDAP back ends.
To activate this optional feature:
Activate the setting ``Ticket::EventModulePost###4100-DynamicFieldFromCustomerUser``.
Activate the setting ``DynamicFieldFromCustomerUser::Mapping``. This setting contains the configuration of which customer user field entry should be stored in which ticket dynamic field.
Create the dynamic fields, if the dynamic fields are not present in the system yet.
Enable the dynamic fields in setting ``Ticket::Frontend::AgentTicketFreeText###DynamicField``, so that they can be set manually.
The dynamic field must not be enabled in the following settings:
If they were, they would have precedence over the automatically set values.
Customer Users ↔ Customers
In an organization, for example, which views its customers as it's departments and teams, a customer user may have to have access to multiple customers tickets for controlling purposes. Maybe you have partners who represent several different companies, or a corporation wants to have a look at all the requests of their subsidiaries.
For all situations, OTRS provides the means. Aside from a primary customer, your customer users can gain access to multiple customer tickets as defined by you.
Use this screen to add one or more customer users to one or more customers. To use this function, at least one customer user and one customer need to have been added to the system. The management screen is available in the *Customer Users ↔ Customers* module of the *Users, Groups & Roles* group.
Manage Customer User-Customer Relations


User avatar None

New source string

OTRS 7 / Administration ManualEnglish

New source string a year ago
Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string location
String age
a year ago
Source string age
a year ago
Translation file
locale/content.pot, string 2987