---
title: "Register Workday-Built Agents and Activate Skills in Agent…"
description: "Exact Agent Management Hub steps to register a Workday-built agent, enable skills, set Available To groups, and activate the Agent System User."
url: https://kiweely.com/guides/workday-asor-register-activate-agent-skills
---

# Register Workday-Built Agents and Activate Skills in Agent Management Hub

After ASOR is on, Workday-built agents still sit on the Unregistered tab until you register them, toggle skills, assign security groups, and activate. This guide is the implementer checklist for that path.

-   **Checked** against Workday on November 18
-   Applies to **Workday AI**
-   5 min read
-   Published November 18
-   By Kiweely

Register a Workday-built agent from the **Unregistered Workday Agent** tab in **Agent Management Hub**, enable each skill you want, put security groups in **Available To** for those skills, then **Activate**. Enabling Agent System of Record alone does not put the agent in front of users.

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

## What “register and activate” actually covers

Workday’s Agent System of Record (ASOR) is the tenant control plane for Workday-built, custom, partner, external (self-built), and Sana User agents. ASOR itself is included in the core subscription; you still only register Workday-built agents that sit in SKUs your organization obtained.

Agent Management Hub runs this lifecycle:

| Phase | What Workday says it does |
| --- | --- |
| Register | Prepares the agent for configuration and activation |
| Configure | Chooses which skills are on and who can access them |
| Activate | Lets users interact under the security you set |
| Deactivate | Hides the agent from users but keeps it in the hub |
| Archive | Removes it from the Agent Registry and keeps history |

Production registration requires Universal Main Service Agreement (UMSA) opt-in. You must set ASOR up in **each** tenant; Workday publishes no migration path for ASOR configuration between tenants.

## Prerequisites before the Unregistered tab

Complete **Set Up Agent System of Record** in the tenant you are working in:

1.  **Maintain Functional Areas** → enable **Agent System of Record** → **Activate Pending Security Policy Changes**.
2.  **Domain Security Policies for Functional Area** → functional area **Agent System of Record** → enable **Agent Compliance**, **Agent Management Hub**, and **Manage: Agents**. Also enable **Reports: AI Agent Security** in the System functional area.
3.  **Maintain Permissions for Security Group** for an **unconstrained** security group (Workday currently only allows unconstrained groups on these ASOR policies). Grant access to **Agent Compliance**, **Agent Management Hub**, **Manage: Agents**, **Reports: Agent Reporting**, **Reports: AI Agent Security**, and **Setup: Agents**.
4.  **Activate Pending Security Policy Changes** again.

Confirm your subscription path for Workday-built agents: on UMSA the feature is available (keep machine-learning data contributions enabled for full agent functionality per Workday’s UMSA AI concept). On MSA, your organization must opt in to UMSA through Innovation Services. Workday states UMSA is required for Workday-built agents in non-Production and Production; UMSA is not required for self-built agents in non-Production.

## Register a Workday-built agent

Exact task path from Workday’s register guide:

1.  Open the **Agent Management Hub** report.
2.  Open the **Unregistered Workday Agent** tab (the hub also surfaces **Find Unregistered Workday Agents** for discovery).
3.  **Register** the agent you want.
4.  Confirm it moved to the **Agent Registry** tab.

You can only register agents included in the SKUs your organization obtained. If the agent is missing from Unregistered, treat that as a SKU or agreement gap—not a missing toggle on a skill.

## Configure skills and Available To

1.  On **Agent Registry**, open the agent name.
2.  Click **Configure Agent**.
3.  In the skill status column, enable each skill with the toggle.
4.  For each enabled skill, populate **Available To** with the security groups that may use that skill. Those groups are the agent’s interaction policy.

Workday evaluates **two** gates at runtime:

| Gate | What it controls |
| --- | --- |
| Interaction (Available To on the skill) | Who may talk to / invoke that skill |
| Tool / API security | Whether those users can run the APIs that make up the skill’s tools |

Use the **View Security for Agent Skill** report to see the tools’ domain or business process policies. Workday recommends aligning Available To groups with the groups that hold tool permissions. Interaction groups do not have to be a 1:1 match with API policy groups, but a user must be in a group that appears on **both** the skill and the API policies for the tool call to succeed.

Ambient-mode skills are different: they run without human interaction (schedule or set initiation) and do not require interaction access the same way delegate skills do.

## Activate (and what that turns on)

After configuration, activate the agent from its profile in **Agent Management Hub**. When you activate, the **Agent System User (ASU)** for the agent also activates automatically. Workday creates and stores the private-key client credentials; your security environment must support OAuth 2.0. You can review ASU accounts on **All AI Agent Accounts** (Workday Accounts domain) or **All Workday Accounts**.

Deactivate when you need the agent hidden: users lose access, the agent stays in the hub for later reactivation. Archive removes it from the registry while retaining history.

## Honest limits implementers hit

-   **Per-tenant work.** ASOR security and registration do not migrate. Sandbox refresh behavior for usage history: Workday does not delete prior weeks’ usage activities during Sandbox refresh; configuration you only made in Sandbox can still be wiped by a Production→Sandbox refresh of tenant config—re-check after refresh.
-   **SKU wall.** Registration is limited to agents in your obtained SKUs.
-   **Analytics asymmetry.** Several hub analytics (for example total sessions and unique users over time) are documented as available for Workday-built agents only.
-   **Flex Credits.** Workday points implementers to Flex Credits for consumption impact; meter lines live on the Flex Credits Rate Card, not on the register task itself.

## Quick verification after Activate

1.  Confirm the agent appears on **Agent Registry** with the skills you enabled.
2.  Sign in as a user in an **Available To** group and open the agent’s documented entry point for that skill.
3.  Sign in as a user **outside** those groups and confirm the skill is not offered.
4.  Open **View Security for Agent Skill** for a tool-backed skill and confirm the test user’s groups cover the listed policies before you call a write path in UAT.

## Frequently asked questions

### Does enabling ASOR automatically turn on Workday-built agents?

No. You still register each eligible agent from the Unregistered Workday Agent tab, configure skills and Available To groups, then activate it in Agent Management Hub.

### Do I need UMSA before registering Workday-built agents?

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

### What happens to the Agent System User when I activate?

When you activate an agent, Workday automatically activates the Agent System User (ASU) for that agent.

## Frequently asked questions

### Does enabling ASOR automatically turn on Workday-built agents?

No. You still register each eligible agent from the Unregistered Workday Agent tab, configure skills and Available To groups, then activate it in Agent Management Hub.

### Do I need UMSA before registering Workday-built agents?

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

### What happens to the Agent System User when I activate?

When you activate an agent, Workday automatically activates the Agent System User (ASU) for that agent.

## Sources checked

-   [Register and Configure Workday-Built Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/manage-agents.html)
-   [Set Up Agent System of Record](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/set-up-agent-system-of-record.html)
-   [About Workday Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/setup-considerations--agent-system-of-record.html)
-   [Workday Agent System of Record](https://www.workday.com/en-us/ai-platform/agent-system-of-record.html)

## Related guides

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

-   [### 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.](https://kiweely.com/guides/workday-first-party-agent-tenant-prerequisites)
-   [### Set up Workday Agent System of Record for HRIS admins ASOR is the tenant control plane for agents. HRIS admins enable the functional area, activate security twice, and permission an unconstrained group. The configuration does not migrate, so Production, Sandbox, Preview, and Implementation each need the same setup.](https://kiweely.com/guides/workday-asor-setup-for-hris-admins)
-   [### 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 Agent System of Record (ASOR): An Admin’s Security and Setup Checklist Workday’s Agent System of Record (ASOR) governs both Workday-built and custom agents through the Agent Management Hub. Here is how ASUs differ from ISUs, how delegate and ambient execution evaluate security, and the exact steps an administrator takes to register, secure, and audit an agent.](https://kiweely.com/guides/workday-agent-system-of-record-security)

### More guides on Custom agents and Workday AI

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

-   [Workday Agent Passport for Implementers: Read Stamps Before You Activate Skills](https://kiweely.com/guides/workday-agent-passport-for-implementers)
-   [Ask skill on but answers feel generic: use CRAFT and “in my tenant”](https://kiweely.com/guides/ask-skill-enabled-still-generic)
-   [Deployment Agent missing? Register it from Unregistered Workday Agent](https://kiweely.com/guides/deployment-agent-not-registered)
-   [Keep Deployment Agent Ask alive across Sandbox refreshes](https://kiweely.com/guides/workday-deployment-agent-ask-after-sandbox-refresh)
-   [Workday Deployment Agent: Q&A Task vs Ask Skill Setup](https://kiweely.com/guides/workday-deployment-agent-qa-vs-ask)
-   [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)
-   [Financials and payroll prompts for the Workday Deployment Agent](https://kiweely.com/guides/workday-ai-prompt-library-financials-payroll)

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

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

-   [ServiceNow AI agents vs Workday AI agents: operations vs HCM/finance build](https://kiweely.com/blog/servicenow-ai-agents-vs-workday-ai-agents)
-   [How Workday prospects should run an AI-agent-driven implementation methodology](https://kiweely.com/blog/workday-prospect-ai-agent-implementation-methodology)
-   [Salesforce Agentforce vs Workday AI agents: what each is actually for](https://kiweely.com/blog/salesforce-agentforce-vs-workday-ai-agents)

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