|
Employee |
Employee that uses this user account. An employee is already entered if the user account was generated by an account definition. If you create the user account manually, you can select an employee in the menu. If you are using automatic employee assignment, an associated employee is found and added to the user account when you save the user account.
You can create a new employee for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click  next to the input field and enter the required employee main data. Which login data is required depends on the selected identity type. |
|
No link to an employee required |
Specifies whether the user account is intentionally not assigned an employee. The option is automatically set if a user account is included in the exclusion list for automatic employee assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an employee (for example, if several employees use the user account).
If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an employee can be filtered according to various criteria. |
|
Not linked to an employee |
Indicates why the No link to an employee required option is enabled for this user account. Possible values:
-
By administrator: The option was set manually by the administrator.
-
By attestation: The user account was attested.
-
By exclusion criterion: The user account is not associated with an employee due to an exclusion criterion. For example, the user account is included in the exclude list for automatic employee assignment (configuration parameter PersonExcludeList). |
|
Account definition |
Account definition through which the user account was created.
Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.
NOTE: The account definition cannot be changed once the user account has been saved.
NOTE: Use the user account's Remove account definition task to reset the user account to Linked status. This removes the account definition from both the user account and the employee. The user account remains but is not managed by the account definition anymore. The task only removes account definitions that are directly assigned (XOrigin=1).
Employee documents can also be created through account definitions. |
|
Manage level |
Manage level of the user account. Select a manage level from the menu. You can only specify the manage level can if you have also entered an account definition. All manage levels of the selected account definition are available in the menu. |
|
First name |
The user’s first name. |
|
Middle name |
User's middle name. |
|
Last name |
The user’s last name. |
|
Short name |
The user’s short name. |
|
Phonetic name |
The user's name in phonetic letters. |
|
Notes domain |
User account's user account. |
|
Certificate |
Certificate with which the user ID file and the user's mailbox file will be registered (when first added) or were registered. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. No certificate is assigned to pure employee documents.
If a certificate is not assigned when a new user account is saved, the certificate cannot be assigned later.
If a certificate is assigned when a new user account is saved, the certificate cannot be removed later. |
|
Organizational unit |
Additional organization unit belonging to the user account. |
|
Display name |
User account display name. The display name is made up of the full name or the first and last names. |
|
Title |
User's title. |
|
Generational affix |
User's generational affix, for example, Junior. |
|
Alternative language |
Alternative language for the alternative names. |
|
Alternative name |
Alternative name in the user's local language.
This can be used to display and search for names in the Domino environment. The alternative name has to linked to one of the user account‘s alternative language. |
|
Email system |
Type of email system used by the user. 1 - Notes is entered by default. The other input fields shown on the main data form depend on the type of email system selected. |
|
Risk index (calculated) |
Maximum risk index value of all assigned groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For detailed information, see the One Identity Manager Risk Assessment Administration Guide. |
|
Category |
Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu. |
|
User account is disabled |
Specifies whether the user account is blocked from logging in to the domain. |
|
Identity |
User account's identity type Permitted values are:
-
Primary identity: Employee's default user account.
-
Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.
-
Personalized administrator identity: User account with administrative permissions, used by one employee.
-
Sponsored identity: User account to use for a specific purpose. Training, for example.
-
Shared identity: User account with administrative permissions, used by several employees. Assign all employees that use this user account.
-
Service identity: Service account. |
|
Privileged user account. |
Specifies whether this is a privileged user account. |
|
Groups can be inherited |
Specifies whether the user account can inherit groups through the linked employee. If the option is set, the user account inherits groups through hierarchical roles, in which the employee is a member, or through IT Shop requests.
-
If you add an employee with a user account to a department, for example, and you have assigned groups to this department, the user account inherits these groups.
-
If an employee has requested group membership in the IT Shop and the request is granted approval, the employee's user account only inherits the group if the option is set. |
