Skip to content
KiweelyKiweelyKiweely

Designing a Single-Screen Employee Hub for Workday Pay, Time Off, and Benefits

Employees open Workday for four recurring tasks—checking their latest payslip, seeing available time off, confirming active benefit elections, and clearing pending My Tasks—yet Workday scatters them across separate hubs. Here is the exact API and UX blueprint to unify all four on one screen.

  • By Kiweely
  • 5 min read
On this page

Ninety percent of non-manager employee visits to Workday boil down to four five-second checks: “Did my paycheck hit and what changed?”, “How many PTO hours do I actually have left?”, “Which medical and dental plans am I enrolled in?”, and “Do I have an overdue task waiting on me?” Combining those four answers onto one clean, scannable screen—backed by four parallel, employee-scoped Workday API reads—replaces a maze of nested Workday hubs, menu drawers, and worklets without copying a single HR row outside Workday.

Inside Workday’s delivered browser and mobile UI, software structure follows Workday’s functional module boundaries: My Tasks sits in the top header, pay and benefits sit inside the Benefits and Pay Hub across separate sub-tabs, and leave balances live inside the Absence worklet. Even with Workday Extend, home page card slots cap out tightly and pages remain bound to .pmd widget constraints (see how external screens work without a Workday Extend license).

Mapping the Four Hub Zones to Exact Workday Self-Service APIs

To build a fast, accurate single-screen hub that enforces Employee As Self security natively, map each visual card directly to its lightweight Workday self-service read path:

Screen Zone What the Employee Sees at a Glance Exact Workday Read Path Required Employee As Self Security Domain
Screen Zone1. Action Banner (Top) What the Employee Sees at a GlanceCount & titles of awaiting My Tasks items (Onboarding, Open Enrollment, To Dos); hidden if total = 0 Exact Workday Read PathGET /common/v1/workers/me/inboxTasks?limit=10 Required Employee As Self Security DomainCore Navigation (Tenant Non-Configurable)
Screen Zone2. Latest Pay Card What the Employee Sees at a GlanceMost recent completed pay date, status, masked Gross/Net toggle, and delta vs. prior period Exact Workday Read PathGET /common/v1/workers/me/paySlips?limit=2 (plus optional self-scoped RaaS line breakdown) Required Employee As Self Security DomainSelf-Service: Payroll (My Payslips) (Core Payroll)
Screen Zone3. Time Off Card What the Employee Sees at a GlanceAvailable balances per eligible plan (hours or days), upcoming approved/pending dates, and 1-click Request Time Off Exact Workday Read PathGET /absenceManagement/v5/balances?worker={me}&effective={today} + /workers/{me}/timeOffDetails Required Employee As Self Security DomainSelf-Service: Time Off Balances & Self-Service: Time Off
Screen Zone4. Active Benefits Card What the Employee Sees at a GlanceEnrolled Medical, Dental, Vision, HSA/FSA, and 401(k) plans, per-paycheck pre-tax cost, and covered dependents Exact Workday Read PathPOST /wql/v1/data on allCurrentBenefitElections (WHERE elected = true) Required Employee As Self Security DomainSelf-Service: Benefits & Self-Service: Dependents

Because all four calls are independent reads scoped strictly to the signed-in employee’s Workday OAuth 2.0 Bearer token (Register API Client with Authorization Code Grant + PKCE), a stateless pass-through layer fires them concurrently (Promise.all) and renders the complete screen in a single round-trip.

Four UX Details That Prevent Confused HR Tickets

Getting JSON back from Workday is straightforward; presenting those fields so employees never misread a balance or deduction requires respecting four Workday data nuances:

1. Shoulder-Surfing Privacy on the Pay Card

Never splash $4,812.40 in 32-pixel type the instant the page loads on an open-plan office monitor or warehouse phone. Render the Payment Date (2026-11-15), Status (Complete), and pay frequency openly, mask currency figures ($••••.••) by default, and provide an inline Show amounts eye toggle that reveals Gross, Taxes, Pre-Tax Deductions, and Net Pay—plus a one-click comparison against the prior completed payslip (offset=1) so workers immediately spot why net pay shifted. Also respect Workday’s built-in Days from Payment Date to Display Payslip rule on the Pay Group, which GET /workers/me/paySlips enforces automatically.

2. Today’s Balance vs. Future-Date Projected PTO Balance

Workday’s absence engine deducts both Approved and Pending time-off requests when projecting balances (how Workday projects future time-off balances). If an employee has 48 hours available today, already has 24 hours approved for December holidays, and wants to check whether they can take a Friday off in January, showing only today’s static balance misleads them.

Add a compact “Balance as of [Date Picker]” control right inside the Time Off card that re-queries GET /absenceManagement/v5/balances?worker={me}&effective=2027-01-15 live—letting Workday’s own period schedule, year-end carryover cap, and pending-request math return the exact available hours or days.

3. Benefit Group Frequency Cost vs. Plan Frequency Cost

Nothing triggers faster Benefits helpdesk tickets than showing a monthly carrier rate ($360.00) to a biweekly employee who sees $166.15 deducted on their payslip. When querying allCurrentBenefitElections in WQL (full Workday Benefits API guide), bind your UI explicitly to the Benefit Group frequency fields:

Works
SELECT benefitType,
       benefitPlan,
       coverage,
       currentElectionCoverageBeginDate,
       employeeCostPerBenefitGroupFrequencyPre_Tax,
       employeeCostPerBenefitGroupFrequencyPost_Tax,
       dependents
FROM allCurrentBenefitElections
WHERE elected = true

Display waived plans (waived = true) behind an optional “Show waived coverage” disclosure link so the primary card stays crisp and uncluttered.

4. Zero-Clutter Conditional Task Banner

Most weeks of the year, an employee has zero items in My Tasks (querying My Tasks via REST and WQL). Instead of wasting a permanent quarter of the viewport on an empty “You’re all caught up!” box, collapse the task zone completely when inboxTasks.total === 0, and elevate it to the top of the screen with direct action buttons (Complete Onboarding Step, Review Document) the moment an Awaiting Action step arrives.

text
+-----------------------------------------------------------------------+
| [!] 1 Action Needed: Complete Annual Compliance Acknowledgment (Due Fri)|
+-----------------------------------+-----------------------------------+
| LATEST PAYSLIP · Nov 15, 2026     | TIME OFF · As of [ Today v ]      |
| Net Pay:  $••••.••  [Show]        | Paid Time Off:    56.0 hrs avail  |
| Status:   Complete                | Floating Holiday:  1.0 day avail  |
| [Compare with Oct 31 Payslip ->]  | Next Off: Nov 26–27 (Approved)    |
|                                   | [+ Request Time Off]              |
+-----------------------------------+-----------------------------------+
| ACTIVE BENEFITS · 2026 Plan Year                                      |
| Medical:  PPO Gold (Employee + Spouse)       $142.50 / paycheck       |
| Dental:   Dental Premier (Employee + Spouse)  $14.20 / paycheck       |
| HSA:      Health Savings Account              $100.00 / paycheck      |
+-----------------------------------------------------------------------+

Publishing Your Employee Hub in Plain English with Kiweely Leaf

Historically, replacing Workday’s multi-hub click path meant either buying a heavyweight HR intranet portal suite (which syncs and caches worker profiles in another vendor’s cloud and takes months of SI consulting) or pulling internal full-stack engineers off core product work to wire OAuth PKCE, WQL, and RaaS endpoints by hand.

Kiweely Leaf (coming next) gives HRIS administrators a direct, stateless path to launch this exact one-page hub:

  • Describe It in Plain English, Wired to Your Real Tenant: Connect your Workday tenant once with a single user-delegated API client (Register API Client). Describe the employee hub you want; Leaf’s AI agents inspect your tenant’s actual absence plans, units (hours vs. days), benefit groups, and languages, and wire the live REST, WQL, and RaaS calls automatically—with no Workday Extend license needed.
  • Zero HR Data Stored at Rest: Leaf is a pure stateless pass-through layer. Payslip amounts, benefit elections, dependent names, and PTO balances stream live from Workday under the signed-in worker’s own OAuth token and vanish from memory when the request completes.
  • Browser, Workplace Chat, and Phone in One Publish: Employees can open their hub at your company’s custom subdomain (hub.yourcompany.example), inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, or inside your company’s branded space in the Kiweely Leaf phone app on iOS and Android (one install, Workday SSO + Face ID/fingerprint, zero App Store review waits).

And when an employee looks at their latest payslip on the hub and wants to ask a follow-up question in natural language—“Why did my tax withholding change by $29 this check?”—Kiweely Bridge (also coming next) answers live inside Claude, ChatGPT, and Gemini on the exact same zero-storage Workday OAuth foundation.

Frequently asked questions

Why do employees get lost between Workday's delivered Benefits and Pay Hub, Absence hub, and My Tasks?

Workday organizes self-service around internal functional modules (Core Payroll, Absence Management, Benefits, and Business Process My Tasks), forcing workers to click across four different navigation trees and respect a 4-card home page ceiling instead of seeing one personal summary.

Should a single-screen employee hub hide net pay dollar amounts by default?

Yes. Rendering net and gross dollar figures behind a single-tap Reveal toggle protects employees opening their hub on an office monitor, commuter train, or breakroom phone while keeping the latest payment date and status immediately visible.

Why do benefit plan monthly rates confuse employees when shown next to payslips?

In Workday WQL (allCurrentBenefitElections), employeeCostPerBenefitPlanFrequency often reflects a monthly carrier rate, whereas employeeCostPerBenefitGroupFrequencyPre_Tax reflects the actual per-paycheck deduction (such as Biweekly). Always display the Benefit Group frequency cost.

Can this four-card hub run without syncing employee HR records into an external portal database?

Yes. Firing four parallel, employee-scoped Workday API calls (REST paySlips, REST absence balances, WQL allCurrentBenefitElections, and REST inboxTasks) under the signed-in worker's OAuth token renders the entire page live in memory with zero HR data stored at rest.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.