AI Assistants and Integrations: Enabling Access
How assistant access works, credentials for server-side agents through the service broker, the setup matrix per client, and the governance switches.
Draft brief for authors. Section page for the administrator; the end-user side is in Working with AI Assistants.
Source in the product repository: docs/joule-integration.md, customer guide §4 "AI agents and integrations" and §6, .claude/rules/api-broker-and-joule.md, .claude/rules/mcp-server.md.
In this section
- How Assistant Access WorksEvery tenant has one endpoint; the subaccount's own XSUAA signs the person in; roles and add-ons apply unchanged; the assistant confirms before it writes.
- Credentials for Server-Side Agents (Service Broker)Register the MDM API service broker once, create an mdm-api instance and a key, and hand the key to SAP Joule Studio or a script; delete the key to cut the integration off.
- Client Setup MatrixOne row per assistant: what the user enters, what the administrator must have prepared, and whether it acts as the person or as a client.
- Governance SwitchesThe confirmation-token mode the provider can switch on for your tenant, named-user tables and agents, browser-based clients, and how to cut an integration off.
Last updated: