jstarrdewar Posted April 26, 2016 Report Share Posted April 26, 2016 So I'm following these instructions: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide.shtml But I have a problem--- When I add people to my cloud organization they start with Developers permissions, which allows them access to all of my repositories. The only way I've been able to block people from repositories is to add them or their group to the repo permissions and then Deny Permissions. But that's the opposite of the default behavior that I want, especially because I have this situation: Devlopers A, B and C belong to Group A and should have access to Repo A Developers B and C also belong to Group B should have access to Repo B but also Repo A But it seems like if I deny permissions of Group B to Repo A then my guys in Group A get blocked too. What am I doing wrong? Link to comment Share on other sites More sharing options...
manu Posted May 6, 2016 Report Share Posted May 6, 2016 Hi! You just need to "not allow, not deny" the "view" permission instead of actively denying it. That will prevent users to see the repositories where the group is not having the permission actively granted. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.