Skip to content
KiweelyKiweelyKiweely

Five Things to Check in Your Workday Sandbox Before Connecting External AI or Custom Screens

Before connecting external AI assistants or pass-through screens to Workday, check five Sandbox settings: OAuth 2.0 Register API Client access, SSO + PKCE redirect behavior, Employee As Self domain permissions, web-service-enabled RaaS reports, and multi-role test personas.

  • By Kiweely
  • 6 min read
On this page

Preparing your Workday Sandbox for user-delegated external AI assistants (Kiweely Bridge, coming next) or stateless pass-through employee screens (Kiweely Leaf, coming next) comes down to five 15-minute administrative checks: enabling OAuth 2.0 user-delegated API clients, verifying Sandbox SSO and Authentication Policy behavior, auditing Employee As Self Report/Task domain permissions, checking Web Service Enable on high-value custom reports, and lining up three real worker personas for boundary testing. Running through these five checks ahead of time turns your first Sandbox connection from a multi-team troubleshooting call into a single afternoon session.

Because both Bridge and Leaf execute every request live under the signed-in employee’s own Workday OAuth 2.0 token—storing zero HR records outside Workday and never using an Integration System User—your Workday tenant’s own security configuration does the heavy lifting. Here is what to inspect in Sandbox first.

Pre-Flight Sandbox Readiness Table

Check # Sandbox Task / Report to Open What You Are Verifying Common Gotcha to Catch Early
Check #1. OAuth Client Gate Sandbox Task / Report to OpenEdit Tenant Setup - Security & Register API Client What You Are VerifyingOAuth 2.0 Clients Enabled is checked; admin holds Integration: API Client Administration permission. Common Gotcha to Catch EarlyOpening Register API Client for Integrations by mistake instead of user-delegated Register API Client.
Check #2. Sandbox SSO & IP Rules Sandbox Task / Report to OpenEdit Tenant Setup - Security & Manage Authentication Policies What You Are VerifyingSP-initiated SAML/SSO works in Sandbox environment; IP allowlists permit OAuth token exchange. Common Gotcha to Catch EarlySAML IdP configured for Production only, or strict IP rules blocking cloud egress before static IP allowlisting.
Check #3. Self-Service Security Audit Sandbox Task / Report to OpenSecurity Analysis for Securable Item and Account What You Are VerifyingEmployee As Self and Manager hold View (Report/Task) on intended domains—and nothing broader. Common Gotcha to Catch EarlyLegacy domains granting Get/Put (SOAP only) instead of View/Modify (REST/WQL), or over-broad directory domains.
Check #4. RaaS Custom Reports Sandbox Task / Report to OpenEdit Custom Report (Advanced tab) What You Are VerifyingHigh-value custom reports are Advanced reports with Enable As Web Service checked and shared to target groups. Common Gotcha to Catch EarlyTrying to call a Workday Standard Report directly over API, or forgetting report-sharing permissions.
Check #5. Three Test Personas Sandbox Task / Report to OpenView Worker / Sandbox test accounts What You Are VerifyingOne Employee, one supervisory Manager, and one constrained HR Partner ready for real sign-in testing. Common Gotcha to Catch EarlyTesting only as a System Administrator or Security Administrator, which masks missing worker permissions.

Check 1: Verify OAuth 2.0 Clients Enabled and Register API Client Access

User-delegated OAuth apps never use Register API Client for Integrations. Confirm two settings in Sandbox:

  1. Open Edit Tenant Setup - Security, scroll to OAuth 2.0 Settings, and confirm OAuth 2.0 Clients Enabled is selected.
  2. Search for the Register API Client task (not the integrations variant). On a user-delegated client:
    • Client Grant Type: Authorization Code Grant (with Enforce PKCE enabled where supported for public/confidential hybrid safety).
    • Access Token Type: Bearer.
    • Scope (Functional Areas): Scoped strictly to least privilege—for example, Staffing, Personal Data, Absence, Time Tracking, Pay, and System (for WQL discovery), rather than checking every Functional Area in the tenant (see Functional Area least-privilege scoping).

When Kiweely Bridge launches, its built-in AI admin agent walks your Workday admin directly through configuring Register API Client and its Functional Areas in Sandbox step by step. Also note your Friday Sandbox refresh schedule so a scheduled Production-to-Sandbox refresh does not surprise you mid-pilot.

Check 2: Confirm Sandbox SAML / SSO Redirects and Authentication Policies

During an OAuth 2.0 Authorization Code flow, Workday’s /authorize endpoint authenticates the employee in the browser using your tenant’s configured sign-in method and then redirects back to the registered Redirect URI with a short-lived authorization code—never exposing the worker’s password or MFA factor to the external app.

Check two authentication settings in Sandbox before testing:

  • Sandbox IdP Coverage: In Edit Tenant Setup - Security under SAML Setup, verify your Identity Provider row includes Sandbox in Used for Environments (or uses a dedicated Sandbox IdP) with SP Initiated enabled, so an unauthenticated /authorize redirect completes corporate SSO cleanly instead of looping (troubleshooting SAML OAuth loops).
  • Network & IP Allowlists: Open Manage Authentication Policies and Maintain IP Ranges. If your security team restricts API Bearer usage by source IP, decide early whether you will use Kiweely Bridge’s Dedicated single-tenant mode (which provides a dedicated static outbound IP to add directly to Maintain IP Ranges) or deploy the Self-hosted stateless container inside your own AWS, GCP, Azure, or Kubernetes VPC.

Check 3: Audit Employee As Self and Manager Domain Permissions (View vs. Get)

Workday’s Domain Security Policies split permissions into two columns that behave very differently over APIs:

  • Report/Task Permissions (View / Modify): Govern the Workday UI, all Workday REST APIs, and all WQL queries.
  • Integration Permissions (Get / Put): Govern Workday SOAP Web Services only.

Run a two-directional check in Sandbox:

  1. Check for accidental over-exposure: Over the years, tenants sometimes accumulate custom domains or unhidden directory fields where Employee As Self was granted View because nobody added the field to a visible UI worklet. Because WQL and REST respect domain security rather than UI worklet layout, verify what a regular employee can actually read—and note any sensitive fields (such as National IDs, home addresses, or bonus targets) where you also want Bridge’s in-RAM field-level redaction applied as defense in depth.
  2. Check for 403 Forbidden gaps on intended tasks: If employees can view time-off balances in the UI, View is already set. If you plan to expose a SOAP read or write alongside REST, verify whether the security group also needs Get (or Business Process Initiate permission on the Business Process Security Policy). And remember: always run Activate Pending Security Policy Changes after any edit!

Check 4: Inventory High-Value Custom Reports for RaaS (Web Service Enable)

While REST and live WQL handle 80% of standard HCM, Absence, Time, and Pay lookups out of the box, almost every mature Workday tenant has ten or twenty battle-tested custom reports containing complex Calculated Fields (such as custom attrition formulas, regional FTE rollups, or multi-level cost-center budget comparisons).

Instead of rebuilding that business logic from scratch, check those reports in Sandbox:

  1. Confirm the report type is an Advanced Custom Report (Workday Standard Reports cannot be web-service-enabled directly—use Related Actions → Custom Report → Copy first).
  2. On the Advanced tab, select Enable As Web Service (which validates report compatibility and locks a stable schema).
  3. On the Share tab, confirm the report is shared with the exact constrained or unconstrained security groups (for example, Manager or Finance Partner) who should be able to query it—never shared globally with All Authorized Users unless every worker should run it.

Check 5: Prepare Three Non-Admin Persona Test Accounts

Never validate an AI connector or custom employee screen while signed in as a Workday System Administrator or unconstrained HR Administrator. Everything will succeed, and you will prove nothing about real security boundaries.

Identify three concrete workers in Sandbox across distinct org branches:

  1. Individual Contributor (Employee As Self only): For example, an associate in Warehouse 4 with zero direct reports. Verify they can read their own pay, PTO balance, and inbox tasks—and receive an immediate denial or empty result when asking for a peer’s compensation or manager notes.
  2. Front-Line Supervisor (Manager constrained to their Supervisory Org): Verify they see direct and subordinate reports in their own supervisory tree, and zero workers in a sibling branch.
  3. Constrained Partner (HR Partner or Finance Partner): Verify Intersection Security Group boundaries (such as seeing EMEA workers below VP level while excluding Executive management levels).

In Kiweely Bridge (coming next), the AI admin agent runs structured role-boundary test suites across these exact personas before you ever publish the connector URL to your company’s Claude, ChatGPT, or Gemini workspace—and Kiweely Vine (live today) runs multi-persona proxy verification for native Extend apps and tenant setup right now.

Frequently asked questions

Should we create an Integration System User (ISU) to prepare for Kiweely Bridge or Kiweely Leaf?

No. Never create an Integration System User or run Register API Client for Integrations for workforce AI or employee screens. Both Kiweely Bridge and Kiweely Leaf (coming next) use standard user-delegated Register API Client with Authorization Code Grant and PKCE so every call runs as the signed-in employee.

Why can an employee see a field via WQL or REST that they never noticed in the Workday UI?

Workday REST and WQL enforce the exact same Report/Task Domain Security Policies as the Workday UI, but custom hubs or hidden worklets sometimes obscure over-broad View grants on Employee As Self. Auditing Employee As Self domain policies in Sandbox closes those gaps before rollout.

What happens to our Sandbox API Client when Workday refreshes Sandbox from Production?

Refreshing Sandbox overwrites Sandbox configuration with Production's state, wiping out any API Client registered only in Sandbox—or bringing down a Production API Client with Disabled in Non-Production Tenants behavior if configured. Document your Sandbox client scopes or promote cleanly via configuration packages.

Can I test user-delegated OAuth and MCP queries before touching our company's Sandbox tenant?

Yes. Kiweely Bridge (coming next) will be free for one person on their own Workday Open Developer Program tenant, which includes synthetic sample workers, organizations, and absence plans with no company PII.

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.