The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Fine granular project permissions
I am aware of this: https://confluence.atlassian.com/bitbucketserverkb/4-levels-of-bitbucket-server-permissions-779171636.html however I am wondering if there is a way to provide more granular permissions or there is a plan to implement such a thing?
Especially in a corporate environment, when you have certain policies to be followed you would like to avoid that anybody messes with security relevant settings like "Merge checks", "project Permissions" and "Branch Permissions", "Branching Model" or even "Branching Strategies"
I would like to have project admins who could create repos by their own and also manage the reviewers list without being able to touch security relevant settings, which could be only managed by "Admins".
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.