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 |
|---|---|
| PhaseRegister | What Workday says it doesPrepares the agent for configuration and activation |
| PhaseConfigure | What Workday says it doesChooses which skills are on and who can access them |
| PhaseActivate | What Workday says it doesLets users interact under the security you set |
| PhaseDeactivate | What Workday says it doesHides the agent from users but keeps it in the hub |
| PhaseArchive | What Workday says it doesRemoves 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:
- Maintain Functional Areas → enable Agent System of Record → Activate Pending Security Policy Changes.
- 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.
- 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.
- 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:
- Open the Agent Management Hub report.
- Open the Unregistered Workday Agent tab (the hub also surfaces Find Unregistered Workday Agents for discovery).
- Register the agent you want.
- 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
- On Agent Registry, open the agent name.
- Click Configure Agent.
- In the skill status column, enable each skill with the toggle.
- 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 |
|---|---|
| GateInteraction (Available To on the skill) | What it controlsWho may talk to / invoke that skill |
| GateTool / API security | What it controlsWhether 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
- Confirm the agent appears on Agent Registry with the skills you enabled.
- Sign in as a user in an Available To group and open the agent’s documented entry point for that skill.
- Sign in as a user outside those groups and confirm the skill is not offered.
- 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.