Skip to content
KiweelyKiweelyKiweely

Pass-Through Workday Screens vs. Caching HR Portals: Security and Sync Tradeoffs

Employee experience portals that replicate Workday worker tables into a second cloud database create stale org permissions, GDPR/PII duplication, and brittle sync pipelines. Stateless pass-through screens query Workday live under each employee’s OAuth token and keep zero HR data at rest.

  • By Kiweely
  • 6 min read
On this page

When putting a cleaner employee or manager interface in front of Workday, the single biggest architectural fork is where worker data and access rules live: inside a caching HR portal that syncs Workday tables into a second vendor cloud, or through a stateless pass-through UI that queries Workday live on demand under each employee’s own OAuth session and stores zero HR records at rest. For security review speed, permission accuracy, and operational upkeep, stateless pass-through wins decisively whenever Workday is already your system of record.

Traditional intranet and employee experience suites grew up before Workday offered fast JSON REST endpoints and Workday Query Language (WQL). To render a page quickly in 2016, portals ran nightly or hourly outbound integrations—via Core Connector: Worker, RaaS CSVs, or SOAP Get_Workers—using a high-privilege Integration System User (ISU) and copied your entire workforce directory, reporting hierarchy, and leave balances into the portal’s own relational database and search index. Today, that shadow-database pattern creates far more security and maintenance debt than it solves.

Architectural Comparison: Stateless Pass-Through vs. Caching HR Portals

Examine what happens to identity, authorization, data freshness, and compliance across the two designs:

Dimension Stateless Pass-Through Workday UI Caching / Synced HR Portal
DimensionHR Data at Rest Outside Workday Stateless Pass-Through Workday UIZero. Stores only UI layout definitions, branding, and tenant endpoint config. Caching / Synced HR PortalFull or partial shadow copy: worker profiles, manager trees, job attributes, cases, and indexed fields stored in vendor DB.
DimensionWorkday Credential Type Stateless Pass-Through Workday UIPer-employee OAuth 2.0 Authorization Code + PKCE (Register API Client). Caching / Synced HR PortalShared Integration System User (ISU) (Register API Client for Integrations) for bulk sync.
DimensionPermission Enforcement Stateless Pass-Through Workday UIWorkday evaluates live on every read and write using the employee’s real security groups. Caching / Synced HR PortalPortal rebuilds ACLs in its own role engine; out-of-sync windows expose stale manager access.
DimensionData Freshness Stateless Pass-Through Workday UIInstant (0-second lag): reflects Change Job, rescinds, PTO submissions, and approvals immediately. Caching / Synced HR PortalDelayed (15 min to 24 hours): stale balances and ghost My Tasks items between sync runs.
DimensionWrite Audit Attribution Stateless Pass-Through Workday UIRecorded in Workday Process History as the actual signed-in worker or manager. Caching / Synced HR PortalOften recorded as ISU_Portal_Prod unless custom on-behalf-of plumbing is maintained.
DimensionInfoSec, GDPR & DPA Scope Stateless Pass-Through Workday UIMinimal: no secondary PII store, no data-retention purge jobs, no backup-snapshot exposure. Caching / Synced HR PortalHeavy: full sub-processor PII storage review, breach-blast-radius assessment, and erasure syncs.

Three Failure Modes of Syncing Workday Into a Portal Database

Teams rarely feel the pain of a caching HR portal on day one of a sandbox demo. The cracks appear three months into production when real Workday staffing complexity hits the sync pipeline.

1. Rebuilding Workday’s Constrained Security Engine Is a Losing Battle

Workday does not decide who sees a record with simple department_id = X filters. It evaluates constrained and unconstrained role-based security groups, subordinate supervisory inheritance, matrix manager visibility, Intersection Security Groups (for example, HR Partner intersected with EMEA Region, excluding Executive Job Management Level), and domain vs. business process security policies.

When a caching portal extracts data using a privileged ISU, Workday strips none of those nuances because the ISU was granted broad Worker Data read permissions to feed the sync. Now the portal’s administrators must recreate every Workday security rule inside the portal’s own ACL syntax. Whenever HRIS updates a Workday security group—or rescinds a misrouted Transfer Employee event—any mismatch between Workday security and portal ACLs becomes an unauthorized data disclosure: a former manager continues viewing a transferred report’s profile or pending actions until the next full delta reconciliation succeeds.

2. Sync Lag Confuses Employees on Transactional Screens

Caching works fine for static cafeteria menus and holiday PDFs. It fails miserably on live HR transactions:

  • An employee submits 16 hours of PTO at 10:02 AM, refreshes the caching portal at 10:05 AM, still sees their old unreduced balance, and submits a duplicate request thinking the first one failed.
  • A manager approves an expense report in Workday mobile on the train, opens the intranet portal at their desk 20 minutes later, still sees the cached “1 Pending Approval” badge, clicks it, and hits a SOAP fault because the Event Record already completed.
  • A newly hired employee whose Assign Pay Group step completed ten minutes ago is still blocked by a portal rule reading yesterday’s synced worker eligibility table.

In a pass-through UI, opening the screen calls GET /absenceManagement/v5/balances or GET /common/v1/workers/me/inboxTasks directly against Workday. The screen cannot drift from Workday because Workday is the only database answering the request.

3. Doubling Your PII Attack Surface and InfoSec Review Timeline

Every Chief Information Security Officer and privacy counsel asks the same first question during HR vendor review: “Exactly which employee fields do you store at rest in your cloud?”

The moment a portal stores employee names, worker IDs, locations, supervisory relationships, leave history, or compensation attributes in Postgres, Elasticsearch, or vector embeddings, your security review expands by weeks or months:

  • You must audit database encryption keys, backup retention windows, tenant row isolation, and search-index access controls.
  • Every GDPR/CCPA data-subject request or Workday Purge Person Data run must also be verified against the portal’s database, logs, and cached backups.
  • Every semi-annual Workday release (R1 and R2) requires regression-testing your outbound change-detection sync alongside the UI itself.
Fails
# Caching Portal Data Flow
Workday Tenant --(Broad ISU Bulk Extract)--> Portal Cloud DB & Search Index --> Custom Portal ACLs --> Employee Browser
Result: Duplicated PII at rest, stale balances/approvals, and shadow security drift.
Works
# Stateless Pass-Through Data Flow
Employee Browser <--(Streams in RAM, Zero Storage)--> Pass-Through UI Layer <--(Employee's Own OAuth + PKCE Token)--> Workday Tenant
Result: Zero HR data at rest outside Workday, 0-second lag, and 100% native Workday security enforcement.

When Caching Still Makes Sense (Outside Core Workday Screens)

Enterprise search across non-Workday knowledge bases—such as indexing 5,000 IT troubleshooting articles, PDF benefits booklets, and facilities policies—legitimately belongs in a content index. Just never confuse indexing public policy documents with replicating per-worker Workday HR records into a portal database.

How Kiweely Leaf and Kiweely Bridge Deliver Pure Pass-Through Access

Both of Kiweely’s upcoming workforce products—Kiweely Leaf (custom employee, manager, and frontline screens, coming next) and Kiweely Bridge (Workday MCP connector for Claude, ChatGPT, and Gemini, coming next)—are engineered strictly as stateless pass-through layers over standard Workday APIs:

  • Zero employee HR data at rest: Leaf stores only your screen layouts, branding, and tenant connection settings; Bridge stores only tenant routing, enabled tool rules, and payload-free call counts (see Bridge’s security model). Worker records, balances, org charts, and pay details stream through memory during the request and are gone when the response finishes.
  • Each employee’s own Workday OAuth token: Both products connect via user-delegated Workday OAuth (Register API Client with Authorization Code Grant and PKCE), never a shared Integration System User. Workday enforces every domain policy, business process policy, and supervisory constraint in real time.
  • No Workday Extend license required: Leaf opens in any desktop or phone browser at your company’s address, inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, or inside the Kiweely Leaf phone app (where employees sign in once with Workday SSO + Face ID/fingerprint and receive privacy-safe notifications that keep HR details inside the app). Bridge connects Claude, ChatGPT, and Gemini across desktop, web, and mobile starting at $499/mo per company (up to 1,000 employees) with unlimited calls, dedicated single-tenant IP options, or self-hosted stateless containers in your own cloud.

Frequently asked questions

What is the difference between a pass-through Workday UI and a caching HR portal?

A pass-through UI stores only layout, branding, and connection metadata; when an employee opens a page, it calls Workday APIs live using that employee's own OAuth token and discards the response from memory once rendered. A caching HR portal periodically extracts worker profiles, org trees, and balances via an Integration System User into its own cloud database.

Why do caching HR portals struggle with Workday security permissions?

Workday evaluates access dynamically across supervisory hierarchies, matrix roles, intersection security groups, and effective-dated staffing events. Once a portal pulls records via a privileged integration user into a separate database, engineers must rebuild and maintain a shadow copy of Workday's security engine that drifts during reorganizations and transfers.

Are live Workday REST and WQL calls fast enough for interactive employee screens?

Yes. Targeted Workday REST endpoints (such as inboxTasks, balances, and worker summaries) and scoped WQL queries return JSON in hundreds of milliseconds when queried for a single signed-in worker or supervisory branch, avoiding any need to pre-sync tens of thousands of worker rows.

How does a pass-through architecture shorten InfoSec and privacy reviews?

Because zero employee PII, compensation, leave history, or bank data is written to disk, databases, search indexes, or application logs outside Workday, there is no secondary HR database to encrypt at rest, purge on right-to-erasure requests, or audit for stale access.

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.