Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.

The following properties are used for mapping different user account types.

• Identity

  The Identity property (IdentityType column) is used to describe the type of user account.

  Table 19: Identities of user accounts

  Identity	Description	Value of the IdentityType column
  Primary identity	Employee's default user account.	Primary
  Organizational identity	Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.	Organizational
  Personalized admin identity	User account with administrative permissions, used by one employee.	Admin
  Sponsored identity	User account used for a specific purpose. For example, for training purposes.	Sponsored
  Shared identity	User account with administrative permissions, used by several employees.	Shared
  Service identity	Service account.	Service

  NOTE: To enable working with identities for user accounts, the employees also need identities. You can only link user accounts to which an identity is assigned with employees who have this same identity.

  The primary identity, the organizational identity, and the personalized admin identity are used for different user accounts, which can be used by the same actual employee to perform their different tasks within the company.

  To provide user accounts with a personalized admin identity or an organizational identity for an employee, you create subidentities for the employee. These subidentities are then linked to user accounts, enabling you to assign the required permissions to the different user accounts.

  User accounts with a sponsored identity, shared identity, or service identity are linked to pseudo employees that do not refer to a real employee. These pseudo employees are needed so that permissions can be inherited by the user accounts. When evaluating reports, attestations, or compliance checks, check whether pseudo employees need to be considered separately.

  For more information about mapping employee identities, see the One Identity Manager Identity Management Base Module Administration Guide.

• Privileged user account

  Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).

Default user accounts

Normally, each employee obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the employee. By default, the link between employee and SharePoint user account is set up through the authentication objects to which the user account is assigned. Alternatively, employees can also be directly linked to the user accounts. Such user accounts can be managed through account definitions. The effect of the link and the scope of the employee’s inherited properties on the user accounts can be configured through an account definition and its manage levels.

To create default user accounts through account definitions

1. Create an account definition and assign the Unmanaged and Full managed manage levels.

2. Specify the effect of temporarily or permanently disabling, deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.

3. Create a formatting rule for IT operating data.

   You use the mapping rule to define which rules are used to map IT operating data for user accounts and which default values are used if no IT operating data can be determined through a person's primary roles.

   The type of IT operating data required depends on the target system. The following setting are recommended for default user accounts:

   • In the mapping rules for the IsGroupAccount_SPSGroup and IsGroupAccount_SPSRLAsgn columns, use the default value 1 and set the Always use default value option.

   • In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.

4. Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.

   Specify in the departments, cost centers, locations, or business roles that IT operating data should apply when you set up a user account.

5. Assign the account definition to employees.

   When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.

Administrative user accounts

An administrative user account must be used for certain administrative tasks. Administrative user accounts are usually predefined by the target system and have fixed names and login names, such as Administrator.

Administrative user accounts are imported into One Identity Manager during synchronization.

You can label administrative user accounts as a Personalized administrator identity or as a Shared identity. Proceed as follows to provide the employees who use this user account with the required permissions.

• Personalized admin identity

  1. Use the UID_Person column to link the user account with an employee.

     Use an employee with the same identity or create a new employee.

  2. Assign this employee to hierarchical roles.

• Shared identity

  1. Assign all employees with usage authorization to the user account.

  2. Link the user account to a pseudo employee using the UID_Person column.

     Use an employee with the same identity or create a new employee.

  3. Assign this pseudo employee to hierarchical roles.

  The pseudo employee provides the user account with its permissions.

Privileged user accounts

Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).

To create privileged users through account definitions

1. Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.

2. If you want to prevent the properties for privileged user accounts from being overwritten, set the IT operating data overwrites property for the manage level to Only initially. In this case, the properties are populated just once when the user accounts are created.

3. Specify the effect of temporarily or permanently disabling or deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.

4. Create a formatting rule for the IT operating data.

   You use the mapping rule to define which rules are used to map IT operating data for user accounts and which default values are used if no IT operating data can be determined through a person's primary roles.

   The type of IT operating data required depends on the target system. The following settings are recommended for privileged user accounts:

   • In the mapping rule for the IsPrivilegedAccount column, use the default value 1 and set the Always use default value option.

   • You can also specify a mapping rule for the IdentityType column. The column owns different permitted values that represent user accounts.

   • To prevent privileged user accounts from inheriting the entitlements of the default user, define a mapping rule for the IsGroupAccount_SPSGroup and IsGroupAccount_SPSRLAsgn columns with a default value of 0 and set the Always use default value option.

5. Enter the effective IT operating data for the target system.

   Specify in the departments, cost centers, locations, or business roles which IT operating data should apply when you set up a user account.

6. Assign the account definition directly to employees who work with privileged user accounts.

   When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.