PLATFORM - Administration (Web) > Users > Introduction to User Management > Login Properties (Person)
Login Properties (Person)
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) 
The user authentication is performed by checking the user password. Authentication modes managed within HOPEX are:
• MEGA (default value)
The HOPEX authentication service checks that the password entered matches the (hashed and encrypted) password stored in HOPEX repository.
• HAS UAS
Password management is delegated to the UAS application of HAS. In this configuration the user cannot connect to HOPEX (Windows Front-End).
• Windows (deprecated)
Passwords are stored and managed by Windows. The user connected via Windows is automatically recognized in HOPEX (his/her password is not requested)