Source string Read only

8/100
Context English State
Street
The street name of the customer.
Zip
The zip code of the customer.
City
The headquarter city of the customer.
Country
The country of the customer user.
It is possible to assign multiple customers to customer users via the :doc:`customer-users-customers` screen.
Customer User Back Ends
The system works with many customer user data attributes such as username, email address, phone number, etc. These attributes are displayed in both the agent and the external interface, and also used for the authentication of customer users.
Customer data used or displayed within the system is highly customizable. The user login and the email address are always needed for customer authentication.
You can use two types of customer back end: database or LDAP. If you already have another customer back end (e.g. SAP), it is possible to write a module that uses it.
The administrator interface does not support the configuration of external back ends. Administrators need to edit the file ``Kernel/Config.pm`` by copying and pasting code snippets from ``Kernel/Config/Defaults.pm`` manually in case of using *On-Premise* system or *((OTRS)) Community Edition*.
Do not modify the file ``Kernel/Config/Defaults.pm``, it will be overwritten after upgrading the system! Copy and paste the code snippets into ``Kernel/Config.pm`` instead.
Database
This is the default customer user back end for new installations. The example below shows the configuration of a database customer back end, which uses customer user data stored in the database table ``customer_user``.
If you want to customize the customer user data, change the columns or add new ones to the ``customer_user`` table in the database.
For example, to add a new field for room number:
Add a new column ``room`` to table ``customer_user``.
MySQL or MariaDB:
PostgreSQL (from the ``/opt/otrs`` directory):
Copy the ``$Self->{CustomerUser}`` section from ``Kernel/Config/Defaults.pm`` into ``Kernel/Config.pm``.
Add the new column to the ``Map`` array.
You can set the HTTP link target and link class (the last two keys) to ``undef`` in map array elements, if they are not to be used. These keys add ``target=""`` and ``class=""`` attributes to the HTTP link element, respectively. They are ignored if HTTP link is not set (it is ``''`` in this example).
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.
LDAP
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.
ComponentTranslation
This translation Translated OTRS 7/Administration Manual Database
The following string has the same context and source.
Translated OTRS 7/OTRS Database

Loading…

User avatar None

New source string

OTRS 7 / Administration ManualEnglish

New source string a year ago
Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Flags
read-only
Source string location
../../content/users-groups-roles/customer-users.rst:157
String age
a year ago
Source string age
a year ago
Translation file
locale/content.pot, string 2962