Managing Access Permissions by Roles
Plan your project's Version Control: Subversion (VCS) access using appropriate projects, roles and permissions. For more information, see Basics: Projects, Roles, Groups, Members and Users and Authentication and Access Control in Codebeamer.
For example:
• For offshore developers to have different access privileges than local developers , you can use roles to govern such privileges. For example, offshore workers can work on the database while local developers work on the web server.
• If there is a code-freeze in one development area, you can provide a temporary role-based edit permission.
• For technical writers to investigate but not accidentally alter the repository, you can provide a role-based read but not write permission.
The users are assigned to different roles, which are then given different permissions. The permissions can be as fine- or coarse-grained as desired: from repository to directory-level access (directory-level access control is available only for Subversion).
The roles are assigned to users in the Members area (tab) of the project.
Figure: Assigning Roles to Users
After the roles and users are configured, the administrators can configure the access to the SCM repositories by assigning the appropriate permissions to the roles. This can be configured for each repository using the Permissions tab on the Repository admin page:
