Help Center/ CodeArts Repo/ User Guide/ Configuring CodeArts Repo/ Security Management/ Permission Management
Updated on 2024-07-05 GMT+08:00
View PDF
Share

Permission Management

Project-level permissions refer to the default permissions of each role in a repository that can be configured in a unified manner in project settings. Repository-level permissions refer to the default permissions of each role in a repository that can be configured in a unified manner in repository settings.

If multiple repositories need to use the same role permission, project-level permission configuration is recommended.

If multiple repositories need to use different role permissions, repository-level permission configuration is recommended.

Project-level Permission Control

Configuration Method:

  1. Log in to CodeArts.
  2. Click the target project name to access the project.
  3. Choose Settings > General > Permissions. The Permissions page is displayed.
  4. Choose Role > CodeArts Repo and click Edit to modify the role permission.

    On the permission management page, the project creator and other users who have management permissions can modify the default operation permissions of different roles on resources in a project.

Table 1 Project-Level permission list

Type

Permission

Project Administrator

Repository Owner

Project Manager

Committer

Developer

System Engineer

Test Manager, Tester, Participant, Operation Manager, and Product Manager

Viewer

Custom Role

Remarks

Repository

Create

1

1

2

2

2

2

3

4

3

-

Fork

1

1

2

2

2

2

3

4

3

Fork means you can copy existing repositories for many times. However, whether the copy is successful depends on whether you have permission to create repositories in the target project.

For example, member A has the fork permission in project A.

  • If member A has permission to create repositories in project B, the fork operation succeeds.
  • If member A does not have permission to create repositories in project B, the fork operation fails.

Delete

1

1

2

4

4

4

4

4

3

-

Settings

1

1

3

4

4

4

4

4

3

-

Code

Commit

1

1

2

1

1

1

3

4

3

-

Download

1

1

2

1

1

1

3

4

3

-

Member (group)

Add

1

1

2

4

4

4

4

4

3

-

Edit

1

1

2

4

4

4

4

4

3

-

Delete

1

1

2

4

4

4

4

4

3

-

Branch

Create

1

1

2

2

2

2

3

4

3

-

Delete

1

1

2

2

2

2

3

4

3

-

Tag

Create

1

1

2

2

2

2

3

4

3

-

Delete

1

1

2

3

3

3

3

4

3

-

MR

Create

1

1

2

2

2

2

3

4

3

-

Edit

1

1

2

2

3

3

4

4

3
  • Merged MRs cannot be edited.
  • MR creators can edit, close, and re-open their own MRs.

Comment

1

1

2

2

2

2

3

3

3

-

Review

1

1

2

2

2

2

4

3

3

-

Approve

1

1

2

2

3

3

4

4

3

-

Merge

1

1

2

2

3

3

4

4

3

-

Close

1

1

2

2

3

3

4

4

3

MR creators can edit, close, and re-open their own MRs.

Re-open

1

1

2

2

3

3

4

4

3

MR creators can edit, close, and re-open their own MRs.
  • Only repository members have permission to view Repository, Code, Member, Branch, Tag, and MR.
  • The repository owner, project manager, committer, and commentator can resolve MR reviews. In scoring mode, committers and project managers can score −2–2 points, and other roles can score −1–1 point. Viewers cannot score.
  • 1: indicates that the role has the permission by default and the permission cannot be removed.
  • 2: indicates that the role has the permission by default and the permission can be removed.
  • 3: indicates that the role can have the permission assigned.
  • 4: indicates that the role cannot have the permission assigned.

Repository-level Permission Control

Configuration Method:

  1. Go to the CodeArts homepage and click the target project name to access the project.
  2. Choose Services > Repo.
  3. Choose Settings > Security Management > Permissions. The Permissions page is displayed.

    You can configure role permissions in six dimensions: Repository, Code, Member, Branch, Tag, and MR.

Table 2 Repository-Level Permission List

Type

Permission

Repository Owner

Project Manager

Committer

Developer

System Engineer

Test Manager, Tester, Participant, Operation Manager, and Product Manager

Viewer

Custom Role

Remarks

Repository

Fork

1

2

2

2

2

3

4

3

-

Delete

1

2

4

4

4

4

4

3

-

Settings

1

2

4

4

4

4

4

3

-

Code

Commit

1

2

1

1

1

3

4

3

-

Download

1

2

1

1

1

3

4

3

-

Members

Add

1

2

4

4

4

4

4

3

-

Edit

1

2

4

4

4

4

4

3

-

Delete

1

2

4

4

4

4

4

3

-

Branches

Create

1

2

2

2

2

3

4

3

-

Delete

1

2

2

2

2

3

4

3

-

Tag

Create

1

2

2

2

2

3

4

3

-

Delete

1

2

3

3

3

3

4

3

-

MR

Create

1

2

2

2

2

3

4

3

-

Edit

1

2

2

3

3

4

4

3

-

Comment

1

2

2

2

2

3

3

3

-

Review

1

2

2

2

2

4

3

3

-

Approve

1

2

2

3

3

4

4

3

-

Merge

1

2

2

3

3

4

4

3

-

Close

1

2

2

3

3

4

4

3

-

Re-open

1

2

2

3

3

4

4

3

-
  • You can modify the configured role permissions according to the preceding table.
  • Only repository members have permission to view Repository, Code, Member, Branch, Tag, and MR.
  • 1: indicates that the role has the permission by default and the permission cannot be removed.
  • 2: indicates that the role has the permission by default and the permission can be removed.
  • 3: indicates that the role can have the permission assigned.
  • 4: indicates that the role cannot have the permission assigned.
Parent topic: Security Management