Understanding application permissions

The following table describes the various features supported by Risk Register and the permissions required to use those features.

FeaturePermission(s) required

View application settings

Global administrator

Change application settings

Global administrator

Change the risk model

Global administrator

Create a project-based risk register

Create risk registers AND Browse projects (project permission)

Create a filter-based risk register

Create risk registers AND permission to access the specified filter

Create a multi-project risk register

N/A. This is a legacy feature and no longer supported

View the list of risk registers

Anybody. Risk registers will appear in the risk register list if the user has permissions as follows:

  • For project-based risk registers, the user must be a global administrator, a project administrator, or have Browse projects permission.

  • For filter-based risk registers, the user must be able to view the specified filter.

  • For multi-project risk registers, the user must be a global administrator or have permission to administer or browse all of the included projects.

Delete a risk register

Global administrator OR administrator of the risk register

View risk register settings

Global administrator OR administrator of the risk register

Change risk register settings

Global administrator OR Risk register administrator. Note that the settings of multi-project risk registers cannot be changed.

Add risk assessments to issues

Edit issues (project permission)

Change risk assessments

Edit issues (project permission)

Remove risk assessments

Edit issues (project permission)

An expired license will still allow users to view risks and risk registers, but will not allow changes to settings, risk registers, nor risk assessments.