Shared files and Checkout/Modify permissions question

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

Moderator: SourceGear

Post Reply
NULL

Shared files and Checkout/Modify permissions question

Post by NULL » Tue Aug 03, 2004 9:54 am

Hi all. I have a general question about the vault.

We are currently splitting a big project into smaller pieces (modules). Each module project contains a few source files, lets call them X and Y for now, although there can be more. This module is not a standalone compilable project, but rather just the source for this piece of the full project.

A module can then be shared into one or more projects. So for example say we have the following two projects and module:

Code: Select all

Project 1                Project 2               Module
   A                         E                     X
   B                         F                     Y
   C                         G
   D                         X
   X                         Y
   Y
The problem is that if a programmer is working inside Project 1, they may make a modification to XY that breaks other projects that depend on XY. They have no good way of knowing that XY is shared code and the rest is local code.

We want to instead deny everyone checkout access (or modification access) to XY, from within Project 1.

This will be the case for most projects, but we also have a project that tests the module, from which we would like to be able to allow modification to XY. The idea is that to the programmer there will be a very explicit division between "local" code (that they own) and "shared" code (that they must be very careful to ensure compatibility with).

So my question is: is there a way to set file-level access permissions with shared files in Vault? Or on the flipside, is there a better way to do what we're trying to do?

Thanks for reading!

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Wed Aug 04, 2004 1:43 pm

NULL:

Currently, Vault only supports security level access at a Project ( Folder ) level basis. So, if a user has Read, Change, and Add on a project, they have full access to all files in the project.

However, not all is lost. You can achieve read-only access on X & Y by pinning those to the current level, and ask the users to respect the pin. If you cannot get their cooperation, the only thing you could do is Share Module or the files into a sub folder of the project and limit security on the sub folder.

HTH
Jeff Clausius
SourceGear

Post Reply