Project-level Permissions

Configuration Method

1. Log in to the CodeArts homepage.
2. Click the target project name to access the project.
3. On the left navigation pane, choose Settings > General > Service Permissions.

   On this page, the project creator and users who have the management permission can modify the permissions on pipelines of different roles in the project.

   Pipeline-related resources are in CodeArts Pipeline, including pipelines, policies (project-level), microservices, environments, and changes.

By default, a user with permissions to edit or execute pipelines can also view pipelines.

Pipeline Permissions

The following table lists the pipeline permissions for each role in a project in the initial state.

• To copy a pipeline, you must have the permission to create a pipeline and modify the source pipeline.
• By default, role permissions in a pipeline inherit and are associated with the role permissions in the project until role permissions are modified in the pipeline.
• By default, a pipeline creator has all permissions on the pipeline.

Policy Permissions

The following table lists the project-level policy permissions for each role in a project in the initial state.

Role	View	Create	Edit	Delete
Project creator	√	√	√	√
Project manager	√	√	√	√
Developer	√	√	√	√
Test manager	√	×	×	×
Tester	√	×	×	×
Participant	√	×	×	×
Viewer	√	×	×	×
Operation manager	√	×	×	×
Product manager	√	×	×	×
System engineer	√	√	√	√
Committer	√	√	√	√

To copy a policy, you must have the permission to create a policy and modify the source policy.

Microservice Permissions

Change Permissions

Environment Permissions

For release environments, the default permissions for each role in a project can be configured in a unified manner. The involved modules include the development environment, test environment, pre-release environment, and production environment.

The following table lists the microservice release permissions for each role in different environments in the initial state.