Help Center/ CodeArts Req/ Best Practices/ Best Practices of CodeArts Req Permission Management/ Procedure
Updated on 2025-07-22 GMT+08:00
View PDF
Share

Procedure

RBAC

The service resources and system roles' default permissions vary depending on the project template (Scrum, Kanban, IPD-system device, IPD-standalone software, and IPD-self-operated software/cloud service).

In IPD-system device projects, CodeArts Req consists of the following 11 service resources: Files, Recycle, Bug, Config, SF, SF Collection, IR, Plan Management, Review, RR, and Task. Each service resource has specific permission items.

Take the developer role of CodeArts Req as an example. If a developer needs the Break down requirements permission for IR work items, the developer needs to apply for the permission from the project manager. The project manager performs the following operations to assign the permission. The procedure for changing the permissions of other roles is the same.

  1. Assess the project, chooses Settings > Permissions > Developer, and expand the CodeArts Req & Defect area. Figure 1 shows the default permissions of developers.

    Figure 1 Default developer permissions

  2. Click Edit at the bottom of the page, select Break down requirements of IR (as shown in Figure 2), and click Save. The developer permissions are configured successfully.

    Figure 2 "Break down requirements" permission configured for the developer role

  3. Developers check whether they can break down requirements on the R&D Requirements page.

ABAC

This section takes an RR as an example. If members with the Config > Configure workflows permission want to control the field permissions of an RR in the Analyzing status, they can perform the following steps:

  1. Access the project and choose Work Item > Work Item Management > RR > Status Flow. The status list page is displayed.
  2. Click Edit. The status flow editing page is displayed.
  3. Click the Analyzing status node. The status information details page is displayed, as shown in the following figure.

    Figure 3 Status details page

  4. You can configure Role to Edit (not configured by default) for desired fields based on your service scenario. Select roles from the drop-down list. The options include default and custom users.

    • If Role to Edit is left empty, only the current owner or users who have the edit permission in the operable project can edit these fields.
    • Otherwise, the temporary role group of the operational project can also edit the field.

    If Role to Edit of Title and Description is set to Proposer, only the Proposer can edit Title and Description of the RR is in the Analyzing state. The following figure shows that the configuration is successful.

    Figure 4 Setting the roles who can edit fields

  5. Click Update Status Flow and then Save. The configuration is successful, and the permission takes effect immediately.

Helpful Links