Managing Access Permissions by Roles
You can plan the Version Control: Subversion (VCS) access of your project using appropriate project roles and permissions.
For more information, see Projects, Users, Accounts, Members, Roles, and Groups and Authentication and Access Control in Codebeamer.
For example you can:
• Grant different access privileges to offshore developers and local developers using roles. For example, offshore workers can work on the database while local developers work on the web server.
• Enable temporary role-based edit permission if there is a code-freeze in one development area.
• Allow role-based read but not write permission for technical writers to ensure that they do not accidentally make any changes to the repository.
You can assign to different roles to users with specific permissions. These permissions can be customized ranging from repository-level to directory-level access.
 |
The directory-level access control is available only for Subversion.
|
You can assign these roles from the Admin tab of a project by clicking the context menu and selecting the Members option.
Figure: Assigning Roles to Users
After the roles and users are configured, the administrators can configure 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 as shown in the following image:
