> ## 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.

# Workflows overview

> How a job req's workflow defines the path every candidate follows, from application to hire.

> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission. Without it, the job req's **Setup** tab doesn't appear.

[Workflows](https://www.youtube.com/embed/Os08Ov-9t88)

A workflow is the hiring process for one job req. It's made of **steps**, each step contains **activities**, and **automation rules** act on candidates as they move through. Every candidate who applies to the job req follows its workflow.

To see a job req's workflow, open the job req and go to **Setup**, then **Workflow**. The page shows the whole process as a flow, from **START** at the top to **HIRED** and **REJECTED** at the bottom.

![The Workflow page under a job req's Setup tab: the Workflow Version header with the Latest pill, its published date and Review Changes, the Create New Version button, and the flow from START through the Screening, Interview and Offer steps with their activities, an automation on the Screening step, and the selected activity's details on the right](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/overview/gen-workflow-page.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=c3c22a027e93216fe7eff93daebaffc5)

## What's on the Workflow page

* **Workflow Version:** which version of the workflow you're looking at. The label under it shows its state, for example **Latest** with the date it was published. Click the version name to look at other versions. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).
* **Steps,** in the order candidates move through them. Each step shows who completes its activities and roughly how many minutes they take in total.
* **Activities** inside each step, with their type, who completes them, how many questions they have and their estimated minutes. Click one to see its details in the panel on the right.
* **Automation rules,** shown as purple bars with a lightning bolt, next to the start, step, activity or outcome they act on.
* **Create New Version** (or **Edit Draft** when there's a draft): opens the editor, where you add, remove and rearrange steps and activities. See [Build a workflow](https://help.journeyfront.com/workflows/build.md).

Each activity row also has three icons:

| Icon | What it does |
| - | - |
| Eye (**Preview Activity**) | Shows the activity the way a candidate sees it. |
| Lightning bolt (**Add Automation**) | Adds an automation rule that runs when candidates complete this activity. |
| Bell (**Notify Users**) | Chooses who gets an email each time a candidate completes this activity. |

![An Assessments step on the Workflow page with Typing Test and Behavioral Assessment activities; the eye, lightning bolt and bell icons on the Typing Test row are highlighted, with the Notify Users tooltip on the bell](https://mintcdn.com/journeyfront/Ki8OScNKQAoeTHdj/images/workflows/overview/gen-activity-icons.png?fit=max\&auto=format\&n=Ki8OScNKQAoeTHdj\&q=85\&s=1ec8095a86c2d594c32f0e3cd289dc45)

## Steps

Steps are the stages a candidate moves through, in order. A typical high-volume workflow looks like this:

**1. Application**

The candidate applies and fills in the application form.

**2. Screening**

Screening questions and assessments check for fit.

**3. Interview**

The candidate books an interview and meets your team.

**4. Offer**

The candidate receives and signs an offer.

**5. Onboarding**

The new hire completes onboarding forms before their start date.

Every new job req starts with a starter workflow you can change: **Pre-screen**, **Recruiter Interview**, **Hiring Manager Interview**, **Offer** and **Onboarding**. See [Create a job req](https://help.journeyfront.com/job-reqs/create.md).

Candidates work on the activities in their current step. Your team, or an automation rule, moves them to the next step. (This is the job req's **Gate Steps** setting, which is on by default.)

> [!TIP]
>
> Keep candidate-facing steps few and clearly named. Candidates see step names on their progress page, and a short, predictable path keeps more of them moving.

## Activities

Activities are what happens inside a step. Common activities include screening questions, assessments, typing and skills tests, interviews, offers, onboarding forms and background checks. Most activities produce a score. See [Activities you can add](https://help.journeyfront.com/workflows/activities.md).

> [!TIP]
>
> Put your quickest, most decisive activities early. Short screening questions before a longer assessment means candidates who aren't a fit find out fast, and the ones who are don't spend time on steps they don't need.

## Automation

Each workflow can have automation rules that act on candidates for you: moving them to the next step, sending a message, or assigning a recruiter when something happens. Automation is what lets a small team keep up with thousands of applicants. See [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md).

## Versions

You change a workflow in a **draft**, and candidates only see the change once you **publish** it. You can publish right away or schedule an exact date and time. Candidates already in progress stay on the version they started with. Every published change becomes a new version, so you can always look back at what candidates followed before. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).

## FAQ

> [accordion] Can different job reqs have different workflows?
>
> Yes. Every job req has its own workflow, so a customer care role and a technical support role can screen candidates differently.

> [accordion] What happens to candidates already in the workflow if I change it?
>
> Nothing, until you publish. After that, new candidates follow the new version, and candidates already in progress stay on the version they started with, keeping their scores, interviews and offers. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).

> [accordion] Why can't I edit the workflow?
>
> Seeing and editing it needs the *Manage Job Req Settings* permission. Ask your Journeyfront admin to check your security role.

> [accordion] Why does the button's name change?
>
> The button names what the editor will open. It reads **Edit Draft** when the job req has a draft, **Edit Scheduled Version** when a version is scheduled to go live, and **Create New Version** otherwise, which starts a new draft from a copy of the live version.

## Related

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

> [card] [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md)
>
> Drafts, versions and when changes reach candidates.

> [card] [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md)
>
> Move, message and route candidates automatically.

> [card] [How scoring works](https://help.journeyfront.com/scoring/how-scoring-works.md)
>
> What the scores from each activity mean.


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