---
title: "Implementation vs support AI rules — Kiweely"
description: "Workday has not published an AMS policy for agents. Implementation can use Deployment Agent in non-Production. Production has no chat assistant."
url: https://kiweely.com/blog/workday-implementation-vs-ams-ai-policy
---

# Implementation and support need different rules for Workday AI

Deployment Agent inspects Implementation, Sandbox, Preview, and Customer Central. It is not a Production chat assistant. Support keeps events, integrations, and change control. A desktop agent still asks before it changes a tenant.

-   By Kiweely
-   November 16
-   6 min read

Workday has **not** published an application-management policy, a support-desk standard operating procedure, or a rule that “AI used in implementation is allowed in Production support.” You have to write that policy. The product facts that constrain it are already public.

Deployment Agent is for implementers and administrators in **Implementation, Preview, Sandbox, and Customer Central** connected to non-Production. It is **not** available as a conversational assistant in Production. A support model that tells analysts to “ask Deployment Agent about the Production worker” is asking them to do something Workday’s setup topic says they cannot do.

## Two modes, two rules

|  | Implementation | Support after go-live |
| --- | --- | --- |
| Tenant the agent may chat in | Implementation, Sandbox, Preview, Customer Central | Still only those. Production chat is not a feature. A Sandbox that has just refreshed is a copy of Production, so it is the closest published place to inspect Production’s configuration. |
| What “done” means | A definition, policy, or package you can migrate, plus a test event | A Production event, integration event, or a change migrated on purpose |
| Change path | Edit in the build tenant, activate security, rehearse Object Transporter | The same tools. A support fix that is configured only in Sandbox disappears on refresh. |
| Chat retention | 14 days, per tenant | 14 days. A support ticket that cites only a chat will rot. |
| Who signs | The person who activates and migrates, then the client who runs the test | The person allowed to change Production, under your change control |

Adoption Agent is a different product. The catalog says you register it in **Preview** to use release-impact analysis. That is a support-relevant agent for “what did this feature release change,” not a substitute for Deployment Agent, and not a Production worker assistant. BP Optimize Agent analyzes business processes and recommends improvements. It is not a ticket bot. Do not write a support policy that treats every Workday-built agent as one queue.

## A policy you can enforce

**Build phase**

-   Ask is allowed for named security groups on the Deployment Agent Users domain, in named non-Production tenants.
-   Prompts that inspect configuration must say “in my tenant” or name the connected tenant. Q&A must not be pasted into a design as if it had seen the tenant.
-   Anything the team will rely on is copied to the decision log the same day.
-   The team verifies Ask once per tenant with a question only the tenant can answer.
-   Setup is also done in Production when Sandbox should keep the agent across refreshes. The policy states that this does **not** authorize Production use. It states who may deactivate the Production registration so a refresh does not turn the agent back on.
-   Flex Credits: the enable topic says Ask consumes none in Production. The policy must not claim that for other agents.

**Support phase**

-   Production incidents are diagnosed from the business process event, the integration event, the domain policy, and, when the question is “does Production match what we deployed,” a Sandbox compare or Tenant Compare after a known refresh. They are not diagnosed by opening Deployment Agent in Production.
-   A proposed fix is built in an Implementation or Sandbox tenant, reviewed on an Object Transporter diff, and migrated. Extracts still cannot be loaded straight to Production. Security policy migration merges unless someone chooses overwrite. Group permissions on business processes are additive and will not remove a Production grant. The policy should say who is allowed to choose overwrite and who removes grants by hand.
-   No worker’s pay, medical detail, or national identifier goes into a prompt. The security example Workday published is about a **field and a role**, not a named person’s compensation amount. Follow that shape.
-   Customer Central access stays with the customer. Workday recommends at least two security administrators and two customer-central administrators when a partner was involved, so the customer can operate after the partner leaves. Support contracts that leave a single partner account as the only administrator fight that recommendation. The initial owner account deactivates after 60 days.
-   A desktop agent used by support, such as [Kiweely Vine](https://kiweely.com/vine), uses a named person’s sign-in, asks before any change, and is scoped to one client per conversation. Proxy tests are watched and recorded as that security group. Production changes are still approved. Vine is not covered by the Deployment Agent setup, and a personal developer tenant being free does not make a client’s Production tenant free. A client tenant needs a Personal license at $99 a month or a firm seat at $149 a month.

## What to measure

Measure records, not prompts.

| Measure | Implementation target | Support target |
| --- | --- | --- |
| Designs that name a tenant object a second person opened | All of them | All fixes |
| Migrations with a saved post-migration summary | All packages that moved | All Production fixes that are configuration |
| Incidents closed with only a chat link | Zero | Zero, because the link dies |
| Production changes made only in Sandbox | Zero, unless an extract exists | Zero |
| Agent users who are not on the domain policy | Zero | Zero |

Workday will not produce this table for you. It will produce the migration summary, the event, and the agent’s 14-day history. Your policy chooses which of those counts.

## Failure modes

-   One policy paragraph: “AI is encouraged.” Analysts then paste Production data into a non-Production agent and call it support.
-   Support “mirrors Production” by testing in a Sandbox that refreshed last night and no longer contains yesterday’s fix.
-   The implementation partner leaves, and the only people who could deactivate the agent or run Object Transporter are gone. The agent keeps returning on every Sandbox refresh because nobody can deactivate it in Production.
-   A support bot promise based on Payroll Agent or Financial Audit Agent. The catalog lines are payroll assistance and procure-to-pay audit samples. Write those down if you enable them. Do not widen them in the policy.
-   Treating Vine and Deployment Agent as interchangeable for a night-shift analyst. One inspects non-Production configuration inside Workday. The other signs in as the analyst and can change what that analyst can change, after approval. The approval is the control. The product name is not.

## Frequently asked questions

### Can support use Sandbox as “almost Production”?

Yes, for configuration that a refresh has copied from Production. No, for data or configuration that existed only in Sandbox, and no, as a way to chat with a Production assistant. Confirm when the refresh ran before you call Sandbox a copy.

### Should AMS ban desktop agents?

Ban unapproved changes and shared sign-ins across clients. A desktop agent that asks before it changes, and that the analyst watches, is compatible with change control. A desktop agent that nobody approved is not. The policy should say which.

### Does implementation’s Ask history transfer to the support team?

No. History is per tenant and deleted after 14 days. Transfer the decision log and the migration summaries. Do not transfer a login and hope the chats are still there.

### Who updates the policy at the next feature release?

The same owner who reads What’s New in Workday in Sandbox Preview, where the HCM course says to run it when the preview window starts. Feature releases reach preview about five weeks before they reach every tenant. Agent behavior in the admin guide can change in those notes. The policy should name the person who rereads the Deployment Agent setup topic each release, not “the AI.”

## Sources checked

Public Workday topics listed above, fetched 2026-11-16. Kiweely prices and approval behavior are from kiweely.com. Workday does not publish an AMS or support-policy document on the pages checked.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### Workday cutover and go-live: the sequence, and a list written from tests](https://kiweely.com/blog/workday-cutover-runbook-from-ai-tests)
-   [November 16 ### Configuration workbooks are not a Workday object](https://kiweely.com/blog/ai-workday-configuration-workbooks)
-   [November 16 ### Fix the Workday Org Feed Behind a ServiceNow Ticket Storm](https://kiweely.com/blog/stop-servicenow-tickets-by-fixing-the-workday-org-feed)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Scoping AI Workday Access for Contingent Workers and Alumni](https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni)
-   [Correlating Workday Audit Events with AI Assistant Tool Calls](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)
-   [Workday Cost Centers and Workers to NetSuite After a Reorg](https://kiweely.com/guides/workday-cost-centers-workers-to-netsuite)
-   [Workday Headcount to Snowflake When Data Cloud Is Not Enough](https://kiweely.com/guides/workday-headcount-to-snowflake-beyond-data-cloud)
-   [Performance Check-In and Goals Screens Managers Will Open](https://kiweely.com/guides/performance-check-in-goals-screens-managers-open)
-   [Building an Open Enrollment Decision Screen on Live Workday Elections](https://kiweely.com/guides/open-enrollment-decision-screen-live-workday-elections)
-   [Mandatory Learning and Acknowledgements with Live Workday Status](https://kiweely.com/guides/mandatory-learning-acknowledgements-live-workday-status)
-   [Day-One Tax, Payment Election, and Form I-9 Pages as Pass-Through](https://kiweely.com/guides/day-one-tax-payment-i9-pass-through-pages)

## 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.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## 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.
