Employees trust internal addresses they recognize—like people.yourcompany.example or timeoff.yourcompany.example—and routinely ignore or report unfamiliar third-party vendor URLs as suspected phishing. Serving custom Workday self-service screens directly on your own company subdomain pairs DNS CNAME routing, automated TLS certificates, character-exact Workday OAuth 2.0 Redirection URI registration, and your corporate design tokens into an internal experience that looks and behaves like first-party software.
Even after IT configures corporate SAML single sign-on (Edit Tenant Setup - Security), employees often struggle to remember Workday’s regional datacenter URLs, bookmark stale implementation links before Sandbox refreshes, or bounce off generic HR portal chrome that looks nothing like the rest of your intranet. Putting clean, focused Workday screens at a memorable subdomain removes that friction while keeping Workday as the sole system of record and security engine.
Why First-Party Company Subdomains Matter for Security and Adoption
Routing employee self-service through a first-party subdomain solves four practical problems for InfoSec, IT Helpdesk, and HRIS teams simultaneously:
- Anti-Phishing Hygiene: Security awareness training teaches employees to inspect the browser address bar before approving requests or reviewing pay details. Sending an email or Slack link to
approvals.yourcompany.examplereinforces that habit instead of training staff to click unfamiliar external SaaS domains. - Memorable Direct Deep Links: Anyone in the company can type
timeoff.yourcompany.exampleor scan a breakroom QR code pointing toshifts.yourcompany.examplewithout searching Confluence for the right Workday worklet path. - Clean First-Party Cookie &
SameSiteBehavior: Modern browsers (especially Safari ITP and Chrome third-party cookie restrictions) aggressively block cross-site session state inside iframes and redirect chains. Running on a dedicated HTTPS subdomain ensuresSecure; HttpOnly; SameSite=LaxOAuthstateand PKCEcode_verifierbindings survive SAML IdP redirects cleanly (avoiding SAML/OIDC redirect loops on Workday’s authorize endpoint). - Password Manager & Passkey Scoping: WebAuthn passkeys and enterprise password managers bind credentials to the relying party domain (
rpId), keeping corporate identity autofill cleanly separated from unrelated external tools.
The Four Technical Layers Behind a Custom Workday Subdomain
Standing up a production subdomain in front of Workday spans DNS, TLS, Workday OAuth client configuration, and HTTP cache-control headers. Compare each layer’s configuration and failure mode:
| Infrastructure Layer | Exact Configuration | Workday / Browser Requirement | What Breaks If Misconfigured |
|---|---|---|---|
| Infrastructure Layer1. DNS Delegation | Exact ConfigurationCNAME record (e.g., timeoff -> edge target) plus CAA check |
Workday / Browser RequirementDNS CAA records on the apex domain must permit the edge Certificate Authority (e.g., Let’s Encrypt / Google Trust Services). |
What Breaks If MisconfiguredAutomated TLS issuance stalls even though dig CNAME resolves cleanly. |
| Infrastructure Layer2. Edge TLS & HSTS | Exact ConfigurationManaged X.509 cert, TLS 1.2/1.3, Strict-Transport-Security |
Workday / Browser RequirementWorkday requires https:// for every non-loopback OAuth Redirection URI. |
What Breaks If MisconfiguredWorkday refuses registration or browser blocks mixed-content redirects. |
| Infrastructure Layer3. Workday OAuth Callback | Exact ConfigurationRegister API Client -> Redirection URI grid |
Workday / Browser RequirementExact scheme, subdomain, port (implicit 443), and path: https://timeoff.yourcompany.example/oauth/callback. |
What Breaks If MisconfiguredPre-login OAuth error on /authorize (invalid_client or redirect_uri mismatch). |
| Infrastructure Layer4. Pass-Through HTTP Headers | Exact ConfigurationCache-Control: private, no-store on all API routes |
Workday / Browser RequirementStatic CSS/JS bundles may cache; worker JSON payloads must never enter CDN or browser disk caches. | What Breaks If MisconfiguredShared kiosk browsers or edge nodes risk retaining stale worker responses. |
Exact Workday Register API Client Alignment
When your HRIS or Security Administrator registers the user-delegated OAuth client in Workday via Register API Client (full OAuth PKCE setup guide), the Redirection URI table supports multiple rows. Use that multi-row table to stage cutovers safely without downtime:
Register API Client — Redirection URI Table:
Row 1 (Sandbox preview): https://timeoff-sandbox.yourcompany.example/oauth/callback
Row 2 (Production domain): https://timeoff.yourcompany.example/oauth/callbackWatch out for subtle string mismatches that cause Workday’s Authorization Endpoint (https://<ui-host>/<tenant>/authorize) to reject the handshake before SAML SSO even runs:
- A trailing slash difference (
/oauth/callback/vs./oauth/callback). - Mixed uppercase characters in the hostname (
https://TimeOff.YourCompany.example/oauth/callbackvs. lowercase DNS normalization). - Pointing the production subdomain at the Sandbox Authorization Endpoint after a Friday night Sandbox refresh (how Sandbox refreshes affect API clients).
Tracing the Stateless Sign-In and Pass-Through Flow
Once DNS and Register API Client are aligned, trace what happens when an employee opens https://timeoff.yourcompany.example on their laptop or phone browser:
# 1. Employee opens your company subdomain:
GET / HTTP/1.1
Host: timeoff.yourcompany.example
# 2. Pass-through edge generates PKCE S256 challenge + CSRF state and redirects to Workday SSO:
HTTP/1.1 302 Found
Location: https://<workday-ui-host>/<tenant>/authorize?response_type=code&client_id=<client_id>&redirect_uri=https%3A%2F%2Ftimeoff.yourcompany.example%2Foauth%2Fcallback&state=7c9a1e4b&code_challenge=K8mN2pQ...&code_challenge_method=S256
Set-Cookie: __Host-oauth_pkce=<sealed_verifier_and_state>; Path=/; Secure; HttpOnly; SameSite=Lax
# 3. Employee completes corporate SAML SSO + MFA; Workday redirects back to your subdomain:
GET /oauth/callback?code=91ab4f82c0...&state=7c9a1e4b HTTP/1.1
Host: timeoff.yourcompany.exampleThe pass-through backend exchanges code + code_verifier at Workday’s Token Endpoint (POST /ccx/oauth2/<tenant>/token), seals the resulting worker-scoped token with AES-256-GCM so nothing is stored in a database, and immediately renders the screen using live absenceManagement/v5, common/v1, WQL, or RaaS calls under that employee’s own Workday security groups.
Pairing a Custom Domain with Your Brand Tokens and Languages
A custom URL is only half of a cohesive internal experience; if the page loads at people.yourcompany.example and still looks like a generic gray enterprise form, employees feel the seam immediately.
When designing branded screens over Workday, four visual and localization details make external screens feel native to your company:
- Typography, Color Tokens, and Dark/Light Surfaces: Apply your exact brand primary color, surface neutrals, border radii, and corporate typeface rather than Workday’s fixed
.pmdcard styles. - Company Terminology: Match the terms your workforce actually uses—whether your retail stores say Partners, Associates, or Team Members, and whether your absence plans say PTO, Annual Leave, or Floating Holiday.
- Automatic Worker Locale: Respect each signed-in worker’s Workday preferred display language so an associate in Montreal sees French-Canadian labels and date formatting (
DD/MM/YYYY) at the exact sametimeoff.yourcompany.exampleURL that an associate in Austin sees in US English (MM/DD/YYYY). - Kiosk & Shared-Terminal Safety: On shared warehouse or clinic breakroom tablets, pair short session lifetimes with explicit one-click sign-out that clears sealed client state and triggers your IdP logout URL.
How Kiweely Leaf Publishes Custom-Domain Workday Screens Without DevOps Overhead
Standing up custom subdomains, certificate rotation, PKCE OAuth state cookies, and Workday API clients from scratch usually pulls platform engineers away from core product work. Kiweely Leaf (coming next) handles the entire pass-through hosting stack out of the box:
- Custom Company Address + Brand Space: Point your subdomain (
timeoff.yourcompany.exampleorhub.yourcompany.example) to Kiweely Leaf, apply your logo, colors, and typography once, and connect your tenant with a single user-delegated Workday API client—no Workday Extend license required. - HRIS Admins Publish in Plain English: Describe the employee hub, leave calendar, onboarding checklist, or manager view you want. Leaf’s AI agents inspect your live Workday tenant configuration, wire the underlying REST, WQL, RaaS, and SOAP calls, and publish directly to your custom address.
- Zero HR Data Stored at Rest: Every request runs live through memory under the signed-in employee’s own Workday OAuth token. Kiweely servers store only your screen definitions, branding, and domain settings—never worker profiles, payslips, or absence balances.
- One Screen Across Browser, Chat, and Phone: The exact same screen running on your custom browser subdomain also embeds cleanly inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, and appears automatically as a tile inside your company’s branded space in the Kiweely Leaf phone app on iOS and Android. *(And when employees want to ask ad-hoc Workday questions inside Claude, ChatGPT, or Gemini, Kiweely Bridge—also coming next—connects on the same zero-storage, user-delegated Workday OAuth foundation.)*
Frequently asked questions
Does hosting a custom employee portal on our own subdomain require a Workday Extend license?
No. External screens hosted at a custom subdomain such as timeoff.yourcompany.example connect over standard Workday OAuth 2.0 (Register API Client), REST, WQL, RaaS, and SOAP APIs included with any core Workday tenant.
Why does Workday reject an OAuth login after we switch from a staging URL to our custom company subdomain?
Workday validates the redirect_uri query parameter on the Authorization Endpoint character for character against the Redirection URI table on Register API Client. You must add your exact HTTPS custom subdomain callback URL to the API client before switching traffic.
How do browser SameSite cookies and corporate SSO interact with a custom company subdomain?
Serving the application on a first-party company subdomain over HTTPS with TLS 1.3 allows strict HttpOnly, Secure, SameSite=Lax session state binding during the OAuth 2.0 PKCE redirect round-trip without triggering third-party cookie blockers in Safari or Chrome.
Is employee HR data cached at the edge CDN when screens run on a custom subdomain?
Never in Kiweely Leaf. Static UI assets (fonts, CSS tokens, layout bundles) can be cached, while every Workday API response carries Cache-Control: no-store and streams through memory under the signed-in worker's own OAuth token with zero HR data stored at rest.