Choose Workday Extend when your organization already holds an Extend subscription and needs new custom Business Objects, custom Business Processes, or Orchestrations living natively inside Workday’s menus; choose external stateless pass-through screens when you do not license Extend, or when employees, managers, and frontline crews need full visual freedom in the browser, on the phone, or embedded inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark without opening Workday. Both architectures preserve per-employee Workday security and keep zero shadow HR databases outside your tenant—they simply solve different layers of the stack.
HRIS leaders frequently treat “build inside Extend” and “build outside Workday” as ideological rivals. In practice, evaluating five concrete technical dimensions—licensing, data model ownership, UI layout freedom, distribution channels, and builder skillset—settles which architecture fits each workflow in minutes.
Decision Matrix: Workday Extend vs. External Pass-Through Screens
Compare what runs inside the Workday tenant (built by developers or with Kiweely Vine, live today) against a hosted pass-through UI layer (Kiweely Leaf, coming next):
| Architectural Dimension | Workday Extend (Inside the Tenant) | External Pass-Through Screens (Kiweely Leaf, Coming Next) |
|---|---|---|
| Architectural DimensionWorkday Licensing Needed | Workday Extend (Inside the Tenant)Commercial Workday Extend subscription (plus Orchestrate quotas where applicable). | External Pass-Through Screens (Kiweely Leaf, Coming Next)Standard core Workday tenant only (Register API Client, REST, WQL, RaaS, SOAP). Zero Extend SKU required. |
| Architectural DimensionCustom Data Storage | Workday Extend (Inside the Tenant)Creates custom Business Objects (model / .amd / .smd) stored natively inside Workday with built-in security domains and custom Business Processes. |
External Pass-Through Screens (Kiweely Leaf, Coming Next)Reads and writes existing Workday objects (Time Off, Leave, Expenses, Staffing, RaaS, Inbox). Stores zero employee HR data at rest on Kiweely servers. |
| Architectural DimensionUI & Layout Freedom | Workday Extend (Inside the Tenant)Bound to Workday Presentation Metadata (.pmd) widgets, Canvas/Horizon page grids, and Workday’s global navigation chrome. |
External Pass-Through Screens (Kiweely Leaf, Coming Next)Complete web and mobile freedom: your company’s brand, custom typography, worker languages, 3-button frontline layouts, or multi-panel dashboards. |
| Architectural DimensionWhere Employees Open It | Workday Extend (Inside the Tenant)Inside the Workday web application and Workday mobile app. | External Pass-Through Screens (Kiweely Leaf, Coming Next)Any desktop/phone browser at your custom domain, inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, or inside the Kiweely Leaf phone app. |
| Architectural DimensionWho Builds & Ships It | Workday Extend (Inside the Tenant)Extend developers writing .pmd, .amd, .pod, and WQL—accelerated end-to-end on Mac and Windows by Kiweely Vine. |
External Pass-Through Screens (Kiweely Leaf, Coming Next)In-house HRIS admins describing the screen in plain English; AI agents inspect the tenant, wire Workday APIs, and publish the hosted screen. |
| Architectural DimensionSecurity & Audit Model | Workday Extend (Inside the Tenant)Runs natively under the signed-in Workday worker’s session and security groups. | External Pass-Through Screens (Kiweely Leaf, Coming Next)Runs live under the signed-in worker’s user-delegated Workday OAuth 2.0 token (never an Integration System User); audited in Workday as that worker. |
Where Workday Extend Wins Decisively
Workday Extend is not just a screen builder—it extends Workday’s internal object model. Reach for Extend whenever your requirements hit any of these three conditions:
1. You Need Net-New Relational Business Objects Inside Workday
Suppose your company tracks tuition reimbursement agreements with multi-year clawback schedules, safety equipment serial numbers issued per warehouse worker, or internal patent disclosures tied to Worker and Cost_Center instances—and you want those records queryable via WQL alongside delivered HCM data, governed by custom Workday security domains, and routed through a custom Workday Business Process with native My Tasks steps.
Delivered Workday objects only give you limited Custom Object extensions on existing parents. Workday Extend lets you define standalone custom Business Objects with their own lifecycle states, relationships, and security policies inside your tenant. With Kiweely Vine (live today for Mac and Windows; 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.), consultants and developers generate, deploy, and multi-persona test complete .pmd/.amd Extend apps and Orchestrations directly against Development tenants without hand-coding every JSON metadata file.
2. The Users Already Live Inside Workday Eight Hours a Day
Compensation analysts, Payroll coordinators, and HR Partners already keep Workday open all day. Dropping a specialized Extend page directly onto a Worker Profile tab or functional hub keeps specialists inside one browser session without switching tabs.
3. Cross-System Orchestrations Triggered by Business Process Events
When a Workday Hire or Change Job event needs an internal orchestration engine to transform payloads and call external endpoints inside Workday’s managed runtime, Extend Orchestrations run right next to the Business Process step.
Where External Pass-Through Screens Win Decisively
Even organizations that love Workday hit hard walls when trying to serve occasional managers, multilingual warehouse or retail crews, or companies without an Extend contract. External pass-through screens solve four structural gaps that Extend cannot:
1. You Do Not License Workday Extend
Many mid-market and enterprise Workday customers run core HCM, Absence, Time Tracking, Payroll, and Financials without purchasing Workday Extend. Every standard tenant already includes Register API Client (OAuth 2.0 Authorization Code Grant with PKCE), Workday REST endpoints, live WQL, RaaS custom reports, and SOAP web services. Kiweely Leaf (coming next) builds directly on those core APIs—requiring zero Extend subscription.
2. Escaping Workday’s .pmd Widget and Menu Constraints
Workday’s Presentation Metadata (.pmd) deliberately enforces Workday’s form, grid, and section conventions so Extend apps look like native Workday tasks. That uniformity becomes a liability when:
- A distribution center worker on a 5-inch phone screen needs three oversized buttons in Spanish or Vietnamese (Clock In, Request Shift Swap, Report Absence) with zero nested Workday menus.
- An engineering VP who opens Workday twice a quarter wants one single-screen view combining open requisitions, direct-report PTO overlaps, and pending approvals without clicking through four separate Workday worklets.
- Your employer brand team wants a day-one new-hire onboarding hub at your own custom web address (
onboarding.yourcompany.com—for instance, an internal subdomain on your corporate domain) in your exact typography and colors.
3. Meeting Employees Inside Teams, Slack, DingTalk, Feishu, and Lark
Frontline and regional workforces rarely check email or bookmark Workday URLs—their entire workday runs inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark. Leaf screens embed directly as workplace apps inside those chat clients, or open inside the Kiweely Leaf phone app (one iOS and Android app on the App Store and Google Play where employees sign in once with Workday SSO plus Face ID or fingerprint, land in your company’s branded space, see both Leaf-built screens and web apps hosted by your own developers, and get privacy-safe lock-screen notifications that keep HR details inside the app—with zero App Store review per company app).
4. Empowering HRIS Admins Without an Engineering Backlog
General-purpose app builders like Retool, Superblocks, or Lovable give you a blank canvas, but still leave full-stack engineers responsible for wiring user-delegated Workday OAuth + PKCE, WQL pagination, REST/SOAP validation errors, and semi-annual release regressions—often cutting corners with a dangerous shared Integration System User. In Kiweely Leaf, HRIS admins describe the screen in plain English; AI agents inspect your tenant’s actual absence plans, business processes, and security domains, wire per-user OAuth APIs, and host the pass-through screen with zero employee HR data stored at rest.
Quick Workflow Triage Checklist
Use these five yes/no checks to pick the right tool on your next intake ticket:
- Does the workflow invent new HR/Finance tables that do not exist in Workday today?
- Yes: Build a custom Business Object in Workday Extend (using Kiweely Vine to ship and test it fast).
- No (reads/writes Time Off, Leave, Time Tracking, Staffing, Pay, Inbox, or RaaS): An external pass-through screen in Kiweely Leaf (coming next) handles it without Extend.
- Do you already hold an active Workday Extend contract?
- No: External pass-through over standard Workday APIs avoids a net-new Extend procurement cycle.
- Must the screen embed inside DingTalk, Feishu, Lark, Teams, Slack, or use a stripped-down frontline mobile layout?
- Yes: Choose an external pass-through screen (
Kiweely Leaf).
- Yes: Choose an external pass-through screen (
- Is there even a screen needed, or do employees just want to ask ad-hoc questions in natural language?
- Ad-hoc questions: Connect Claude, ChatGPT, and Gemini directly to your tenant with Kiweely Bridge (coming next), which shares the exact same user-delegated OAuth and zero-stored-data pass-through architecture.
- Can your security team accept a vendor caching worker tables in a secondary database?
- No: Both Workday Extend (data stays in Workday) and Kiweely Leaf / Bridge (stateless pass-through, zero HR data at rest) satisfy strict zero-duplication security mandates, unlike caching HR portals.
Frequently asked questions
When is Workday Extend the better architectural choice over an external pass-through UI?
Choose Workday Extend when your company already licenses Extend and the workflow requires new tenant-resident Business Objects with custom state machines, custom Business Processes, or native tasks embedded directly inside Workday menus and hubs.
Does an external pass-through UI require a Workday Extend commercial subscription?
No. External pass-through screens built with Kiweely Leaf (coming next) connect over standard Workday OAuth 2.0 Authorization Code Grant, REST APIs, WQL, RaaS, and SOAP web services included with a core Workday tenant.
Do external pass-through apps weaken Workday's security or duplicate HR data?
Not when engineered as stateless pass-through. Every request executes live under the signed-in employee's own Workday OAuth token—never an Integration System User—and zero employee HR records are stored at rest outside Workday.
Can an organization run both Workday Extend apps and external pass-through screens?
Yes. Many teams use Kiweely Vine to build and maintain deep back-office Extend Business Objects inside Workday while planning external pass-through screens for frontline workers, managers in Teams or DingTalk, and branded portals.