Open topic with navigation

Controlling access to specific branches

You can apply security to a branch and override the global security group settings. You can enable or disable file actions for a specific branch in a repository. The security you set only affects one branch in the selected repository. For example, you branch your code into multiple versions. When development starts in a new version, you only want the development group and projects leads to have access to the branch. You can set branch security that restricts all other groups, such as QA or technical writers, from accessing the branch.

Note: If you do not have access to a branch or any repositories in it, the branch is not displayed in the Branches tree or Branch menu. If you do not have access to a parent branch but have access to a child branch, the parent branch is displayed as <restricted>.

1. Select a branch and choose Activities > Properties.

The Properties dialog box opens.

2. Click the Security tab.

3. Select a Branch Security option.

• Use security that applies to all branches uses the server-level security settings.
• Use own security overrides the branch security with the selected value. Copy the security that applies to all branches uses the security applied to all branches but lets you change the permissions for the selected branch. Copy the parent branch’s security is available if the parent branch uses its own security or inherits security. Start with no specific security applied uses the server defaults.
• Inherit parent’s security uses the same security as the parent branch.

4. Click OK to save the changes.

If you set the branch to use its own security, you need to enable or disable commands for the security groups that can access the branch. See Setting branch security commands.