Capability

Secure Execution

Each workflow run is isolated from every other run — one run's failure, retry, or bad input can't leak into or block a different run, even if they share the same connectors and credentials underneath.

Session controls apply the same role-based limits to a live user session as to an automated run: a user who can't approve a refund in the UI can't trigger one through a workflow either. Every action — human or automated — is checked against the same permission model and lands in the same audit log.

For the full access-control and audit-log picture, see Security. For approval rules and policy guardrails, see Governance.