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 SharePoint Online > User accounts category.
-
Select the user account in the result list.
-
Select one of the following tasks.
-
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
In order for SharePoint Online user accounts to obtain permissions for individual websites, assign SharePoint Online roles to the groups. SharePoint Online roles and groups must belong to the same site collection.
NOTE: SharePoint Online roles with the Hidden option that reference permission levels, cannot be assigned to groups.
To assign SharePoint Online roles to a group
-
In the Manager, select the SharePoint Online > Groups category.
-
Select the group in the result list.
-
Select the Assign SharePoint Online roles task.
-
In the Add assignments pane, assign the roles.
TIP: In the Remove assignments pane, you can remove assigned roles.
To remove an assignment
- Save the changes.
Related topics
In order for SharePoint Online user accounts to obtain permissions for individual websites, assign SharePoint Online roles to the groups. SharePoint Online roles and groups must belong to the same site collection.
NOTE: SharePoint Online roles with the Hidden option that reference permission levels, cannot be assigned to groups.
To assign groups to a SharePoint Online role
-
In the Manager, select the category SharePoint Online > Roles.
-
Select the role 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.
Related topics
When groups are assigned to user accounts an identity 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.
The effectiveness of the assignments is mapped in the O3SUserInO3SGroup and O3SBaseTreeHasGroup tables by the XIsInEffect column.
Example: The effect of group memberships
- Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.
Jo User1 has a user account in this site collection. They primarily belong to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to them 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 identity 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 12: Specifying excluded groups (O3SGroupExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 13: Effective assignments
|
Pat Identity1 |
Marketing |
Group A |
|
Jan User3 |
Marketing, finance |
Group B |
|
Jo User1 |
Marketing, finance, control group |
Group C |
|
Chris User2 |
Marketing, control group |
Group A, Group C |
Only the group C assignment is in effect for Jo User1. It is published in the target system. If Jo User1 leaves the "control group" business role at a later date, group B also takes effect.
The groups A and C are in effect for Chris User2 because the groups are not defined as mutually exclusive. If this should not be allowed, define further exclusion for group C.
Table 14: Excluded groups and effective assignments
|
Chris User2
|
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 no 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 site collection.
To exclude a group
-
In the Manager, select the SharePoint Online > 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.
