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

# Contacts

> Learn how to integrate a YiDA form with DingTalk Contacts via DingTalk Admin permissions to automatically remove a user's contact information after they leave the company. This guide covers creating and configuring the form, adding a connector, and submitting the form to trigger the connector.

<Warning>
  Note: Only DingTalk Organization Admins can operate this connector. To learn how to become a DingTalk Admin, see 👉 [**Become a DingTalk Admin**](/yida/integration/ncdt7p3g2db6d11n).
</Warning>

## Use Case

Manually removing departed employees from Contacts is time-consuming and error-prone; this connector automates the cleanup as soon as the departure form is submitted.

## Demo

Go to DingTalk Admin Console > User activity statistics > View departed employees.

Create a form, then create and configure the Contacts connector for it. Once configured, submitting the form completes the data integration between the YiDA form and DingTalk Contacts.

## Step 1: Create and Configure the Form

**Steps:**

1. Create a new form and name it "Employee Departure Record."
2. Add a member component, name it "Specified User," and set it as required. (See Figure 2.1-6.)

Figure 2.1-1 Add and configure the member component

3. Click **Save** in the upper-right corner of the page.

## Step 2: Add and Configure the Connector for the "Employee Departure Record" Form

The previous step built the "Employee Departure Record" form and laid the data foundation for invoking the connector. Next, configure the form connector to enable communication between YiDA and DingTalk Contacts.

**Steps:**

1. On the admin console page, select the "Employee Departure Record" form, click **Integration & Automation** at the top of the page, and then click **Create Integration & Automation**. (See Figure 2.2-1.)

Figure 2.2-1 Connector entry point

2. Enter "Delete employee from Contacts" as the connector name, select **Form event trigger** as the trigger type, and click **Confirm**.

(See Figure 2.2-3.)

Figure 2.2-2 Create a connector

3. Configure the form event trigger: set the event trigger to **Create success**, set the data filter to **All data**, and click **Save**.

(See Figure 2.2-3.)

Figure 2.2-3 Configure the form trigger event

4. Select the connector app. (See Figure 2.2-4.)

Figure 2.2-4 Select the connector app

5. Set the action to **Delete user information**. (See Figure 2.2-5.)

Figure 2.2-5 Select the connector action

6. Configure the action. (See Figure 2.2-6.)

Figure 2.2-6 Configure the connector action

7. Click **Save** at the top of the page, and then click **Publish**.

## Step 3: Submit the Form to Invoke the Connector

Steps 1 and 2 completed the form build and connector configuration. Next, submit the form to invoke the connector and automatically update user information in DingTalk Contacts.

**Steps:**

Fill in the "Employee Departure Record" form and submit it. (See Figure 2.3-1.)

Figure 2.3-1 Submit the form

## FAQ

**Q: Why do I get a "no permission" message when selecting an action for the Contacts connector?**

A: This connector requires the operator to be a DingTalk Admin. If you are not an Admin, the system displays a no-permission message.

**Q: How do I become a DingTalk Organization Admin?**

A: To become a DingTalk Admin, ask the Super Admin who created the organization to grant you the permission. Path: DingTalk Admin Console > Settings > Permission settings > Admin group > Add admin group.

Figure 4.2-1 Path for a DingTalk Super Admin to add a Sub Admin

Figure 4.2-2 A DingTalk Super Admin editing an admin group