Immutable configuration
Publishing records a versioned snapshot and checksum. Environments identify their active version, and routing changes also update a routing revision. Historical versions preserve the configuration that was published.
Publication is not delivery
A successful publication creates a delivery request. Check requested and delivered versions and any error before claiming an integration is updated. The MCP exposes configuration-history and delivery-status tools for the same checks.
Credential lifecycle
Server credentials are environment scoped and shown privately when created. Revoke unused or compromised credentials from the Integration section. AI tools can list credential metadata and revoke a confirmed credential with separate administration permission; they do not return secret values.