Skip to content
KiweelyKiweelyKiweely

Bringing Developer-Built Web Apps and HRIS-Built Screens Together in One Employee App

Internal engineers build domain-specific tools like shift-swap boards while HRIS teams need self-service pay, PTO, and approval screens. Mounting both inside your company’s Kiweely Leaf space gives employees one sign-in and lets developers use one stateless Workday OAuth pass-through.

  • By Kiweely
  • 6 min read
On this page

In almost every large enterprise, internal tools fracture across two disconnected camps: internal software engineers maintain custom web apps (like a warehouse shift-swap board, clinical credential tracker, or retail bonus calculator), while HRIS administrators field endless requests for cleaner Workday pay, time-off, and approval screens. Kiweely Leaf (coming next) brings both camps together inside one branded company space—so HRIS teams publish Workday screens in plain English, engineers mount their own hosted web apps right alongside them as tiles, and both share a single stateless, per-employee Workday OAuth 2.0 pass-through.

Without a shared employee home and authentication edge, workers end up juggling four bookmarks and three mobile logins, while every internal engineering squad wastes weeks reinventing Workday OAuth PKCE, WQL pagination, and SOAP XML envelopes from scratch.

How Employee Tools Fracture When Engineering and HRIS Build Separately

Look at what happens in a typical 4,000-person logistics, healthcare, or retail organization when an operational team needs a custom Shift Swap & Overtime Bid app alongside standard Request Time Off and My Payslip flows:

  1. Software Engineers Build the Operational Logic Fast, Then Stall on Workday Plumbing: Engineers spin up a clean TypeScript/React web app backed by Postgres for shift-swap matching rules in days. Then they need to verify each worker’s Supervisory Organization, scheduled shift blocks (timeTracking/v7 or WQL allTimeBlocks), job profile eligibility, and accrued absence balances in Workday—hitting browser CORS blocks, PKCE token exchange rules, and SOAP WSDLs.
  2. Mobile Distribution Strandings: Even after engineers ship shiftswap.company.example on desktop web, getting that tool onto hourly workers’ personal iPhones and Android phones with biometric sign-in and push notifications requires either a doomed App Store submission or corporate MDM that hourly staff refuse to install (see publishing mobile Workday apps without App Store review).
  3. HRIS Bottlenecks Engineering Sprints for Simple UI Tweaks: Once engineers own the employee portal repo, HRIS has to file Jira tickets and wait two sprints just to add a new Floating Holiday absence plan or update an Open Enrollment banner.
  4. Sprawling Integration System Users (ISUs): Tempted by deadline pressure, different engineering teams ask Workday admins for separate ISU service accounts, scattering high-privilege credentials across AWS Secrets Manager and forcing every app to re-implement Workday security filters in application code.

Division of Labor: What HRIS Builds in Plain English vs. What Engineers Host

Combining agent-built HRIS screens and developer-hosted web apps inside Kiweely Leaf lets each team own what it actually does best, while presenting one unified tile grid to the workforce:

Capability Agent-Built HRIS Screens (Kiweely Leaf) Developer-Hosted Web Apps Mounted in Leaf Employee & Security Experience
CapabilityWho builds & updates it Agent-Built HRIS Screens (Kiweely Leaf)HRIS administrators in plain English Developer-Hosted Web Apps Mounted in LeafInternal software engineers in your own Git repo & cloud (React, Next.js, Vue, etc.) Employee & Security ExperienceConsistent tiles side by side in your company’s branded space
CapabilityIdeal workloads Agent-Built HRIS Screens (Kiweely Leaf)Time off, leave calendars, pay summaries, benefits hubs, manager headcount, chat approvals, 3-button frontline flows Developer-Hosted Web Apps Mounted in LeafProprietary business logic: algorithmic shift bidding, territory commission simulators, lab/plant equipment checkout Employee & Security ExperienceEmployees never care which team built which tile
CapabilityWhere business state lives Agent-Built HRIS Screens (Kiweely Leaf)100% in Workday (zero external database) Developer-Hosted Web Apps Mounted in LeafOperational state in your database + live worker/org reads & writes in Workday Employee & Security ExperienceZero employee HR data stored at rest on Kiweely servers
CapabilityWorkday authentication Agent-Built HRIS Screens (Kiweely Leaf)Per-employee Workday OAuth 2.0 (Register API Client + PKCE) Developer-Hosted Web Apps Mounted in LeafShares Leaf’s per-employee Workday OAuth pass-through (no shared ISU needed) Employee & Security ExperienceEmployee signs in once with Workday SSO + Face ID / fingerprint
CapabilityMobile & chat delivery Agent-Built HRIS Screens (Kiweely Leaf)Instant across browser, Teams/Slack/DingTalk/Lark, and Kiweely Leaf phone app Developer-Hosted Web Apps Mounted in LeafInstant tile in the Kiweely Leaf phone app + privacy-safe push notifications Employee & Security ExperienceOne public App Store / Google Play install; zero store review per update

How the Shared Stateless Workday Pass-Through Works for Developers

When your engineers mount a custom web app inside your company’s Kiweely Leaf workspace, they no longer have to become Workday OAuth 2.0, WSDL, or SAML experts just to read who signed in or check their supervisory hierarchy.

1. Single Sign-On Once Across Every Tile

An employee opens the Kiweely Leaf phone app on iOS or Android (or your company’s custom browser domain) and signs in once through Workday SSO (Authorization Code Grant with PKCE; see user-delegated OAuth setup), verifying subsequent mobile sessions with Face ID or fingerprint.

Whether the worker taps Time Off & Pay (built by HRIS in Leaf) or Warehouse Shift Swap (hosted on your AWS/GCP VPC by your engineering team), they are already authenticated in your company’s branded environment—no second login prompt, no lost mobile browser tabs.

2. Calling Workday REST, WQL, RaaS, and SOAP as the Signed-In Worker

Instead of provisioning an over-privileged Integration System User, your developer-built app routes Workday requests through the worker’s live user-delegated session:

http
# Developer-built Shift Swap backend reads the signed-in worker's schedule & peers
# via user-delegated Workday WQL — Workday enforces constrained org visibility natively:
POST /ccx/api/wql/v1/{tenant}/data HTTP/1.1
Accept: application/json
Content-Type: application/json

{
  "query": "SELECT worker, businessTitle, location, supervisoryOrganization FROM workersByOrganization WHERE supervisoryOrganization = 'Warehouse 4 - Day Shift'"
}

Because the request executes under the signed-in employee’s (or supervisor’s) own Workday OAuth Bearer credential:

  • Workday enforces row- and field-level security natively: A day-shift associate cannot query compensation grades or pull schedules from an unrelated corporate department, even if an engineer makes a mistake in a frontend query parameter.
  • Real Worker Audit Trails: If the shift-swap app submits a schedule change or absence request after supervisor sign-off, Workday’s Business Process History records the actual employee or manager—not a generic ISU_ShiftApp service user (SOAP and REST Bearer token behavior).
  • No Workday Extend License Needed: Both Leaf’s HRIS screens and your engineers’ external web apps talk to standard Workday REST, WQL, RaaS, and SOAP APIs included with any core Workday tenant. (If your engineers also build in-tenant .pmd/.amd apps on Workday Extend or Studio assemblies, Kiweely Vine accelerates that developer workflow today on Mac and Windows.)

3. Privacy-Safe Notifications for Developer Apps Too

When Associate A offers a Saturday shift to Associate B in your developer-built shift-swap app, Associate B shouldn’t miss the offer because they don’t have a corporate email inbox—and shouldn’t have shift details plastered across a public lock screen. Through the Kiweely Leaf phone app, your company space delivers a privacy-safe push notification alerting Associate B that an action awaits them, keeping all shift and worker details strictly inside the biometric-protected app.

Practical Architecture Pattern: Keeping Boundaries Clean

To get the most out of pairing HRIS-built Leaf screens with engineer-built web apps, draw a crisp boundary on Day 1:

  1. Never Duplicate Core Workday Self-Service in Custom Code: Let HRIS own Pay Summaries, Time Off Requests, Team Absence Calendars, Onboarding Checklists, and Manager Approvals in Kiweely Leaf using plain English. When HRIS updates an absence plan or business process rule next quarter, HRIS updates the Leaf screen in two minutes without filing an engineering ticket.
  2. Reserve Engineering Headcount for Differentiated Operations: Point your software engineers exclusively at workflows where proprietary rules live outside Workday—like multi-constraint shift trading, production-floor incentive trackers, or field-service dispatch—and mount those web apps as tiles inside your Leaf space.
  3. Standardize on Least-Privilege Register API Client Scopes: Scope your tenant’s user-delegated API client strictly to the Functional Areas your combined tiles actually invoke (Staffing, Time Off and Leave, Time Tracking, System), and verify behavior across Employee, Manager, and HR Partner personas in Sandbox before production launch.
  4. Add Conversational Reach Where Helpful: Alongside visual tiles in Kiweely Leaf, Kiweely Bridge (also coming next) gives employees and managers conversational Workday access inside Claude, ChatGPT, and Gemini on the exact same zero-storage, user-delegated OAuth architecture.

Frequently asked questions

Do our internal developers have to rewrite their existing React, Vue, or Next.js web apps to appear in Kiweely Leaf?

No. Developer-hosted web apps run on your own cloud infrastructure and mount as native tiles inside your company's branded Kiweely Leaf space, inheriting single sign-on and mobile distribution without mobile binary builds.

Why shouldn't each internal web app register its own Integration System User in Workday?

Registering shared Integration System Users bypasses Workday's per-worker security groups and obscures Process History audit trails. Routing calls through a shared user-delegated Workday OAuth pass-through ensures every read and write executes as the signed-in employee.

Who owns HR self-service updates versus custom operational logic in this hybrid model?

HRIS administrators describe and update Workday self-service screens (time off, pay summaries, approvals, manager views) in plain English inside Kiweely Leaf, while software engineers focus exclusively on proprietary operational apps such as shift bidding, fleet dispatch, or commission calculators.

Does mounting developer web apps alongside Leaf screens store HR records on Kiweely servers?

No. Kiweely Leaf operates strictly as a stateless pass-through layer: zero employee HR data is stored at rest on Kiweely servers, and every Workday API request runs live under the signed-in worker's own OAuth token.

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.