Setting Up Approval Policies

Require approval for workflows before they can be published.

Overview

The Require Workflow Approval setting is a workspace-level toggle that flags workflow changes for review. It is a workspace-wide control, not a per-workflow setting, so once it is on it applies to every workflow in the workspace.

For approvals on individual steps inside a running workflow (the more common pattern - "pause and get sign-off before issuing this refund"), use a Human node inside the workflow itself. See Using Human Approval Nodes.

Before You Start

  • You need the Owner or Admin role to change the workspace setting.

Steps

  1. Open Settings -> General.
  2. Toggle Require Workflow Approval on.
  3. Click Save. The setting applies to subsequent workflow changes in this workspace.

Tips

  • Use the workspace setting on shared production workspaces, and keep a separate sandbox workspace without it for fast iteration.
  • Pair this workspace-level gate with per-step Human nodes inside each high-risk workflow for the strongest review story.
  • If the goal is "every refund over $500 needs sign-off", build that as a Human node inside a refund Subworkflow rather than relying on the workspace toggle.

Common Pitfalls

  • Confusing this workspace toggle with per-step Human approvals. The toggle is one boolean; Human nodes are the granular per-workflow mechanism.
  • Toggling without communicating - changes to the workspace setting affect every workflow author, so let the team know before flipping it.

Related Articles

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.