Roles
Last updated
Last updated
Roles are used for categorizing users in different ways and could be used for different purposes in Flow. Roles can for example be used to describe an organizational structure or to reflect different types of access groups.
A User can be connected to one or many Roles. In order to structure the roles, many different Role Trees can be created. There are two types of inheritance methods for each Role Tree; Inherit Children and Inherit Parent.
Workflows and inboxes are added into menus, roles are connected to menus, and users to roles in order to give users access to workflows and inboxes.
Select a role group from the list to view and edit the information or click on Add in the top-right corner of the roles list to add a new role group.
When a new role group is created, enter a Group id and a Group name.
If the Roles group should Inherit Children, check the check box (Inherit Parent is the default).
Click on the + button to add a new Role, a new role named New role will appear, rename the role by double-clicking the new role.
It is possible to add levels of roles, add another level by marking the role and clicking the + button, a new role named New role will be created. Double-click on the New role to rename.
Tips: Delete a role by marking the role to delete and tap delete on the keyboard.
Consider the following Role structure with a menu connected to each node, one menu assigned to node Stockholm, a second to Team 1 and a third to Team 2.
A user assigned to a role node will always get the menus assigned to the parent nodes up to the root.
A user in Team 1 gets the Team 1 menu and the menu for Stockholm. Depending on the checkbox for InheritChildren more menus might be added.
With InheritChildren checked, a user assigned to Team 1 would get the menu for Team 1 and Stockholm.
A user assigned to Stockholm would get the menu for Stockholm and its children, Team 1 and Team 2.
Let’s say that people in Team 1 sometimes work for Team 2, we can then change the inheritance to make the menus available both teams. If InheritChildren is unchecked a user assigned to Team 1 would get the menu for Team 1 and Stockholm but also for its sibling in Team 2.
It might be easier to think of the inheritance from the menu perspective, if you check Team 2 it will also check the Stockholm node. This means that a user in Team 1 will get all inherited menus in the Stockholm node, both Team 1 and Team 2.
If the role is set to Inherit Parent (InheritChildren unchecked) then the parent node Stockholm will automatically be included:
If InheritChildren is checked then no parent nodes will be included:
Connect the role to one or more menus and users, read more about menus and users here:
MenuUsers