Concept card

Joule Work — SAP's personal AI workspace (web, mobile 3.2, desktop) and its MCP extensibility

As of 2026-10-04

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Joule Work?

Joule Work is the end-user layer of Joule: a web client, a desktop app and a mobile app (3.2, successor of SAP Mobile Start) where Joule Assistants coordinate agents. Mobile is generally available, web and desktop are Early Adopter Care with no GA announcement found as of 4 October 2026, and custom MCP servers connect through OAuth with XSUAA single sign-on.

What Joule Work is, and what it is not

Joule Work is the end-user layer of SAP's Joule family. SAP describes it as a workspace that adapts to the user's intent: people state an outcome, Joule Assistants (organised by function) coordinate Joule Agents, and the result is assembled into conversations and "Spaces" rather than a sequence of application screens (SAP News, Sapphire, May 2026). It reaches users through three clients: a cloud web client, a desktop application that can work with local files and applications, and a mobile app. It is the user-facing component of Joule, not a separate model and not a replacement for the transactional apps underneath.

Status matters more than the marketing arc, so read it surface by surface. The mobile app is generally available; version 3.2.0 is live in the App Store. The web client was positioned at Sapphire as an Early Adopter Care (EAC) offer with general availability targeted for the second half of 2026; this card found no general-availability announcement as of 4 October 2026, so treat the web client as "check the SAP Roadmap Explorer". Joule Work Desktop runs on macOS and Windows, is used inside SAP, and reaches selected customers through EAC; no general-availability date was announced in the sources reviewed. SAP's own materials also describe the agent layer as maturing, and independent commentary says the same.

Why it matters

Joule Work is where SAP's agent strategy meets end users, yet its three clients sit at three different maturity levels: mobile is GA, web and desktop are Early Adopter Care. Promising one client's status for another is the commonest scoping error.
MCP turns Joule Work into an extensible client, and the authentication flow you pick (interactive OAuth with PKCE versus a shared technical client) decides whether user authorisations and audit survive.
Version 3.2 of the mobile app adds cross-device conversation sync and a user-controllable memory toggle, which moves privacy and retention from a roadmap topic to a deployment topic.

Key points

Joule Work = Joule's end-user layer: conversations and Spaces, Joule Assistants coordinating Joule Agents; web, desktop and mobile clients (SAP News, May 2026).
Mobile: generally available; version 3.2.0 adds voice (incl. Apple CarPlay), mobile-web conversation sync, agentic thinking mode, @-mentions, a memory toggle; iOS 26+.
Web client: Early Adopter Care at Sapphire with GA targeted for H2 2026; no GA announcement found as of 4 October 2026.
Joule Work Desktop (macOS, Windows): used inside SAP, selected customers via Early Adopter Care; no GA date announced in the sources reviewed.
The mobile app is the renamed SAP Mobile Start (same core functions); Joule relies on the SAP Build Work Zone navigation service for application jumps and role-based access.
Custom MCP servers: interactive login uses Authorization Code + PKCE with a loopback callback registered in XSUAA; technical access uses client credentials from a service key.
MCP spec baseline: 401 + WWW-Authenticate, protected-resource metadata (RFC 9728), resource parameter (RFC 8707), audience validation, no token passthrough.

Terms used on this page

Joule Work: SAP's end-user workspace layer of Joule, delivered as web, desktop and mobile clients.
Joule Assistant: Function-oriented AI teammate that understands context and directs Joule Agents.
Space: Dynamic work area assembled around a goal, viewable without reopening the originating conversation.
Early Adopter Care (EAC): SAP programme giving selected customers pre-GA access with programme-specific prerequisites; features may change before GA.
XSUAA: SAP Authorization and Trust Management service issuing OAuth 2.0 tokens on SAP Business AI Platform (formerly SAP BTP).
PKCE: Proof Key for Code Exchange: verifier/challenge pair that stops interception of an OAuth authorization code.
Protected resource metadata: RFC 9728 document by which an MCP server names its authorization servers.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →