Overview
CodeArts offers role-based permissions management to facilitate project development from start to finish.
CodeArts presets multiple system roles and allows you to customize roles and permissions. You can save the roles and permissions in a project as a permission template and apply the template to other projects. You can also adjust the role permissions for your projects as needed.
This practice describes how to configure permissions for IPD project members. In addition to reusing the system roles of CodeArts, the practice customizes roles with required permissions. You can refer to this practice to configure permissions for members of different roles in your project, save the permissions as a template, and reuse the template in other projects.
Solution Architecture
The following figure shows the project architecture. There are nine teams in the project team.

The responsibilities and required permissions of each role in the preceding architecture are described in the table below.
Team |
Role |
Responsibility |
Required Permission |
Authorization |
---|---|---|---|---|
/ |
Project manager |
|
|
|
R&D team |
R&D leader |
|
|
|
Developer |
|
|
||
R&D leader (middle-end) |
|
|
||
Developer (middle-end) |
|
|
||
Architecture team |
Architecture leader |
|
|
|
System engineer |
|
|
||
Test team |
Test manager |
|
|
|
Tester |
|
|
||
PO team |
Product leader |
|
|
|
Product manager |
|
Maintain RRs, IRs, and USs |
||
PM team |
Project management leader |
|
|
|
Project management team member |
|
|
||
Big data team |
Big data leader |
|
|
|
Big data product manager |
|
Maintain RRs, IRs, and USs |
||
Big data developer |
|
|
||
O&M team |
O&M leader |
|
Maintain and build pipelines |
|
O&M engineer |
|
Execute pipelines |
||
On-call engineer |
|
No CodeArts permission required |
||
DBA team |
DBA leader |
|
Pipeline-related permissions (for SQL automation) |
|
DBA team member |
|
Pipeline-related permissions |
||
Security group |
Security architect |
|
|
Advantages
- Extended CodeArts role matrix
This practice extends the system role matrix of CodeArts by adding more roles. For example, in addition to the developer role of CodeArts, you can also add the R&D leader and developer roles to facilitate your project development. You can assign permissions to different roles so that they can complete their tasks.
- Permission templates
You can save the project roles and permissions in this practice as a template, and reuse the template in other projects with small changes.
Constraints
- To complete this practice, you must have the Tenant Administrator role. After this practice, your project members who have the DevUC > project-role > privilegeconfig permission can modify the permission matrix on the Permissions page.
For details about how to grant the Tenant Administrator role to a user, see Creating a User Group and Assigning Permissions.
- This practice uses an IPD-system device project (currently available in AP-Singapore) as an example. Purchase a CodeArts Pro package in advance by referring to Enabling CodeArts Pro.
Concepts
- Middle-end team: Builds and maintains a middle-end system to share an enterprise's reusable service capabilities, data, and technical resources with the frontend.
- Middle-end system: A key part of an enterprise's IT architecture. It reuses and shares service capabilities, data, and technical resources to improve operational efficiency and service quality. The middle-end system can be divided into multiple layers, such as the business, data, and technical layers. These layers have different functions and roles.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot