This topic is for administrators who manage Apsara DevOps and DingTalk organizations. It describes how to link an Apsara DevOps organization with a DingTalk organization. This link enables the synchronization of organizational structures and members, DingTalk message notifications, and DingTalk Docs integration.
Prerequisites
Before you bind an Apsara DevOps organization to a DingTalk organization, you must install the Apsara DevOps application in your DingTalk organization.
You must have DingTalk administrator or sub-administrator permissions to perform this operation.
Install Apsara DevOps in DingTalk
A DingTalk administrator can add a sub-administrator in the or in the . For more information, see the DingTalk Help Center.
Open the DingTalk mobile app and scan the QR code for the Apsara DevOps application, or search for "Apsara DevOps" on the Workbench to create an organization and install the application.

After scanning the code, select a Team and a Scope. Click Activate Now to install the Apsara DevOps application.
NoteScope: Specifies which members are synced to Apsara DevOps. If you choose to sync only specific members instead of departments, Apsara DevOps cannot retrieve department information from DingTalk. Consequently, the department information for these members will not be visible in Apsara DevOps.
ImportantApsara DevOps does not support the School Address Book (for students and parents) in DingTalk. If your DingTalk organization is in the education industry, you must select specific employees in the scope settings and exclude the School Address Book.
Bind a DingTalk organization to an Apsara DevOps organization
Before you perform this operation, confirm that you have the Apsara DevOps organization administrator role. After the synchronization is complete, the DingTalk organization chart replaces the Apsara DevOps organization chart. Members who have not attached a DingTalk account are moved to Unassigned Members. After their accounts are attached, they are moved to the corresponding organization chart. Additions and deletions made to the organization structure in the DingTalk management console are automatically synchronized with Apsara DevOps.
In the DingTalk mobile app, go to to open the application. If your DingTalk organization is not bound to an Apsara DevOps organization, you are prompted to bind or create one.

Create or bind an account. The binding method depends on the type of destination account.
Bind an Alibaba Cloud account
To register a new Alibaba Cloud account:

You can choose to attach an existing Alibaba Cloud account.

Bind a RAM user

Choose to bind an existing Apsara DevOps organization or create a new one.
Bind an existing Apsara DevOps organization

Create a new Apsara DevOps organization
This creates a new Apsara DevOps organization with the same name as your DingTalk organization and binds them together.

After the binding is complete, return to the web version of Apsara DevOps. Go to . You can view the binding information, which confirms that the Apsara DevOps organization structure has been replaced by the DingTalk organization structure.
Activate Apsara DevOps users:
Members from the DingTalk organization must access Apsara DevOps and bind their accounts to activate their Apsara DevOps user profiles. For more information about user activation, see Organizations.
You can also activate Apsara DevOps members by sharing a link.
Method 1: Invite target members
Go to . Click Add Members, select Invite Organization Members, copy the invitation link, and share it with the relevant groups. Members of these groups can then click the link to activate their Apsara DevOps accounts.
Method 2: Invite members who have never logged on
Go to , click Copy Invitation Link, and share the link with members who have not yet logged in. Members can access this link to activate their Apsara DevOps membership.

Modify the synchronized part of the organization structure
On the Workbench, open Apsara DevOps.
To modify the Visible Scope, select Application Management.
To make changes, go to Visible Scope. Select the departments and members to sync, and then follow the on-screen instructions to complete the setup.

If you choose to sync only specific members and not entire departments, Apsara DevOps cannot retrieve department information from DingTalk. As a result, the department information for those members will not be visible in Apsara DevOps.
DingTalk message notifications
After you bind your DingTalk account at both the organization and individual levels, actions that trigger notifications, such as creating or modifying a task, send a "Work Notification" message to the DingTalk accounts of the task participants.
You do not receive work notifications for actions that you perform.
Work notifications are sent only to task participants. If you are not a participant in a specific task, you will not receive the work notification for that task, even if you are the project owner.
DingTalk notifications are sent for the following events:
Project module |
Dynamic Notifications |
Project Collaboration |
Basic events: Includes creating a task, moving a task, or moving a task to the recycle bin. |
Update events: Includes notifications for comments, status changes, content updates, assignee changes, due date changes, and priority changes. |
|
Events related to linked content. |
|
Code Management |
Notifications for third-party library import events. |
Operations on merge requests. |
|
Changes to member permissions. |
|
Transfers or path changes for repositories or groups. |
|
Notifications for code repository or group deletion events. |
|
Changes to the visibility of repositories or groups. |
|
Alerts. |
|
Pipelines |
Manual review notifications. |
Adding, deleting, or modifying members of a pipeline. |
|
Failures or cancellations of pipeline runs. |
|
Deleting pipelines. |
|
You can transfer the pipeline owner. |
Unbind an organization
If you have bound an organization and want to switch to a different one or unbind it, you can do so in Apsara DevOps. You can then follow the steps described earlier to bind a new organization. To unbind an organization:
Contact an organization administrator to navigate to the page. Click Unbind and follow the prompts to unbind the Apsara DevOps and DingTalk organizations. After the organizations are unbound, the organization structure reverts to the one defined in Apsara DevOps.



