Recommendations? Folder Security vs New Repository

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
mikecausi
Posts: 20
Joined: Wed Mar 03, 2010 12:48 pm

Recommendations? Folder Security vs New Repository

Post by mikecausi » Wed Mar 16, 2016 12:27 pm

Can I get some feedback and recommendations of when to use Folder Security and when to create a new repository?

I have a single, significantly large repo and I would like to create a new top level folder for only a few people to access. I could enable Folder Security on the whole repo and then go in and assign permissions. I could also create a new repo for this content and then assign permissions.

Are there performance, maintenance, administration considerations that I should think about? I assume there is a good reason that folder security is OFF by default.

Please advise asap as we are trying to get off the ground with a new project asap. Thanks!

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Recommendations? Folder Security vs New Repository

Post by Beth » Wed Mar 16, 2016 1:12 pm

If the code being added doesn't need any kind of link with code already in the database, then it can have its own repository. More details about things to think about when deciding between a repository or folder are found in this KB article: http://support.sourcegear.com/viewtopic.php?p=5183.

Security set at the repository level is faster than folder level security.
Beth Kieler
SourceGear Technical Support

Post Reply