Who can access source code?





Full access, with exceptions
No access, with exceptions
Assign all developers "No access" by default, then assign each type of developer access to certain directories and files according to their responsibilities.
Note: You can control access to a path or to an individual file. This is different from normal Subversion checkout and commit operations, which are performed on directories but not individual files.

No Access


Note: An individual user can have multiple roles. When two roles have permissions that conflict with each other, the role with the more expansive permissions takes precedence.

View Only

Users with a role that has "View Only" access to a path can browse the contents of the repository on the Web site or by connecting directly to the repository from a client, such as Tortoise, CollabNet Desktop for Eclipse, or CollabNet Desktop for Visual Studio.

View and Commit

Users with a role that has "View and Commit" permission to a path can browse and download code, and can also check code into the repository.

Wildcard-based access control and path-based permissions

You can create rules that use wilcards to control access to specific paths in a repository. See Wildcard-based access control and path-based permissions in TeamForge for more background information about wildcard and path based permissions.

Scenario 1


@build = rw
@dev = r
@build = rw
@dev = r
@build = rw
@dev = r
Instead, you can write a rule using wildcards such as:
Later, you can create and assign roles to users such as "build engineers" and "developers" with "read-write" and "read-only" access permissions respectively.
Scenario 2


Scenario 3



The "**" matches any number of folder levels in a repository. For example, this rule applies to the following paths:

Notes about path-based permissions

If two paths have different permissions, the permissions on the lower-level path take effect. For example, consider a role that has "No Access" set for the path /branches/version3/users, but has "View and Commit" access to /branches/version3/users/vijay. A user with this role can:

Users with this role cannot:

Commit messages


Users with a "No Access" role on a repository cannot monitor that repository to receive commit messages by email.


Toolbar button
