Configuring Repo-Level Permissions
The permission matrix of a repository can be modified only by project administrators, parent repository groups, and the owners of the repositories. After confirming that you are an administrator, go to the CodeArts Repo homepage and click the name of the code repository to be set. On the displayed code repository details page, click Members on the navigation bar to add members to the code repository. Complete the member configuration of the code repository. On the navigation bar, choose Settings. On the settings page that is displayed, choose Security Management >. Permissions. If Inherit from project is enabled, the permissions of members in the current role list will be the same as those of the project, and the current permission configuration will be overwritten.
Click on the right to synchronize the custom role of the project. By default, the custom role does not have the repository operation permission. After the synchronization, you can add the permission in Table 1 as required. A indicates that the role has the permission by default and cannot be removed. B indicates that the role has the permission by default and can be removed. C indicates that the role can be assigned with the permission. D indicates that the role cannot be assigned with the permission.
Role/Permission |
Permission |
Project Manager |
Product Manager |
Test Manager |
Operation Manager |
System Engineer |
Committer |
Developer |
Tester |
Participant |
Viewer |
Custom Role |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Repository |
fork |
B |
C |
B |
C |
B |
B |
B |
C |
C |
D |
C |
Delete |
B |
D |
D |
D |
D |
D |
D |
D |
D |
D |
C |
|
Set |
B |
D |
D |
D |
D |
D |
D |
D |
D |
D |
C |
|
Code |
Commit |
B |
C |
C |
C |
A |
A |
A |
C |
C |
D |
C |
Download |
B |
C |
C |
C |
A |
A |
A |
C |
C |
D |
C |
|
Members |
Add |
B |
D |
D |
D |
D |
D |
D |
D |
D |
D |
C |
Edit |
B |
D |
D |
D |
D |
D |
D |
D |
D |
D |
C |
|
Delete |
B |
D |
D |
D |
D |
D |
D |
D |
D |
D |
C |
|
Branch |
Create |
B |
C |
C |
C |
B |
B |
B |
C |
C |
D |
C |
Delete |
B |
C |
C |
C |
B |
B |
B |
C |
C |
D |
C |
|
Tag |
Create |
B |
C |
C |
C |
B |
B |
B |
C |
C |
D |
C |
Delete |
B |
C |
C |
C |
C |
C |
C |
C |
C |
D |
C |
|
MR |
Create |
B |
C |
C |
C |
B |
B |
B |
C |
C |
D |
C |
Edit |
B |
D |
D |
D |
C |
B |
C |
D |
D |
D |
C |
|
Comment |
B |
C |
C |
C |
B |
B |
B |
C |
C |
C |
C |
|
Review |
B |
D |
D |
D |
B |
B |
B |
D |
D |
C |
C |
|
Approve |
B |
D |
D |
D |
C |
B |
C |
D |
D |
D |
C |
|
Merge |
B |
D |
D |
D |
C |
B |
C |
D |
D |
D |
C |
|
Close |
B |
D |
D |
D |
C |
B |
C |
D |
D |
D |
C |
|
Re-open |
B |
D |
D |
D |
C |
B |
C |
D |
D |
D |
C |
Permissions
- Download and comment permissions are fixed in the public repos' settings, while other permissions mirror those of the private repos
- If you are the creator of an MR, you have the highest permission on it. If there is no other policy settings, you can edit, comment, review, approve, merge, close, re-open, or delete the MR, regardless of the permission matrix.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.