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! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to lock settings so only system admins can change them?

s
December 9, 2014

Because of PCI 3 compliance, my management team wants us to dictate that all teams use a workflow that does not allow direct pushes to any repo and requires that all groups and projects use pull requests and code reviews to merge code into master or release branches.

Is there a way to set this universally? Or is there a way to lock settings in repositories so that only system administrators (rather than project administrators) can change them?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
jpoh
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 27, 2015

Stash has three 'tiers' of permissions, where you can set global, project-level or repo-level administration, read and write access to your repositories. You can also set up branch-specific permissions to prevent pushes by certain users/groups to specific branches.

It sounds like you want write-access to certain branches but only allow merges to master or release branches via pull request. We have an open feature request for this functionality, which you can vote for and watch for updates on our progress - https://jira.atlassian.com/browse/STASH-2910

TAGS
AUG Leaders

Atlassian Community Events