---
title: "Workday Deployment Agent: Q&A Task vs Ask Skill Setup"
description: "Compare Deployment Agent (Q&A) with the ASOR Ask skill: tenant inspection, setup tasks, and when each applies in non-Production."
url: https://kiweely.com/guides/workday-deployment-agent-qa-vs-ask
---

# Workday Deployment Agent: Q&A Task vs Ask Skill Setup

Deployment Agent (Q&A) answers from documentation without reading your tenant. The ASOR-enabled Ask skill adds read-only tenant inspection as documented, after Agent Management Hub setup. This guide compares both and lists the Workday tasks to enable each.

-   **Checked** against Workday on November 19
-   Applies to **Workday Extend**
-   3 min read
-   Published November 18
-   By Kiweely

**Deployment Agent (Q&A)** answers from Workday documentation and Community. The **ASOR-enabled Deployment Agent with the Ask skill** adds read-only inspection of your live non-Production configuration as Workday documents it. Workday’s [Configuration Cloud](https://blog.workday.com/en-us/configuration-cloud.html), in opt-in early access for Workday partners since 18 November 2026, adds that Deployment Agent can carry out changes once approved. Pick Q&A when you need free general guidance on Customer Central; pick Ask when implementers need tenant-grounded answers.

## Comparison

|  | Deployment Agent (Q&A) | ASOR Deployment Agent with Ask skill |
| --- | --- | --- |
| How you open it |  **Deployment Agent (Q&A)** task (global search: Deployment Agent) | Register/activate in **Agent Management Hub**, then use the conversational agent in that tenant |
| Tenant inspection | None — “can’t access your specific data or live tenant configurations” | Read-only inspection of calculated fields, condition rules, business processes, reports (and more) via Ask; change-making only in partner early access (Configuration Cloud) |
| Knowledge corpus | Administrator/User Guides, Community, implementer-only docs, WSDLs | Same documentation corpus **plus** live configuration context |
| UMSA / ASOR | Not required | Required: set up Agent System of Record; enable skills in Agent Management Hub |
| Where | Documented for Implementation, Sandbox, Preview, and Customer Central (Q&A). Ask conversational use is for non-Production; **not** available as a conversation assistant in Production | Same non-Production rule for conversational use |
| Customer Central note | Provided by default as a **free-of-charge** general Q&A experience after Customer Central activation | Separate ASOR registration; configuring one tenant does **not** enable others |
| Skills Workday names | General Q&A only (no tenant-aware Ask) | Enable **Tenant Inspection** and **Implementation Knowledge** to turn on Ask |

Ask capabilities Workday lists once enabled: Configuration Intelligence, Technical Troubleshooting, and Knowledge Discovery (see the skills reference).

## Setup: Deployment Agent (Q&A) on Customer Central

1.  Activate Customer Central with Customer Central administrator and security administrator accounts (**Steps: Set Up Customer Central Accounts** in Workday docs).
2.  Sign in to Customer Central as a Customer Central security administrator.
3.  Run **Maintain Feature Opt Ins**.
4.  On **Deployment Agent (Q&A)**, confirm **Opt Out of Feature** is unchecked.
5.  Instruct users: global search **Deployment Agent** → open the **Deployment Agent (Q&A)** task.

Workday states Q&A currently supports US and EU data centers and is not yet available in Canada, Australia, UK, Japan, or to Federal customers.

## Setup: ASOR Ask skill (per tenant)

Workday does not auto-enable the agent across tenants. For each Implementation, Sandbox, Preview, or Customer Central tenant where you want Ask:

1.  Confirm subscription path: UMSA vs MSA opt-in (profile → organization → **Subscription Service Agreement**), per the setup guide.
2.  Complete **Set Up Agent System of Record** (and the Customer Central variant if configuring there). Optionally grant **Reports: AI Agent Security**.
3.  Prefer initial security/ASOR setup in **Production** so Sandbox refreshes keep the configuration—even though you cannot *use* the conversational agent in Production. If you need Sandbox before the next refresh, configure Production **and** Sandbox.
4.  Run **Create Security Policy for Domain** for **Deployment Agent** if the policy does not already exist.
5.  Open domain **Deployment Agent Users** → related actions → **Edit Security Policy Permissions** → add groups (example: Implementers) with the needed report/task permissions.
6.  Run **Activate Pending Security Policy Changes**.
7.  Open **Agent Management Hub** → register the Deployment Agent from **Unregistered Workday Agent**.
8.  Configure skills: enable **Tenant Inspection** and **Implementation Knowledge** (Workday’s example for enabling Ask). For each skill, set **Available To** security groups that are also on **Deployment Agent Users** (mismatch → validation error).
9.  **Activate** the agent. Chat history is isolated per tenant and retained **14 days**.

To stop Sandbox reactivation after a refresh, deactivate in **Production** Agent Management Hub as well as Sandbox.

## Operational limits (both)

-   Assists; does not replace human expertise — validate against official documentation.
-   Long threads auto-summarize; start a new chat per topic.
-   Ask path is advisory and read-oriented as Workday documents it; treat its outputs as guidance to apply manually. Configuration Cloud’s change-making is separate and in partner early access.

## Sources

All steps and distinctions above are from the `doc.workday.com` pages listed in frontmatter (fetched 2026-11-18).

## Sources checked

-   [Deployment Agent in Implementation Environments and Customer Central](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/concept--deployment-agent-in-implementation-enviro.html)
-   [Deployment Agent Skills and Capabilities](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/reference--deployment-agent-skills-and-capabilitie.html)
-   [Deployment Agent (Q&A)](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/deployment-agent-q&a-/concept--workday-deployment-agent.html)
-   [Verify Deployment Agent (Q&A) Availability in Customer Central](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/deployment-agent-q&a-/verify-deployment-agent-availability-in-customer-c.html)
-   [Set Up Deployment Agent in Implementation Environments and Customer Central](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/set-up-deployment-agent-on-implementation-environm.html)

## Related guides

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

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [Should each Workday AI integration use its own ISU with no UI sessions?](https://kiweely.com/guides/workday-isu-per-area-no-ui-sessions-for-agents)
-   [How do I secure Workday RaaS access for an internal LLM or AI agent?](https://kiweely.com/guides/workday-raas-for-ai-agents-security)
-   [Set up Workday Agent System of Record for HRIS admins](https://kiweely.com/guides/workday-asor-setup-for-hris-admins)
-   [Financials and payroll prompts for the Workday Deployment Agent](https://kiweely.com/guides/workday-ai-prompt-library-financials-payroll)
-   [HCM prompt library for Workday implementers using Deployment Agent](https://kiweely.com/guides/workday-ai-prompt-library-hcm-implementers)
-   [Stop or audit a Workday AI agent: an admin runbook](https://kiweely.com/guides/stop-audit-workday-ai-agent-admin-runbook)
-   [Workday Developer Agent Prompt Templates That Hold](https://kiweely.com/guides/workday-developer-agent-prompt-templates)
-   [A Learning Path on a Workday Build Personal Tenant](https://kiweely.com/guides/workday-build-personal-tenant-learning-path)

### From the blog on Custom agents and Workday AI

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

-   [Insurance and MSA Language for AI Agents That Touch Workday](https://kiweely.com/blog/insurance-msa-language-ai-agents-workday)
-   [Load and Concurrency: When AI UI Agents Are the Wrong Tool for Workday](https://kiweely.com/blog/when-ai-ui-agents-wrong-tool-workday-load-concurrency)
-   [Migrating a Workday Extend App from Hand-Edited JSON to an Agent-Maintained Repo](https://kiweely.com/blog/migrate-extend-app-to-agent-maintained-repo)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

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

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
