Mobile lock-screen push notifications for Workday tasks should never contain subordinate names, leave of absence categories, disciplinary step titles, or net pay amounts. A privacy-safe mobile architecture sends a zero-PII wake-up alert (“1 approval needs your attention”) through Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) and fetches the actual Workday record live into memory only after the user completes biometric verification (Face ID or fingerprint) inside the app.
Whenever teams build custom mobile experiences, SMS alerts, or chat-to-phone bridges on top of Workday, someone inevitably suggests making push banners “more informative”: “FMLA Medical Leave Request from Taylor Brooks — Tap to Approve” or “Your November payslip ($4,812.40 net) is ready.” That single design mistake creates four immediate privacy and compliance leaks before the user ever touches their phone.
Four Places Verbose Push Payloads Leak Sensitive HR Data
Unlike an authenticated HTTPS response rendered inside an active signed-in session, an operating-system push payload (aps.alert on iOS or notification.body on Android) leaves your application’s security boundary the instant you send it:
| Exposure Surface | What Happens with a Verbose Push Payload | What Happens with a Zero-PII Wake-Up Alert |
|---|---|---|
| Exposure SurfaceLocked Phone on a Desk / Breakroom Table | What Happens with a Verbose Push PayloadColleagues see “Termination Review: Jordan Lee” or “Wage Garnishment Notice” on the lock screen if the user has default OS preview settings. | What Happens with a Zero-PII Wake-Up AlertBanner shows only “New item in your workspace”—zero names, zero process types, zero dollar figures. |
| Exposure SurfaceCarPlay, Android Auto & Smartwatches | What Happens with a Verbose Push PayloadDashboard screen or Siri/Google Assistant reads “Approve Bereavement Leave for...” aloud with passengers in the car. | What Happens with a Zero-PII Wake-Up AlertGeneric ping; sensitive HR context stays inside the biometrically gated mobile app. |
| Exposure SurfaceAPNs / FCM Transport & Push Provider Logs | What Happens with a Verbose Push PayloadThird-party push gateways and middleware retry queues handle cleartext JSON containing employee PII and health/pay inferences. | What Happens with a Zero-PII Wake-Up AlertPush gateway sees only a device push token and a static localized string. |
| Exposure SurfaceTerminated or Shared Devices | What Happens with a Verbose Push PayloadCached banners remain visible in the OS Notification Center even after corporate SSO is revoked until cleared. | What Happens with a Zero-PII Wake-Up AlertNotification Center holds zero HR facts; opening the banner triggers an OAuth check that immediately fails after revocation. |
Anatomy of a Zero-PII Push + Biometric Fetch Flow
Separating signal delivery from data retrieval gives employees instant responsiveness on iOS and Android without ever putting HR records into push infrastructure or onto a lock screen.
1. The Push Payload Carries Zero HR Content
Compare an unsafe payload against a privacy-safe payload sent to APNs or FCM:
// UNSAFE: Leaks PII, health inference, and org relationship to APNs/FCM and lock screens
{
"aps": {
"alert": {
"title": "Leave Approval: Maria Santos",
"body": "Request Leave of Absence (Medical - Surgery) Nov 18 - Dec 14"
},
"sound": "default"
},
"worker_id": "29810",
"leave_type": "FMLA_Medical"
}// PRIVACY-SAFE: Zero PII, zero business process details, opaque route hint only
{
"aps": {
"alert": {
"loc-key": "ACTION_NEEDED_TITLE",
"body": "Something in your company space needs your attention."
},
"badge": 1,
"sound": "default"
},
"route": "approvals"
}Even if a curious bystander reads the phone on a restaurant table, or an enterprise security auditor inspects every byte sent to Apple and Google push relays, there is nothing to redact because no Workday payload data was ever placed in the notification.
2. Biometric Gate Before Token Unsealing
When the employee taps the notification on their iPhone or Android phone:
- Keychain / Keystore Biometric Check: Rather than storing an unencrypted Workday refresh token in
AsyncStorageorSharedPreferences, the mobile app stores sealed credentials in the iOS Secure Enclave-backed Keychain (kSecAccessControlBiometryCurrentSet) or Android Keystore (setUserAuthenticationRequired(true)). - Face ID / Fingerprint Verification: Tapping the notification prompts Face ID or fingerprint authentication in under half a second.
- Live Workday API Call: Once authenticated, the app calls
GET /common/v1/workers/me/inboxTasksor the relevant self-service endpoint directly over TLS using the employee’s own Workday OAuth 2.0 token. - Ephemeral Memory Rendering: The leave request, payslip breakdown, or shift swap renders live on screen. When the session closes or the worker’s
Workday Accountis disabled, nothing sensitive sits in an offline SQLite cache on the device.
Aligning Workday’s Own Notification Settings So Emails Don’t Leak What Push Protected
Locking down mobile push notifications accomplishes very little if Workday simultaneously fires a custom business process email containing the exact same sensitive fields to an insecure inbox preview—or spams managers with duplicate alerts across three channels.
Check three Workday configuration points when rolling out privacy-safe mobile workflows:
- Audit Custom Business Process Notifications (
Business Process > Edit Notification): HRIS teams frequently build custom notifications usingExternal Fieldreport fields in the Subject and Body grids. Never put compensation amounts, medical leave reasons, or National IDs into email or SMS subject/body grids—use a link back to the authenticated task instead, and set Email Option to Work Only (alongside Enable Work-Only as Default Destination for Emails onEdit Tenant Setup - Notifications) so Workday never falls back to a worker’s shared home email address. - Review Workday Native Push Domains: If you also run Workday’s native mobile app, Workday governs push permissions via two domains in the System functional area:
Manage Mobile Notifications(securesTurn Off Mobile Notifications for Workerfor admins during offboarding or leave) andSelf-Service: Mobile Notifications(securesTurn Off Mobile Notificationsfor workers). - Tune Notification Routing Rules to Eliminate Double Pings: Use
Create Notification Routing RuleandEdit Tenant Setup - Notifications(Notification Delivery Settings) so managers approving on mobile or chat are not bombarded with immediate emails for every routine step. See our step-by-step guide on tuning Workday notification delivery settings to suppress duplicate emails.
How the Kiweely Leaf Phone App Built Privacy-Safe Notifications In
We designed the Kiweely Leaf iOS and Android app (coming next) around this exact privacy architecture for frontline workers, employees, and managers:
- One App Store Install, Zero Store Reviews Per Company: Employees install Kiweely Leaf once from the App Store or Google Play, sign in once with Workday SSO, and sign in from then on with Face ID or a fingerprint into your company’s branded space—holding every screen built in Kiweely Leaf plus any web app your own developers host.
- Private Notifications by Design: When an approval or update needs someone, Kiweely Leaf sends a private notification saying something needs them while keeping all HR details inside the app behind biometric sign-in.
- Zero HR Data Stored on Kiweely Servers: Every screen reads and writes live against Workday under the signed-in worker’s own OAuth token—nothing is cached at rest on our servers, and no Workday Extend license is required. (Note: employees use the Kiweely Leaf app; Workday consultants and HRIS admins supervising Vine and Nest sessions use the separate Kiweely companion phone app.)
Frequently asked questions
Why is putting employee names, leave types, or pay amounts inside a mobile push payload a security issue?
Push payloads transit third-party push relays (Apple APNs and Google FCM), cache in mobile OS notification centers, mirror onto paired smartwatches and CarPlay/Android Auto screens, and light up on locked phones sitting face-up in conference rooms or break areas.
How does a zero-PII 'wake-up' push notification pattern work?
The push payload contains only a generic localized prompt (such as 'You have a new item waiting for review') and an opaque reference or deep-link route. Only after the employee unlocks the app with Face ID, Touch ID, or biometric authentication does the app fetch the live Workday task over TLS using the user's OAuth token.
Does a generic push notification require storing HR task details on a push server?
No. Triggering a wake-up alert requires knowing only that an opaque user device registration has an update—zero compensation numbers, absence reasons, disciplinary steps, or subordinate names ever enter the push service or its logs.
How do administrators control Workday's own native mobile push and email channels?
In Workday, run Edit Tenant Setup - Notifications to configure Mobile App Notification Settings (Apple Push Notifications and Google Cloud Messaging) and assign Notification Routing Rules per notification type, plus manage domain access on Self-Service: Mobile Notifications and Manage Mobile Notifications.