Managing Repository Members and Permissions in an Enterprise

Background

An enterprise has 30 members in two teams involved in software development. Each team develops a product and has a CodeArts project. Test_Project has 20 team members, including one project manager, one product manager, one test manager, three committers, four testers, and 10 developers.

Creating a Project

Click the profile picture in the upper right corner and choose All Account Settings > General > Project Creators. Select Only specified members can create or maintain programs (By default, the organization system administrator can create projects.) and grant the project creation permission to Sam.

Then, Sam goes to the CodeArts homepage, clicks Create, and creates a Scrum project named Test_Project. By default, Sam has project manager permissions.

Managing Project Members

Repository groups and repository members must be project members added to the project. As the project manager, Sam configures project members and assigns them role permissions.

To manage project members, Sam syncs project members to repository groups and repositories in the project.

1. He goes to the Test_Project project and chooses Settings > Repo from the navigation pane.

   

2. Sam chooses Security Management > Member Sync and enables Sync project members to add team members to repository groups and repositories in the project.

   

Managing Project Members' Permissions

Administrator Sam has the permission to configure permissions for users of different roles. The following picture shows that Sam is a project manager and has all permissions of CodeArts Repo by default. He can cancel any permission and configure his own permissions.

The following picture shows that Sam adds a custom role Test. Click Create Role to copy the permissions of a role in another project.

Managing Repository Group Members' Permissions

Considering there are many other repositories under this project, Sam creates a repository group Test_Group and configures its permissions for easier management. Sam does not inherit the project permissions and configures another set of permissions for this repository group.

In the following figure, indicates that the permission is granted, and you can cancel the permission. indicates that the permission has not been granted and can be granted. indicates that the permission has not been granted and cannot be configured. indicates that the permission has been granted and cannot be canceled.

Managing Repository Member Permissions

Sam enters the target repository to configure permissions for developers and does not inherit the parent repository group's permissions because developers are working on different repositories. The following picture shows what permissions Sam configures for each role in Test_Repo.

indicates that the permission has been granted and can be canceled. indicates that the permission has not been granted and can be granted. indicates that the permission has not been granted and cannot be configured. indicates that the permission has been granted and cannot be canceled.