Workday’s implementation tenants are a secure place for prototyping, training, integration tests, legacy loads, and unit and end-to-end testing. You may have more than one. That is the tenant to point an agent at when the idea is not in Production yet. It is not a place where an agent’s conversation becomes the prototype. The prototype is the configuration in the tenant.
Sandbox will not hold it. Sandbox is typically a copy of Production, and a refresh replaces it. Sandbox Preview is that copy plus features coming in the next release, shown in preview about five weeks before the feature release hits every tenant. Weekly service updates land in the maintenance window. None of those cycles are a prototype store.
What a prototype tenant is for
| Goal | Tenant | Why |
|---|---|---|
| GoalTry a business process or a report the client does not have in Production | TenantImplementation | WhyProduction’s copy will not contain it, so Sandbox will not either until you put it there on purpose. |
| GoalSee how Production works today | TenantSandbox, after you know it has refreshed | WhyIt is the copy. Do not prototype on top of it if you need the prototype next week. |
| GoalSee the next feature release against your data | TenantSandbox Preview | WhyNew features arrive there first. It is still a copy of Production plus those features, not your design workshop. |
| GoalLearn from sample workers | TenantGlobal Modern Services, or AMU for education, or GOV for government | WhyFictitious data. Do not migrate it into the client as if it were theirs. |
| GoalStart from factory HCM, absence, reports, or integrations | TenantConfiguration Catalog into the implementation or sandbox tenant | WhyContent comes from WDSetup, which has configuration and no workers. Test it. Then change it. |
Metadata stays Workday’s. The prototype is tenanted data: your supervisory organizations, definitions, reports, and security grants.
How the agents help, without becoming the tenant
Deployment Agent in that Implementation tenant, with Ask on, can explain a calculated field, list reports, and interpret a rule that did not fire. Confirm Ask before the prototype week: five calculation fields you can open. There is no badge. From Customer Central, name the implementation tenant or you may inspect a different connected tenant.
The agent does not create the prototype. The calculated-field example ends when you run Create Calculated Field. Security changes end when you activate them. Chat disappears after 14 days, so the rationale for the prototype has to be copied out if anyone will care after the demo.
Kiweely Vine can make the change after you approve it, on the screen or straight in, using your sign-in. It can test as a person with Start Proxy while you watch, and it can file a design note from that tenant. Point the conversation at this client only. A personal developer tenant is free with Vine Free; a client tenant needs a Personal license at $99 a month or a firm seat at $149 a month. Vine is not Deployment Agent. Workday does not register it when you enable Ask.
Use Vine to build the thing you can see. Use Ask to check what the tenant now contains and to pull a guide citation. Use neither as the archive.
Make the prototype survivable
Before the demo, decide which outcome you need:
- Throwaway. Leave it in the Implementation tenant. Accept that the only durable copy is whatever you migrated or extracted. The chat will not save it.
- Replay after a refresh. Configuration Change Tracker can package changes by who changed them and when. Extract that package. The extract is an encrypted file you cannot edit. Download it, and reload it after the refresh. Tracker will not include a dependency nobody touched inside the window. If the prototype is missing a parent object, the reload fails the same way a migration fails.
- Keep it as the source for Production. Reference IDs first, unique across tenants. Then Object Transporter, rehearsed onto another non-Production tenant. Extracts do not load to Production. The path to Production is a migration from Implementation or Sandbox after the diff. Security policies merge unless you choose to overwrite. Security group permissions on business processes migrate additively and will not revoke Production groups you forgot about.
- Start from delivered content. Migrate a Configuration Catalog package into the implementation tenant, then change it. Ask may suggest a package. Open View Configuration Catalog Content and read the SKU and prerequisites before you treat the suggestion as the package.
Demo the business process event, not the agent. Inheritance may run a different definition than the one you edited if the organization’s own definition is in error or if you edited the default while testing another organization. Say which organization the demo worker is in.
Failure modes
- Prototyping in Sandbox on Monday and presenting on Friday after a refresh. The work is gone. The agent’s memory of it is not a restore.
- Prototyping in GMS and calling it the client’s design. The workers are fictional.
- Two implementation tenants, two sets of Reference IDs, one demo. The migration will treat them as different instances or as mismatches.
- An agent creates objects in a tenant whose IDs you never set. You now have a prerequisite problem you cannot see in the transcript after two weeks.
- “The prototype passed” because Ask said the condition was valid. Run the event. Use Test Rule on that event if a condition is the point of the prototype.
- Promoting by refreshing. A refresh copies Production onto Sandbox. It does not copy your Implementation tenant onto Production.
Frequently asked questions
How many implementation tenants should the prototype use?
Workday says you may have several, split by purpose: integrations, legacy data, unit test, end-to-end test. A prototype that shares a tenant with a data load will be blamed for the load’s failures. Separate them when the tests would confuse each other. You do not need a new tenant for every prompt.
Can the agent stand up a foundation from nothing?
It can suggest steps and, in Vine’s case, perform approved tasks. The six HCM concepts still have to exist before staffing transactions make sense: supervisory organizations, staffing models, job profiles, compensation, security, and business processes. WDSetup and the catalog are the delivered start, not a client’s hierarchy.
Should we enable Deployment Agent in the prototype tenant only?
Enable it in every non-Production tenant where people will ask questions, and in Production if you want Sandbox refreshes to keep that setup. Enabling it only in the prototype tenant means a Sandbox refresh will not carry the agent, and Customer Central will not automatically have it either.
What do we show the client?
The worker completing the step in the Implementation tenant, the definition name, and what is still throwaway. Show a migration diff only if you are claiming the prototype can move. Do not show a chat window as the build.
Sources checked
Public Workday topics listed above, fetched 2026-11-16. Vine’s behavior is from kiweely.com, not from Workday.