> ## Documentation Index
> Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.
# CC Node
> Learn how to configure the CC node in YiDA, which supports multiple CC recipient types such as specific users, roles, and department managers. This article also covers detailed setup steps and important notes.
| **Feature** | **Free plan** | **Basic edition** | **Professional edition** | **Dedicated edition** | **Dedicated - OA Enhancement Pack** |
| --------------------- | ------------- | ----------------- | ------------------------ | --------------------- | ----------------------------------- |
| **Condition mode** | Not supported | Not supported | Not supported | Not supported | Supported |
| **Permission matrix** | Not supported | Not supported | Not supported | Not supported | Supported |
In YiDA, you can add a CC node when configuring a workflow. After the approver completes the approval, CC recipients receive a message notification. CC recipients do not need to approve or take any action.
For example, when an employee submits a reimbursement request and the finance team approves it, a manager may want to know what the reimbursement is used for. In this case, add the manager as a CC recipient so that they receive the notification directly.
## Add a CC Node
Follow these steps to add a CC node.
Sign in to the [YiDA workbench](https://www.yidaapps.com/workPlatform). Select the target app to open its **Page management** page.
Select the workflow form, click the down arrow next to its edit button, and then select **Workflow design**.
3. Hover over the connection line between steps to display the **+** button. Click **+** and select the CC node.
## CC Recipient Settings
CC recipient roles vary across business scenarios. YiDA CC nodes support the following CC recipient types.
⚠️ **Note: A single node supports a maximum of 100 users, roles, managers, or department liaisons.**
| **CC recipient type** | **Description** |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Specific users** | Specify one or more fixed CC recipients for the step. Multiselect is supported. |
| **Specific role** | Send CC notifications to a specified role that groups multiple users. Both **DingTalk roles** and **YiDA roles** are supported.
• Manage YiDA roles on the YiDA workbench > Platform management page.
• Manage DingTalk roles in the DingTalk admin console.
For details on role configuration, see [Role management](/yida/platform-admin/fb7uip). |
| **Department manager** | Specify the department manager of the initiator or a user variable from the member component on the page.
**Note**: Up to 20 levels of managers are supported. |
| **Department liaison** | Manage department liaisons on the **Platform management** page. Click the **Liaison management** button on the right to open the platform management page and configure department liaisons. For details, see [Liaison settings](/yida/platform-admin/ka1xu9).
**Note**: A department liaison is the designated contact for a department. A department may have multiple layers of hierarchy, but there is usually one designated liaison. |
| **Initiator** | The CC recipient of the current node is the workflow initiator. This is useful when the initiator needs to review information again. |
| **Initiator's choice** | The initiator selects the CC recipient when submitting the workflow.
You can configure the selectable scope by **Entire company**, **Specific users**, or **Specific role**.
• **Entire company**: The initiator can select any user in the company as the CC recipient.
• **Specific users**: The initiator can select CC recipients only from a specified group of users.
• **Specific role**: The initiator can select CC recipients only from a specified role. |
| **Form user field** | Use a member variable or the initiator variable in the form as the CC recipient. |
| **Third-party service** | Use a third-party service to set the CC recipient. Register the service under **Platform management** > **Service registration** first, and then select it in the workflow.
For details on service registration, see Service registration. |
| **From connector** | Retrieve CC recipients from a custom connector (YiDA Connector Factory or DingTalk Connect Platform). Configuration is the same as for the connector node.
Select **Connector** > **Execute action** > **Configure action**.
The workflow automatically uses the user information returned by the connector as the CC recipient.
`{ "result": [ "5014533041684350", "01432910392321237660" ], "success": true, "error": ""}`
**Note**: For connector configuration, see [YiDA Connector Factory](/yida/platform-admin/zbq17y) and DingTalk Connect Platform. |
| **Permission matrix** | Set approvers from the permission matrix. Configure it under **Platform management** > **Permission matrix**, and then select it in the workflow.
For permission matrix configuration, see [Permission matrix](/yida/platform-admin/bqc0fgwy5usglvrn). |
## Condition Mode
> Gradual rollout
With conditions configured, the system automatically matches CC recipients based on predefined rules. Different conditions can trigger different CC recipients.
This feature is exclusive to the **Dedicated - OA Enhancement Pack**.
For more information about the OA Enhancement Pack, contact your YiDA account manager.
1. Open the approval settings page: On the YiDA platform, open the approval process settings page.
2. Select condition mode: In the operator settings of the CC node, select **Condition mode**. Condition mode supports multiple groups of approvers, and you can define different conditions to route requests to different approvers.
3. Configure condition rules: Click **Add an item** to add a new record under the approval condition. Click **Set condition** to open the condition configuration dialog, and configure the rules based on your needs.
For example: If the requested amount is less than 1,000 CNY, the finance manager approves it.
If the requested amount is 1,000 CNY or more, the finance director approves it. See the following figure.
4. Multiple rule execution:
* Execute by priority:
* Execute in parallel:
5. Save and publish: After all conditions are configured, save the settings and publish.
## Configure Field Permissions
Field permission control for steps lets you specify which form fields a CC node can view. You can set fields to editable, read-only, or hidden by component name. For more information, see [Workflow permission control](/yida/process/daeh3v).
## FAQ
**Q: Why don't CC recipients receive message notifications?**
* If no one receives notifications, troubleshoot as follows:
* If only some users do not receive notifications, troubleshoot as follows: