A demo hits live workers when the sign-in URL is the production tenant. The fix is a different tenant, not a disclaimer in the prompt. The uncomfortable part: a sandbox is often a copy of production, so it can show the same people.
Kiweely Bridge (coming next) includes Production and every non-production tenant in the company price. Inclusion is not permission to use production for a rehearsal. The admin setup is described as happening in Sandbox first. Publish to the production URL only when the persona tests are done.
The tenant types Workday teaches
Workday Tenants and Tools is the source for the names:
| Tenant | What the course manual says | Demo implication |
|---|---|---|
| TenantProduction | What the course manual saysLive, active data, including confidential employee information | Demo implicationNot a demo target |
| TenantSandbox | What the course manual saysWhere administrators and consultants test configuration before production. Data is typically a copy of production | Demo implicationReal workers can appear. Do not treat the name “sandbox” as anonymized |
| TenantSandbox Preview | What the course manual saysAlso a copy of production, plus functionality coming in a future release. Preview tenants receive features about five weeks before the release, and then all tenant types get the release on the same date | Demo implicationSame data caution, plus behavior production does not have yet |
| TenantImplementation | What the course manual saysA secure place for testing, prototyping, training, integrations, and legacy loads. A customer may have several | Demo implicationA better demo target if the data was loaded for practice rather than copied from production |
| TenantGMS (Global Modern Services) | What the course manual saysA demonstration tenant with sample data for a fictitious customer, for HCM and Finance learning | Demo implicationThe manual’s explicit sample-data tenant |
Each tenant has its own URL. Metadata is Workday’s and you do not change it. Tenanted data is yours. An API client is registered in one tenant and signs users in on that tenant’s URL. A client ID from sandbox does not become a production grant because the redirect looks similar.
About Workday Agents adds one operational fact if you also use Workday’s agents: Workday does not delete usage activities from previous weeks during the Sandbox refresh. That sentence is about agent usage rows. It is not a full description of what a refresh does to worker data. This guide does not invent a weekly wipe of all sandbox configuration.
How a connector stays on the tenant you meant
- Decide the audience. A sales demo that must not show employees uses GMS or a personal developer tenant’s sample data. Bridge is free for one person on their own Workday developer tenant, and that tenant holds sample data. A configuration test with production-like security uses sandbox or an implementation tenant, knowing the people may be real.
- Register Register API Client in that tenant. Authorization code with PKCE, for the worker, not an integration system user.
- Give the assistant the connection for that tenant only. On a company assistant plan, an owner adds a connector once. That is a reason to keep the demo connection off the production workspace, not a reason to share one URL.
- Sign in as the test worker on the non-production URL and read the tenant name in the answer path before you ask about a person.
- Keep writes off on any tenant that still contains a copy of production workers, until you intend to submit a business process there. Sandbox business processes are still processes in that database.
Bridge’s AI admin agent is specified to set up the API client and functional areas in Sandbox, set field rules, and test as real roles before production. Follow that order when the product is available. It is not available now.
Checks that catch a crossed wire
| Check | Pass | Fail |
|---|---|---|
| CheckURL | PassThe host and tenant name are the non-production tenant | FailThe production tenant name appears anywhere in the sign-in |
| CheckPerson | PassA known test worker, or a GMS sample worker | FailA current employee who exists only as live data and was not copied on purpose |
| CheckClient | PassCreated in the tenant you are signed in to | FailA production client ID reused because it was handy |
| CheckWrite | PassAbsent from the tool list, or allowed only in the tenant you meant to change | FailA time-off request that landed on a live worker |
| CheckRefresh | PassYou know this sandbox may be replaced by a new copy of production | FailYou stored a demo script that depends on sandbox-only workers surviving a refresh you have not verified |
Non-production is also where Workday says most of its own agents can be tried without the production credit meter, with exceptions the rate card marks. That is a Workday billing fact, not a privacy fact. A free test in sandbox can still display a real worker’s pay if the sandbox was copied from production.
Frequently asked questions
If the price includes sandbox, why not demo there by default?
Because the course manual says sandbox data is typically a copy of production. The price means you do not buy a second subscription for the sandbox. It does not scrub names. Use GMS or the personal developer tenant when the room should see fictitious people.
Can one connection serve both, with a toggle?
Not as a published Bridge feature. The safe pattern is two registrations and two URLs, and a demo that never receives the production one. Kiweely Bridge is coming next. Register interest if you want that separation built with the admin agent rather than by memory.