A request processing policy defines the approval workflow applied when someone requests access to APIs published in DataService Studio. As a Workspace Administrator, you create policies that specify which data is covered, who approves requests at each stage, and how approvers are notified.
Prerequisites
Before you begin, ensure that you have:
A DataWorks Enterprise Edition workspace
The Workspace Administrator role in the workspace
How it works
When a user submits a permission request for an API, DataWorks routes it through the processing nodes you define in the policy — in sequence. Each approver must approve before the request moves to the next node. Approvers are notified through the channels you configure (text message, email, DingTalk chatbot, or webhook URL).
The three parties involved are:
| Role | Responsibility |
|---|---|
| Requester | Submits a permission request for access to a DataService Studio API |
| Workspace Administrator | Creates and manages request processing policies; defines the approval chain and notification channels |
| Approver | Receives notifications when a request is submitted; approves or rejects requests at their assigned node |
Create a request processing policy
Step 1: Open the policy list
Log on to the DataWorks console. In the top navigation bar, select the target region. In the left-side navigation pane, choose Data Development and O&M > Data Development. Select the target workspace from the drop-down list and click Go to Data Development.
Click the
icon in the upper-left corner, then choose All Products > More > Approval Center.In the left-side navigation pane of the Approval Center page, choose Policies > DataService Studio. This page lists all existing request processing policies. You can edit or delete policies from this list.
Click Create Policy in the upper-right corner to open the policy wizard.
Step 2: Configure policy parameters
The wizard has four steps. The table below summarizes all parameters:
| Step | Parameter | Required | Description |
|---|---|---|---|
| Basic information | Policy Name | Yes | A name that identifies this policy |
| Basic information | Purpose | Yes | A description of the business scenario this policy applies to |
| Data range | Data range | Yes | The scope of data covered by this policy. Permission requests for data in this range must follow this policy |
| Notification methods | Notification channels | Yes | One or more of: text message, email, DingTalk chatbot, webhook URL |
| Processing nodes | Approver and role per node | Yes | The sequential approval chain; each node requires an approver and an assigned role |
Enter basic information

Set Policy Name and Purpose to describe this policy and the business scenario it covers.
Specify the data range

Define which data this policy applies to. After the policy is created, all permission requests for data within this range are routed through this policy's approval chain.
Configure notification methods

Choose how approvers are notified when a permission request is submitted. Supported channels: text message, email, DingTalk chatbot, and webhook URL.
This step configures notification channels only. Approvers are assigned in the next step.
For text message and email notifications
Add approvers as alert contacts in DataWorks. For details, see Configure and view alert contacts.
For DingTalk chatbot notifications
When adding the chatbot in DingTalk, set Security Settings to Custom Keywords and enter DataWorks as the keyword. Make sure all other Security Settings checkboxes are cleared.
If the DataWorks keyword is missing, or if any other Security Settings checkbox is selected, approvers will not receive DingTalk notifications.
Configure request processing nodes

In the Configure Processing Links step, define the approval chain. Each node requires an approver and a role for the approver.
Supported approver types:
DataWorks workspace-level roles
DataWorks workspace member
table owner
Alibaba Cloud account
MaxCompute roles
How sequential approval works:
Requests move through nodes in order. The next approver receives a notification only after the current approver approves. If a node has multiple approvers with the same role, notifications go to all of them — but one approval is enough to advance to the next node.
To make sure approvers on each node receive text message or email notifications, add them as alert contacts in DataWorks. For details, see Configure and view alert contacts.