limit next-gen project access level

[Bert Pattyn]

How can I prevent as an admin that project managers create next-gen projects with an open or limited access level. Every project at our company needs to be private.

[Bert Pattyn]

Jack,

No, because Project Managers can create their own next-gen projects and as an admin, I want to prevent them to create projects with an access level other then 'private'.

[David]

This is exactly what I am trying to do. Did you resolve this Bert?

[Jack Brickey]

when you create the project you can select open/limited/private. does that not meet your needs?

[Jack Brickey]

brining it back into the one thread here...

So the fundamental principal of NG is to allow "anyone" to create and manage their own project w/o needing an admin. This will not change. If you want configurable permissions you should use Classic. if you are an admin and don't want to allow NG then you should disable this project template.

[Bert Pattyn]

I want them to create and manage projects, but I need to prevent that customer projects are public available on the internet.

So the only solution here is: education and faith?

[Jack Brickey]

your projects are open to the public by default? When I create an "anyone" project it is restricted to anyone w/ access to my companies domain. Disclaimer - i don't use NG for anyone projects but some of my users do.

You might want to give feedback to Atlassian via the Feedback link.

[Bert Pattyn]

Jack, the default is open (Anyone with access to <account> can create and edit issues.). This means that a customer who has an account and has access to 1 specific project gets full access to this new next-gen project (of another customer) if it is created with the default access setting. Not the default we want, because it makes things very error-prone.

Thanks, I'll contact Atlassian.

[Jack Brickey]

yes but I didn't consider "<account>" to be public. for example i have a NG test project in my companies instance but that doesn't mean you can access. it means any user currently defined in my Jira instance can access. 

[Bert Pattyn]

true. I hadn't explained it well. Sorry about that.