> ## 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.

# Delegation Center

> Learn about the delegation center on the YiDA platform, including plan entitlements, use cases, delegation setup, and offboarding settings.

| **Plan entitlement**     | **Free plan** | **Basic edition** | **Professional edition** | **Dedicated edition** | **Dedicated - OA add-on** |
| ------------------------ | ------------- | ----------------- | ------------------------ | --------------------- | ------------------------- |
| **Delegated processing** | Supported     | Supported         | Supported                | Supported             | Supported                 |
| **Delegated submission** | Not supported | Not supported     | Not supported            | Not supported         | Supported                 |

The delegation center lets you assign a designated user to handle your approval tasks during a specified period. Offboarding delegation must be arranged through the platform administrator. A direct manager can set up delegation on behalf of their direct reports.

## Use Cases

In daily work, approvers on leave or vacation often cannot process approval forms in time, which delays business operations. This YiDA upgrade introduces the delegate capability to keep approvals moving while the approver is away.

<Note>
  All members of an organization can set up a delegate. Managers can set up delegation for themselves and their direct reports. Offboarding delegation can only be set up by the [platform administrator](/yida/platform-admin/omvowq).
</Note>

## Delegation Workflow

<Steps>
  <Step title="Step 1">
    Sign in to the YiDA workbench.
  </Step>

  <Step title="Step 2">
    Click **Task Center** in the upper-right corner, then click **Delegation Center**.
  </Step>
</Steps>

3. Click **Add delegation**. In the dialog box, set the **Delegate**, **Delegator**, and **Delegation period**. For **Delegation type**, select Pending processing. Click **Confirm** to save.

Delegated submission lets specified users submit workflows on behalf of other users in certain business scenarios.

<Note>
  * You can choose whether to notify the delegator about delegated tasks.
  * The delegate and delegator are required and cannot be the same person.
  * If the delegator is not your direct report, you cannot set up delegation. The platform administrator can select any user.
  * If a delegation relationship with the same delegate, delegator, and effective time already exists, you cannot create a duplicate. Open the existing delegation relationship to adjust its scope.
</Note>

#### Delegated Submission

> In gray release

1. The delegation center now supports delegated submission. Set up the delegator and delegate in the delegation center. Only the delegator or the platform administrator can configure the delegation relationship. The effective scope can be set to specific workflows or all workflows.

2. Select All workflows or Specific workflows. When Specific workflows is selected, choose the workflows to delegate, as shown below:

3. Click Save to save the delegation configuration.

4. In the To-Do center, you can see the "Submitted on behalf" tab.

**Entry point**

1. Once the delegation relationship is established, when the delegate initiates a workflow, they can choose whether to submit it in their own name or on behalf of the delegator.

2. If the delegate chooses to submit as the delegator, the workflow displays `xxx` **submitted on behalf**.

3. After the workflow is created, you can see that it was **submitted on behalf** by `xxx`.

#### Delegated Processing

1. The delegation center now supports delegated processing. Set up the delegator and delegate in the delegation center.

Click Save to save the delegation configuration.

<Note>
  After delegation takes effect, you remain responsible for the approval outcomes. Complete any handovers and risk assessments in advance to avoid risks during the delegation period.
</Note>

## Offboarding Settings

When an approver leaves the organization, you can set up a delegate for the offboarded user with one click. If the offboarded user has pending approval tasks, the system automatically sets up a delegation relationship for them on their last day. The priority order for the effective delegate is:

**Designated new delegate** > **Direct manager** > **Department manager** > **YiDA platform administrator** > **DingTalk organization administrator.**

<Note>
  A delegation relationship is not a transfer of approval tasks; it only grants the delegate the relevant approval permissions.
</Note>

* Upon offboarding, any existing standard delegation relationships are revoked, and an offboarding delegation relationship is generated automatically.
* The Dedicated edition supports secondary editing of tasks under a delegation relationship.

**If the user leaves before offboarding delegation is set up, and in-progress workflows reach that user after they leave and generate pending tasks, handle it in two steps.**

**1. Handle in-flight workflows.** For workflows that have already been triggered, **go to Platform management > Work handover**, search for the offboarded user, and transfer the in-flight tasks to a designated user.

**2. Handle workflow permissions by transferring any workflow permissions that include this user's approval to someone else.**

Note:

## Delegation Records

Delegation records have the following four statuses:

* Pending
* In progress
* Expired
* Revoked

**Note: You can only revoke pending or in-progress instances in the delegation center. Deleting delegation instances is not supported.**

## FAQ

**Q: Can I modify the delegation period if I selected the wrong time?**

Modifying an existing delegation instance is not currently supported. If the information is incorrect, revoke it and create a new one.

**Q: What is the logic for assigning a delegate?**

The priority order for the effective delegate is: **Designated new delegate** > **Direct manager** > **Department manager** > **YiDA platform administrator** > **DingTalk organization administrator.**