Workday’s Deployment Agent and a desktop Workday agent answer different questions. Deployment Agent, with Ask enabled, helps an implementer understand configuration in Implementation, Preview, Sandbox, and Customer Central. It is not a conversational assistant in Production, and Workday’s concept topic describes its configuration inspection as read-only. Separately, Workday’s Configuration Cloud announcement says that with Configuration Cloud, in opt-in early access for Workday partners since 18 November 2026, Deployment Agent can carry out changes once a plan is approved. Kiweely Vine is a desktop app that signs in to Workday the way you already do and can do the tenant work itself after you approve it.
Use both on a build, if you have both. Use Deployment Agent when the question is “what is in this non-Production tenant, and what does Workday’s documentation say to do?” Use a desktop agent when the question is “make this change, show me, and test it as the worker who will live with it.”
What Workday documents for Deployment Agent
The Workday-built agents catalog describes Deployment Agent as implementation knowledge plus inspection of in-tenant configuration in those non-Production tenants. The skills topic says enabling Ask turns on three capabilities:
| Capability | What Workday says it does |
|---|---|
| CapabilityConfiguration intelligence | What Workday says it doesStep-by-step instructions, such as calculated fields or linking compensation grades, grounded in tenant context. Configuration Catalog suggestions and help with catalog setup. |
| CapabilityTechnical troubleshooting | What Workday says it doesInterpretation of web-service and SOAP errors, and why a rule or business process did not run. |
| CapabilityKnowledge discovery | What Workday says it doesPlain-language explanations, such as Top of Stack, with links back to Community and the Administrator Guide. |
Ask grounds those answers by searching, opening tasks, and running reports, and by retrieving documentation. There is no indicator in the chat window that Ask is on. Workday’s verification prompt is to ask for five calculation fields in the Implementation tenant and check them with View Calculated Field.
Two products share the name:
| Deployment Agent (Q&A) | ASOR Deployment Agent with Ask | |
|---|---|---|
| Tenant data | Deployment Agent (Q&A)None. It cannot see your instances or security policies. | ASOR Deployment Agent with AskRead-only inspection of the active tenant, or of a named connected tenant from Customer Central. |
| Agreement | Deployment Agent (Q&A)No Universal Main Service Agreement or Agent System of Record setup. On by default through Maintain Feature Opt-Ins. | ASOR Deployment Agent with AskUniversal Main Service Agreement, or an opt-in from a Main Service Agreement. Register and activate in Agent Management Hub. |
| Where | Deployment Agent (Q&A)Implementation, Sandbox, Preview, Customer Central | ASOR Deployment Agent with AskSame non-Production set. Not a chat assistant in Production. |
Workday retains chat for 14 days, isolates it by tenant, and summarizes long threads. You must validate suggestions against official documentation. In the documented Ask examples, the calculated-field example ends in Create Calculated Field, which you run. The security example ends in an edit to a domain security policy and Activate Pending Security Policy Changes, which you run.
Sandbox refreshes copy Production. Workday recommends configuring the agent in Production so the Sandbox copy keeps it, even though you cannot use it in Production. Ask consumes no Flex Credits in Production. Deactivate in Production as well as Sandbox if a refresh should not turn the agent back on.
What Kiweely Vine is for
Kiweely Vine is the desktop Workday agent described on kiweely.com/vine. Public product copy says it signs in to the client’s Workday as you, does the work there, and asks before anything changes. Two ways in, and neither requires an API client. Changes can run on the Workday screen, where you watch each step, or straight in, which is faster. Sign-ins stay on that computer. Each conversation uses one client’s sign-ins.
The same pages say Vine can:
- Answer from the tenant’s real setup through your own Workday sign-in.
- Change configuration and business processes in any Workday task screen, after you approve.
- Build reports and calculated fields, load data with Enterprise Interface Builder, and work in your own Workday Studio: build, test, deploy, run, and debug, asking before each deploy and run.
- Design, build, deploy, and promote Extend apps and orchestrations through Sandbox. Workday checks each version. Production stays yours.
- Test as real people with Start Proxy in a browser you can watch, and fix what fails.
- Write design documents, test scripts, and decks from the real tenant and file them on the project.
- Read Workday Community and the Developer Forum signed in as you.
Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs a Personal license, $99 a month, or a seat in your firm. A firm seat is $149 a month, two seats at least.
That is a product description from Kiweely’s site, not a Workday claim. Workday’s Deployment Agent pages do not mention Vine.
Side by side
| Job on a build | Deployment Agent | Kiweely Vine |
|---|---|---|
| Job on a buildExplain a Workday concept with a citation | Deployment AgentYes. Knowledge discovery, including Top of Stack. | Kiweely VineYes, and it can read Community signed in as you. |
| Job on a buildRead this tenant’s calculated fields, rules, and security | Deployment AgentYes, with Ask, in non-Production. Name the tenant from Customer Central. | Kiweely VineYes, through your sign-in, including tenants you can open. |
| Job on a buildCreate the calculated field or edit the business process | Deployment AgentNot with Ask as documented; you enter it. Configuration Cloud (partner early access) can carry out approved changes. | Kiweely VineYes, after you approve, on screen or straight in. |
| Job on a buildMigrate with Object Transporter | Deployment AgentCan interpret a SOAP fault. Does not run the migration. | Kiweely VineDoes not replace Object Transporter’s diff. It can work in the tasks your sign-in can open. |
| Job on a buildTest as the employee, manager, and HR partner | Deployment AgentNo published proxy test. | Kiweely VineYes. Start Proxy in a browser you can watch. |
| Job on a buildProduction | Deployment AgentNo conversational assistant. | Kiweely VineProduction changes stay behind your approval. Extend promotion through Sandbox; Production stays yours. |
| Job on a buildRecord of the conversation | Deployment AgentDeleted after 14 days, per tenant. | Kiweely VineDesign documents and test scripts filed from the tenant, on the project. |
| Job on a buildSetup | Deployment AgentDomain policy, Agent Management Hub, Ask, security groups. | Kiweely VineSign in to Workday the way you already do. |
How a build team actually splits the work
Monday, shared language. Open Deployment Agent (Q&A) or Ask and request the lay explanation of a concept the workshop keeps misusing. Copy the bullets into the decision log the same day.
Tuesday, the broken rule. In the Sandbox where the rule lives, prompt Ask with “in my tenant” and the business process name. If the answer names a condition, open the definition and use Workday’s rule test from the event. Do not paste the answer into a design document as fact until someone has opened the step.
Wednesday, the change. If the team only needs instructions, stay in Deployment Agent Ask and run Create Calculated Field or Edit Definition by hand. If the team wants the change made and then watched, use Vine, approve the edit, and test it as the worker the step is for.
Thursday, the refresh. Deployment Agent’s registration survives a Sandbox refresh only if it was configured in Production. Configuration built only in Sandbox does not. Save that configuration with Configuration Change Tracker and an extract if it has to come back. Vine’s sign-in does not preserve Workday configuration across a refresh either. The refresh still replaces the tenant.
Failure modes
- Treating Q&A as inspection. Q&A cannot see instances. If the answer never names a field you can open, Ask is off or you never said “in my tenant.”
- Asking Deployment Agent to “just build it.” The published Ask examples stop at your hands on the task.
- Asking a generic chat window, with no Workday sign-in, to debug a tenant. It can draft steps. It cannot see the condition that failed.
- Leaving the only copy of a design decision in a Deployment Agent thread. Fourteen days later it is gone.
- Assuming a desktop agent is a Workday-built agent. It is not in the Workday-built agents catalog, and it is not registered by the Deployment Agent setup topic.
Frequently asked questions
Is Deployment Agent the desktop copilot?
No. You open it inside Workday with the Deployment Agent task, in a non-Production tenant or Customer Central. A desktop agent runs on the computer and signs in to Workday.
Do I need both?
You need Deployment Agent when you want Workday’s own assistant, its documentation corpus, and Ask’s read of non-Production configuration, under your Workday agreement. You need a desktop agent when the remaining work is to change the screen, load a file, build an integration in Studio, or test as another person. One does not include the other.
Will Deployment Agent answers match Vine’s?
Not by contract. Deployment Agent can be wrong; Workday says to validate against official documentation. Vine’s public copy says Workday, not Kiweely, decides whether an Extend version passed. Compare both answers to the task you open, not to each other.
Can I use Deployment Agent in Production hypercare?
No. Workday says it is not accessible for use in Production. Configure it in Production only so Sandbox refreshes keep the setup.
Sources checked
Workday admin-guide topics above, fetched 2026-11-16. Kiweely Vine behavior is from the product pages and site copy published on kiweely.com, not from Workday.