HOPEX Administration > Administrator Guide > Managing Users > Actions to be Performed to Define a User
Actions to be Performed to Define a User
 
Before defining a user: profile concepts
Compulsory Actions to be Performed to Define a User
Optional Actions to be Performed to Define a User
Other Actions to Set or Manage a User
To define a user, some actions are compulsory, while others are only necessary depending on HOPEX options selected, and others are optional.
Before defining a user: profile concepts
To connect to HOPEX a user select the profile with which he/she wants to work.
This profile defines:
• the products accessible
*If a user already has restricted access rights to products (see Viewing the Login Characteristics), the products accessible to this user are at the intersection of values of the Command Line attribute of the user login and profile.
• the desktops to which the user can access.
• the user's access rights to UIs (permissions)
Assigning a profile to a person defines:
• the repository concerned by the assignment
• the person's access rights to repositories with this profile assignment
• (optional, with read-only access to the repository) connection repository snapshot
• (optional) the validity period of the assignment
Compulsory Actions to be Performed to Define a User
To create a user who can connect to HOPEX you must:
• define the name of the person
• define the login of the user
*A person must have a login to be able to connect to HOPEX.
*The login of the user is created automatically on creation of the person, see Creating Users (If necessary, see Creating the Login of a Person).
*The login status must be active so the person can connect, see Inactive user (Status).
• (recommended) define the e-mail address of the person
*The e-mail address is necessary, for example, for distributing documents, receiving notifications and questionnaires, or when a Web user lost his/her password.
• assign a profile to a person
*The user must have at least one profile assigned to be able to connect to HOPEX.
Optional Actions to be Performed to Define a User
According to the selected options you must:
• (recommended) define the e-mail address of the person
*The e-mail address is necessary, for example, for distributing documents, receiving notifications and questionnaires, or when a Web user lost his/her password.
• (where writing access management is activated) define the writing access area of the user
• (where reading access management is activated) define the reading access area of the user
Other Actions to Set or Manage a User
You can:
• define the telephone number and initials of the person
• restrict user access to certain products
*The products accessible to this user are at the intersection of the values of the Command Line attribute of the user login and profile.
• modify user authentication mode
• make the user inactive.