You do not need a commercial Workday Extend license to give employees, frontline workers, or busy managers cleaner screens in front of Workday. Every standard Workday tenant already includes user-delegated OAuth 2.0 (Register API Client), Workday REST APIs, Workday Query Language (WQL), Reports-as-a-Service (RaaS), and Workday Web Services (SOAP)—everything required to run custom, branded pass-through screens under each signed-in worker’s own Workday permissions.
Many HRIS and IT leaders assume they face a binary choice: either live with Workday’s multi-menu browser screens for warehouse workers and occasional manager approvers, or budget for a commercial Workday Extend subscription plus specialized .pmd and .amd developer headcount (see whether Workday Extend is free). Understanding what sits inside Extend versus what ships with every core tenant clarifies when an external pass-through UI is faster, freer in layout, and simpler to govern.
Inside the Tenant (Workday Extend) vs. Outside the Tenant (Standard APIs)
Workday Extend is an in-tenant application platform: your pages live inside Workday’s navigation shell, use Workday’s presentation metadata (.pmd) widget components, and can persist new .businessobject tables inside Workday’s database. When you already license Workday Extend and want apps inside Workday, Kiweely Vine builds, validates, and browser-tests those Extend apps today.
However, a huge share of employee experience requests do not need new database tables inside Workday—they need a radically simpler screen over existing Workday tasks and records:
- A 3-button phone screen in Spanish, Vietnamese, or Mandarin where warehouse associates check shift schedules, clock or review hours, and request a day off without hunting through Workday’s navigation.
- A single onboarding and self-service hub combining pay, absence balances, open My Tasks, and benefits status on one branded page.
- Inline leave, expense, and timecard approval screens embedded directly inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark.
- A one-page manager view showing team headcount, open positions, and who is out this week for leaders who open Workday twice a quarter.
Compare the two architectural paths side by side:
| Architectural Dimension | External Pass-Through UI on Standard APIs | Workday Extend (In-Tenant App) |
|---|---|---|
| Architectural DimensionWorkday Licensing | External Pass-Through UI on Standard APIsIncluded with core Workday tenant (Register API Client, REST, WQL, RaaS, SOAP). |
Workday Extend (In-Tenant App)Requires commercial Workday Extend subscription (Core, Professional, or AI). |
| Architectural DimensionUI & Brand Freedom | External Pass-Through UI on Standard APIsComplete web/mobile layout freedom: custom typography, languages, 3-button frontline flows, custom subdomains (timeoff.company.com). |
Workday Extend (In-Tenant App)Bound to Workday .pmd page widgets, Workday navigation shell, 100 KB page limits, and a 4-card home page ceiling. |
| Architectural DimensionWorkplace Chat Embedding | External Pass-Through UI on Standard APIsEmbeds directly as an app tab or modal inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark. | Workday Extend (In-Tenant App)Renders inside the Workday web/mobile app rather than third-party workplace super-apps. |
| Architectural DimensionEmployee Security Model | External Pass-Through UI on Standard APIsNative per-worker enforcement via Workday OAuth 2.0 Authorization Code + PKCE tokens. | Workday Extend (In-Tenant App)Native per-worker enforcement via Workday in-tenant sso endpoint binding. |
| Architectural DimensionData Storage | External Pass-Through UI on Standard APIsStateless pass-through reads/writes live Workday objects; zero HR records stored outside Workday. | Workday Extend (In-Tenant App)Stores custom .businessobject rows inside Workday (needed only when Workday lacks a native object). |
The Five Standard Workday Building Blocks That Power External Screens
When you build a stateless external UI layer over a core Workday tenant, five delivered platform capabilities do all the heavy lifting:
1. User-Delegated Identity: Register API Client (OAuth 2.0 + PKCE)
Security starts by avoiding shared Integration System Users (Register API Client for Integrations). Instead, an administrator runs Register API Client, selects Authorization Code Grant with Support Proof Key for Code Exchange (PKCE) enabled, sets Access Token Type to Bearer, and selects only the Functional Areas the screens require (such as Time Off and Leave, Time Tracking, Staffing, and System for WQL; see OAuth API Client with PKCE setup).
When an employee opens your custom screen, they complete corporate SSO and MFA on Workday’s own sign-in page—or map cleanly from single sign-on inside Microsoft Teams, DingTalk, Feishu, or Lark to their Workday worker session. Every subsequent HTTP request carries that employee’s own short-lived Bearer token.
2. Fast Self-Service Reads and Actions: Workday REST APIs
Workday’s versioned REST catalog covers high-frequency employee and manager interactions cleanly in JSON:
common/v1: Worker profile headers (/workers/me), direct reports, supervisory organizations, pay slip summaries, and pending My Tasks items (/workers/{ID}/inboxTasks).absenceManagement/v5: Live absence plan balances (/balances), eligible absence types, holiday/schedule-awarevalidTimeOffDates, andPOST /workers/{ID}/requestTimeOff.timeTracking/v7: Web clock events (/timeClockEvents), worker time blocks, time totals, and time attestations.businessProcess/v1: Event step details, comments, attachments, and/eventSteps/{ID}/approve,/deny,/sendBack, or/toDo.
3. Live Cross-Object Queries: Workday Query Language (WQL)
Whenever a custom screen needs tailored columns—such as a manager’s open positions combined with team absence calendar dates or unsubmitted project hours—GET and POST /wql/v1/data execute SQL-like queries against hundreds of Workday data sources (compare RaaS, WQL, and REST). Because WQL honors object- and field-level security for the issuing user token, a manager querying workersByOrganization or allOpenPositions sees only their authorized supervisory hierarchy.
GET /ccx/api/wql/v1/{tenant}/data?query=SELECT+worker,location,hireDate+FROM+myDirectReports HTTP/1.1
Authorization: Bearer <employee_oauth_access_token>
Accept: application/json4. Tenant Calculated Fields: Reports-as-a-Service (RaaS)
If your HRIS team has already built complex conditional logic in Workday calculated fields—such as local statutory leave balances, custom shift differentials, or onboarding readiness flags—enabling Enable as Web Service on an Advanced Custom Report exposes a JSON RaaS endpoint immediately. Calling that RaaS URL with the employee’s Bearer token runs the report as that employee without migrating formulas out of Workday.
5. Deep Transactional Reach: Workday Web Services (SOAP)
For long-tail HR, Payroll, Benefits, or Financial operations not yet surfaced in the REST catalog, Workday’s mature SOAP web services (Human_Resources, Absence_Management, Time_Tracking, Staffing, Financial_Management) accept the exact same OAuth 2.0 Bearer token in the HTTP Authorization header. Translating clean UI form state into typed SOAP envelopes in memory gives external screens full transactional parity without storing anything on disk.
When You Should Still Choose Workday Extend
If your workflow requires inventing brand-new multi-object data models that have no home in core Workday (for example, a 15-table grant-equipment ledger or internal patent-award registry that must live inside Workday’s database), Workday Extend is the right tool—and Kiweely Vine builds Extend apps rapidly (Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.). When the data and business processes already live in Workday and the problem is Workday’s UI, an external pass-through layer solves it without an Extend license.
How Kiweely Leaf Builds and Hosts Custom Workday Screens—With Zero Stored HR Data
Wiring per-employee Workday OAuth PKCE, tenant-specific absence plans, WQL aliases, RaaS prompts, and SOAP error handling by hand takes months of full-stack engineering. Kiweely Leaf (coming next) turns that architecture into a plain-English workflow for HRIS administrators:
- Describe the screen in plain English: Connect your tenant once with a single Workday API client, then describe the portal, chat approval view, manager dashboard, or 3-button frontline app your workforce needs. Leaf’s AI agents inspect your live Workday tenant—your actual business processes, absence plans, security domains, and units—wire the underlying REST, WQL, RaaS, and SOAP calls, and host the screen.
- Stateless pass-through security: Leaf stores zero employee HR data at rest on Kiweely servers—only screen layouts, branding, and tenant connection settings. Every read and write runs live under the signed-in employee’s own Workday OAuth token.
- Browser, Workplace Chat, and One Workforce Phone App: Employees open screens in any browser at your company’s custom address, embedded inside DingTalk, Feishu, Lark, Microsoft Teams, or Slack, or inside the Kiweely Leaf phone app on iOS and Android. With the Kiweely Leaf phone app, employees install once from the App Store or Google Play (zero App Store review per company app), sign in once with Workday SSO plus Face ID or fingerprint, land in your company’s branded space holding both Leaf-built tiles and web apps hosted by your own developers, and receive privacy-safe notifications that keep HR details inside the app. (Consultants and HRIS admins use the separate Kiweely companion phone app for Vine and Kiweely Nest; employees use the Kiweely Leaf app.)
And if your employees prefer asking questions or submitting simple requests in Claude, ChatGPT, or Gemini rather than opening a screen at all, Kiweely Bridge (also coming next) pairs naturally alongside Leaf on the exact same standard-tenant, zero-storage Workday OAuth foundation.
Frequently asked questions
Does a standard Workday HCM or Financials tenant allow external web apps to call Workday APIs?
Yes. Every standard Workday tenant includes Register API Client (OAuth 2.0 Authorization Code Grant with PKCE), Workday REST APIs, Workday Query Language (WQL), Reports-as-a-Service (RaaS), and Workday Web Services (SOAP) without requiring a Workday Extend license.
When do you actually need a commercial Workday Extend subscription?
You need Workday Extend when custom pages must render inside the Workday browser chrome (.pmd/.amd), store new custom relational tables (.businessobject) up to 10M or 100M rows inside the Workday tenant, or run Extend Orchestrations inside Workday's runtime.
How does an external custom screen enforce Workday's constrained security?
Instead of connecting with a shared Integration System User, the external UI layer authenticates each employee via Workday OAuth 2.0 Authorization Code Grant. Every API call passes that employee's own short-lived Bearer token, so Workday evaluates their exact Employee as Self or Manager security groups.
Where can external pass-through Workday screens run that Workday Extend pages cannot?
External screens can run at your own company subdomain, embedded natively inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, or inside a dedicated multi-language mobile space—completely free of Workday's page layout constraints and 4-card home page limits.