We are integrated to AD with BB.
each project name has 3 AD associated groups appropriately assigned:
proj1-RO
proj1-RW
proj1-OWN ( Admin)
each repo in proj1 has 3 groups in AD appropriately assigned:
proj1repo1-ro
proj1repo2-rw
proj3repo3-own (Admin)
A project owner user report if they place a user in proj1repo2-rw the user cannot access the repo, unless assigned to one of the proj1-XXX groups.
I was going to test this but thought I ask also , is this by design? If so , how can I give access to a repo and not the project in this scenario please? thanks.
What you see is per design. Project permissions controls who have access to the repositories within the project. So if a user do not have access to the project they will not be able to access the repository, even if they have full permission to it. See Using project permissions for more information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hoping the link will provide an alternate method to support goal , ie no way to read project or see it , albiet necessary membership necessary to get to a repo under it, unless the alternative is separate projects , so project and security boundaries are basically one in the same. not robust from agile stand point but does offer simplicity. -tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.