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 - Getting issue details... STATUS for more details.

You need both global permission and user permission to perform tasks in Portfolio for Jira.


The permissions in Portfolio for Jira will take precedence over the global permissions that are set up in your Jira instance.


You need to configure user permissions, to ensure that users have access to the correct plans and programs in Portfolio for Jira, as necessary.

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


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


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


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.


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.


  • 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)

権限の計画Program permissionAdd plan to programView plan in programRemove plan from program

Note that Portfolio for Jira administrators are able to grant themselves the View and Edit permissions for plans and programs.

最終更新日 2020 年 6 月 10 日


Powered by Confluence and Scroll Viewport.