Workday Sana
Workday Sana Testing: What to Test Before You Switch It On
Introduction
Your employees may soon ask for time off, expense help or an approval from inside Claude, Teams or Slack, and Workday will answer.
That is why Workday Sana testing deserves a plan before launch. Workday announced on 13 October 2026 that Sana will work inside the AI tools staff already use. If a role, approval or policy is wrong, the error now appears in a chat window, not on a familiar Workday screen.
This post explains what Sana is, how it connects to Claude, Microsoft Copilot, Teams, Slack and Gemini Enterprise, and what to check first. You will get a checklist for roles, approvals and user acceptance testing that you can adapt to your own tenant.
Key takeaways
Sana now reaches staff through Claude, Gemini Enterprise, Microsoft Copilot, Teams and Slack, so one Workday setup serves several channels.
Availability differs by channel. Some are generally available and others are in early access, so confirm yours first.
Start with Workday security roles testing: a chat answer must never show more than Workday would.
Add Workday approval workflow testing for routing, delegation and the audit trail.
Finish with Workday user acceptance testing by persona and by channel.
Why Workday Sana testing matters now
What Workday announced
On 13 October 2026, Workday said Sana will work inside Claude, Google Cloud’s Gemini Enterprise, Microsoft Copilot, Microsoft Teams and Slack. According to Workday’s newsroom announcement, self-service with Sana is generally available in Gemini Enterprise, Microsoft Copilot, Teams and Slack, and Sana in Claude Cowork is in early access. A Microsoft Copilot extension is expected in early access in late 2026.
What stays the same
Workday says one connection carries each company’s permissions, policies and approvals. That is a design promise, not a test result. Your security groups, business processes and policy text still decide what each person can do.
Why the next few weeks matter
Early access features are arriving before year end, so pilot decisions are being made now. Every new channel is another place where a wrong role or a broken approval can reach an employee. Plan Workday release testing too, because each update can change the roles and processes Sana relies on.
Example: a Teams and Slack pilot
Illustrative, not a real customer.
A mid-sized company wants staff to ask Sana about time off and expense reports in Teams and Slack. The HR systems lead builds a short test plan before the pilot. She picks five personas: employee, manager, HR partner, finance approver and contractor. For each one she writes the questions they might ask and the answer Workday should give.
The team runs the plan in a sandbox first. They find that a delegated approver can see an expense report the original approver’s role would hide. They fix the role setup, rerun the test and keep the evidence for audit. Only then does the pilot start.
Pre-launch checklist
Test area | What to check | Pass looks like |
|---|---|---|
Security roles | Ask each persona for data they should and should not see | Answers match Workday screens and role limits |
Approvals | Submit, approve, reject, delegate and reassign a request | Routing, status and audit trail are correct |
Policy answers | Ask about leave and expense rules | Replies match current policy, not old text |
Integrations | Run Workday integration testing on downstream payroll or finance feeds after an action | Data arrives once, with correct values |
Channel parity | Repeat key cases in each channel | Same result in Teams, Slack, Claude and the rest |
Failure handling | Try expired sessions and missing permissions | Clear message and no partial transaction |
How PeopleFlow helps
A new front door needs the same locks as the old one. PeopleFlow offers no-code Workday testing with 1000+ pre-built tests for HCM, Payroll, Finance and Integrations, so your team can check the processes Sana will trigger without writing scripts. Our Workday AI agents cover Configuration, Report, Support, Testing and Integration; see the AI agents page. PeopleFlow is a Workday Innovation Silver Partner.
Frequently asked questions
What is Workday Sana?
Workday describes Sana as its engine for agentic experiences and orchestration. In practice, employees ask for help with HR and finance tasks in a chat interface, and Sana works with Workday data under your company’s permissions, policies and approvals. Your own tenant setup still decides what each person can see and do.
Which tools can Sana work inside?
Workday’s 13 October 2026 announcement names Claude, Google Cloud’s Gemini Enterprise, Microsoft Copilot, Microsoft Teams and Slack. Self-service is generally available in Gemini Enterprise, Copilot, Teams and Slack, while Sana in Claude Cowork is in early access. Confirm what is enabled for your own tenant before you plan.
How do I test Sana before go-live?
Start with security roles, then approvals, then user acceptance testing with real personas. Write the expected answer for each question, run it in a sandbox, and keep screenshots as evidence. Repeat the core cases after every configuration change so a small edit does not quietly break a chat journey.
Do I need to test each channel separately?
Yes, at least at smoke-test level. Workday says one connection carries your permissions, but each channel has its own sign-in, interface and behaviour. A practical split is a short smoke test in every channel and full acceptance testing in the channel most employees will use first.
Conclusion
Sana puts Workday inside the chat tools your people already use, which makes Workday Sana testing a launch task, not an afterthought. Check roles first, then approvals, then run acceptance tests in each channel and keep the evidence. Revisit the plan as early access features reach your tenant. To speed up those checks, try PeopleFlow yourself or book a short demo.
