SAP Business AI: Joule Work, Assistants, Agents and Studio

In 30 seconds

What it is Five layers, one request: how Joule Work, assistants, agents and Studio fit.

You use it when You need one picture of SAP Business AI before you read about any single product or agent.

Next in this section Joule capability watch →

Five layers, one request: people ask in Joule Work, assistants coordinate, agents act, guardrails check, systems hold the truth.

40-second version of this explainer, no sound.

Part 1 of 26 in SAP Business AI, Explained.

SAP Business AI comes with a lot of names, and most of them start with Joule. On projects, the first question I get is usually some version of “so which Joule is which?” This page puts them on one map, then follows a single finance question through every layer.

In a sentence: people ask in Joule Work, assistants and agents do the work, and guardrails keep them to what they’re allowed to touch.

The short version

Joule Work is the front door, the one place where people talk to Joule, its assistants and its agents, according to SAP’s Business AI page.
Joule Assistants coordinate agents around a role. Joule Agents, which SAP builds, carry out multistep processes across SAP and non-SAP systems, and custom agents built in Joule Studio do the same for your own processes.
Underneath sit grounding and guardrails: the SAP Knowledge Graph for business context, an enterprise agent gateway for identity and policy, and the SAP AI Agent Hub for inventory and governance.

Think of a hospital

You explain your problem at the front desk (Joule Work). A ward coordinator (a Joule Assistant) works out which specialists (Joule Agents) should see you. Each one reads your file first, and a medical board (governance) decides who is licensed to do what.

Joule Studio is a different building. If Joule Work is an airline’s app, Joule Studio is its engineering hangar. Most people only see the app, and a smaller team works in the hangar to keep it flying.

The layers, from the top down

SAP’s product pages describe roughly these layers.

People. Anyone from a CFO to a shared-services clerk asks a question or starts a task in plain language.
Joule Work. That happens here. SAP says it’s powered by the SAP Knowledge Graph, an enterprise agent gateway and agentic thinking orchestration that plans multistep work. An SAP Community recap of SAP TechEd Berlin 2026 describes two ways of working inside it: Conversations and Spaces.
Joule Assistants. SAP’s Joule Agents and Assistants page describes them as coordinating agents for a role, such as finance or procurement.
Joule Agents and custom agents. Agents do the specialist work across SAP and non-SAP systems. SAP ships prebuilt Joule Agents, which it says use the Model Context Protocol (MCP) and the Agent2Agent (A2A) protocol. Teams build custom agents in Joule Studio, which SAP places inside the SAP Business AI Platform. SAP also describes building n8n workflows there, but SAP sources differ on when that is available, so check the Joule capability watch.
Grounding and guardrails, then systems. The SAP Knowledge Graph supplies business context, the agent gateway checks identity, access and policy at runtime, and the SAP AI Agent Hub keeps the inventory. SAP News (22 September 2026) says it covers agents, large language models and MCP servers, mapped to capabilities and owners. Below all of that sit the systems of record: SAP Cloud ERP, SAP SuccessFactors, SAP Ariba and non-SAP tools.

One credit hold at NextSAP, layer by layer

NextSAP Utilities is the fictional Dubai utility used across this site’s SAP content. It serves about 5 million customers across electricity, water, gas and district cooling, has a shared services team in India, and runs SAP S/4HANA with SAP Utilities (IS-U) and Contract Accounts Receivable and Payable (FI-CA), plus SAP SuccessFactors and SAP Ariba. The company is invented, and the flow below mirrors how SAP describes its own agents.

On a Monday morning the commercial accounts manager calls Layla, the CFO. Marina Bay Café LLC, a commercial customer that pays by bank transfer, can’t get a new premises connected because its contract account (the account its electricity and water bills are charged to) is on credit hold. Layla opens Joule Work and types: “Why is Marina Bay Café LLC on credit hold and what should we do?”

Step	Layer	What happens	Time
1	Joule Work	Layla’s question arrives under her own identity. Agentic thinking splits it into sub-tasks: find the exposure, explain the cause, propose an action.	Seconds
2	Joule Assistant	A finance assistant picks the agents that fit: the collections prioritiser and the payment clarification agent.	Seconds
3	Grounding	The SAP Knowledge Graph links the customer to its contracts, open items and payments.	Seconds
4	Agent gateway	Each agent’s call to SAP Cloud ERP gets checked. Is Layla allowed to see this customer, and is this agent allowed to read these items?	Seconds
5	Agents	The collections prioritiser finds exposure of AED 2,140,000 (UAE dirhams) against a credit limit of AED 2,000,000 across 37 open items. The payment clarification agent finds one incoming payment of AED 180,000, received nine days ago, still sitting on clarification account 1190100 because the reference was missing.	About 2 minutes
6	Proposal back to Layla	Joule Work answers that an unapplied payment caused the hold. Applying it brings exposure to AED 1,960,000, under the limit. It proposes the clearing and a hold release, and routes both for approval.	About 4 minutes in total
7	Human approval	Omar, the finance controller, checks the remittance advice and approves the clearing. The credit hold lifts through the normal process.	10 minutes

Before agents, that question cost an accounts receivable analyst about two hours of pulling exposure, scanning open items, searching the bank statement and emailing the customer. Now the analyst checks one well-prepared proposal.

Notice what the agents didn’t do. Neither released the hold on its own. Both finance agents sit at L2 Propose on this series’ autonomy ladder, so they prepare and a person decides. Post 02 explains why.

SAP shows similar patterns with real customers. Its Joule Agents page features Bosch with a classification agent and Uniper with a custom procurement agent built in Joule Studio, and the SAP Business AI page lists stories from PostNL, Timken and Bosch Digital. I read these as SAP-published examples rather than independent benchmarks.

Where should a new idea start?

You want to…	Start with	Why
Ask a question or start a task	Joule Work	It’s the front door for people. Agents built elsewhere are used here.
Cover a whole role, like finance close	A Joule Assistant	Assistants coordinate several agents for one role.
Automate a standard SAP process	A prebuilt Joule Agent	SAP builds and maintains it. You configure and govern it.
Automate your own process or data	A custom agent in Joule Studio	Low-code or pro-code, with your data and system landscape as context.
Know which agents exist and who owns them	SAP AI Agent Hub	One register of agents and owners.
Check who an agent acts as, every time	The agent gateway	Identity, access and policy at runtime.

What stays with you

You get one place to ask, agents that prepare multistep work across systems, grounded answers and a register of agents with owners. Some things stay with you:

It doesn’t decide your autonomy levels. You do.
It doesn’t replace clean master data. Agents read whatever is there.
Not every announced feature is available today. Check the current status in the capability watch linked above.
Every agent still needs an owner.

Explain it to your CFO

People ask in one place, and digital helpers do the legwork across our systems and bring back a proposal.
Each helper works under a named person’s permissions, has an owner, and does only as much as we allow before a person signs off.

Three calls to make early

Which layer owns a new idea? My default is to try Joule Work and prebuilt Joule Agents first, and go to Joule Studio only when a prebuilt agent can’t cover the process.
Who owns each agent? The process owner. IT owns the platform.
How far may each agent go? Start every new money-touching agent at L2 Propose and use the climb rule in post 02 to move it up. Whatever the agent, name the layer before you name the product.

Go deeper

Technical detail for architects and developers

SAP’s Joule Agents page says prebuilt agents use MCP and A2A. The MCP specification describes a host, client and server model using JSON-based remote calls, where servers expose tools, resources and prompts. Its security section is blunt: tools amount to arbitrary code execution, tool descriptions should be treated as untrusted unless the server is trusted, and the protocol itself can’t enforce these principles. The A2A specification describes agents discovering each other through an Agent Card and collaborating without sharing internal memory, tools or reasoning. So MCP is how an agent plugs into a tool, and A2A is how one agent hands work to another.

SAP describes the enterprise agent gateway as handling identity, access and policy at runtime and governing agent communications, tool use and human oversight. The member recap of SAP TechEd Berlin 2026 adds that third-party agents can invoke Joule Agents through this governed gateway. Design for principal propagation, so the agent acts as Layla and not as a technical super-user (post 21 goes into this).

SAP News (22 September 2026) describes SAP AI Agent Hub inventorying agents, large language models and MCP servers, mapped to capabilities and owners. It also mentions a new AI Governance Assistant, announced to add EU AI Act and NIST compliance intelligence with automated risk classification; check availability before you plan around it. An SAP Community post on the agent mesh describes agents placed against business capabilities in SAP LeanIX, each exposing an A2A endpoint and connecting tools through MCP.

SAP says Joule Studio builds agents and n8n workflows from a prompt, low-code or pro-code, and supports LangChain and LlamaIndex. SAP sources differ on when the n8n part is available, so treat it as something to confirm in the capability watch. Apps in Joule Studio are marked “coming soon” on SAP’s product page.

Map of this series

The 26 posts, grouped by area.

Joule

Autonomous Enterprise

Agent Design

Open Standards

AI Agent Hub

AI Security

AI Governance

Joule Studio

Words you’ll hear

Joule Work: the single experience where people use Joule, its assistants and its agents.
Joule Assistant: a role-based coordinator that pulls in the right agents for a job, such as finance.
Joule Agent: an SAP agent, prebuilt by SAP; custom agents are built in Joule Studio.
Joule Studio: SAP’s environment for building custom agents and n8n workflows, part of the SAP Business AI Platform. SAP sources differ on when n8n workflows are available.
SAP Knowledge Graph: the business context layer that links customers, contracts, orders and other records so answers are grounded.
Agent gateway: the building security desk for agents, with a badge check, floor access and a visitor log at runtime.
SAP AI Agent Hub: the HR register for digital employees: who they are, their owner, their access and their review.
MCP and A2A: Model Context Protocol works like a universal power socket for tools. The Agent2Agent protocol is a formal handover note between agents.

Keep going

Independent explainer, not affiliated with or endorsed by SAP SE. SAP, Joule and other SAP product names are trademarks of SAP SE.

Frequently asked questions

What is the difference between Joule Work and Joule Studio?

Joule Work is where people use Joule, its assistants and its agents. Joule Studio is where teams build custom agents and n8n workflows, although SAP sources differ on when n8n workflows are available, so check the Joule capability watch. SAP says agents built in Joule Studio are used through conversations in Joule Work.

Is a Joule Assistant the same as a Joule Agent?

No. SAP describes agents as executing multistep processes across SAP and non-SAP systems, and assistants as coordinating agents around a role. An assistant is closer to a coordinator, and an agent does one specific job.

Do I have to build agents to use SAP Business AI?

No. SAP offers prebuilt Joule Agents. Joule Studio is for the gaps, where your process or data needs a custom agent or workflow.

Where are agents governed?

SAP describes the SAP AI Agent Hub as the place that inventories agents, large language models and MCP servers and maps them to capabilities and owners. At runtime, an enterprise agent gateway checks identity, access and policy.

Is everything on this page generally available?

Not necessarily. Some capabilities are announced, in preview or marked coming soon. Check the current status in the Joule capability watch on this site before you plan around a feature.