Skip to content
KiweelyKiweelyKiweely

Sandbox Checklist Before AI Chat, Custom Screens, or Integration Platforms

Use a non-production tenant, a client scoped to that job, and activated security policies before any external chat, screen, or integration platform calls Workday. Confirm the connection again after the weekly sandbox refresh.

  • Checked against Workday on
  • Applies to Workday Extend
  • 9 min read
  • Published
  • By Kiweely
On this page

Connect external AI chat, a custom employee screen, or an integration platform to a non-production Workday tenant first, with a client and a Workday user that match that job. Do not point any of them at Production until a real employee, a real manager, and a denied user have been tested, and until any security-policy edit has been activated. Sandbox and Sandbox Preview are refreshed every week with production data, so plan to recheck the connection after that refresh. Workday’s public pages checked for this guide do not say whether a registered API client survives the refresh. Confirm it. Do not assume it.

The steps below are Workday’s. Kiweely Bridge, Kiweely Leaf, and Kiweely Roots are coming next and describe the same three jobs: employee chat, custom screens, and integrations outside the tenant. Use the checklist for them or for any other product. Checked against Workday’s public pages on November 16, 2026.

Pick the tenant on purpose

Workday’s HCM administrators course defines the tenant types you will actually see:

Tenant What Workday says it is for Use it for this checklist when
TenantProduction What Workday says it is forLive, active data. Security is critical because it holds confidential employee and business information Use it for this checklist whenYou are done testing. Not before
TenantSandbox What Workday says it is forDevelop and test features and configuration before Production. Data is typically a copy of Production Use it for this checklist whenYou need production-like data and security
TenantSandbox Preview What Workday says it is forAlso a copy of Production, plus functionality coming in a future release. Preview tenants receive feature releases about five weeks ahead Use it for this checklist whenYou also need the next release’s behavior
TenantImplementation What Workday says it is forA secure place for testing, prototyping, and training. Customers may have several, for integrations, legacy loads, and end-to-end tests Use it for this checklist whenYou are still implementing, or you need a tenant that is not the weekly production copy

The Orchestrate course describes Sandbox the same way: production-like, refreshed every week with production data. It describes Implementation as a controlled environment that uses partial production data. That “partial” line is the orchestration course’s wording. The HCM course does not say every implementation tenant is partial. Read the tenant you were given.

The Extend course repeats the weekly refresh and adds a different warning: once an Extend app is installed on an Implementation, Sandbox, or Production tenant, you cannot remove it. An external screen or a chat connector is not that install. Keep an Extend promotion off this checklist.

Sandbox data in the copied areas is production data. Handle it that way. The pages checked here do not publish a field-by-field list of what a core HCM refresh preserves. After the weekly refresh, sign in, open the API client, and make one test call before you tell anyone the connector still works.

Separate the three connections

Do this once per job. A client registered so employees can ask questions is the wrong client for a payroll file.

Job Workday identity What to register in the non-production tenant
JobEmployee AI chat Workday identityThe employee who is asking What to register in the non-production tenantAuthorization Code Grant. Functional areas only for the questions you will allow. The person signs in to Workday
JobCustom screen Workday identityThe employee who opened the screen What to register in the non-production tenantThe same pattern. One client for that screen layer, not one client per widget
JobIntegration platform, unattended Workday identityA dedicated integration system user What to register in the non-production tenantOne user per integration, a security group, domains for that feed only, UI sessions disallowed

User-as-self is the documented pattern for a person who must log in. Workday’s Live Data Query page says this method enforces the full security model, including row-level controls and contextual security, based on the permissions of the user who authorizes the connection. The task on that page is Register API Client: Authorization Code Grant, Bearer access tokens, a redirect URI, refresh-token timeout left at the default unless you have a reason to change it, and only the functional areas that should be exposed. Include Workday Owned Scope is selected on that page. Save the client id, the client secret, and the authorize and token endpoints when they are displayed. Workday says you cannot view all of that information later.

The Time Kiosk instructions show how small a scope can be: Proof Key for Code Exchange selected, Bearer tokens, one redirect URI, and a single functional area. Copy the narrowness, not the Time Tracking selection, unless the job is time tracking.

For an unattended integration, follow Workday’s integration pattern rather than the employee pattern. The Cloud Connect for Learning page states the policy in general terms: integration system users must be unique across integrations, and it is Workday policy to use one with only the appropriate access. Do not run the integration as an administrator. Select Do Not Allow UI Sessions so the user cannot sign in through the Workday interface. Create an integration system security group, put that user in it, and grant domains.

Activate, then test

Editing a domain or business process security policy does not turn the edit on. Workday’s security course says the change is saved and will not take effect until someone runs Activate Pending Security Policy Changes. The comment should record who signed off. Select Confirm. Changes to security-group membership or to the group definition take effect immediately and do not need that task. They also survive if you later activate a previous security timestamp. Timestamps roll back policy edits only.

The edit task and the activate task can sit in different domains: Security Configuration versus Security Activation. If the person who built the client cannot activate, the checklist is not finished.

Then prove the grant:

  1. Run View Security for Securable Item on each task, report, or web service the chat, screen, or feed will call. Domain security policies secure most web service operations. Some Put operations are secured by a business process security policy, because they start a business process.
  2. Grant Get for a read. Grant Put or Modify only for a write or a launch. The Securing Connectors course says Delivery Assurance will raise integrations with more access than they need.
  3. Sign in as three people: an employee who should succeed, a manager whose rows should differ, and a worker who should be denied. If all three see the same workers, the call is not running as the signed-in user.
  4. For a write, complete it once in the non-production tenant and read the business process back. A chat transcript or a form success message is not the audit.
  5. For a connector field override or a calculated field, test security on the underlying fields. Calculated-field values follow the domains of the fields underneath.

A failed call with a generic integration error usually means the security group is on no policy, or the policy is still pending. Open the integration event’s audit, find the operation name, and return to View Security for Securable Item. Do not widen every functional area to get past the error.

Before anyone mentions Production

  • Register the client in the non-production tenant you tested. The Live Data Query page shows the tenant on the authorize and token endpoints. Repeat the registration when you deliberately move to another tenant. Do not create the production client “so the redirect is ready.”
  • One product, one client. Chat, screens, and integrations do not share a client or a user. Redirect URIs are exact.
  • You can disable the OAuth 2.0 client if you suspect the grant was copied. The Agent Security FAQ says Workday cannot detect that for you, and a stolen access token can be replayed until it expires. Integration clients can set expiry. Workday’s own external agents cannot customize access-token expiry. A third-party connector that uses Register API Client is not automatically one of those agents. Ask which one you registered.
  • Leave writes off until the read tests pass.
  • After the next weekly sandbox refresh, confirm the client, a sign-in, and one read. If the client is gone, register it again. The pages checked here do not say that Workday deletes it.
  • Keep your own note of functional areas and domains. A refresh can restore production configuration over a sandbox-only edit. Retest either way.

Where this meets a coming-next product

Bridge, Leaf, and Roots are not available to connect this week. When you do test them, the product pages describe the sandbox shape as follows. Bridge’s AI admin agent sets up Register API Client in Sandbox, sets field rules, and tests as real roles such as Employee, Manager, and HR Partner. The page says non-production tenants are included and that a company still implementing Workday uses its implementation tenants. Leaf says you connect the tenant once with one API client and that every call runs as the signed-in employee. Roots says every build and every fix runs on Sandbox with real data first, and that each integration has its own API client scoped to what it reads. None of those sentences replaces the activation and persona tests above.

Kiweely Vine is the product that is live if the sandbox work is a change inside the tenant rather than an outside connection. It asks before it writes. Nest, coming next, is the in-house team that also builds in a lower tenant and waits for your approval before Production.

Failure modes

Production first, because sandbox data is “old.” Sandbox is typically a copy of Production, and it is refreshed weekly. Old means days, not a toy dataset. The worker rows are still real.

One integration system user for the chat screen. Employees then see that user’s domains, not their own. User-as-self exists so Workday, not the outside app, applies row and contextual security.

Pending policy, successful-looking diagram. The vendor’s setup screen can say connected while Workday is still evaluating the previous security timestamp. Run a denied-user test. If the denied user succeeds, stop.

Extend install mixed with an external screen. Installing an Extend app on Sandbox cannot be undone, on the Extend course’s statement. Connecting a pass-through screen is a different action. Do not accept an install when you asked for a connection.

Refresh on Friday, demo on Monday. The weekly refresh may have replaced the data and the configuration you practiced on. The demo script from last week is not evidence.

Frequently asked questions

Is a personal Workday developer tenant the same as Sandbox?

No. Sandbox, on the HCM course, is a production tenant type whose data is typically a copy of Production. A personal developer tenant is a different account, with sample data, used to try a product before a company tenant exists. Bridge’s page offers that developer tenant for free and still says the product is coming next. Do not load a company worker file into a personal tenant to make the demo look real.

Do we have to finish this checklist for all three jobs before we register interest?

No. Interest on a coming-next page does not connect your tenant. Finish the checklist in the non-production tenant when a vendor, including Kiweely, is actually ready to register a client. You can register interest in Bridge, Leaf, or Roots before that day.

What if our only non-production tenant is an implementation tenant?

Use it. The HCM course lists implementation tenants for testing, prototyping, training, integrations, and end-to-end tests. Say so in the test notes. Do not label the results as a Sandbox test. Sandbox Preview is the tenant that also carries the next feature release, about five weeks ahead.

Which Workday task tells us the call is really as the employee?

A persona test, not a setting label. Sign in as the employee and as someone who must not see that employee’s data. User-as-self, as Workday describes it for Live Data Query, applies the authorizing user’s row-level and contextual security. If the second person sees the first person’s pay, the connection is not that pattern, whatever the diagram says.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.