---
title: "Workday AI ecosystem map 2026 — Kiweely"
description: "A plain map of Workday’s AI stack in 2026: Sana as the experience layer, ASOR as governance, and Workday-built, partner, customer, and external agents."
url: https://kiweely.com/guides/workday-ai-ecosystem-map-2026
---

# The 2026 Workday AI map: Sana, ASOR, Workday-built, custom, partner, and external agents

Workday’s public AI story has five layers: Sana orchestrates, ASOR governs, Workday-built agents ship in the product, partners and customers bring their own, and build tools such as Developer Agent create new ones. This guide places each layer with Workday’s own words.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   6 min read
-   Published November 16
-   By Kiweely

Workday’s AI stack is not one product. Public Workday pages describe **Sana** as the agentic experience layer, the **Agent System of Record (ASOR)** as the place to register, secure, and observe agents, **Workday-built agents** that ship with the platform, and routes for **partner-built**, **customer-built**, and **external** agents. Developer Agent and Agent & App Builder are how teams create new agents and apps on Workday Build.

If you only remember one sentence: Sana is where people ask; ASOR is where IT governs; Workday-built agents are product offers; Extend / Developer Agent is how you build your own.

## The five layers (Workday’s own grouping)

| Layer | What Workday says it does | Where to start |
| --- | --- | --- |
| Experience | Sana interprets intent and coordinates multi-step work across Workday-native agents |  [Workday AI Agents](https://www.workday.com/en-us/ai-agents.html) |
| Governance | ASOR registers agents, applies security and Agent Passport style controls, and keeps auditability |  [AI Platform](https://www.workday.com/en-us/ai-platform.html) · Agent Management Hub in-tenant |
| Workday-built | Purpose-built HR, finance, IT, and “everyone” agents Workday maintains |  [Workday-Built Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/reference--workday-built-agents.html) |
| Partner / marketplace | Partner agents connected into ASOR and surfaced through Marketplace | AI Agents page “Partner-Built” |
| Customer / external build | Custom agents in Extend / Agent & App Builder; external agents over open protocols |  [Custom Agents](https://developer.workday.com/documentation/GUID-c3910467-0fd6-4f27-b78e-436cfe0a3147-enHYPHENus) |

Workday’s marketing page also names three build/run pillars on the AI Platform: **Agent & App Builder**, **Agent-Ready Tools**, and the **Developer Platform**, plus governance products **Agent System of Record**, **Agent Passport**, and **Agent Analytics**.

## Sana: the experience layer

On [Workday AI Agents](https://www.workday.com/en-us/ai-agents.html), Workday states that Sana anticipates work, advises with exceptions for review, and can act in the flow of work. The same page’s FAQ says Sana interprets user intent, coordinates workflows across Workday-native agents, and routes actions through ASOR so security and audit stay unified.

Practical consequence for implementers: turning on a Workday-built agent without deciding how employees will reach it (Self-Service Agent chat, Sana, Teams/Everywhere patterns your tenant already uses) leaves the agent registered but unused.

## ASOR: the control plane

Workday’s AI Platform page positions ASOR as one place to manage, track, and govern every agent with the right permissions. The admin guide for registering Workday-built agents requires **Agent System of Record setup**, then:

1.  Open **Agent Management Hub**
2.  Register from **Unregistered Workday Agent**
3.  Configure skills and populate the **Available To** security groups per skill
4.  Activate (which also activates the Agent System User for that agent)

Workday documents that runtime checks both the user’s access to the agent and the user’s access to the APIs the agent’s tools call. UMSA (or an Innovation Services opt-in path from MSA) is required for Workday-built agents in the tenants where you run them—confirm your agreement type before you assume an agent will appear.

ASOR is not “optional telemetry.” If an agent is not registered and activated with the right skill security groups, users simply cannot use it.

## Workday-built agents (admin-guide catalog)

The [Workday-Built Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/reference--workday-built-agents.html) reference (last updated 2026-09-04 on that page) lists product agents including:

| Agent | One-line purpose from Workday |
| --- | --- |
| Deployment Agent | Implementation knowledge and in-tenant configuration inspection in non-Production (Implementation, Preview, Sandbox, Customer Central connected to non-Production) |
| Adoption Agent | Release Impact Analysis in Preview |
| BP Optimize Agent | Analyze business processes and recommend improvements |
| Case Agent | HR case creation suggestions, assignment, and conversation summaries |
| Core Reporting Agent | Conversational reporting on enabled reports |
| Self-Service Agent | Self-service reads and common actions (personal info, time off, goals, policy articles) |
| Payroll Agent | Assist with Workday Payroll |
| Planning Agent | Natural-language analyst in Adaptive Planning |
| Decision Intelligence | Investigate Adaptive Planning data and submit changes through existing approvals |
| Financial Audit Agent | High-volume procure-to-pay audit sample support |
| Revenue Contract Agent | Customer contracts from uploaded documents and contract insights |
| Contingent Sourcing Agent | VNDLY applicant grading and prior-applicant surfacing |
| Travel Agent | Search, book, and modify travel |
| Talent Sentiment Agent | Survey sentiment insight cards and follow-up questions |

Marketing pages may show additional named agents (for example Talent Acquisition or Workforce Management). Treat the **admin-guide reference table** as the configuration catalog for “what can I register in Agent Management Hub today,” and treat marketing as the demand-side story. Only register agents your SKU includes—Workday’s register guide says you can only register agents in the SKUs your organization obtained.

## Customer-built custom agents

Workday’s developer documentation describes a three-stage custom-agent path:

1.  **Build and deploy** in App Builder (Agent app or Extend app), manually or with Developer Agent, producing `.agent` and `.agentskill` artifacts into ASOR
2.  **Register / configure / activate** security in ASOR (automatic registration in development; higher environments need App Manager plus ASOR steps)
3.  **Invoke** from Self-Service Agent chat, Sana, business processes, Agent-to-Agent (A2A), or Model Context Protocol surfaces

Custom agents are **delegate mode only** in that documentation: they act with the user’s authority model Workday describes for delegate agents, not as unconstrained ambient workers.

## Partner-built and external agents

Workday’s AI Agents page separates Partner-Built (Marketplace) from Customer-Built (Agent & App Builder). The AI Platform page states you can plug agents into Workday over Model Context Protocol and inherit governance and permissions. Exact partner listings change; the durable rule is: if it is not in ASOR with clear ownership and skill security, it is not governed the way Workday describes enterprise agents.

## What this map deliberately excludes

-   **Flex Credit metering math** — published on the Rate Card and Platform Consumption Console guides; do not guess rates here.
-   **Desktop co-pilots that sit outside Workday’s agent runtime** — they are not Workday-built agents and are not registered in ASOR unless you deliberately connect them as external agents.
-   **Community-only setup tips** — this guide only cites public Workday product and developer pages.

## Decision checklist for a Workday program

1.  Name the **experience** employees will use (Sana / Self-Service Agent / other).
2.  Confirm **UMSA / Innovation Services** readiness for Workday-built agents.
3.  Register only the **SKU-entitled** Workday-built agents you will actually operate.
4.  Decide whether net-new automation is a **configuration** change, a **custom agent**, or an **external** agent before anyone opens App Builder.
5.  Assign an **owner**, skill security groups, and a deactivation path in Agent Management Hub before Production use.

## Frequently asked questions

### Is Sana an agent or a shell around agents?

Workday describes Sana as the single agentic experience that orchestrates Workday-native agents and routes actions through ASOR. Treat it as the shell and router, not as a substitute for registering each underlying agent.

### Do I need Extend to use Workday-built agents?

No. Workday-built agents are registered through Agent Management Hub per the admin guide. Extend / Developer Agent is the path for **customer-built** custom agents and apps.

### Where do I see every agent my company runs?

Workday positions ASOR / Agent Management Hub as that registry for Workday, partner, and customer agents that participate in the platform. Agents that never register there are outside that control plane.

### Can Workday-built agents run without security group configuration?

No. For each skill you enable, Workday requires **Available To** security groups, and runtime still checks tool/API permissions for those users.

## Sources checked

Public Workday pages listed in the frontmatter, fetched 2026-11-16.

## Sources checked

-   [Workday AI Agents](https://www.workday.com/en-us/ai-agents.html)
-   [Workday AI Platform](https://www.workday.com/en-us/ai-platform.html)
-   [Workday-Built Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/reference--workday-built-agents.html)
-   [Register and Configure Workday-Built Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/manage-agents.html)
-   [Custom Agents on Workday's AI Platform](https://developer.workday.com/documentation/GUID-c3910467-0fd6-4f27-b78e-436cfe0a3147-enHYPHENus)

## 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 Illuminate, Agent System of Record, and Custom Agents: What Each Covers Understand how Workday’s AI stack divides responsibilities across Workday-built agents, the Agent System of Record (ASOR) governance hub, and custom or external agents built with Workday Extend AI, Agent-Ready Tools, and Custom Agent Actions.](https://kiweely.com/guides/workday-illuminate-asor-custom-agents-comparison)
-   [### 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)
-   [### 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)

### More guides on Custom agents and Workday AI

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

-   [Why Generic IDE Agents Still Need Workday Developer Agent for Extend](https://kiweely.com/guides/why-generic-ide-agents-need-workday-developer-agent)
-   [Complimentary Workday Flex Credits: What They Are and What Happens When They Run Out](https://kiweely.com/guides/complimentary-workday-flex-credits-what-happens-when-exhausted)
-   [AI Agents That Edit Workday Studio XSLT Safely: Diff, AUnit, Then Deploy](https://kiweely.com/guides/ai-agents-edit-workday-studio-xslt-safely)
-   [Best AI Agent Setup for Workday Security Policy and Pay-Access Audits](https://kiweely.com/guides/best-ai-agent-setup-for-workday-security-audits)
-   [Forecasting Workday Flex Credits for HCM Agents vs Financials Workloads](https://kiweely.com/guides/forecasting-workday-flex-credits-hcm-vs-financials)
-   [Best AI Agent Setup for Workday Orchestrate for Integrations](https://kiweely.com/guides/best-ai-agent-setup-for-workday-orchestrate)
-   [Chargeback Models for Workday Flex Credits Across HR, Finance, and IT](https://kiweely.com/guides/workday-flex-credits-chargeback-hr-finance-it)
-   [Build a Workday UI Test Charter an AI Agent Can Run Without Brittle CSS](https://kiweely.com/guides/workday-ui-test-charter-for-ai-agents)

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

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

-   [App Builder vs Claude Code for Workday Developer Agent](https://kiweely.com/blog/app-builder-vs-claude-code-developer-agent)
-   [What to put in a Workday SOW when agents are in scope](https://kiweely.com/blog/workday-implementation-sow-ai-agents)
-   [Can AI agents speed up a Workday implementation? What they do in the tenant today](https://kiweely.com/blog/kiweely-vine-workday-implementation-project)

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