Understanding application permissions
The following table describes the various features supported by Risk Register and the permissions required to use those features.
Feature | Permission(s) required |
---|---|
Global administrator | |
Global administrator | |
Global administrator | |
Create risk registers AND (Global administrator OR Project administrator OR Browse projects) To create a new project and a new risk register based on that project, the user must be a Jira administrator. | |
Create risk registers AND permission to access the specified filter | |
N/A. This feature is no longer supported, having been replaced by filter-based risk registers. | |
Anybody. Risk registers will appear in the risk register list if the user has permissions as follows:
| |
Global administrator OR administrator of the risk register | |
Global administrator OR administrator of the risk register | |
Global administrator OR Risk register administrator. Note that the settings of multi-project risk registers cannot be changed. | |
Edit issues (project permission) | |
Edit issues (project permission) | |
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.