Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


In Portfolio does Plan Editor Permissions override Admin Permissions?

In Portfolio I have Admin permissions however I notice that for several plans if the Plan permissions are not setup to include me, my access is restricted to Read-only?
There appears to be no way to access the administration for these plans without expressly having been granted it by the plan creator which can become difficult if they are unavailable to do so.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 05, 2017

Hi Brendan,

When you say "admin" permissions are you referring to the admin permissions from JIRA itself?  If so the answer is yes:

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.

You can read more about the permissions in the Permissions in Portfolio for Jira knowledge base article.



I have admin privileges configured in both Jira and Portfolio but it seems I can still be locked out of individual Plans if not granted specific editor permissions for that specific plan.

In this particular instance the user who created the plan is away and we either need to wait for them to return or gain access to their specific account to update the permissions.

This seems odd to me but if its how it works currently I suppose we can look into the above workaround.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events