Permissions in Portfolio for Jira
We'll soon be introducing some changes for plan access in Portfolio for Jira.
When these changes are implemented, the following will be able to access all private plans: users with the Portfolio for Jira administrator user permission, users with the Jira administrators global permission, Jira administrators, and system administrators.
We recommend you start ensuring that your private plans are not displaying any confidential data. See JPOSERVER-247 - Jira project doesn't exist or you don't have permission to view it. for more details.
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 | Can perform all administrative functions in Portfolio for Jira, including accessing any private plans. By default, Jiraadministrators are automatically made administrators in Portfolio for Jira. |
Portfolio for Jira user | Can perform the following actions:
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'll still need this permission to view and add the 'Beta' plan to that program. |
Portfolio for Jira restricted user | Can perform the actions available to Portfolio for Jira users. However, users with this role are not permitted to update issues in Jira projects from within Portfolio for Jira. |
Portfolio for Jira viewer | Can perform the following actions:
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 | Can access and use the features of Portfolio for Jira that are in Labs mode |
| Shared team management | Can access global team management and edit teams that are shared across plans and programs in Portfolio for Jira |
Plan permissions
The following plan permissions are available in Portfolio for Jira:
| Plan permission | View plan | Edit plan | Modify issues in plan | Delete plan |
| Edit |  | | | |
| View | | (only for specific actions) | (only for specific actions) |  |
See Permissions for more details.
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 plans and programs.