Skip to content
KiweelyKiweelyKiweely

Workday First-Party Agent Tenant Prerequisites for Implementers

Before a Workday-built agent can be used, each tenant needs ASOR enabled, the right domains on an unconstrained group, UMSA for Workday-built agents, and registration limited to SKUs you obtained.

  • Checked against Workday on
  • Applies to Workday AI
  • 4 min read
  • Published
  • By Kiweely
On this page

A Workday-built (first-party) agent does not become usable from a SKU alone. Each tenant needs Agent System of Record enabled, ASOR domains on an unconstrained security group, UMSA for Workday-built agents, and a successful Register from agents you actually obtained—then skill configuration and Activate.

  • Checked against Workday on November 18, 2026
  • Applies to Workday AI
  • 7 min read

Prerequisite matrix

Prerequisite Why it blocks first-party agents Workday task / artifact
PrerequisiteASOR functional area enabled Why it blocks first-party agentsHub and agent tasks sit behind ASOR Workday task / artifactMaintain Functional Areas → Agent System of Record
PrerequisitePending security activation Why it blocks first-party agentsDomain enables do nothing until activated Workday task / artifactActivate Pending Security Policy Changes (after FA and after group grants)
PrerequisiteASOR domains enabled Why it blocks first-party agentsHub, manage, compliance, reporting Workday task / artifactDomain Security Policies for Functional Area
PrerequisiteUnconstrained group permissions Why it blocks first-party agentsWorkday currently allows only unconstrained groups on ASOR policies Workday task / artifactMaintain Permissions for Security Group
PrerequisiteOAuth 2.0 capable security environment Why it blocks first-party agentsASU private-key credentials Workday task / artifactTenant security posture (Workday stores credentials)
PrerequisiteUMSA for Workday-built Why it blocks first-party agentsRequired in non-Production and Production for Workday-built agents Workday task / artifactCommunity profile Subscription Service Agreement / Innovation Services opt-in if on MSA
PrerequisiteSKU entitlement Why it blocks first-party agentsYou can only register agents in SKUs obtained Workday task / artifactUnregistered Workday Agent tab emptiness is a signal
PrerequisiteFlex Credits understanding Why it blocks first-party agentsSkills meter credits per Rate Card Workday task / artifactPlatform Consumption Console + Rate Card
PrerequisitePer-tenant repetition Why it blocks first-party agentsNo ASOR config migration Workday task / artifactRepeat in Implementation, Sandbox, Preview, Production as needed

ASOR security domains to grant

After enabling the functional area, enable and permission:

Domain Workday’s purpose
DomainAgent Compliance Workday’s purposeCompliance reports and data
DomainAgent Management Hub Workday’s purposeCentral hub for viewing and managing agents
DomainManage: Agents Workday’s purposeConfigure, activate, deactivate
DomainReports: Agent Reporting Workday’s purposeAgent analytics data sources
DomainReports: AI Agent Security Workday’s purposeExample: View AI Agent User Audit Trail
DomainSetup: Agents Workday’s purposeSetup tasks and activities

Also enable Reports: AI Agent Security in the System functional area as called out in the set-up guide.

Agreement and SKU gates

  1. Confirm UMSA vs MSA on the organization’s Community profile (Workday’s register guide walks the avatar → organization → Subscription Service Agreement value).
  2. On UMSA, keep machine-learning data contributions enabled for full agent functionality per Workday’s UMSA AI concept.
  3. On MSA, plan the Innovation Services opt-in before promising dates.
  4. Open Agent Management Hub → Unregistered Workday Agent and list only what you will register. Missing agents mean SKU/agreement work, not a skill toggle problem.

Flex Credits before first Activate

Workday Flex Credits meter defined skills and capabilities on the Rate Card—not tokens. The public Rate Card (last updated November 5, 2026) includes first-party lines such as:

Agent / offer Example meter Credits
Agent / offerSelf Service Agent Example meterBase retrieval / Advanced write Credits1 / 5 per request
Agent / offerDeployment Agent Example meterAsk skill interaction (IMPL/Sandbox agentic response) Credits5 (footnote: uses Flex Credits in non-Production)
Agent / offerAdoption Agent Example meterRelease Impact Analysis per release note Credits10 (same non-Production footnote family)

Marketing pages describe Complimentary Flex Credits and testing in non-production for most agents. Treat Rate Card footnotes as authoritative when an offer is an exception.

Sandbox refresh pattern (Deployment Agent example)

Workday’s Deployment Agent setup guide recommends configuring in Production so Sandbox refreshes keep the registration—even though the agent is not available for interactive use in Production. Chat histories are tenant-isolated and retained 14 days.

To stop Flex Credit burn after a trial: Agent Management Hub → Agent Registry → agent → Deactivate Agent, with Manage: Agents and Setup: Agents. Deactivate in every tenant you configured—including Production if you used the refresh pattern—or Sandbox reactivation follows the next refresh.

Go / no-go before register

Go when ASOR domains are live, an unconstrained admin group can open Agent Management Hub, UMSA covers Workday-built agents for the environments in scope, and the Unregistered tab shows the target agents.

No-go when ASOR exists only in Sandbox, Available To groups are constrained-only (unsupported for ASOR policies today), UMSA is unresolved, or stakeholders expect Production conversational use of an agent Workday marks non-interactive there.

Frequently asked questions

Do I set up ASOR once for all tenants?

No. Workday says you must set up and configure ASOR in each tenant; there is no current method to migrate those configurations.

Is UMSA required for Workday-built agents?

Yes for non-Production and Production tenants. Workday says UMSA is not required for self-built agents in non-Production tenants.

Why configure Deployment Agent in Production if it is not interactive there?

Workday recommends Production setup so Sandbox refreshes keep the configuration. The agent is not accessible for use in Production; deactivate in Production too if you need Sandbox consumption to stay off after refresh.

Frequently asked questions

Do I set up ASOR once for all tenants?

No. Workday says you must set up and configure ASOR in each tenant; there is no current method to migrate those configurations.

Is UMSA required for Workday-built agents?

Yes for non-Production and Production tenants. Workday says UMSA is not required for self-built agents in non-Production tenants.

Why configure Deployment Agent in Production if it is not interactive there?

Workday recommends Production setup so Sandbox refreshes keep the configuration. The agent is not accessible for use in Production; deactivate in Production too if you need Sandbox consumption to stay off after refresh.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.