The GIRI Role Management feature was released in December 2024 and is an optional module, that might not be included in your plan. If you're interested in testing or adding it to your organisation, please reach out to [email protected] or contact us here in the chat.

The role management system extends across two levels:

To prevent the need to assign permissions individually to each user for every project, the groups are used to regulate access. The new aspect is that each user within their group now also takes on a specific role.

A user can only have one specific role in the organisation (Organisational role), but with the “Role Management” feature enabled, users can have various Project Roles and thus permissions in different groups. So to every group a user gets assigned to, they need a permission set which is bundled up as a Project role. This permissions apply to all instructions of all projects inside this group as well.

The best way to make use of this feature, is to create appropriate roles on the organisation level first (or use the existing roles). It would be best practice to indicate the role type (organisational role vs. project role) in the role name. Eg Org-name-of-role, to indicate, that it is an org-role and Proj-name-of-role, to indicate that it is a project role.

Here are 2 screenshots, 1 of each role type:

1-Organisational roles:

​

2-Project roles:

Notice that in the screenshot of 2-project roles you can see a common use case, where these 2 users have only very limited access rights to grant the approvals of instructions.

The role management is explained by us in the bootcamp #5. You can find out more about the bootcamps here: Bootcamps.
If you have further questions regarding the role management, please don't hesitate to contact us.