HOPEX Administration > Administrator Guide > Managing Users > Introduction to User Management > Person Properties
Person Properties
*For information on a user, see User: Definition
*To consult properties of a person, see Viewing Person Characteristics.
*To define the properties of a person, see Defining a Person.
Name 
The name of the person can include name and first name. It can comprise letters, figures and/or special characters. Format of the name of the person is free. It is recommended that the same format be used for all persons.
Example: DURAND Pierre
Image 
You can download an image in .ico, .bmp, .gif or .png format up to a size of 30 MB.
E-mail 
The person e-mail address is useful, for distribution of reports (MS Word) for example.
It is mandatory for password change and for receipt of questionnaires for example.
Example: pdurand@mega.com
Phone number and initials 
The phone number and initials of the person are optional.
Example: +33102030405 / DP
Data language 
The Data language attribute of the person is specific to Web applications. It enables definition of a specific data language for this user. It is the language in which data names are displayed by default, in case several languages are available.
*By default, the data language is defined in the environment options for all users at installation (Options/Installation/Web application) via the Data language option.
*To define interface language, see Managing Languages.
Default library 
The Default Library attribute enables attachment of objects created by the person in a library, when the creation context does not permit this.
Person's reading access area and reading access area at creation 
*Information related to the reading access area are only visible when the Activate reading access diagram is selected in Options of the Repository of the Environment.
Certain objects or modeling projects may be confidential or contain data (costs, risks, controls) that should be visible only to authorized users.
The HOPEX administrator can hide objects corresponding to this confidential data.
To implement a data confidentiality policy, objects must be organized in distinct sets. Each set of objects is a reading access areas.
Each user is associated with a reading access area that determines objects the user can see. A user can only see objects located in his/her own reading access area or in the lower reading access areas.
*For more details on reading access areas, see Managing Data Reading Access.
Person writing access area and writing access area at creation 
*Writing access management is available with the HOPEX Power Supervisor technical module.
A writing access area is assigned to an object to protect it from inadvertent modifications. At creation, an object takes the writing access area of the user that creates it.
By default, a new user is connected to the only writing access area: "Administrator".
There is a hierarchical link between writing access areas: a user can only modify an object when he/she has the same writing access level as this object or a higher writing access area level.
Login 
The login of a person is a unique character string uniquely identifying the person that can connect. The person without a login cannot connect to HOPEX.
Example: pdurand, pdd
*For more details, see Login Properties.
Belongs to a Person Group 
*Managing person groups is a functionality available in HOPEX (Web Front-End). For more information on managing this functionality, see Introduction to Person Group Management.