Global permissions configuration
Administering the classic plans
On this page
Related content
- Installing Java for Confluence
- Setting the JAVA_HOME Variable in Windows
- How to switch from the bundled JRE to System Java when using Confluence as Windows Service
- How to use system Java instead of the bundled JRE
- Confluence Service stops after a few seconds; Confluence Service won't start
- Start Confluence Automatically on Windows as a Service
- Windows Service failed to be created due to JAVA_HOME environment variable configuration
- Confluence Cannot Start Due to 'Unsupported major.minor version 49.0'
- Upgrade to Confluence 5.8.x failed due to Unsupported major.minor version 52.0 (unable to load class com.atlassian.confluence.setup.ConfluenceConfigurationListener)
- Unable to start Windows Service due to "Failed creating java jvm.dll" "The specified module could not be found"
This page refers to Portfolio classic plans. If you are currently running Portfolio 2.0, please check this link to access the latest page version.
Configuring Jira permissions to manage Portfolio for Jira
A Portfolio for Jira administrator can grant access to the add-on by using Jira applications global permissions.
Configuring Portfolio for Jira permissions
The classic plan permission option allows you to configure the user's access at a plan level. Note that permission settings at the plan level take precedence over global permission settings.
- You can configure the user groups' permissions by going to the main Jira menu bar and selecting Portfolio > Administration.
Click Add and choose the user group you would like to add for the type of role.
If you want to create additional user groups, see Managing groups.
Permission | Description |
---|---|
Portfolio Administrator | Ability to perform all administration functions in Portfolio for Jira. Jira administrators are automatically Portfolio for Jira administrators. |
Portfolio User | Ability to create, view and edit plans.
|
Portfolio Restricted User (It only applies to Portfolio for Jira 1.0) | 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 |
Portfolio Viewer | Ability to browse and view plans in read-only mode. |
Portfolio LABS Access | Ability to access and use Portfolio features that are in LABS mode. |
Shared Team Management | Ability to access global team management and edit teams which are shared across plans in Portfolio for Jira. |
Related content
- Installing Java for Confluence
- Setting the JAVA_HOME Variable in Windows
- How to switch from the bundled JRE to System Java when using Confluence as Windows Service
- How to use system Java instead of the bundled JRE
- Confluence Service stops after a few seconds; Confluence Service won't start
- Start Confluence Automatically on Windows as a Service
- Windows Service failed to be created due to JAVA_HOME environment variable configuration
- Confluence Cannot Start Due to 'Unsupported major.minor version 49.0'
- Upgrade to Confluence 5.8.x failed due to Unsupported major.minor version 52.0 (unable to load class com.atlassian.confluence.setup.ConfluenceConfigurationListener)
- Unable to start Windows Service due to "Failed creating java jvm.dll" "The specified module could not be found"