What changed with Workday Learning, powered by Sana?

The system-of-record responsibilities

Workday's administrator documentation says assignments, enrolments and learning records remain in Workday Learning. Reporting and learning management continue to depend on that administrative foundation.

These functions describe who receives learning and what the organisation retains about participation and completion. They are different from how an author creates a lesson or how a learner interacts with its material, even when the experiences are presented as one product.

What Sana adds to the experience

The official proposition describes AI authoring, tutoring, search and personalised learning. Sana supports authoring and the in-lesson experience, while Workday people and skills data provide wider context.

The change therefore reaches both content operations and the learner's encounter with knowledge. A course can be produced or experienced differently while still needing to fit the organisation's assignment, record and reporting model.

Why the boundary matters during transition

A familiar learning record does not mean the authoring and support process is unchanged. Equally, a new learner-facing experience does not mean all administrative history and controls have moved into a new system.

The cited sources establish the combined proposition and a documented responsibility split. General availability is a product statement; entitlement, tenant enablement and migration remain customer-specific. This introductory brief explains those components, while the separate stack-assessment article asks whether the combination can replace particular adjacent tools.

This explanation draws on What changed with Workday Learning, powered by Sana? — Workday evidence, What changed with Workday Learning, powered by Sana? — Workday evidence, Workday Learning remains the system of record in the integrated Sana model, Workday and Sana responsibilities are split across administration, authoring and learner experience, Workday L&D reports three years of Sana Learn use before integrated rollout. The evidence limits and publication history remain below.

What changed

The Workday learning proposition now explicitly combines the existing Workday learning foundation with Sana's AI-native learning experience and authoring capabilities.

Why it matters

A richer learner and authoring experience can alter content operations, support models, governance and the boundary between human capital management data and learning interactions. Migration should therefore be evaluated as an operating-model change as well as a product change.

Use cases & proof

Where this holds up in practice

These examples show how a specific claim is supported by documentation or an implementation. Read their limits before applying them to your own environment.

Proof pattern · Evidence C

Workday Learning remains the system of record while Sana changes authoring and learner experience

Scenario

An organisation adopts Workday Learning, powered by Sana either as a new Workday Learning deployment or by adding the Sana capability to an existing Workday Learning estate.

Architecture pattern

Workday Learning system of record, catalog, assignments, enrollments, reporting and permissions → integrated Sana provisioning → Sana Create authoring and Sana in-lesson learner experience → status and completion updates retained in Workday Learning.

Observed / documented outcome

Workday administrator documentation defines a split operating model between Workday Learning and Sana. Workday also reports that its own L&D team used Sana Learn for three years across a global workforce before planning the integrated Workday Learning, powered by Sana rollout.

What this proves

Workday Learning, powered by Sana is not simply a front-end replacement. Workday Learning remains the system of record for core learning administration while Sana changes authoring and in-lesson experience, creating real security, provisioning, content-lifecycle and operating-model decisions for adopters.

What it does not prove

It does not prove that migration is low effort, that every Workday tenant is entitled or ready to enable the capability, that Workday’s internal Sana Learn outcomes will transfer to other organisations, or that Workday’s internal team had completed production deployment of the fully integrated offering when its case was published.

Apply with these constraints

Confirm subscription entitlement, tenant activation, Workday/Sana tenant linkage, security domains, provisioning, creator roles, content migration and reuse expectations, reporting continuity, regulated or sovereign environment constraints, accessibility, audit requirements and measurable rollout outcomes.

Proof sourcesOfficial ArchitectureWorkday: Workday Learning remains the system of record in the integrated Sana model Official Content LifecycleWorkday: Workday and Sana responsibilities are split across administration, authoring and learner experience Named Internal Use CaseWorkday: Workday L&D reports three years of Sana Learn use before integrated rollout

Last checked 18 Sept 2026 · Reviewed before publication.

Implementation implications

Prerequisites

Confirm commercial availability and entitlement, migration path, tenant prerequisites, data residency, AI controls, existing content dependencies, reporting continuity and the operating ownership of generated content.

Architecture implications

Model human capital management people and skills data, learning administration, AI authoring, learner tutoring, compliance evidence and external content as related but distinct architecture concerns.

Risks

Treating a new front-end experience as a low-risk upgrade; assuming vendor-reported productivity outcomes will transfer unchanged; weakening review controls for generated content; or overlooking historic reporting and compliance evidence.

Testing implications

Run controlled migration and regression tests across assignments, completions, historic learning records, reporting, content rendering, authoring, AI tutor responses, accessibility, permissions and audit trails.

Source register