---
title: "Suppressing Duplicate Workday Emails for Chat & Mobile"
description: "Configure Edit Tenant Setup - Notifications, Notification Routing Rules, and Maintain System Notifications so chat or mobile approvals don't spam emails."
url: https://kiweely.com/guides/workday-notification-delivery-settings-suppressing-duplicate-emails
---

# Tuning Workday Business Process Notifications When Using External Mobile or Chat Approvals

Stop duplicate email spam during chat or mobile approval rollouts using Notification Routing Rules (Daily Digest or Mute), Edit Tenant Setup - Notifications overrides, or Maintain System Notifications step suppression while keeping tasks in My Tasks.

-   **Checked** against Workday on November 15
-   Applies to **Workday Notifications & Business Processes**
-   7 min read
-   Published November 15
-   By Kiweely

To stop managers from receiving duplicate emails for every workflow step they already handle in chat or mobile, **do not** turn off global tenant email; instead, tune **`Create Notification Routing Rule`**, **`Edit Tenant Setup - Notifications`** (*Notification Delivery Settings*), or **`Maintain System Notifications`** on the specific business process definitions (such as *Request Time Off* or *Expense Report Event*). Disabling or muting the email delivery channel suppresses outbound SMTP messages **without** removing awaiting tasks from **My Tasks**, REST `inboxTasks`, or WQL queues.

When organizations launch mobile or chat approval screens alongside default Workday notification rules, a single time-off request can trigger an immediate system email, a custom business process email, a native mobile push, and a chat card—followed by another burst on completion. Understanding Workday’s three-tier notification hierarchy lets administrators quiet redundant emails cleanly while keeping security OTPs, statutory notices, and **My Tasks** records untouched.

## Choosing the Right Lever in Workday’s Notification Hierarchy

Workday evaluates outbound messages across three distinct layers. Pick the surgical layer that matches your rollout scope:

| Configuration Layer | Workday Task / Path | Scope of Impact | Keeps Task in `My Tasks` & API? | Best Use Case |
| --- | --- | --- | --- | --- |
|  **1\. Single BP Step (System Notification)** | BP Definition -> `Notifications` tab -> **Maintain System Notifications** | One specific step (e.g., *Approval by Manager* on *Request Time Off*) |  **Yes** | Silencing immediate emails on one high-volume workflow now handled in chat or mobile. |
|  **2\. Single BP Custom Notification** | BP Definition -> `Notifications` tab -> **Maintain Custom Notifications** | One custom notification rule on a BP |  **Yes** (hides from bell icon & channels) | Retiring legacy custom HTML/text email reminders built before mobile/chat rollout. |
|  **3\. Notification Type Routing Rule** | `Create Notification Routing Rule` + `Edit Tenant Setup - Notifications` | Specific notification type (e.g., *Time Off*, *Business Process Tasks*) or parent category |  **Yes** (still visible on Notifications page) | Switching emails from *Immediately* to *Daily* digest or *Mute*, or letting managers self-mute via `Change Preferences`. |
|  **4\. Environment Restrictions** | `Edit Tenant Setup - Notifications` -> *General Notification Restrictions* | Entire `SANDBOX` or `IMPL` environment across tenant refreshes |  **Yes** | Redirecting or blocking all non-Production test emails/SMS after Production refreshes (**never** use `Disable All` in `PROD`). |

> **Warning on `Disable All Notifications`:** In **General Email Notification Settings** and **General Notification Restrictions** on `Edit Tenant Setup - Notifications`, selecting **Disable All Notifications** for the *Email* channel disables Workday security emails—including **One-Time Passcode (OTP)** MFA emails and the **Forgot Password** link configured on `Edit Tenant Setup - Security`. Never use global disablement to silence business process chatter in Production.

## Method 1: Suppress Email on Specific Business Process Steps (`Maintain System Notifications`)

If your rollout moves *Request Time Off*, *Enter Time*, or *Expense Report Event* approvals into a mobile or chat experience first—while leaving low-frequency workflows like *Create Job Requisition* or *Propose Compensation Change* on email—configure suppression directly on the business process definition.

Requires security domains in the *System* functional area: **`Business Process Administration`** and **`Manage: Business Process Definitions`**.

1.  Search for the business process definition (for example, **Request Time Off (Default Definition)**) and open its **Notifications** tab.
2.  Click **Maintain System Notifications**.
3.  Locate the noisy step row (such as `Approval by Manager`) and check **Disabled**. *(For steps inside a subprocess, disable the related system notification on the initiation step of the subprocess on the parent definition.)*
4.  Click **OK**.

**What happens at runtime:** Workday still creates the `Event Record`, routes it into the approver’s **My Tasks**, and exposes it immediately via `GET /common/v1/workers/me/inboxTasks` and `GET /businessProcess/v1/eventSteps`. Workday simply skips sending the system notification over outbound channels like Email.

If the same business process also has custom notifications configured on step entry or exit, click **Maintain Custom Notifications** on the same **Notifications** tab and check **Disabled** on redundant rules (note that disabling a custom notification suppresses email, SMS, and the in-app bell icon for that custom message).

## Method 2: Switch Notification Types to `Daily` Digest or `Mute` via Routing Rules

When you want to stop *instant* email interruptions across an entire notification category while still giving managers a single morning safety-net summary—or letting power users mute emails themselves—use **Notification Routing Rules**.

Requires security domain in the *System* functional area: **`Set Up: Tenant Setup - BP and Notifications`**.

### Step 1: Create the Routing Rule

1.  Run the **`Create Notification Routing Rule`** task.
2.  Leave **Notification Type Usage** blank (so the rule is reusable across multiple notification types) or pick a specific type.
3.  Under **Channel Frequencies**, click **Add** and configure the **Email** row:
    -   **Channel:** `Email`
    -   **Default Frequency:** Select `Daily` (consolidates into one Daily Digest email) or `Mute` (sends zero outbound emails while still logging the item on the user’s Notifications page inside Workday).
    -   **Allowed Frequencies:** Select `Immediately`, `Daily`, and `Mute`. Including `Mute` in **Allowed Frequencies** empowers individual managers to silence email alerts for that notification type themselves via the **`Change Preferences`** self-service task.

### Step 2: Apply the Rule in `Edit Tenant Setup - Notifications`

1.  Run **`Edit Tenant Setup - Notifications`** and scroll to **Notification Delivery Settings**.
2.  Expand the relevant parent notification type (for example, **Business Process** or **HCM** / **Absence**).
3.  On the target child **Notification Type** (for example, *Business Process General Notifications* or *Time Off* notifications), check **Override Notification Parent Type Settings**.
4.  In **Routing - Rule**, select the routing rule you created in Step 1.
5.  If using `Daily` frequency, verify **Daily Digest Start Time** under **Default Email Settings** at the top of `Edit Tenant Setup - Notifications`. Set the start time immediately *after* your tenant maintenance window ends (for example, `06:00:00` if maintenance runs `02:00:00`–`06:00:00`) so maintenance never interrupts digest generation. Note that Workday caps each Daily Digest email at 50 action items and 50 notification items, linking to any overflow inside the tenant.

*(SMTP detail to remember: if a custom business process notification uses a custom From Address via a **Customer SMTP** override, switching its routing rule to **Daily** causes the digest to send from the **Default SMTP Configuration** From Address instead, since Workday bundles all notification types into one daily digest per worker.)*

## Fixing Three Subtle Causes of Duplicate Approval Emails

Even after tuning routing rules, HRIS admins frequently encounter surprise duplicate emails caused by workflow configuration quirks:

1.  **`Manager` vs. `Awaiting Persons` on `Approval Chain` Custom Notifications:** When you attach a custom notification to an **Approval Chain** step, selecting `Manager` in the **Groups / Recipients** prompt causes Workday to email the initiator’s direct manager at *every single level* of the management chain. Change the recipient to **`Awaiting Persons`** so only the currently active approver is notified.
2.  **Duplicate Alerts to Both Delegator and Delegate:** When a manager sets up a delegation via **`Manage Delegations`** for *all* or *specific* business processes, Workday automatically checks **Retain Access to Delegated Tasks within My Tasks** by default. While checked, *both* the delegator and the delegate receive process notifications. Clear that check box during leave delegations, or—on sensitive custom notifications—check **Exclude Delegates in Notifications** on the custom notification definition.
3.  **Sandbox Refresh Leaks:** Before testing external approval apps in `SANDBOX` or `IMPL`, configure **General Notification Restrictions** inside your **Production** tenant with **OMS Environment Selected for Restriction** set to `SANDBOX` and `IMPL` (using **Redirect All Notifications to Contact**). Because you define the rule in Production, every weekly Production-to-Sandbox refresh automatically carries the restriction over before background processes can fire live emails to employees.

## Verification Checklist Before Rollout

-   Confirm `Disable All Notifications` under **General Email Notification Settings** remains **unchecked** in Production so MFA OTP and password-reset emails continue working.
-   Trigger a test *Request Time Off* or *Expense Report Event* in Sandbox for a test manager persona.
-   Verify the awaiting `Event Record` still appears in `GET /common/v1/workers/me/inboxTasks` and `GET /businessProcess/v1/eventSteps` even when **Maintain System Notifications** is set to `Disabled` or the Email channel routing rule is set to `Mute`.
-   Check **Enable Work-Only as Default Destination for Emails** on `Edit Tenant Setup - Notifications` and set custom notification **Email Option** values to **Work Only** so remaining transactional emails never route to personal home addresses.

When pairing tuned Workday notification rules with [Kiweely Leaf](https://kiweely.com/leaf) (**coming next**), managers receive a single clean chat card in Teams, Slack, DingTalk, Feishu, or Lark—or a privacy-safe wake-up alert in the **Kiweely Leaf** mobile app—and complete the approval live against Workday without an inbox full of duplicate system emails.

## Frequently asked questions

### If I disable a system notification on an Approval step, does the task disappear from My Tasks and REST APIs?

No. Selecting Disabled under Maintain System Notifications on a business process definition stops Workday from delivering external channel alerts such as email, while still generating the awaiting-action Event Record in My Tasks and on GET /common/v1/workers/me/inboxTasks.

### Why should I never check Disable All Notifications on Edit Tenant Setup - Notifications in Production?

Checking Disable All Notifications (Disable All Emails) under General Email Notification Settings suppresses security authentication emails—including One-Time Passcode (OTP) multifactor authentication emails and Forgotten Password Reset links—across the entire tenant.

### How can managers consolidate Workday task emails into one morning summary instead of per-request emails?

Run Create Notification Routing Rule, set the Email channel Default Frequency to Daily (or allow users to choose Daily/Mute on Change Preferences), assign that rule under Notification Delivery Settings on Edit Tenant Setup - Notifications, and set Daily Digest Start Time after your maintenance window.

### Why do managers at the first level of an Approval Chain get emailed for every higher-level approval?

On custom notifications attached to an Approval Chain step, selecting Manager as the Recipient emails the worker's direct manager at every level of the chain. Select Awaiting Persons as the Recipient instead so the notification follows the active approver up the chain.

## Sources checked

-   [Reference: Edit Tenant Setup - Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/wil1451433814625.html)
-   [Create Notification Routing Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/notifications-and-alerts/car1554145887062.html)
-   [Create Custom Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-notifications/dan1370797382653.html)
-   [Set Up Mobile Push Notifications](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/mobile-setup/dan1370796452612.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Querying Pending Workday My Tasks and Inbox Approvals via API and WQL Retrieve pending Workday My Tasks items for the signed-in worker via GET /common/v1/workers/{ID}/inboxTasks, or query awaiting approvals with WQL data sources such as businessProcessTransactionsAwaitingMyAction and businessProcessStepsAwaitingMe alongside businessProcess v1 REST calls.](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [### How Workday Task Delegation Works When Managers Approve Through APIs When managers delegate via Manage Delegations or Delegate Task, Workday routes eligible awaiting Event Records to the delegate’s inboxTasks and WQL queues, enforces Delegation Rules and Routing Restrictions, and records ‘On Behalf Of’ attribution in audit history.](https://kiweely.com/guides/workday-delegation-rules-external-approvals-acting-on-behalf)
-   [### Approving, Denying, and Sending Back Workday Business Process Steps via REST and SOAP APIs Advance pending Workday workflow steps via businessProcess v1 REST endpoints (/eventSteps/{ID}/approve, /deny, /sendBack, /toDo, /reassign) using the Event Record WID, or via Integrations SOAP operations (Approve\_Business\_Process, Deny\_Business\_Process, Send\_Back\_Business\_Process).](https://kiweely.com/guides/workday-business-process-approve-deny-rest-soap-api)
-   [### Workday Awaiting Action: who is the step waiting on, and how do you move it? Awaiting Action means a step is waiting for someone to act, and a day or more is normal. Open Business Process > Full Process Record to see who, then have them finish it in My Tasks, or reassign, delegate or manually advance the step.](https://kiweely.com/guides/business-process-awaiting-action)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Workday Time Off vs. Leave of Absence: Helping Employees Pick the Right Request Type](https://kiweely.com/guides/workday-leave-of-absence-vs-time-off-employee-request-routing)
-   [How to Trace Who Approves a Leave or Expense Request in a Workday Supervisory Org](https://kiweely.com/guides/workday-find-approver-chain-supervisory-org-business-process)
-   [Validating Country-Specific Address and Emergency Contact Formats in Workday Self-Service](https://kiweely.com/guides/workday-emergency-contact-home-address-change-validation-rules)
-   [Why Workday Says ‘This Task Is Not Available’ or ‘Waiting on Initiator’ on a Business Process Step](https://kiweely.com/guides/workday-business-process-this-task-is-not-available)
-   [Why Can’t a Security Group See a Workday Dashboard or Worklet After You Added Permission?](https://kiweely.com/guides/workday-worklet-dashboard-not-visible-security)
-   [What does rescinded mean in Workday? Rescind vs cancel vs correct, and when each applies](https://kiweely.com/guides/workday-business-process-rescind-cancel-correct)
-   [Workday custom validations and condition rules: block bad data with Critical or Warning severity](https://kiweely.com/guides/workday-custom-validations-condition-rules)
-   [Workday Role-Based, User-Based, Intersection, and Aggregation Security Groups](https://kiweely.com/guides/workday-role-based-user-based-intersection-security-groups)

### From the blog on Business processes and security

[All posts](https://kiweely.com/blog)

-   [How Submitting Workday Time Off from Claude or ChatGPT Works Safely End to End](https://kiweely.com/blog/submitting-workday-time-off-from-claude-chatgpt-with-approval)
-   [Preparing Workday Domain and Business Process Security Policies for a SOX Audit in Hours, Not Weeks](https://kiweely.com/blog/auditing-workday-segregation-of-duties-before-sox-review)
-   [The Anatomy of a Production-Safe Workday Change: Propose, Approve, Execute One by One, Read Back](https://kiweely.com/blog/anatomy-of-a-production-safe-workday-change)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
