Creating Roles and Groups using Policy Configurator UI
Set of textual constants that are used to separate users into different roles.
Roles can be created by adding Role Property and its Value in Policy Configurator as shown below:
This is used for setting Permissions for a block, which limits which users can see this block or access it via the API.
Note: Permissions do not affect the Block via Events.
Groups are separate sets of documents access , which can be limited to users who are members of the group.
Note: A user can be included into any number of groups with a single role within each. User roles can be different in different groups.
The name of the group
Role which is assigned to the creator of the group
The list of roles which can be assigned to members of the group
· Single – only a single user can be included in the group. This type is maintained for backward compatibility with historic policy versions.
· Multiple – the group can include multiple users. This is the new mode of operation.
· Global – static group is created at the start. The creator of the group is the creator of the policy.
· Private – a new instance of the group is created every time a user selects group creation action. The creator of the group is the user who executed the group creation action.
documentsSourceAddon has multiple filters which allow us to select relevant documents
Owned by User
Owned by Group
Documents are not filtered by Owner.
Only documents created by the current user (in all groups)
Only documents created in the current group (by all users)
Only documents created by the current user in the current group
When a policy contains multiple groups, users have an option to switch between those they are included in. The selection menu also allows to switch to the ‘no group’ default state, i.e. the state in which the user is not acting as a member of any group.