When you assign a group to an IT Shop shelf, it can be requested by the shop customers. To ensure it can be requested, further prerequisites need to be guaranteed:
-
The group is not a dynamic group.
-
The group must be labeled with the IT Shop option.
-
The group must be assigned a service item.
TIP: In the Web Portal, all products that can be requested are grouped together by service category. To make the group easier to find in the Web Portal, assign a service category to the service item.
-
If you only want the group to be assigned to employees through IT Shop requests, the group must also be labeled with the Use only in IT Shop option. Direct assignment to hierarchical roles or user accounts is no longer permitted.
NOTE: With role-based login, the IT Shop administrators can assign groups to IT Shop shelves. Target system administrators are not authorized to add groups to IT Shop.
To add a group to the IT Shop.
-
In the Manager, select the HCL Domino > Groups (non role-based login) category.
- OR -
In the Manager, select the Entitlements > Notes groups (role-based login) category.
-
In the result list, select the group.
-
Select the Add to IT Shop task.
-
Select the IT Shop structures tab.
-
In the Add assignments pane, assign the group to the IT Shop shelves.
- Save the changes.
To remove a group from individual shelves of the IT Shop
-
In the Manager, select the HCL Domino > Groups (non role-based login) category.
- OR -
In the Manager, select the Entitlements > Notes groups (role-based login) category.
-
In the result list, select the group.
-
Select the Add to IT Shop task.
-
Select the IT Shop structures tab.
-
In the Remove assignments pane, remove the group from the IT Shop shelves.
- Save the changes.
To remove a group from all shelves of the IT Shop
-
In the Manager, select the HCL Domino > Groups (non role-based login) category.
- OR -
In the Manager, select the Entitlements > Notes groups (role-based login) category.
-
In the result list, select the group.
-
Select the Remove from all shelves (IT Shop) task.
- Confirm the security prompt with Yes.
-
Click OK.
The group is removed from all shelves by the One Identity Manager Service. All requests and assignment requests with this group are canceled.
For more information about requesting company resources through the IT Shop, see the One Identity Manager IT Shop Administration Guide.
Related topics
To react quickly to special requests, you can assign groups directly to user accounts. This task is not available for dynamic groups.
To assign user accounts directly to a group
-
In the Manager, select the HCL Domino > Groups category.
-
Select the group in the result list.
-
Select the Assign members task.
-
Select the User tab.
-
In Add assignments pane, assign user accounts.
- (Optional) To filter the user accounts, select a domain in the Notes domains input field.
TIP: In the Remove assignments pane, you can remove assigned user accounts.
To remove an assignment
- Save the changes.
Related topics
Groups can be assigned directly or indirectly to a user account. Indirect assignment is carried out by allocating the employee and groups in hierarchical roles, such as departments, cost centers, locations, or business roles. If the employee has a Notes user account, groups in the hierarchical roles are inherited by this user account.
To react quickly to special requests, you can assign groups directly to the user account. You cannot directly assign groups that have the Only use in IT Shop option.
To assign groups directly to user accounts
-
In the Manager, select the HCL Domino > User accounts category.
-
Select the user account in the result list.
-
Select the Assign groups task.
-
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.
User accounts cannot be manually added to dynamic groups. You can assign user accounts additionally to dynamic groups using the additional list.
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 (NDOGroupInGroup table).
The effectiveness of the assignments is mapped in the NDOUserInGroup and BaseTreeHasNDOGroup tables by the XIsInEffect column.
Example: The effect of group memberships
- The groups A, B, and C are defined in a domain.
- 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 domain. 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 18: Specifying excluded groups (NDOGroupExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 19: 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 20: 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 domain
To exclude a group
-
In the Manager, select the HCL Domino > 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.
.