Configuring Risk access roles
Who is this article for?Administrators and Managers who want to learn how to configuring Risk access roles.
Administrator permissions are required.
Risk Access roles are pivotal in managing and controlling access to sensitive information within organisations. These roles are designed to strike a balance between enabling necessary business operations and mitigating potential security risks associated with data access.
1. Risk access roles
Users are given different permission levels based upon their access requirements. Permissions for all Lucidity applications are set via Lucidity Access and are generally configured by the system administrator. The standard roles typically provided in all new Lucidity system builds are as follows. These can be edited by system administrators as required.
|
User role |
Role description |
|---|---|
|
Read Only |
Using Risk, a user can view project risk registers and manage own actions. |
|
Manager |
Using Risk, a user can manage, archive and delete project registers, run reports, use dashboard widgets and manage actions. |
|
Administrator |
Administrator role for Risk. |
1.1. Read only
End-users may be given read only to Lucidity Risk in order to allow them to view project risk registers and run reports. These users will be able to perform the following tasks for the projects they have access to:
- View project risk registers at the high level only (no editing permissions).
- Run reports.
The menu and tab options relevant for base users are:
- Risk Registers menu.
- Reports menu.
- Actions tab.
1.2. Manager
Managers, with correct scoping applied, will only be able to view the project risk registers from specified organisational areas. Generally, they will be able to perform the following tasks for the projects they have access to:
- Create, edit and delete project risk registers.
- View, add, edit or delete individual risks in the project risk register (does not impact master risks).
- Run reports.
- Create individual dashboards.
The menu and tab options relevant for project managers are:
- Risk register menu.
- Archived risk register menu.
- Reports menu.
- Actions tab.
- Dashboards tab.
1.3. Administrator
Administrators will generally have access to all functionality within the system. In addition to the same functionality as managers, administrators can also:
- Create, edit and delete master risks.
- Create, edit and delete risk templates.
- Access risk dashboards and templates.
- Access all menu and tab options.
2. Retaining System Integrity
Only the administrator has the permission to manage master data such as master risks and managed lists. It is recommended that the number of administrators per instance of Lucidity Software is kept to a minimum to retain integrity and consistency across the system configuration and to avoid duplication. It is a worthwhile exercise to create a standard set of guidelines that all new master data entered must follow.