---
title: "System of record for agents — Kiweely"
description: "Agent System of Record is where Workday registers, secures, and audits agents. It is included in the core subscription and it is not the worker system of…"
url: https://kiweely.com/blog/workday-system-of-record-for-agents
---

# Workday as the system of record for agents

ASOR is Workday’s control plane for Workday-built, custom, external, partner, and Sana user agents. You register, configure skills, activate, and review usage there. Worker, payroll, and financial records stay in their own domains. The agent account is a Workday account, not a second HR file.

-   By Kiweely
-   November 16
-   5 min read

Workday’s name for the control plane is Agent System of Record, ASOR. It is where an agent is defined, who may use it, and what it did. It is not a replacement for the worker record, the ledger, or the plan. A September 2025 press quote called the platform a system of action. The admin guide, fetched 2026-11-16, still tells administrators to govern agents in a system of record. Use the admin name when you write a control design. Use the press line only as positioning, under that release’s forward-looking-statement notice.

ASOR ships inside the core Workday subscription. Workday says you do not buy another SKU for the hub itself. Production registration still requires UMSA. Flex Credits policy is what the built-agent setup pages require before Production use. Those are commercial gates on top of a hub you already have.

## What is stored about an agent

Workday’s definition of an agent: an autonomous assistant that can answer and take multistep actions, using a large language model, either as itself or for a human. Every agent has skills. Each skill has tools. For Workday, tools are APIs. Resources are the API style: REST, SOAP, Graph, or WQL.

Five types share the hub: Workday-built, custom (Extend), external (self-built, registered through an API), partner (certified partner), and Sana user agents.

The lifecycle in Agent Management Hub:

| Phase | What changes for users |
| --- | --- |
| Register | The agent can be configured. Self-built agents are registered through an API. Production registration needs UMSA. |
| Configure | Which skills are on, and which security groups can use each delegate skill. Workday then creates the Agent System User. |
| Activate | People in those groups can interact, subject to tool security. The ASU activates with the agent. |
| Deactivate | Hidden from users, still in the hub, can be turned back on. This is also how you stop spend. The consumption console does not deactivate an agent for you. |
| Archive | Removed from Agent Registry. History remains. |

The registry shows status and the last time an administrator changed configuration. Open the agent for its profile, skills, and analytics.

## Security is two lists, not one

Delegate skills list security groups. Workday’s example is Employee as Self. If a person is in any group on any skill, they can interact with the agent. Ambient skills skip that list because nobody is in the loop; they run on a schedule or another start.

Tool security is separate. **View Security for Agent Skill** shows the domain and business-process policies for each tool. The groups do not have to match one for one, but the person who runs the skill must also be allowed to call the API. Otherwise the tool fails. That is the control that keeps ASOR from becoming a privilege elevator.

Agent System Users are Workday accounts. **All AI Agent Accounts** (Workday Accounts domain) and **All Workday Accounts** list them. Workday creates and stores the OAuth private key. You still have to run an environment that can do OAuth 2.0. Partner and external agents call through Agent Gateway with that ASU.

## What you can audit

| Report or data source | Who it covers | Domain |
| --- | --- | --- |
| Active Agents | All agents | Agent Management Hub |
| Total Agent Sessions, sessions over time, unique users | Workday-built only | Hub reports |
| Skill interactions and unique users per skill | Workday-built only | Reports: Agent Reporting |
| Agent Input and Output Request Details, Generate Agent Input and Output Report, Input and Output Report For Registered Agents | Workday-built only | Agent Compliance |
| View AI Agent User Audit Trail | Agent accounts | Reports: AI Agent Security |
| View Security for Agent Skill | Tools and policies | Security Administration and Manage: Agents |
| All Agent Definitions, All Agent Registrations | Registered and unregistered definitions; registrations | Reports: Agent Reporting |
| Agent Input and Output Details | Interactions for the past 30 days | Agent Compliance |
| Usage analytics data sources | Past 30 days | Reports: Agent Reporting |

Workday tells you to review the audit log regularly. A Sandbox refresh does not delete usage activity from previous weeks. The 30-day input and output data source is a shorter window than “we kept everything.” Say both facts when legal asks about retention. Workday has not, on this page, published a longer default retention period than those statements.

Domains to grant the admin team, all in Agent System of Record unless noted: Agent Compliance, Agent Management Hub, Manage: Agents, Reports: Agent Reporting, Reports: AI Agent Security, Setup: Agents.

## What ASOR is not

-   It is not the HR system of record. Contingent workers are still excluded from Self-Service Agent even if that agent is active in the hub.
-   It is not the financial system of record. Financial Audit Agent reads procure-to-pay evidence the user can access. It does not become the ledger.
-   It is not Marketplace. Discovery of partner agents is a commercial front door. The tenant record is the registry row.
-   It is not Platform Consumption Console. The console is the credit balance. ASOR is the agent-level usage the console points you back to.
-   It does not, by itself, orchestrate a conversation. The marketing FAQ says Sana interprets intent and routes through ASOR so security and audit stay in one place. If Sana is not provisioned, you still have the hub and Workday Chat for the agents you activated.
-   Session analytics tiles are not a portfolio view of partner and custom agents. Those tiles are Workday-built only.

A practical owner model is one ASOR administrator who can deactivate, one security administrator who aligns **Available To** with domain policies, and the business owner of each Workday-built skill. Custom, partner, and external agents need a named owner because the pretty usage tiles will not describe them.

## Frequently asked questions

### Do we need ASOR if we only turn on one Workday-built agent?

Yes. The setup topics for those agents start with Set Up Agent System of Record, then register from the hub. There is no documented path that skips the hub for a built agent.

### Is the Agent System User a worker we have to hire or terminate?

It is a Workday account Workday generates when you configure the agent. You review it on the account reports. It is not a hire in the staffing sense on any page fetched here.

### Can we call the press “system of action” the official control name?

You can quote the September 2025 release. The tasks, domains, and reports you will be audited on use Agent System of Record. Put that name in the RACI.

## Sources checked

About Workday Agents, Register and Configure Workday-Built Agents, Platform Consumption Console, the Workday AI Agents page, and the 16 September 2025 newsroom post, fetched 2026-11-16.

## Read next

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

-   [November 16 ### Data Cloud, agents, and Flex Credits](https://kiweely.com/blog/workday-data-cloud-agents-flex-credits)
-   [November 16 ### From Workday Illuminate to AI agents](https://kiweely.com/blog/workday-illuminate-to-ai-agents-naming)
-   [November 16 ### When not to build a Workday custom agent](https://kiweely.com/blog/when-not-to-build-workday-custom-agent)

### More guides on Custom agents and Workday AI

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

-   [Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat](https://kiweely.com/guides/workday-custom-agent-actions-permission-denied-tool-wids)
-   [Fixing invalid\_request OAuth Token Exchange Errors When Connecting Microsoft Copilot Studio to Workday A2A](https://kiweely.com/guides/workday-a2a-copilot-studio-oauth-invalid-request)
-   [Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites](https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing)
-   [Fixing Workday Developer Agent VS Code Sign-In With a Personal Developer Account and Subagent Interrupt Errors](https://kiweely.com/guides/workday-developer-agent-vscode-personal-account-login)
-   [Finding Workday tool IDs with the Agent Resource Search (finder) API](https://kiweely.com/guides/workday-finder-api-tool-discovery)
-   [Connecting an Extend app to the Workday Self-Service Agent and Microsoft Teams](https://kiweely.com/guides/workday-extend-self-service-agent-teams)
-   [How to build a chatbot in Workday Extend](https://kiweely.com/guides/workday-extend-chatbot)
-   [How to call AI Gateway Document Intelligence from a Workday Extend app](https://kiweely.com/guides/workday-extend-ai-gateway-document-intelligence)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

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

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
