---
title: "Deployment Agent Users domain and View Security for Agent…"
description: "Ask’s security groups must also sit on the Deployment Agent Users domain. Use View Security for Agent Skill; activate pending policy changes before testing."
url: https://kiweely.com/guides/workday-deployment-agent-users-domain-security
---

# Deployment Agent Users domain and View Security for Agent Skill

When you enable Deployment Agent Ask, every security group on the skill must also belong to the Deployment Agent Users domain security policy. Workday validates this and blocks access if it does not. Confirm with View Security for Agent Skill, then Activate Pending Security Policy Changes.

-   **Checked** against Workday on November 18
-   Applies to **Workday Deployment Agent, domain security**
-   2 min read
-   Published November 18
-   By Kiweely

The security groups you put on the **Ask** skill are the agent’s **interaction policy**—and they must **also** belong to the **Deployment Agent Users** domain security policy. Workday validates that link. If the group is only on the skill, you get a validation error and those users cannot use Deployment Agent in the tenant.

Confirm with **View Security for Agent Skill** before you tell the project the agent is “on.”

## Build the domain once per tenant

1.  **Create Security Policy for Domain** — for Domain, search **Deployment Agent**. If it does not appear, the policy already exists; skip create.
2.  Open domain **Deployment Agent Users** → related actions → **Edit Security Policy Permissions**.
3.  In **Report/Task Permissions**, add a row for the security groups that should use the agent (example: Implementers) with the documented permissions.
4.  Assign people to those groups (**Assign Users to User-Based Security Group** or **Assign User-Based Security Groups for Person**; aggregation groups are allowed).
5.  **Activate Pending Security Policy Changes** — comment, review, confirm, activate.

Repeat in **each** tenant where Ask will run (Customer Central, Implementation, Preview, Sandbox/Production-for-refresh). ASOR registration does not invent this domain for you.

## Wire the same groups onto Ask

1.  **Agent Management Hub** → register Deployment Agent if needed → **Configure Agent**.
2.  Enable **Ask**; in the skill’s security-group prompt, select the **same** groups that hold **Deployment Agent Users**.
3.  Run **View Security for Agent Skill** and fix gaps before activate.
4.  **Activate** the agent.
5.  Verify with a configuration-retrieval prompt (no UI skill indicator exists), then confirm in a real task such as **View Calculated Field**.

## Decisions that avoid rework

| Decision | Why |
| --- | --- |
| One canonical user-based group for Ask (for example Implementers) | Same group on domain + skill avoids validation thrash. |
| Activate security **before** agent activate | Pending policy changes leave “configured” agents that nobody can open. |
| Re-check after Sandbox refresh | Unless Production carries the domain + agent setup, Sandbox security and registration reset. |
| Deactivate in Production when retiring Ask | Refresh will otherwise restore an active Sandbox agent from Production. |

Deployment Agent Users is the gate. Skill toggles without that domain membership are incomplete setup, not a mysterious product bug.

## Frequently asked questions

### What error shows if the group is only on the Ask skill?

Workday displays a validation error when a security group added to the agent skill is not also part of the Deployment Agent Users domain security policy. Users in that group will not have access to Deployment Agent in the tenant.

### Which report checks skill security?

View Security for Agent Skill. Use it to confirm the groups you selected on Ask also have the permissions the agent needs.

### Which tasks create the domain policy?

Create Security Policy for Domain (search Deployment Agent), then Edit Security Policy Permissions on Deployment Agent Users, then Activate Pending Security Policy Changes.

## Sources checked

-   [Enable Deployment Agent Ask Skill](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/enable-the-tenant-inspection-ask-skill-for-the-dep.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)

-   [### What Workday’s Deployment Agent Can and Cannot Do in Your Tenant Workday’s ASOR-enabled Deployment Agent reads tenant configuration in Implementation, Sandbox, Preview and Customer Central. It doesn’t run in Production, and edits configuration only in partner early access. Workday publishes no price; the Rate Card meters 5 credits per Ask interaction.](https://kiweely.com/guides/workday-deployment-agent-tenant-inspection)
-   [### Workday Flex Credits Explained: What Counts as an Action Flex Credits replace per-employee pricing for Workday AI with credits drawn down per metered action. What Workday publishes about the Rate Card, the Platform Consumption Console, non-production use and how to reduce consumption.](https://kiweely.com/guides/workday-flex-credits-explained)
-   [### When does the Workday Sandbox refresh, and what does it wipe? Weekly: Workday replaces the Sandbox with a full copy of Production data and configuration. Public Workday docs give no day or hour, so ask your tenant management contact. Preview refreshes twice a year, Implementation on demand.](https://kiweely.com/guides/workday-sandbox-refresh)

### More guides on Custom agents and Workday AI

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

-   [Deployment Agent prompt patterns: in my tenant and CRAFT](https://kiweely.com/guides/workday-deployment-agent-prompt-patterns)
-   [Deployment Agent Configuration Catalog Support for Implementers](https://kiweely.com/guides/deployment-agent-configuration-catalog)
-   [Workday Custom Agent First POC Checklist for Implementers](https://kiweely.com/guides/workday-custom-agent-first-poc-checklist)
-   [Workday Developer Agent and Agent-Ready Tools for Implementers](https://kiweely.com/guides/workday-developer-agent-and-agent-ready-tools)
-   [Workday First-Party Agent Tenant Prerequisites for Implementers](https://kiweely.com/guides/workday-first-party-agent-tenant-prerequisites)
-   [Deployment Agent in Customer Central vs Implementation tenants](https://kiweely.com/guides/workday-deployment-agent-customer-central-vs-implementation-tenant)
-   [Register Workday-Built Agents and Activate Skills in Agent Management Hub](https://kiweely.com/guides/workday-asor-register-activate-agent-skills)
-   [Workday Agent Passport for Implementers: Read Stamps Before You Activate Skills](https://kiweely.com/guides/workday-agent-passport-for-implementers)

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

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

-   [How FDEs Scope AI Agent Work Without Becoming the Unpaid Helpdesk](https://kiweely.com/blog/fde-scope-ai-agent-work-without-unpaid-helpdesk)
-   [FDE vs Workday Partner SOW: Who Owns Tenant Risk When the Agent Writes](https://kiweely.com/blog/fde-vs-partner-sow-tenant-risk-when-agent-writes)
-   [When Flex Credits Make Extend AI Cheaper Than Hiring Another Integrator—and When They Do Not](https://kiweely.com/blog/when-flex-credits-cheaper-than-hiring-integrator)

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