Security and Governance v2

Apply least-privilege Site and Environment access, keep credentials in Connections, and scope API Keys to the required Workflows and consumers. Use revision history, Release Management, Workflow Logs, relationships, and audit trails as operational evidence.

Workflow execution and placement

Keep the Workflow and all required Connections compatible with the selected Cluster. Protect Local Cluster hosts, certificate trust, service configuration, and outbound connectivity. Cluster availability remains separate from Environment-specific Workflow status.

Published interfaces

Review trigger configuration, Workflow status, Environment hostname, API Key scope, and allowed origins before enabling HTTP or MCP access. Treat App bundles as public client code and keep business logic in authorized Workflows.

Use Workflow Log Redaction for sensitive Properties. For Builder MCP and the assistant, work in a Test Environment, review mutation tools and proposed YAML, and save only tested work.

See also

See Secure Workflow Design, App Security Model, and MCP Server.