---
title: "Sana agents vs Workday Chat — Kiweely"
description: "Sana Enterprise can build custom agents. The desktop Workday Chat is Self-Service Agent. Workday does not publish a product named desktop copilot for that chat."
url: https://kiweely.com/blog/sana-custom-agent-vs-desktop-workday-copilot
---

# Sana custom agents vs the desktop Workday chat

People say desktop Workday copilot and mean Workday Chat. Workday’s admin guide calls that experience Workday Chat and Workday Assistant, backed by Self-Service Agent. Custom agents in natural language are a Sana Enterprise agent-builder feature, and a separate ASOR type called Sana user agents.

-   By Kiweely
-   November 16
-   5 min read

“Desktop Workday copilot” is not a name on the admin pages fetched for this article. The desktop experience Workday documents is **Workday Chat**, and before that **Workday Assistant**. The agent behind the employee chat is **Self-Service Agent**. Custom agents you describe in natural language are **Sana Enterprise** agent builder. Sana user agents are their own type in Agent System of Record.

A 2025 Workday press release used “Business Process Copilot Agent” for a different announced agent. Do not paste that label onto the chat bubble.

## Three experiences people mix up

|  | Workday Chat on the desktop tenant | Sana Core | Sana Enterprise |
| --- | --- | --- | --- |
| What it is | In-tenant chat. Activating Self-Service Agent with at least one skill shows the Workday Chat bubble and hides the Workday Assistant bubble. | Conversational agentic AI for HCM and Financials, in Workday and in the Sana Workspace | Sana Core plus third-party connectors and orchestrations |
| Custom agents | Not the agent builder | No agent builder | Yes. Describe the agent in natural language. Trigger manually, on a schedule, or from third-party events. |
| Workday reads and writes | Self-Service Agent skills | Same, through Self-Service Agent | Same, through Self-Service Agent |
| Custom MCP connectors | No | No | Yes, OAuth, for internal or long-tail systems |
| Third-party connectors | No | No | Yes, with admin controls on who can use them |
| Human confirmation | Self-Service Agent has its own skill security | Yes, for actions that need human approval. Cross-system actions are logged. | Same |
| Where users subscribe to admin-built agents | Not described | No | Yes, and only for agents that run on a schedule |
| Meeting notes | Not part of Self-Service Agent | No | Meeting Agent for Google Meet, Microsoft Teams, and Zoom |

Sana’s marketing page says Sana orchestrates Workday agents and routes actions through ASOR. Orchestration is not a substitute for activating Self-Service Agent. Workday’s Self-Service page says Sana returns Self-Service Agent answers only when that agent is active, at least one skill is on, and the person has Sana access.

## What Self-Service Agent will do on the desktop

It retrieves and summarizes self-service data and takes common actions: update personal information, request time off, manage organizational goals, view team learning status, and view policy articles stored in Workday. Chat replies can include tables and buttons.

Skill names carry the audience: ESS for employees, MSS for managers, Advanced for complex actions, Base for retrieval. You may put any security group on **Available To**, and the user still cannot run a tool without the underlying API domains. MSS payroll tools do not start working for a non-manager just because the group was added.

It does not support contingent workers, additional jobs, implementer or proxy accounts, delegated actions, hiding or requiring fields with **Configure Optional Fields**, reading document attachments on help articles, or seeing My Tasks. Delegated actions can look successful in the chat and create no event. Article extraction tests belong in an implementation tenant; Workday says Sandbox is the wrong place for that case. Responses vary week to week because the agent is non-deterministic.

If you turn on Payroll Agent and not Self-Service Agent, you can see both the Workday Assistant bubble and the Workday Chat bubble. One bubble is not “the copilot.”

## What “build a custom agent in Sana” means

Only Sana Enterprise. An administrator can publish agents to the organization, push updates to subscribers, and block subscribe until requirements are met. Users browse those agents in the Sana Workspace and can subscribe only to scheduled ones. Each created agent has its own page for history and configuration. Sana Inbox holds completed outputs and pending approvals.

Sana Core includes the workspace (file upload, LLM chat, web only), Workday read/write through Self-Service Agent, citations, Workday SSO, security mirroring, code-backed charts, rich chat elements, search-as-you-type to people, reports, and tasks, and conversational search with deep links. It does not include the agent builder.

Commercial gates on the Sana concept page:

-   UMSA for everyone using this functionality.
-   Complimentary Flex Credits toward Sana Core, then the Flex Credits and Platform Entitlement Policy once they are used up.
-   Sana Core also requires the Core HCM or Core Financials SKU.
-   Sana Enterprise requires that Flex Credits policy and the Sana Enterprise SKU.
-   MSA customers opt in to UMSA and enable the feature through Innovation Services. Keep data contribution on if you want full agent behavior under UMSA.

Setup notifications go to security administrators (**Set Up AI Admin Security Permissions**), ASOR administrators (configure and activate Self-Service Agent), Sana administrators (workspace defaults), and user-provisioning administrators. Users open Sana with **Ask Sana** in Workday global navigation, or land on the Sana home page and click **Workday** to return.

Extend custom agents remain a different type in ASOR. Building in Extend is not the Sana agent builder.

## Kiweely is a third desktop, for a different job

[Kiweely Vine](https://kiweely.com/) is the desktop AI agent for Workday consultants and developers, live today, for Extend apps, Studio integrations, and tenant changes. It is not Workday Chat and it is not Sana. [Kiweely Nest](https://kiweely.com/) is coming next: an in-house AI HRIS team for tickets, projects, and routines. [Kiweely Bridge](https://kiweely.com/bridge) is coming next and connects Claude, ChatGPT, and Gemini to a standard tenant as the signed-in employee. None of those replace Self-Service Agent inside Workday Chat, and none of them are the Sana Enterprise agent builder.

## Frequently asked questions

### If we buy Sana Core, did we buy custom agents?

No. Agent builder, published agent library, custom MCP connectors, and third-party connectors are Sana Enterprise on the comparison table.

### Can Sana do something Self-Service Agent cannot, inside Workday HCM?

Sana Core’s Workday read and write path is Self-Service Agent. Limits on that agent still apply, including contingent workers and delegation. Sana Enterprise can also act in connected third-party systems, which Self-Service Agent does not claim to do.

### Which chat should help-desk staff test?

Test Workday Chat in the tenant with a real employee and a real manager, not a proxy. Test Sana only after provisioning and after Self-Service Agent is active. Test a custom Sana agent only on Enterprise, and only the trigger you configured: manual, schedule, or a third-party event.

## Sources checked

Sana Workspace, Set Up Sana for Workday, About Self-Service Agent, About Workday Agents, and the Workday AI Agents marketing page, fetched 2026-11-16.

## Read next

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

-   [November 16 ### Workday Agent Gateway, MCP, and A2A](https://kiweely.com/blog/workday-agent-gateway-mcp-a2a-explained)
-   [November 16 ### Case Agent and HR service delivery](https://kiweely.com/blog/workday-case-agent-hr-service-delivery)
-   [November 16 ### Blended workforce and the agent system of record](https://kiweely.com/blog/workday-blended-workforce-asor)

### More guides on Custom agents and Workday AI

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

-   [Workday Implementation Phases: Workday’s Own Stages, and What Stays Manual vs What an AI Agent Does](https://kiweely.com/guides/workday-implementation-phases)
-   [Deployment Agent Users domain and View Security for Agent Skill](https://kiweely.com/guides/workday-deployment-agent-users-domain-security)
-   [Deployment Agent prompt patterns: in my tenant and CRAFT](https://kiweely.com/guides/workday-deployment-agent-prompt-patterns)
-   [Deployment Agent Configuration Catalog Support for Implementers](https://kiweely.com/guides/deployment-agent-configuration-catalog)
-   [Workday Custom Agent First POC Checklist for Implementers](https://kiweely.com/guides/workday-custom-agent-first-poc-checklist)
-   [Workday Developer Agent and Agent-Ready Tools for Implementers](https://kiweely.com/guides/workday-developer-agent-and-agent-ready-tools)
-   [Workday First-Party Agent Tenant Prerequisites for Implementers](https://kiweely.com/guides/workday-first-party-agent-tenant-prerequisites)
-   [Deployment Agent in Customer Central vs Implementation tenants](https://kiweely.com/guides/workday-deployment-agent-customer-central-vs-implementation-tenant)

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