Joule is working. Are you sure?

If every Joule test was run by a global administrator, the UAT sign-off should not say:

“Joule is working.”

It should say:

“Joule worked for one identity.”

For supported SAP SuccessFactors use cases, Joule follows the same configurations and permissions as the web.

Once configured on the web, a supported use case becomes available in Joule automatically. It cannot be enabled in one channel and disabled in the other.

Agents add another control layer.

The Performance Preparation Agent, for example, requires its own AI Access permission.

It is designed for managers with direct reports, and SAP states that it follows the data-access configurations of the underlying modules, including permissions and target populations.

That changes how I run UAT.

Test every critical prompt with the real:

👉 Employee

👉 Manager

👉 HR partner

👉 Local administrator

For each prompt, compare:

✔️ Web authorization

✔️ Agent permission

✔️ Target population

✔️ Expected Joule result

✔️ Actual Joule result

Your permission design is now your AI design.

A global administrator can prove that Joule runs.

Only the real personas can prove that Joule is ready.