Web toolWeb toolA hosted utility you use at a URL, rather than run or install. May be free or paid; source_available says whether anything behind it is inspectable.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
Joule Work
SAP’s workspace where people express a goal, work with the results in contextual Spaces and direct Joule Assistants and Joule Agents across SAP and third-party systems.
Joule Work lets people express a goal, work with the resulting information in Spaces and direct Joule Assistants and Joule Agents across SAP and third-party systems. Its Develop entry opens Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrella, and SAP describes web, desktop and mobile experiences. Access controls and policy enforcement belong to the SAP Business AI Platform behind the workspace. As checked on 15 October 2026, SAP’s Connect 2026 guide says general availability starts in October; the agent reference architectureAgentic AI & AI AgentsSAP's target picture for AI agents: Joule as the engagement layer — Joule Work, Joule Assistants, Joule Agents — with custom agents from customers, partners and SAP teams connecting through A2A for agent-to-agent collaboration and MCP for tool connectivity, on the SAP Business AI Platform. It says up front that parts are not generally available yet, in particular bidirectional communication with third-party agents through the Agent Gateway, so it reads as direction with the building blocks named rather than a design to copy today.published 2026-08-27 still marks some integration capabilities as not generally available.
Where it sits
Lives in
Provides
Agent workspacesBTPAgent workspacesGiving people a workspace to direct agents, retain the context of a task and interact with its results across connected applications. This is the user-facing experience around agents; building their logic belongs to [Agent tooling](capability:agent-tooling), and controlling their calls belongs to [Tool governance](capability:tool-governance).
Part of
SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.
Serves
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Web tool
- Origin
- By SAP
As a web tool
- Access
- does not say
- What it sends to its vendor
- does not say
Connections
Group by
NodeRelationBasis
Functional
Agent workspacesAgent workspacesWorkspaces where people direct agents and work with their resultsSAP only
provides
stated
provides Agent workspaces
Combines natural-language conversations, goal-oriented Spaces and an entry point for building custom agents in [Joule Studio](artifact:sap-joule-studio).
“Joule Assistants surface through Joule Work.”“The experience is available across web, desktop and mobile and surfaces through three interfaces: **Conversations** for dialogue-driven intent and task execution, **Spaces** for goal-oriented, persistent workstreams with full context and the **Develop** interface for building and managing agents and automations via Joule Studio.”
Workspaces where people direct agents and work with their results
Lineage
SAP JouleSAP JouleSAP's AI engagement layer across SAP applicationssap official, btp
part of
stated
part of SAP Joule
“SAP's approach centers on **Joule** as the unified AI engagement layer: **Joule Work** is where users express intent and AI orchestrates outcomes across systems”
SAP's AI engagement layer across SAP applications
Download
Learn more
Readings
- Be the First to Understand Joule Work's Agentic ThinkingBe the First to Understand Joule Work's Agentic ThinkingA Devtoberfest 2026 session on the agent harness behind agentic thinking in Joule Work: generic operating-system tools in a gVisor-isolated sandbox instead of hand-wired domain functions, a react loop, a warm pool of sandboxes torn down after each task, tenant-separated skill loading, and placeholder tokens the agent never sees swapped for real credentials at the egress path. A skill is a folder with a SKILL.md carrying metadata and instructions, and where it reaches a system, an SAP connectivity JSON that declares each connector by ORD ID with its guardrails — GET allowed by default, POST, PUT, PATCH and DELETE requiring human approval, everything else blocked. The demo uploads a cost-centre skill through the skills view, then has agentic thinking delegate over A2A through Agent Gateway to a custom agent built in Joule Studio, whose MCP tools read cost centres from an S/4HANA Cloud system, and ends by turning the result into a PDF; the Joule Studio trace is what shows the tool call actually happened.SAP Developers, published 2026-10-15SAP Developers, YouTube — SAP Developers playlists
- 🟣 AI Eating Brains! How I Fed Mine to Joule Work Desktop🟣 AI Eating Brains! How I Fed Mine to Joule Work DesktopDevtoberfest 2026 session AI-22. Mathias Kemeter connects his Obsidian note vault to Joule Work Desktop with VaultGate, a local HTTP MCP server he wrote in his spare time because the desktop's sandbox accepts HTTP MCP servers and not stdio ones, and because he wanted the vault reached through Obsidian's own command line rather than by direct file access. The demo builds a Space of management tasks from notes and mailbox together, has the assistant pick up a conventions file in the vault without being told where the reporting rules are, finds a conflict the notes never name by semantic search over local embeddings, and appends a task to a sprint note behind a write confirmation, which is where the edges to Joule Work and Agent workspaces hold. The second half is about the guardrails he had AI choose for the project it then had to live inside: tests and coverage, type safety, static checks, dependency and secret scanning, blocking on commit, on push and in CI.published 2026-10-01Mathias Kemeter, YouTube — SAP Developers playlists
- 🔴 Your Agent Wants to Call SAP. Now What?🔴 Your Agent Wants to Call SAP. Now What?Devtoberfest 2026 session INT-23, on what belongs between an agent and an SAP system. A solution advisor and an enterprise architect point Joule Desktop extensions at MCP servers built on API Management inside SAP Integration Suite, and ask it for business partners, orders and line items from an S/4HANA demo system; asked for the ten largest customers it answers from a sample of 200 orders rather than reading the whole table. They then open the API proxy behind it, where a spike arrest policy caps the backend at ten calls per second and the MCP server is configured to expose only the GET resources of the business-partner API so that an agent cannot create one, which is where the edges to Serve your application over MCP and Rate limiting hold. For totals across all sales orders they send the agent to SAP Business Data Cloud instead of the transactional system, since it aggregates and is read-only, and back through Integration Suite for writes such as journal entries.SAP Developers, published 2026-09-30SAP Developers, YouTube — SAP Developers playlists
1 more
- Supercharge Joule Desktop: Connect Any SAP API in Minutes with MCP GatewaySupercharge Joule Desktop: Connect Any SAP API in Minutes with MCP GatewayDevtoberfest 2026 session INT-13, in which an SAP solution advisor connects a live S/4HANA system to the desktop experience of Joule Work through the MCP gateway in SAP Integration Suite. One OpenAPI specification covering business partners, sales orders, material stock, billing and purchase requisitions is uploaded as an MCP server artifact, deployed to integration cell with XSUAA inbound authentication, and registered as an MCP connector; the destination behind it is then switched from basic authentication to principal propagation, and the Cloud Connector monitor shows the same question arriving as the presenter's own user. That demonstration is the serve your application over MCP edge, and the second half is Joule Work itself: a Markdown skill that fixes the steps and format of a customer briefing, and a Space the skill rebuilds with each run.SAP Developers, published 2026-09-23SAP Developers, YouTube — SAP Developers playlists
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainumbrella, ai-and-agents
History in the atlas
- RA0029 describes the workspace across SAP and non-SAP systems: "Users express a goal and Joule orchestrates actions across SAP and non-SAP systems to get it done." Its customer-managed BTP agents connect to Joule, establishing the BTP served view; no separate BTP catalogue listing for Work was established.
- web-tool; umbrella retained
- First seen.
For your agent
- Ref
artifact:sap-joule-work- JSON
- /artifacts/sap-joule-work.json
- MCP
- Connecting an agent