To react quickly to special requests, you can assign entitlements directly to a user account. You cannot directly assign permissions that have the Only use in IT Shop option set.
To assign entitlements directly to a user account
-
In the Manager, select the Google Workspace > User accounts category.
-
Select the user account in the result list.
-
Select one of the following tasks.
-
Assign groups
-
Assign products and SKUs
-
Admin role designations
-
In the Add assignments pane, assign the entitlements.
TIP: In the Remove assignments pane, you can remove assigned entitlements.
To remove an assignment
- Select the entitlement and double-click
.
- Save the changes.
Related topics
To add all user accounts of a customer as members in a Google Workspace group, assign the groups directly to the Google Workspace customer. In the calculation of inheritance, for all user accounts of the customer, an entry is made in the GAPUserInGroup table. The origin of the assignment is indicated in the XOrigin column with the value 16.
To assign groups directly to a customer
-
In the Manager, select the Google Workspace > Google Workspace customers category.
-
Select the customer in the result list.
-
Select Assign groups category.
-
In the Add assignments pane, assign the groups.
TIP: In the Remove assignments pane, you can remove the assignment of groups.
To remove an assignment
- Save the changes.
Related topics
To add all user accounts of a customer as members in a Google Workspace group, assign the Google Workspace customers directly to the group. In the calculation of inheritance, for all user accounts of the customer, an entry is made in the GAPUserInGroup table. The origin of the assignment is indicated in the XOrigin column with the value 16.
To assign customers directly to a group
-
In the Manager, select the Google Workspace > Groups category.
-
Select the group in the result list.
-
Select Assign Google Workspace customer as member.
-
Assign the customers in the Add assignments view.
TIP: In the Remove assignments pane, you can remove assigned customers.
To remove an assignment
- Select the customer and double-click .
- Save the changes.
Related topics
When groups are assigned to user accounts an employee may obtain two or more groups, which are not permitted in this combination. To prevent this, you can declare mutually exclusive groups. To do this, you specify which of the two groups should apply to the user accounts if both are assigned.
It is possible to assign an excluded group at any time either directly, indirectly, or with an IT Shop request. One Identity Manager determines whether the assignment is effective.
NOTE:
- You cannot define a pair of mutually exclusive groups. That means, the definition "Group A excludes group B" AND "Group B excludes groups A" is not permitted.
- You must declare each group to be excluded from a group separately. Exclusion definitions cannot be inherited.
- One Identity Manager does not check if membership of an excluded group is permitted in another group (GAPGroupInGroup table).
The effectiveness of the assignments is mapped in the GAPUserInGroup and GAPBaseTreeHasGroup tables by the XIsInEffect column.
Example: The effect of group memberships
- The groups A, B, and C are defined in a customer.
- Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.
Clara Harris has a user account in this customer. She primarily belongs to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to her secondarily. Without an exclusion definition, the user account obtains all the permissions of groups A, B, and C.
By using suitable controls, you want to prevent an employee from obtaining authorizations of groups A and group B at the same time. That means, groups A, B, and C are mutually exclusive. A user, who is a member of group C cannot be a member of group B at the same time. That means, groups B and C are mutually exclusive.
Table 19: Specifying excluded groups (GAPGroupExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 20: Effective assignments
|
Ben King |
Marketing |
Group A |
|
Jan Bloggs |
Marketing, finance |
Group B |
|
Clara Harris |
Marketing, finance, control group |
Group C |
|
Jenny Basset |
Marketing, control group |
Group A, Group C |
Only the group C assignment is in effect for Clara Harris. It is published in the target system. If Clara Harris leaves the "control group" business role at a later date, group B also takes effect.
The groups A and C are in effect for Jenny Basset because the groups are not defined as mutually exclusive. If this should not be allowed, define further exclusion for group C.
Table 21: Excluded groups and effective assignments
|
Jenny Basset
|
Marketing |
Group A |
|
Group C
|
|
Control group |
Group C |
Group B
Group A |
Prerequisites
-
The QER | Structures | Inherite | GroupExclusion configuration parameter is set.
In the Designer, set the configuration parameter and compile the database.
NOTE: If you disable the configuration parameter at a later date, model components and scripts that are not longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide.
-
Mutually exclusive groups belong to the same customer.
To exclude a group
-
In the Manager, select the Google Workspace > Groups category.
-
Select a group in the result list.
-
Select the Exclude groups task.
-
In the Add assignments pane, assign the groups that are mutually exclusive to the selected group.
- OR -
In the Remove assignments pane, remove the groups that are no longer mutually exclusive.
- Save the changes.
