Creating and using Roles
Last updated
Last updated
For a demo example of following steps, here is the policy timestamp: 1675164531.823309003
Switch to the Roles tab
Create 2 new roles called βExample role 1β and βExample role 2β
In the root container create 4 more βinterfaceContainerBlockβ container called βno_roleβ, βownerβ, βrole_1β and βrole_2β
Note: By default all containers would have βAny Roleβ set and thus they would be visible to all users (with all roles)
Change the βPermissionsβ properties in each container in the following way:
no_role: No Role
owner: Owner
role_1: Example role 1
role_2: Example role 2
This would result in the following visibility of containers:
The first container (called βno roleβ) would be visible only to new users which have no role assigned to them
The βownerβ container would be visible only to the Standard Registry which created (or imported) this policy
The βrole 1β container would be visible only to users with βExample role 1β
The βrole 2β container would be visible only to users with βExample role 2β
Add a βpolicyRolesBlockβ to the βno_roleβ container and name it βchoose_roleβ
Since this block is located inside the container βno_roleβ which has βNo roleβ permission setting it would only be visible to new users without an assigned role.
The βAvailable Rolesβ property allows to configure which roles would be available to users to chose from at this stage of the Policy workflow
Select βExample role 1β and βExample role 2β
Add βinformationBlockβ to other containers just to display results
New users would end up on the policy choice form upon entering the policy
After the selection of the role users would see only 1 container corresponding to their roles
The owner of the Policy (the Standard Registry user) upon executing the policy would skip the role selection form and would immediately end-up in the corresponding container