Skip to content
KiweelyKiweelyKiweely

A hybrid Workday build: people, Deployment Agent, and a desktop agent

Hybrid delivery is an operating choice. Workday still runs Object Transporter, security activation, and business processes. Ask is read-only in non-Production, with 14-day chat; changes are in partner early access. Kiweely Vine signs in as you and asks before it changes anything.

  • By Kiweely
  • Updated
  • 6 min read
On this page

Hybrid delivery means a person, Workday’s own agent, and a desktop agent each do the part Workday will actually accept. It is not a blend in which every tool is allowed to “help with configuration.” Configuration changes when a task runs, a policy is activated, or Object Transporter finishes a migration. Anything else is a draft.

Who owns which action

Action Who can finish it Who can prepare it
ActionExplain a concept, cite a guide, inspect a calculated field or a domain in a non-Production tenant Who can finish itA person confirms by opening the task. Who can prepare itDeployment Agent with Ask. Q&A can explain and cannot see the tenant.
ActionEdit a business process, a calculated field, a domain policy Who can finish itA person, or a desktop agent that you approve and that uses your sign-in. Who can prepare itAsk’s step list. The published examples end in Create Calculated Field or a policy edit you perform. Configuration Cloud, in partner early access, is the exception.
ActionActivate security Who can finish itA person runs Activate Pending Security Policy Changes. Who can prepare itAnyone can draft the comment. Activation is the task.
ActionMigrate configuration Who can finish itA person in Customer Central, after the error check, the prerequisite check, and the diff. Who can prepare itAsk can interpret a SOAP fault from Object Transporter. It is not Migrate with Object Transporter.
ActionLoad inbound data Who can finish itThe integration you launch and verify. Who can prepare itA connector, EIB, Orchestrate, or Studio, chosen in Workday’s published order. A desktop agent can help build a Studio assembly in your Studio and must ask before deploy and run if it is Kiweely Vine.
ActionTest as a worker Who can finish itThat worker, or a watched proxy of that worker. Who can prepare itVine’s Start Proxy, in a browser you can watch. Deployment Agent has no published proxy test.
ActionProduction hypercare chat Who can finish itPeople, looking at events. Who can prepare itNot Deployment Agent. It is not a conversational assistant in Production.

Vine is Kiweely’s desktop app: sign in the way you already do, no API client required, changes on the screen or straight in, approval before a change, sign-ins stored on that computer, one client’s sign-ins per conversation. Vine Free is free for a Workday personal developer account and its tenant. Any other tenant needs a Personal license at $99 a month or a firm seat at $149 a month. Those are Kiweely’s terms, not Workday SKUs.

Workday-built agents in the catalog, such as BP Optimize, Payroll Agent, and Adoption Agent, stay in their published jobs. Adoption Agent’s catalog line is release-impact analysis in Preview. Do not staff them as general implementers because Deployment Agent is enabled.

A weekly split that does not double the work

People own scope, the decision log, Customer Central access, security activation, migration, and the client’s signature. They also own Reference IDs. Object Transporter treats the same ID and type as the same instance. An agent that mints a new ID in prose has created a future prerequisite failure.

Deployment Agent owns first-pass explanation and inspection in Implementation, Sandbox, Preview, and Customer Central. One topic per chat. “In my tenant” or the connected tenant’s name, because nothing on screen shows that Ask is on. Copy anything you will still need into the decision log the same day. Workday deletes the chat in 14 days and does not show Sandbox threads inside Preview. Ask is read-only as documented; with Configuration Cloud, in opt-in early access for partners since 18 November 2026, Deployment Agent can carry out changes once a plan is approved.

Configure the agent in Production if Sandbox refreshes should keep it, even though you cannot talk to it in Production. Deactivate it in Production when a refresh should leave Sandbox off. Ask uses no Flex Credits in Production.

A desktop agent owns work you are willing to watch or approve: a calculated field, a report, an EIB template filled from a file you provide, a Studio assembly, an Extend app promoted through Sandbox with Workday checking the version. It does not own the Object Transporter diff. It does not own Production by default; Vine’s Extend copy says Production stays yours.

Handoffs that need a named artifact

From To Artifact
FromAsk ToThe person editing ArtifactObject names that open in the tenant, plus the guide topic cited.
FromThe editor ToMigration ArtifactReference IDs, package name, and the prerequisites already cleared in a rehearsal.
FromMigration ToThe client test ArtifactPost-migration summary (kept two years) and the business process event the client ran.
FromVine ToThe decision log ArtifactThe design document or test script it filed, after a person has checked it against the event.
FromAnyone ToNext week’s Sandbox ArtifactAn extract or a Production copy. A refresh will not keep Sandbox-only work.

What “hybrid” must not mean

  • The same change described in a workbook, a chat, and a tenant, with nobody saying which one was migrated.
  • A client demo performed as an implementer security group while the notes say the manager did it.
  • Q&A answers filed as tenant inspection. Q&A cannot see instances.
  • A desktop agent and Deployment Agent both “fixing” one definition in one afternoon, with no approval and no effective date. Inheritance will run whichever definition is valid. You may not know which one you tested.
  • Sharing one Vine conversation across two clients. The product copy says each conversation uses one client’s sign-ins. Keep it that way. Workday’s own chat is already isolated by tenant.
  • Treating Customer Central data as customer data. Workday says it is not, and Customer Central is not part of the service. Still do not paste worker rows into an agent to “analyze the foundation.” Foundation questions are about organizations, policies, and definitions.

Failure modes

  • No owner for activation. The policy looks right in the chat and does nothing for users.
  • No owner for the diff’s security choice. Merge is the default. Overwrite is a choice. Additive group migration does not revoke.
  • Agents used in Production because the project plan said “AI hypercare.” Only the people and the events are there.
  • Two agents, no log. Fourteen days later the only remaining record is the tenant, and nobody remembers which prompt produced it. That is survivable if the tenant is right and fatal if you needed the rationale.
  • Flex Credit surprises. Ask in Production does not consume Flex Credits. Workday’s setup topic does not say the same about every other agent. Do not assume.

Frequently asked questions

Do we still need implementers if we have both agents?

Yes. Someone registers Deployment Agent, activates security, reads the Object Transporter diff, and answers the client. The agents do not hold Customer Central roles. Customer Central accounts cannot hold multiple roles at once, and the initial owner account deactivates 60 days after Workday issues it. Staff those administrator accounts on purpose.

Can both agents be in the same working session?

Yes, on different jobs. Ask explains and inspects. Vine, if you approve it, edits and can proxy-test. Do not let them edit the same definition without a person deciding which version is the source for migration.

Is this only for implementation tenants?

Inspection and prototype work belong there, or in Sandbox when you mean to test a Production copy. Migration to Production is Object Transporter from a non-Production tenant that already rehearsed the package. The hybrid model does not create a third path.

What do we tell the client they are paying for?

People accountable for the design, Workday’s migration and test records, and optional agents with the limits above. Do not tell them the chat is the configuration.

Sources checked

Public Workday topics listed above, fetched 2026-11-16. Kiweely Vine’s behavior and prices are from kiweely.com product copy, not from Workday.

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.