# Users

The main screen for users shows a list of created users, and allows for the creation of a new user with the button _**Create new user**_**.**

![](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkhT6bU-vG8tMu7uoBR%2F-MkhTCiJRlvbif1lhk90%2Fimage.png?alt=media\&token=ca886cd8-454b-4bbe-8285-1c5d5518cc7b)

Creation and edition of users is much alike, apart from the impossibility to change the user identifier. Users will be allowed to change some fields in their own files, while others will not; system administrators will have access to almost all fields. The fields involved are:

* **Full name**. Not editable by the user.
* **E-mail**. Not editable by the user, and unique to the user base.
* **Language**. Browsing language for the user, from the available ones (Spanish and English for the time being, though updates may be requested).
* **User groups**. Those to which the user belongs, and for this an individual DDL selection is shown. A user in the detail page will only see the assigned groups.
* **Local machine user**. Not shown to the user. Read the installation manual for information on what (system) user to associate to it and the implications.
* **Status**. Active or inactive; not visible by a user (which would obviously be active if logged in).
* **Authentication type**: local and/or AD/LDAP. The user will only be able to log in in the specified way. This selection sets which of the following fields are shown for configuration/visualization.
* **Domain user (AD/LDAP)**. Shown for AD/LDAP authentication; it is the name of the user in the domain.
* **Local user name**. Name of the user in **LIBSAFE**. It is mandatory, even if authentication is only done through AD/LDAP.
* **Local password**. Shown and used for local authentication.
* **Retype local password**. Shown and used for local authentication; it is a check for proper password introduction.

You should note that the user password for AD/LDAP authentication is not saved, because the server will save it and will validate the user identification.

**LIBSAFE** limits the insertion and edition of some user fields to the system administrator, to avoid the insertion of false administrative information, which could lead to data or identity theft. The internal procedures of the company or institution using **LIBSAFE** should be responsible for the verification of the data, and for the management of the same by the **LIBSAFE** systems administrator.

{% hint style="info" %}
**Note:** the user password for AD/LDAP authentication is not saved, since the very server will be saving this data and validating the user’s identification.
{% endhint %}

**LIBSAFE** has a security option called _Two-Factor Authentication_. This security option is inactive by default and can be individually configured at user level.

The method currently implanted is known as OTP (One-Time Pin). It can be selected both at user creation or user edition. Once selected, we will have access to a specific section where the user authentication can be configured. It is explained in detail next.
