Governance Switches
The 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.
Draft brief for authors. Replace with the final text; keep the structure.
Page type: Reference · Audience: Administrator, Security officer
Contains: the "confirmation token required" mode (a write without a confirmation becomes a dry run that reports the facts and the token; the apps are never held back); named-user tables and agents without a person; origins for browser-based clients; how to cut an integration off (delete the key); what every assistant action leaves in Application Logs.
Related information: safe-use-with-assistants, service-broker-credentials.
Source in the product repository: .claude/rules/mcp-server.md (D97), docs/joule-integration.md.
Last updated: