MEGA 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".
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 address
The person e-mail address is useful, for distribution of reports (MS Word) for example.
It is mandatory for password change in Web mode and for receipt of questionnaires for example.
Example: pdurand@mega.com
Telephone number and initials
The telephone 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", page 377.
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.
User writing access area and writing access area at creation
*Writing access management is available with the MEGA 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.
*See "Managing Data Writing Access", page 297.
Reading access area
*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 MEGA 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 or lower reading access areas.
*For more details on reading access areas, see "Managing Data Reading Access", page 321.
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 MEGA.
Example: pdurand, pdd
*For more details, see "Login Properties".
Belongs to a person group
A person can:
• belong to a group
*See "Creating a Person Group".
*See "Creating Users (Web Front-End)".
• have the Belongs to a person group attribute selected
When the "Belongs to a person group" attribute of the person is selected, the person belongs to a dynamic group (LDAP group or group connected to a macro).
*See "Defining a dynamic person group with LDAP".
*See "Defining a dynamic person group with a Macro".
When the "Belongs to a person group" attribute of the person is selected, but the person is not listed in a person group, this means that the person is not directly connected to a group or does not belong to a dynamic group (LDAP group or groups connected to a macro): the person belongs to the default group.
*See "Default connection group".
A person who belongs to a person group or who has the Belongs to a person group attribute selected, can only connect to the application through the group, with one of the business roles/profiles defined for the group (the assignments defined for the person are ignored).