Edit your workflow without disrupting the team

Improve a workflow in a private Draft while everyone keeps running the stable Published version. Publish the Draft when it's ready — and keep a full version history you can restore at any time. Runs are always created from the published workflow.

Available on the Enterprise plan. See pricing · About Enterprise

Vendor Onboarding — Versions
Add security review step Draft
Q3 process update Published Jul 14, 2026 Published
Initial version Apr 2, 2026

Stop editing a live workflow mid-run

When a workflow is always changing under people's feet, edits land while teams are partway through a run — and a mistake is instantly everyone's problem. Versioning gives every change a safe place to happen before it goes live.

Editing in place
  • Changes hit active runs the moment you save
  • A half-finished edit confuses people mid-task
  • No clean way to undo or see what changed
With versioning
  • Work in a private Draft; the team runs the Published version
  • Publish once, deliberately, when it's ready
  • Full history — restore any earlier version

Draft, test, publish — in three steps

1

Create a Draft

From your workflow, create a Draft and give it a name. Manifestly clones the current Published version into a private copy for you to work on — the live version keeps running untouched.

2

Edit and test privately

Change steps, assignments, reminders, and logic in the Draft. Start test runs against it — they're ephemeral and walled off from your real integrations, so nothing leaks out while you experiment.

3

Publish it

When the Draft is ready, publish it. It becomes the new Published version, the previous one moves into your history, and every new run uses the update from that moment on.

Two lanes: one to run, one to build

At any moment your workflow has one Published version that everyone runs, and — when you want to make changes — one Draft you're building next. New runs always come from the Published version, so work in progress never reaches your team until you decide it's ready.

  • The Published version stays stable while you edit the Draft.
  • Runs already in flight keep their original structure — nothing changes underneath them.
  • One Draft at a time keeps changes deliberate — edit, publish, or discard it before starting the next.
Published version Live
Collect vendor details
Manager approval
Add to payment system
Every new run starts from here
Draft — “Add security review” Private
Collect vendor details
Security & data review new
Manager approval
Add to payment system

Test the Draft without side effects

Runs you start against a Draft are ephemeral — kept separate from your real work. By default their outward-facing integrations are switched off, so a test run can't fire a webhook, ping Slack, send notifications, or kick off another workflow. Walk the new process end to end, then throw the test away.

  • Notifications, reminders, webhooks, Slack, and automations stay off unless you opt in.
  • Ephemeral runs stay out of your standard run lists and reports.
  • Need to test one integration for real? Enable just that feature for the test run.
Test run of Draft Ephemeral
Outward integrations for this run
Notifications
Slack messages
Webhooks
Automations
Off by default — flip on only what you want to test.

A full history, and a way back

Every published version is snapshotted and kept. Open the version dashboard to see what was published and when — and if a change doesn't work out, restore an earlier version to make it the Published one again. New runs pick up the restored version; runs already in progress are left as they are.

  • Each version is stored as a complete snapshot of the workflow.
  • Creating and publishing versions is recorded in the workflow's activity.
  • Restore rolls a past version back to Published in one click.
Version history
Q3 process update Published Jul 14, 2026 Published
Reorder approval steps Published May 30, 2026
Initial version Published Apr 2, 2026

Every workflow, in one of three states

DraftPrivate, being edited PublishedLive — runs come from here PreviousKept in history, restorable

Turn it on where it helps

  • Enable versioning across the whole account, or turn it on for individual departments.
  • Only one Draft exists per workflow at a time — you can't create a Draft of a Draft.
  • Drafts stay private to the people working on them until published.
  • Discard a Draft and the workflow rolls straight back to its current Published version.
Account-wide versioning on
Every department gets Draft and Published versions
Compliance dept
versioning enabled
Field ops dept
versioning enabled

Where teams reach for versioning

Regulated processes

Onboarding, compliance, and audit procedures that must stay stable while they're in use.

Refine the procedure in a Draft, publish deliberately, and keep every prior version on record.

Continuous improvement

Recurring workflows you tweak often as the team finds better ways to work.

Trial a change in a Draft, test it end to end, and restore the old version if it doesn't pan out.

High-volume operations

Workflows with many runs going at once, where an in-place edit would ripple everywhere.

Publish updates on your schedule while runs already in flight finish on the version they started with.

Workflow versioning, answered

Workflow versioning is part of the Manifestly Enterprise plan. See the pricing page or read more about Enterprise. It can be turned on for your whole account or for specific departments.

They keep the structure they started with — nothing changes underneath a run already in flight. Only runs created after you publish use the new version.

No — a workflow has at most one Draft at a time. You edit, publish, or discard that Draft before starting a new one, and you can't create a Draft of a Draft. This keeps changes deliberate and easy to follow.

Yes. Runs started against a Draft are ephemeral: by default their outward integrations — notifications, reminders, webhooks, Slack messages, and automations — are switched off, and they're kept out of your standard run lists. You can opt a specific feature in if you need to test it for real.

Yes. Every published version is snapshotted and kept in the version history. Restore an earlier one to make it the Published version again — new runs use it, while runs already in progress are left unchanged.

Discarding a Draft throws away its changes and returns the workflow to its current Published version. Nothing your team is running is affected.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Workflow Versioning

With Manifestly, your team will Never Miss a Thing.