DMS sends notifications when ticket and task flow statuses change, so the right people know immediately and can take action. Notifications are enabled by default. This topic explains how to customize who gets notified and which events trigger notifications.
Prerequisites
Before you begin, ensure that you have:
-
A DMS administrator or database administrator (DBA) role. For role details, see System roles
How notification rules work
Each notification rule corresponds to a specific status update event — for example, a data change ticket being approved, or a task flow run failing. When that event occurs, DMS notifies the configured recipients.
Default recipients: DMS automatically selects a recipient based on the event type:
-
Tickets pending approval — the users responsible for approving the ticket
-
All other ticket and task flow events — the users who submitted the ticket or task flow
You can add more recipients to any rule, or disable rules for events you do not need notifications about.
Notification methods: DMS supports DingTalk, text messages, email, and DingTalk chatbot messages. Configure your preferred methods in your personal settings. See Configure personal information and notification methods.
Configure notification recipients
Add or change who receives notifications for a specific event.
-
Log in to the DMS console V5.0.
-
In the top navigation bar, click O &M. In the left-side navigation pane, click Notification.
-
Find the notification rule to update and click Modify in the Operation column.
-
In the dialog box, select recipients from the following options:
Recipient type Description Default notification role Auto-selected by DMS based on the event type. Optional notification role Additional roles you can add for this event. Available roles vary by event and include: Approver, Related Person, Data Owner, Instance DBA, DBA, Administrator, and Security Administrator. Additional notification User Specific users under the current tenant. Use this when a team outside the default roles needs to act on the event — for example, notifying big data developers immediately after a schema change to prevent report failures. -
Click Confirm.
Disable a notification rule
Disable a rule to stop receiving notifications for a specific event. After you disable the rule, you cannot receive notifications about this type of status update.
Find the rule to disable and toggle off Status in the Status column.
Enable or disable multiple rules at once
-
On the Notification tab, select the rules to enable or disable.
-
Click Batch enable or Batch disable.

Supported events
The following table lists all events that trigger notifications, organized by feature.
Tickets
| Feature | Events | Default recipients |
|---|---|---|
| Permission application | Pending approval; Approved; Rejected | Pending approval: approvers. Others: submitter |
| Data change | Precheck failed; To be submitted for approval; Pending approval; Approved; Rejected; Data change successful; Data change failed; Task pending scheduling; Task timed out | Pending approval: approvers. Others: submitter |
| Data export | Precheck failed; To be submitted for approval; Pending approval; Approved; Rejected; Data export successful; Data export failed | Pending approval: approvers. Others: submitter |
| Data tracking | DMS failed to retrieve binlogs; To be submitted for approval; Pending approval; Approved; Rejected; Binlogs parsed; Binlogs failed to be parsed | Pending approval: approvers. Others: submitter |
| Database clone | Pending approval; Approved; Rejected; Data copied successfully; Data failed to be copied | Pending approval: approvers. Others: submitter |
| Test data generation | Pending approval; Approved; Rejected; Test data generated; Test data failed to be generated | Pending approval: approvers. Others: submitter |
| Schema design | Schema changed; Pending approval; Approved; Rejected; Schema design successful; Schema design failed | Pending approval: approvers. Others: submitter |
| Table synchronization between databases | Precheck failed; To be submitted for approval; Pending approval; Approved; Rejected; Tables synchronized; Tables failed to be synchronized | Pending approval: approvers. Others: submitter |
| SQL review | Passed; Failed; Approve/Disapprove; Parsing Exception; Pending Analysis | Submitter |
Task flows
| Feature | Events | Default recipients |
|---|---|---|
| Task orchestration | Tasks run; Tasks failed | Submitter |
| Data warehouse development | Tasks run; Tasks failed | Submitter |