Permissions in Portfolio for Jira
You need both global permission and user permission to perform tasks in Portfolio for Jira.
Global permissions
The permissions in Portfolio for Jira will take precedence over the global permissions that are set up in your Jira instance.
User permissions
You need to configure user permissions, to ensure that users have access to the correct plans and programs in Portfolio for Jira, as necessary.
| Permission | Details |
|---|---|
Portfolio for Jira administrator | Ability to perform all administrative functions in Portfolio for Jira. By default, Jira application administrators are automatically made administrators in Portfolio for Jira. |
Portfolio for Jira user | Ability to create, view, and edit public plans and programs. Note that this permission at both the program level and the plan level are independent of each other. This means that even if you can edit the 'Mobile expansion' program, you still need this permission to view and add the 'Beta' plan to that program. |
Portfolio for Jira viewer | Ability to browse and view plans in read-only mode. Note that this permission at both the program level and the plan level are independent of each other. This means that even if you can view the 'Mobile expansion' program, you still need this permission for a particular plan to view that plan in the 'Mobile expansion' program. |
Portfolio for Jira Labs | Ability to access and use the features of Portfolio for Jira that are in Labs mode |
Portfolio for Jira restricted user | Includes all of the abilities of the Portfolio for Jira user; however, users with this role are not permitted to update issues in Jira projects from within Portfolio for Jira. |
| Shared team management | Ability to access global team management and edit teams that are shared across plans and programs in Portfolio for Jira |
Plan permissions
The permissions in Portfolio for Jira take precedence over the permissions in your Jira application. This means that even if you're a project administrator in your Jira application, you'll still need specific permissions in to perform specific actions with the plans in Portfolio for Jira.
The following plan permissions are available in Portfolio for Jira.
| Plan permission | View plan | Edit plan | Delete plan | Modify issues in plan |
|---|---|---|---|---|
| Viewers |  |  | | |
| Editors | | | | |
Program permissions
By default, all Portfolio for Jira users in your Jira application instance can view and edit a newly created program. However, as soon as view permissions (Portfolio for Jira viewer) or edit permissions (Portfolio for Jira user) for that program are assigned to any user, the program then becomes restricted to that specific user.
Note the following details:
- If you don't have view permissions for a program, you won't be able to see that program in Portfolio for Jira.
- To add a plan to a program, you must have view permissions for that plan.
- If you can view a program, but you don't have view permissions for a plan, you won't see the plan or any issues from that plan in Portfolio for Jira.
The following table lists how user permissions work when you're performing specific actions involving plans and programs.
| User permission | Actions when configuring a program (at the program level) | |||
|---|---|---|---|---|
| Plan permission | Program permission | Add plan to program | View plan in program | Remove plan from program |
| None | None | | | |
| View | None | | | |
| Edit | None | | | |
| None | View | | | |
| View | View | | | |
| Edit | View | | | |
| None | Edit | | | |
| View | Edit | | | |
| Edit | Edit | | | |
Note that Portfolio for Jira administrators are able to grant themselves the View and Edit permissions for public plans and programs.