Manually linking identities to Google Workspace user accounts
An identity can be linked to multiple Google Workspace user accounts, for example, so that you can assign an administrative user account in addition to the default user account. One identity can also use default user accounts with different types.
To manually assign user accounts to an identity
-
In the Manager, select the Identities > Identities category.
-
Select the identity in the result list and run the Assign Google Workspace user accounts task.
-
Assign the user accounts.
- Save the changes.
Related topics
Supported user account types
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 type
The Identity type property (IdentityType column) is used to describe the type of user account.
Table 14: Identity types of user accounts
Primary identity |
Identity's default user account. |
Primary |
Organizational identity |
Secondary user account used for different roles in the company, for example for subcontracts with other functional areas. |
Organizational |
Personalized administrator identity |
User account with administrative permissions, used by an identity. |
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 multiple identities. |
Shared |
Service identity |
Service account. |
Service |
-
Privileged user account
Privileged user accounts are used to provide identities 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).
Detailed information about this topic
Default user accounts
Normally, each identity obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the identity. The effect of the link and the scope of the identity’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
-
Create an account definition and assign the Unmanaged and Full managed manage levels.
-
Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships at each manage level.
-
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 an identity'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_Group, IsGroupAccount_PaSku, and IsGroupAccount_OrgAdminRole 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.
-
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.
-
Assign the account definition to identities.
When the account definition is assigned to an identity, a new user account is created through the inheritance mechanism and subsequent processing.
Related topics
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.
NOTE: Some administrative user accounts can be automatically identified as privileged user accounts. To do this, in the Designer, enable the Mark selected user accounts as privileged schedule.
Related topics