HOPEX Administration (Web) > Managing Users > Introduction to User Management > Person Login Properties
Person Login Properties
To:
• create the login of a person, see Creating a User or Creating the Login of a Person.
• view login characteristics, see Viewing the Login Characteristics.
• configure the login of a person, see or Defining the Login of a Person.
User code  
The User Code is the short identifier (upper case, maximum length 6 characters) of the user that serves as the basis for private workspace naming.
This code is defined automatically on user creation. To ensure data consistency, it should not be modified.
E.g.: PDD
Login Holder 
The login holder is the person associated with the login.
E.g.: DURAND Pierre
Status (Login) 
Login status can be used to make a user inactive (value: Inactive). The user no longer has access to repositories, but trace of his/her actions is retained. The user can be easily reactivated (value: Active).
*When you delete a user from the repository, the commands connected to this user become orphans and you lose part of the history saved in logs. With Inactive status, the user no longer has access to repositories, but the history of commands connected to the user is kept in logs.
Products accessible on the license (Command Line) 
The Command Line field enables restriction of access of a user or profile to available products.
*If a user is connected to a profile, and both the user and profile have access to products restricted by the Command Line attribute, the products accessible to the user are the intersection of the values of the Command Line attribute of the user and profile.
Authentication mode (case of authentication managed within HOPEX) 
Default value of the Authentication Mode parameter on the user login is inherited at user creation from the Authentication Mode option defined in the options of the environment (Options > Installation > User Management).
User authentication is done by checking the user password. Available authentication modes are:
• MEGA (default value)
The HOPEX authentication service checks that the password entered matches the password stored (hashed and encrypted) in HOPEX repository.
*For more details, see Authentication in HOPEX.
• LDAP
Passwords are managed and stored in the LDAP server of the enterprise. The directory configuration is stored in HOPEX options.
The HOPEX user is authenticated at the LDAP server level.
*For more details, see Configuring LDAP Authentication.
• Custom
Password management is delegated to an SSO or external module.
• Windows
Passwords are managed by Windows.
LDAP server 
*This field only appears when the Authentication Mode is "LDAP", see Authentication mode (case of authentication managed within HOPEX).
The LDAP Server is the server with which the HOPEX user is authenticated in LDAP authentication mode.
This server contains the LDAP directory in which the HOPEX user is registered.