Publish changes and manage flow versions

Saving, publishing, enabling a public registration link and inviting a client are distinct operations. Check the intended outcome before choosing the final control.

Review the draft

Confirm the audience, steps, required fields, design, authored language, email actions and any connected providers. For an active flow, inspect the pending changes against the currently published version.

Choose who receives the new version

Versioned flows can publish for new onboardings only or promote changes to eligible existing onboardings. The current eligibility check decides which existing records can move. Review blocked records rather than assuming completed signatures or payment steps can simply be replaced.

Confirm publication

Complete the offered publication review, then check the active/published state. A saved draft remains unsuitable for normal client invitations. The published version fixes flow-owned content, while workspace email templates and provider settings can still follow current workspace configuration.

Recover safely

If a later edit is wrong, preserve the existing response history and reconcile the intended correction before publishing again. A completed versioned submission can have a supported restart path that preserves its original history; it is different from editing answers on the original version. Do not restart a client's work just to test a design change.