---
name: journeyfront
description: Use when building and managing high-volume hiring workflows,
  configuring job requisitions, setting up automation rules, moving candidates
  through hiring steps, scoring and evaluating candidates, scheduling
  interviews, and analyzing hiring metrics and performance.
metadata:
  mintlify-proj: journeyfront
  version: "1.0"
---

# JourneyFront Skill

## Product summary

JourneyFront is an applicant tracking system (ATS) built for high-volume hiring. It combines job requisitions, workflows, assessments, interview scheduling, offers, and analytics in one platform. Agents use JourneyFront to design hiring processes (workflows), manage candidate pipelines, automate repetitive tasks, and measure hiring effectiveness.

**Key files and locations:**
- Job reqs: Core hiring efforts, each with one workflow
- Workflows: Steps and activities candidates move through (Setup → Workflow)
- Automation rules: Trigger-condition-action rules that move, message, or assign candidates
- Candidates page: Central list for searching, filtering, and bulk actions
- Settings: Company details, users, security roles, custom fields, integrations (gear icon, top right)

**Primary docs:** https://journeyfront.mintlify.app

## When to use

Reach for this skill when:
- **Building hiring processes:** Creating or modifying job reqs, designing workflows with steps and activities, setting up automation rules
- **Managing candidates:** Moving candidates through steps, rejecting, hiring, bulk actions, filtering and exporting
- **Configuring assessments:** Adding screening questions, typing tests, skills tests, language assessments, or behavioral assessments to workflows
- **Scheduling interviews:** Setting up interview activities, connecting calendars, managing availability, booking candidates
- **Setting up automation:** Creating rules that move candidates based on scores, send messages, assign recruiters, or route by location
- **Analyzing hiring:** Reading scores, understanding attribute roll-ups, checking funnel analytics, measuring time-to-hire
- **Account setup:** Configuring company details, users, security roles, custom fields, email templates, job boards, integrations

## Quick reference

### Core concepts

| Term | Definition |
|------|-----------|
| **Job req** | A role you're hiring for (not a single opening). One job req can stay open all year and hire hundreds of people. |
| **Workflow** | The hiring process for one job req: steps, activities, and automation rules. Every candidate on that req follows it. |
| **Step** | A stage in the workflow (e.g., Screening, Interview, Offer). Candidates move through steps in order. |
| **Activity** | What happens inside a step (e.g., screening questions, typing test, interview). Produces a score. |
| **Automation rule** | Trigger → Conditions → Actions. Moves, messages, assigns, or rejects candidates automatically. |
| **Hiring class** | A group of hires with the same start date. One job req can have many classes. |
| **Job profile** | A role as your company measures it (e.g., "Customer Service"). Many job reqs feed one profile. |
| **Candidate Application** | One person's progress through one job req. Same person can have multiple applications. |
| **Candidate Profile** | One person, all their applications across all job reqs. |

### Common workflows

**Create a job req:**
1. Go to Job Reqs → New Job Req
2. Fill Details (name, external title, job profile, location)
3. Set up Application Form (what candidates fill in)
4. Build Workflow (Setup → Workflow → Edit Draft)
5. Add hiring team (Setup → Team)
6. Create job posting (Setup → Job Postings)
7. Publish workflow to activate

**Build a workflow:**
1. Open job req → Setup → Workflow → Create New Version (or Edit Draft)
2. Drag New Step from building blocks; name it
3. Drag activities into steps (screening questions, assessments, interviews, offers)
4. Configure each activity (questions, time limit, instructions)
5. Save Draft, then Publish when ready

**Move candidates through steps:**
1. Open Candidate Application → Click Current Step (top right)
2. Pick target step → Change Candidate Step window opens
3. Handle moving actions (send email, assign onboarding form, create offer)
4. Review & Execute → Move Candidate

**Create an automation rule:**
1. Open job req → Setup → Workflow
2. Click lightning bolt (Add Automation) next to trigger point
3. Set Trigger (e.g., Candidate Completes Activity)
4. Add Conditions (optional, e.g., score ≥ 4)
5. Add Actions (e.g., Change Step, Send Email, Assign User)
6. Enable and Save

**Filter and export candidates:**
1. Go to Candidates page
2. Click Filters → add Job Req, Step, Status, Score, custom fields
3. Click Edit Columns to choose what shows
4. Save as New View for reuse
5. Click Actions → Export Data → CSV or Excel

## Decision guidance

### When to use automation vs. manual moves

| Situation | Use automation | Use manual |
|-----------|---|---|
| Every candidate who scores ≥4 should move to next step | ✓ Automation rule with score condition | |
| You need to review each candidate before moving | | ✓ Manual Change Step |
| Route candidates by location to regional recruiters | ✓ Automation rule with location condition | |
| One-off candidate needs special handling | | ✓ Manual move |
| Reject candidates who don't meet minimum bar | ✓ Automation rule (after testing) | |

### When to create a new job req vs. add a hiring class

| Scenario | New job req | Add hiring class |
|----------|---|---|
| Same role, different start date next month | | ✓ Add class to existing req |
| Same role, different location or language | ✓ Different workflow/team | |
| Completely different role | ✓ New req | |
| Same role, same workflow, same team | | ✓ Add class |

### When to use different workflow versions

| Situation | Action |
|-----------|--------|
| Test new screening questions on future applicants only | Create New Version in editor, publish as scheduled |
| Change workflow mid-hiring without affecting current candidates | Create New Version, publish. Current candidates stay on old version. |
| Revert to previous workflow | Click version name on Workflow page, view old version |

## Workflow

### Typical task: Set up a new job req with automation

1. **Understand the role:** What steps does your hiring process have? What activities (screening, tests, interviews)? Who decides when candidates move?

2. **Create the job req:**
   - Go to Job Reqs → New Job Req
   - Fill in name (internal), external job title, job profile, location
   - Save

3. **Build the workflow:**
   - Open Setup → Workflow → Edit Draft
   - Add steps matching your process (Screening, Interview, Offer, Onboarding)
   - Drag activities into each step
   - Configure each activity (questions, time limits, instructions)
   - Save Draft

4. **Set up automation:**
   - On Workflow page, click lightning bolt next to activities or steps
   - Create rules for common moves (e.g., score ≥4 → advance, score <2 → reject)
   - Test with first few candidates before automating rejections
   - Enable rules and save

5. **Configure the job req:**
   - Setup → Application Form: choose what candidates fill in
   - Setup → Team: add recruiters, hiring managers, interviewers
   - Setup → Configurations: set candidate assignment, interview reminders, re-apply rules
   - Setup → Job Postings: create postings and link to job boards

6. **Publish and activate:**
   - Workflow page → Publish (now or scheduled)
   - Job req header → Actions → Activate (if not auto-activated by publish)

7. **Verify before candidates apply:**
   - Preview each activity (eye icon on Workflow page) on mobile view
   - Check automation rules are correct
   - Test with a test candidate if possible

### Typical task: Move candidates and manage pipeline

1. **Filter candidates:** Candidates page → Filters → add Job Req, Current Step, Status, Score
2. **Save your view:** Set up columns, filters, sort → Save as New View
3. **Open a candidate:** Click name to open side panel; use arrows to navigate
4. **Move to next step:** Click Current Step → pick step → handle moving actions → Move Candidate
5. **Bulk move:** Select multiple candidates → Change Step → pick step → Move Candidates
6. **Reject:** Select candidates → Reject → pick reason → confirm
7. **Hire:** Open candidate → Hire button → set hiring class, job profile, start date → Hire
8. **Export:** Actions → Export Data → choose CSV or Excel

## Common gotchas

- **Automation rules don't trigger other automation rules.** If a rule moves a candidate to a step, a second rule with "Candidate Moved to Step" won't run for that move. Put all actions in one rule.

- **Candidates already in progress stay on their workflow version.** Publishing a new version doesn't affect candidates who started on the old one. Plan to move them manually or with a rule if changes must reach them.

- **Gate Steps is on by default.** Candidates don't move to the next step automatically when they finish an activity; your team or an automation rule must move them. Turn off Gate Steps in Configurations if you want auto-advance.

- **Scoring needs attributes in attribute groups.** A score only appears if the attribute is in an attribute group on the job req's Attributes page. Check Setup → Attributes if a score is missing.

- **Onboarding forms are required to move to that step.** The Change Candidate Step window won't let you proceed without assigning a form. Pick one under Onboarding form.

- **Job req names are internal; external job titles are what candidates see.** Don't confuse them. Candidates see the external title in emails, on their application, and on referral portals.

- **Duplicate job req doesn't copy postings.** If you duplicate a job req, create new postings on the copy. Deactivating a job req turns off all its postings; reactivating doesn't turn them back on.

- **Automation rules belong to a workflow version.** Rules on the Latest version take effect immediately. Rules in a draft take effect when you publish. Check the version name before editing a rule.

- **Candidates on different workflow versions can't be bulk-moved together.** Add the Job Version column to spot mismatches, then move each group separately.

- **Fraud detection and AI features need to be turned on.** Ask your Customer Success Manager to enable AI resume scoring, AI agents, fraud detection, or referrals if they're not available.

## Verification checklist

Before submitting work on a job req or workflow:

- [ ] **Workflow is published** (not in draft) and job req is Active
- [ ] **Automation rules are enabled** and tested with first few candidates
- [ ] **Preview each activity** on mobile view (eye icon on Workflow page)
- [ ] **Hiring team is assigned** (Setup → Team) with correct permissions
- [ ] **Job posting is active** (Setup → Job Postings → Make job posting page active + Post job to job board)
- [ ] **Attributes are in attribute groups** if you're using scoring (Setup → Attributes)
- [ ] **Email templates are set up** for invitations, rejections, and reminders (Settings → Templates)
- [ ] **Onboarding forms are assigned** if the workflow has an Onboarding step
- [ ] **Interview activity has interviewers with connected calendars** (Interviews → My Profile)
- [ ] **Hiring class is created** if you hire in cohorts (Hiring Classes tab)
- [ ] **No low-scoring automation rules are live** until you've tested them (e.g., auto-reject rules)

## Resources

**Comprehensive navigation:** https://journeyfront.mintlify.app/llms.txt

**Critical pages:**
- [How the pieces connect](https://journeyfront.mintlify.app/getting-started/how-the-pieces-connect) — Job reqs, workflows, postings, candidates, hiring classes, and how they relate
- [Workflows overview](https://journeyfront.mintlify.app/workflows/overview) — Steps, activities, automation, and versions
- [Automation rules](https://journeyfront.mintlify.app/workflows/automation-rules) — Triggers, conditions, actions, and common recipes
- [Admin setup checklist](https://journeyfront.mintlify.app/getting-started/admin-setup-checklist) — Everything to configure before hiring starts

---

> For additional documentation and navigation, see: https://journeyfront.mintlify.app/llms.txt