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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Prevent outside vendors from accessing next-gen project with limited permissions


We use Jira for our internal projects as well as to coordinate with some outside vendors. By default, we used groups and permissions to so that new "classic" projects are accessible to all internal users (jira-software-users group), and groups of outside vendors (each vendor with their own group) would be added to specific projects as necessary.

With next-gen projects this is broken. We only have "open," "limited," and "private" as permission options for next-gen projects. Both "open" and "limited" allow viewing for all users, with no way that I can find to block specific users/groups. So the only option remaining is private, which means that every specific user has to be invited. As far as I can tell there's no way with next-gen projects to allow our pre-existing permission scheme.

Right now I've had to disable next-gen projects entirely as individual users are creating them and not locking down the permissions appropriately to block outside people.

Any suggestions?

1 answer

1 accepted

0 votes
Answer accepted
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 03, 2019

Hello Adam,

Thank you for getting in touch with Atlassian Community!
Currently, it's not possible to manage permissions on next-gen projects. We have a feature request suggesting the implementation of this ability:
In line with our Feature Request Policy, we'd suggest you vote for it as well as setting yourself as a watcher in order to hear about updates on the development cycle.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events