> ## Documentation Index
> Fetch the complete documentation index at: https://help.journeyfront.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is the Journeyfront Help Center for hiring teams. Journeyfront is an applicant tracking system (ATS). Use the Help Center's terms: job req, Candidate Profile (the person), Candidate Application (one person on one job req), hiring class. Link to the article you used in your answer.

# Publish workflow changes

> Save workflow changes as a draft, review them and publish a new version, now or at a time you choose, and know what happens to candidates already in progress.

> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission.

Changes to a job req's workflow don't reach candidates the moment you make them. You make them in a draft, check what's different, and publish the draft as a new version, either right away or at a date and time you choose. Candidates already in progress stay on the version they started with.

## How versions work

Every published change to a job req's workflow is a **version** with its own name. The job req has one live version, marked **Latest**, that new candidates follow. You change the workflow by editing a draft, and the draft becomes the new Latest version when you publish it.

On the Workflow page (**Setup**, then **Workflow**), the version name at the top is a menu. Click it to look at any version:

![The version menu open under Workflow Version on the Workflow page, listing Workflow 3.0 as Draft, Workflow 2.0 as Latest and Workflow 1.0 as Inactive, with the Edit Draft button at the top right](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/publish/gen-version-menu.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=3661e8f406d7a17b0db1d646caa09d86)

| Label | What it means |
| - | - |
| **Latest** | The live version. The date beside it shows when it was published. |
| **Draft** | Changes you've saved but not published. The date beside it shows when it was last saved. |
| **Scheduled** | A version set to go live later, shown with when it goes live, for example "Goes live Tue, Nov 17, 2026 at 9:00 AM MST". |
| **Inactive** | An earlier version. Candidates who started on it may still be on it. |

A job req has one draft or scheduled version at a time. When it has one, the Workflow page opens on it.

**Review Changes**, under the version name, lists everything that's different from the version before the one you're looking at, step by step. The number on the button is how many changes there are.

![The Review Changes window with the columns Where, What Changed, Workflow 2.0 (Latest) and Workflow 3.0 (This Draft), listing a time change and an instructions change on the Screening Questions activity and an activity renamed in the Interview step](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/publish/gen-review-changes.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=1a5db5825d42c876d823f6535386f62b)

## Make and publish changes

**1. Open the editor**

On the Workflow page, click **Create New Version** to start from a copy of the Latest version. If there's already a draft, the button reads **Edit Draft** (or **Edit Scheduled Version** for a scheduled one) and opens that version instead.

![The Workflow page showing the Draft Workflow 3.0 with its last saved time and Review Changes, and the Edit Draft button at the top right highlighted](https://mintcdn.com/journeyfront/MP6XVW1Unu3e4opR/images/workflows/publish/workflow-edit-draft.png?fit=max\&auto=format\&n=MP6XVW1Unu3e4opR\&q=85\&s=244783b06d1bd80516339f677b0f898a)

**2. Make your changes**

Add, remove and rearrange steps, activities and automation rules. See [Build a workflow](https://help.journeyfront.com/workflows/build.md). Nothing changes for candidates while you work.

**3. Name the version**

The version's name is the title at the top of the editor. A new version is named for you from the last one, so **Workflow 2.0** is followed by **Workflow 3.0**. To rename it, click the title and type, like "Added typing test, Oct 2026". Each version on the job req needs a different name.

**4. Save the draft**

Click **Save Draft** as often as you like. Journeyfront saves the draft and you stay in the editor.

**5. Review your changes**

Click **Review Changes** to compare your draft with the Latest version.

**6. Publish**

Click **Publish**. If you have unsaved changes, Journeyfront saves them first. In the **Publish Workflow** window, choose when the version goes live (below), then click **Publish Now** or **Schedule Publish**.

![The Publish Workflow window with Schedule selected, a Go live date of 11/17/2026 at 9:00 AM, the note that times are in your time zone, a summary that the version goes live Tue, Nov 17, 2026 at 9:00 AM MST, the note that candidates who apply after it goes live follow it, and the Cancel and Schedule Publish buttons](https://mintcdn.com/journeyfront/vQCJ8-ZVzF3DfqCc/images/workflows/publish/publish-window.png?fit=max\&auto=format\&n=vQCJ8-ZVzF3DfqCc\&q=85\&s=f36dc9aab462494b8d68ce8e963425c7)

If saving fails, for example because another version already uses the name, the **Publish Workflow** window doesn't open. Fix the problem and click **Publish** again.

To leave without publishing, click **Exit**. If you have unsaved changes, Journeyfront asks whether to **Save Draft** or **Discard** them. To throw a draft away entirely, click **Delete Draft** in the editor; this can't be undone.

### Choose when it goes live

* **Publish now:** the version goes live right away.
* **Schedule:** pick a **Go live** date and time, in half-hour steps. Times are in your own time zone, which the window names, and a summary underneath shows exactly when it goes live, for example "Goes live Tue, Nov 17, 2026 at 9:00 AM MST". The time has to be in the future. The version shows as **Scheduled** until then.

To change when a scheduled version goes live, click **Edit Scheduled Version** on the Workflow page, then **Edit Publishing Details**. The new time replaces the old one. To cancel a scheduled version, open it the same way and click **Delete Draft**; it won't go live.

When the version goes live, the version it replaces becomes **Inactive**. If the job req is **Inactive**, it becomes **Active**.

### Who follows the new version

A new version is for candidates who apply from the moment it goes live.

* **Candidates already in progress** stay on the version they started with and keep their scores, interviews and offers.
* **Hired, rejected and withdrawn candidates** stay where they are.
* **New candidates** follow the new version.

This is the same whether you publish now or schedule: only candidates who apply after the version goes live follow it. The **Publish Workflow** window says so under the go-live time.

## Candidates on different versions

On the job req's candidate list, the **Job Version** column shows which version each candidate is on. **Change Step**, **Send Offers** and **Compare** work on one version at a time, so they're hidden when your selection mixes candidates from different versions.

Automation rules belong to a version too. Each candidate is checked against the rules of the version they're on.

> [card] [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md)
>
> How rules act on candidates, and which version's rules apply.

## A new job req's first version

A new job req starts with a draft named **Workflow 1.0**, holding its starter workflow, and stays **Inactive**. Change the draft as you need, then publish it. Publishing the first version makes the job req **Active**, so candidates can apply. See [Create a job req](https://help.journeyfront.com/job-reqs/create.md).

## FAQ

> [accordion] Why is the Publish button greyed out?
>
> Publish needs something to publish: changes in the editor or a saved draft. The version also needs a name that isn't used by another version on the job req. An empty title turns its underline red, and a name that's already used shows a note under it.

> [accordion] Can I have more than one draft?
>
> A job req has one draft or scheduled version at a time. When you open the editor, it picks up where that version left off.

> [accordion] Can I go back to an earlier version?
>
> You can view earlier versions from the version menu on the Workflow page. To go back to an earlier process, make the same changes in a new draft and publish it.

> [accordion] Do candidates see anything when a new version goes live?
>
> No. Candidates already in progress stay on their version, so nothing changes for them, and nothing is sent to anyone when you publish. Candidates who apply after the version goes live see its steps and activities.

> [accordion] Can I change automation rules without publishing?
>
> Yes, on the Workflow page itself. Changes you make to rules there save straight to the version you're viewing, so on the Latest version they're live right away. Changes made in the editor (**Create New Version** or **Edit Draft**) are part of your draft and take effect when you publish.

> [accordion] Can I move candidates who are already in progress to the new version?
>
> Not yet. Candidates already in progress stay on the version they started with, so their interviews and offers are never affected by a publish.

> [accordion] What time zone is the go-live time in?
>
> Yours. The **Publish Workflow** window names your time zone, and the version goes live at that moment everywhere. A teammate in another time zone sees the same moment in their own time.

## Related

> [card] [Build a workflow](https://help.journeyfront.com/workflows/build.md)
>
> Add steps and activities.

> [card] [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md)
>
> Rules that act on candidates for you.

> [card] [Workflows overview](https://help.journeyfront.com/workflows/overview.md)
>
> How steps, activities and automation fit together.

> [card] [How scoring works](https://help.journeyfront.com/scoring/how-scoring-works.md)
>
> What rescoring means for a candidate.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.