Granting View-Level Access Rights

Usually, granting access rights at the project level is not a fine enough level of granularity. For example, one set of developers may maintain Release 1.0 of the product in one view, while another set of developers writes the source code for Release 2.0 in another view.

To handle this situation, you may want to create new groups, such as 1.0 Developers, 2.0 Developers, 1.0 Testers, and 2.0 Testers. You can give the 1.0 Developers and 1.0 Testers access to files and/or change requests in the Release 1.0 view and. Then you can give the 2.0 Developers and 2.0 Testers access to files and/or change requests in the Release 2.0 view.

In this case, you need to set access rights at the view level. However, you must still set project access rights at the project level because that is the only place where the Project node appears.

View and Child View Access Rights

Access rights in a child view at the view level are independent of the access rights of the parent view at the view level. Therefore, a child view starts out with no access rights at the view level.

A new child view is represented by a different object in the repository from the parent view. It has a different name, description, place in the view hierarchy, etc.

View-level access rights can be set for a new child view. For example, suppose a reference view contains only one branch of the parent view’s folder hierarchy. The reference view has a root folder named QA Tests. In this situation, you can make the Testers the only group with file access rights in the reference view, even if Developers is the only group that has file access rights in the parent view.

Access Rights at Different Levels

Sometimes a group has different access rights at the view and the project levels for the same type of object in the same view. In this situation, the access rights at the lowest level are enforced.

When the StarTeam Server searches for access rights, it starts from the lowest level and moves to the highest level. When it finds a level at which a group has access rights, it does not search any higher levels for that type of object.

Remember that the project access rights exist only at the project level, so the project level is always searched for these rights. File access rights, on the other hand, exist at the file, folder, view, and project levels. the server stops at the first level at which it finds file access rights.