Skip to content
KiweelyKiweelyKiweely

Blended workforce and the agent system of record

Agent System of Record registers Workday-built, custom, partner, external, and Sana user agents in one hub. Self-Service Agent still excludes contingent workers, while Contingent Sourcing Agent runs in VNDLY under that same hub. One registry is not one security model.

  • By Kiweely
  • 5 min read
On this page

A blended workforce is employees plus contingent workers. Workday does not publish one agent that serves both populations the same way. It publishes one control plane, Agent System of Record (ASOR), and then separate agents with separate limits.

ASOR is included in the core Workday subscription. Workday says you do not buy an extra SKU to use it. It is where you find, register, configure, monitor, and manage agents, and where you audit them. The agent types in that hub are:

  • Workday-built
  • Custom, built by you in Workday Extend
  • External, also called self-built, built on a platform outside Workday
  • Partner, built by a certified Workday partner
  • Sana user agents, built by you in Sana

Employees and contingent programs show up in different rows.

What an employee can use that a contingent worker cannot

Self-Service Agent retrieves and acts on common employee and manager interactions: personal information, time off, organizational goals, team learning status, and policy articles stored in Workday. Workday’s limitations list says it does not support contingent workers. It also does not support additional jobs, implementer and proxy accounts, or delegated actions. A delegate can see an action look successful in chat and still create nothing. When the person says they are acting for someone else, the agent says the action cannot be performed.

So the chat bubble that appears when Self-Service Agent is on is an employee and manager channel. Pointing contingent workers at it is not a configuration Workday documents as supported.

Case Agent is for Workday Help case owners and solvers: suggest a case type, assign some new cases, summarize the conversation. That is an HR operations agent. It is not documented as a contingent-worker self-service channel.

Where contingent work actually is

Contingent Sourcing Agent is the VNDLY agent in the Workday-built catalog. It grades applicants and surfaces prior candidates from the VNDLY talent pool. Setup requires a Workday tenant and a VNDLY tenant. You register it in Agent Management Hub, then enable Candidate Grading and Recommendations in VNDLY Company Settings, then grant VNDLY permissions. Vendors do not get the agent in their VNDLY UI.

That is the blended pattern Workday actually published:

Population Agent Workday documents Where it runs Registry
PopulationEmployees and managers Agent Workday documentsSelf-Service Agent Where it runsWorkday Chat, and Sana when Sana is enabled and at least one skill is on RegistryASOR
PopulationHR case owners and solvers Agent Workday documentsCase Agent Where it runsWorkday Help RegistryASOR
PopulationClient, MSP, and program team on contingent jobs Agent Workday documentsContingent Sourcing Agent Where it runsVNDLY RegistryASOR, plus VNDLY permissions
PopulationVendor users Agent Workday documentsNone of the agent UI Where it runsEmail of a recommendation, if you send one RegistryNot a VNDLY agent login

Registering the VNDLY agent in the Workday hub does not give a contingent worker a Self-Service Agent conversation. It gives program staff grades and recommendations.

What ASOR unifies, and what it leaves split

Unified:

  • One Agent Management Hub lifecycle: register, configure skills and Available To, activate, deactivate, archive.
  • Production registration requires UMSA opt-in.
  • Delegate skills need a security group. Ambient skills do not, because they run without a person in the loop, on a schedule or other initiation. Case assignment is set up as an ambient skill with an integration system user.
  • After Configure Agent, Workday creates an Agent System User. You can see those accounts on All AI Agent Accounts and All Workday Accounts.
  • Interaction security and tool security are separate. The user must be in a group on the skill and in a group allowed to call the API or the tool fails. View Security for Agent Skill shows the policies.
  • Active Agents is reported for all agents. Session counts and unique users in the hub reports Workday lists are only for Workday-built agents.

Not unified:

  • VNDLY still has its own permission strings (applicant_grade.read, job.recommendation.read, and the rest). A Workday security group does not replace them.
  • Self-Service Agent’s contingent-worker exclusion is a product limit, not an ASOR toggle.
  • Input and output detail reports Workday lists for compliance are only for Workday-built agents. A custom or partner agent does not automatically appear in those same reports.
  • Sandbox refresh does not delete prior weeks of usage activity. That is useful for audit, and it also means a refresh is not a privacy wipe of agent history.

How to brief HR and procurement together

  1. List the worker types you intend to cover: employee, manager, contingent worker, vendor, MSP.
  2. Map each type to a documented agent. If the cell is empty, say so. Do not fill it with Self-Service Agent for contingent workers.
  3. For contingent hiring, plan the dual setup: Workday registration and VNDLY Company Settings, including the initial period of up to 48 hours before grades appear.
  4. For employee chat, plan Self-Service Agent skills (ESS, MSS, base retrieval, advanced actions) and accept the proxy and delegation gaps.
  5. Keep one ASOR owner who can deactivate an agent without waiting for a VNDLY-only admin, and one VNDLY admin who can turn grading off on a job after publish. Turning a job toggle off keeps existing grades visible and stops new ones.

Frequently asked questions

Is ASOR the system of record for contingent workers?

No. Contingent workers remain VNDLY and Workday worker records. ASOR is the system of record for the agents, their skills, who may invoke them, and Workday-built usage.

Can a partner agent close the contingent self-service gap?

Workday allows partner and external agents in the same hub. It does not say a partner agent inherits Self-Service Agent’s employee tools or overrides the contingent-worker exclusion. A partner agent still needs its own registration, skills, and tool security.

Do we pay a separate ASOR fee for VNDLY agents?

Workday says ASOR itself is in the core subscription. Agent registration in Production still follows UMSA and the Flex Credits policy described on the agent setup pages. Those commercial gates are separate from the “no extra ASOR SKU” sentence.

Sources checked

About Workday Agents, About Self-Service Agent, Set Up Contingent Sourcing Agent, and the Workday-Built Agents reference, fetched 2026-11-16.

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.

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.

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