Branches and Security

[NigeNZ]

Hi,
I'm currently reviewing Vault for use in our company (around 10 developers) and one feature we may need I can't seem to work out.

We have a set of core libraries that sadly some of the developers occasionally modify when they shouldn't. What we'd like to do is to be able to lock the core trunk down to only a certain few but allow everyone to be able to branch from that trunk and modify the code (and submit their changes for review back to the trunk).

However it looks like Vault copies the trunk folder permissions (which is sensible) meaning our junior developers do not have permission to modify the Branch they just created.

Is there anyway to override this behavior?

Thanks

[Beth]

If you have folder permissions turned on, you can specifically give those junior developers only access to the branch. What might make the most sense is to not make a branch every time they are to work on it, but to just make one branch that always stays that way that those people would have access to.

[jclausius]

Another option may be to actually pin the top level folder. This won't stop anyone from unpinning and modifying folder changes, but at least it would be an operation you could monitor.

[Brody]

You could also set the permissions at a higher level so that the file you are sharing is using inherited permissions only. When you share it to a new location it inherits the permissions there instead.