Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article contains:

Table of Contents

1. Overview

This section allows you to define the key projects for Project Risks (as part of the Project Risk Register).

  • STEP 1: Go to Menu > Administration > Projects. All existing projects will appear on the left hand side listing. If you have Camms.Project, this will pull through the list of projects added and available from Camms.Project as well. Any projects added/updated from either side will be synced with the other side as well. 

  • STEP 2: You can search the project you are looking for by either using the 'Search' entering the project title/code or the project owner as per the option you select from the dropdown list available below. Any closed projects can be hidden from 'Hide Closed' option in the list as well.

  • STEP 3: Add the details of the project and click on the Add button to define a new project.

Below details can be added for a project. 




Project Code

The unique identifier for the project. This will be editable for the administrator when risk is in standalone mode but if you have Camms.Project, the code will follow any sequence configurations done from Camms.Project


Project Type

Specify the type the project belongs to. This will not be available for Camms.Risk standalone mode but if Camms.Project is available, all project types configured from Camms.Project will be displayed here 


Project Title

Specify the title of a project.


Responsible Officer

Select from the pre-defined ‘STAFF’ records in the drop down list. The person selected here will be the one that is responsible for the project, however within Camms.Risk there is no updating mechanism for the specific project. Please contact CAMMS if you wish to explore camms- planning solution for the managing and updating of projects.



The status of the project (Open/Closed). 


The new project will appear on the left hand side of the screen and also allows you to create Project Risks now within this project to manage.

1.1 Add Project Specific Permissions for Project Risks


Note: This feature applies only to users using a standard security framework (not to users using the flexible security model.

This will let you to restrict the Register, Dashboard, and EIS view of users based on the Projects linked to. 

  • Enable this feature by checking the ‘Enable Project Specific Permission’ setting via Administration > Configuration > Settings.

  • An icon to assign permission for each project will appear under the Project creation area in the Risk accessed via Administration > Projects.

  • The below mentioned user roles can be assigned by clicking the person icon which appears in front of each project.

    • Project Owner – You have to assign a staff member at the point of creating a project. Project Owner has the ability to create/edit/delete project risks linked to an assigned project.

    • Risk Editor – A Risk Editor will have the ability to edit project risks for which permissions are given.

    • Risk Viewer – A Risk Viewer has the ability to only view the project risks for which permissions are given.

  • Standard user permissions such as Administrator, Risk Manager, Project Risk Editor, Project Risk Coordinator, Project Risk Viewer, does not need to be assigned for these Project Roles to function.

1.2 Viewing Linked Project Risks in Project Risk Register

  • To view project risks linked to respective projects in the Project Risk Register, either one of the Project Owner, Risk Editor, and Risk Viewer permission, must be assigned.


Note: This would work only if standard user permissions are not assigned.

  • To view project risks linked to respective projects in EIS and Dashboards, either one of the Project Owner, Risk Editor, or Risk Viewer permissions has to be assigned. Additionally, the ‘Executive Intelligence’ permission requires to be assigned via Administration > Manage Users.



In the following instances, the standard user permissions will supersede the project role permissions: 

  • Users with ‘Administration’, ‘Risk Manager’ and ‘Project Risk Editor’ permissions assigned via Administration > Manage Users, in addition to any of these project roles, the user can create/edit/delete project risks irrespective of the project which they are assigned to.

  • Users with ‘Project Risk Viewer’ permission given via Administration > Manage Users for any of the roles, can view all the project risks in risk registers, irrespective of the project which they are assigned to.

Image RemovedUG Footer 2024-20240103-072111.pngImage Added