| 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 an authentication object is assigned, the connected employee is found through the authentication object by using a template. If there is no authentication object assigned, the employee can be assigned automatically or manually.
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). |
| 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. |
|
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).
NOTE: If employees obtain their SharePoint user accounts through account definitions, the employees must own user accounts in the Active Directory domain or LDAP domain. This domain is stored in the SharePoint farm in which the SharePoint user accounts are to be created. |
| Site collection |
Site collection the user account is used in. |
| Group authenticated |
Specifies whether the user account's authentication object is a group. This option is disabled for user authenticated user accounts. |
| |
Authentication object referencing the user account. Each SharePoint user account represents an object from an authentication system trusted by the SharePoint installation. If this authentication system is managed as a target system in One Identity Manager, the SharePoint object used for authentication can be saved as the authentication object in the user policy.
The authentication object is assigned during automatic synchronization. You can assign an authentication object when setting up a new user account in the Manager. The authentication object cannot be changed after saving.
The following authentication objects can be assigned to a user-authenticated user account:
- Active Directory user accounts from the domain that is assigned to the farm or a trusted domain
- LDAP user accounts from the domain assigned to the farm
User accounts that refer to the default SIDs of an Active Directory environment cannot reference an authentication object in One Identity Manager.
NOTE: The SharePoint user account is also created if the user account that is used as the authentication object is disabled or locked. |
| |
Authentication mode used for logging in on the SharePoint server with this user account.
The login name of new user accounts depends on the authentication mode. The authentication mode is set by a template. The value depends on the Claims-based authentication option of the associated web application. If you have defined custom authentication modes, select your authentication mode in the menu.
NOTE: Modify the template for this column (SPSUser.UID_SPSAuthSystem) to assign a custom authentication mode to user accounts. |
| Display name |
Any display name for the user account. By default, the display name is taken from the authentication object display name. Enter the display name by hand if no authentication object is assigned. |
| Login name |
User account login name. It is found using a template. Enter the login name by hand if no authentication object is assigned.
NOTE: Modify the template for this column (SPSUser.LoginName) to assign a custom authentication mode to user accounts. |
| Email address |
User account email address. It is formatted using templates from the authentication object's email address. |
|
Risk index (calculated) |
Maximum risk index value of all assigned SharePoint roles and 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. |
| Advice |
Text field for additional explanation. |
|
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. |
|
Roles can be inherited |
Specifies whether the user account can inherit SharePoint roles through the linked employee. If the option is set, the user account inherits SharePoint roles through hierarchical roles, in which the employee is a member, or through IT Shop requests. |
| Administrator |
Specifies whether the user account is a site collection administrator. |
| Auditor |
Specifies whether the user account is a site collection auditor. |
