Activation or deactivation of roles to a project

[oosterop]

It's clear that Roles are made at account level. But for certain project we need only a part of the roles to be activated.
So, an option to activate or deactivate a role to a project is needed. When setting up the project the Account admin can validate the roles that should be activated for this certain project. By default all roles can be activated, so only the roles this project doesn't need to have, can be deactivated.

For example, we have a confidential project with confidential roles in it, the project admin will see all roles when adding users, also roles for projects they are not allowed to see. Also in the transmittal tool, all users can see all roles and companies.

[oosterop]

In other words 😛

Role Activation or Deactivation for Projects

It is evident that roles are established at the account level. However, for specific projects, it becomes necessary to activate or deactivate certain roles as per project requirements. To address this, we propose an option that allows project-specific role management. During project setup, the Account Admin can review and validate the roles that should be activated for that particular project. By default, all roles are active, and only the roles unnecessary for the project can be deactivated.

For instance, let's consider a confidential project with specific confidential roles. When the project admin adds users, they will have visibility of all roles, including roles intended for projects they are not allowed to access. Similarly, in the transmittal tool, all users can see all roles and all companies in the account (not per project).

To ensure proper role management for each project, the Account Admin will have the authority to enable or disable roles according to project requirements. This feature will enhance project-specific access and confidentiality, ensuring that only relevant roles are active for each project.