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

# Hiring classes overview

> Group candidates into cohorts so one job req can fill seat after seat.

> [!NOTE]
>
> **Who can do this:** Anyone on the job req can see its hiring classes. Seeing classes across every job req needs the *All Hiring Class Access* permission.

High-volume teams hire for the same role again and again: a new class of agents every few weeks. In many systems, each wave means a new requisition. In Journeyfront, you keep **one job req** and organize each wave as a **hiring class**.

A hiring class has a name, a number of openings, a start date and, optionally, the offer package its hires receive.

## Why hiring classes matter

* **One job req, many waves.** Your posting, workflow and assessments stay in one place.
* **Clear start dates.** Candidates and recruiters always know which cohort someone belongs to.
* **Progress at a glance.** See how many openings each class has filled.
* **Better reporting.** Compare classes side by side to see which waves filled fastest and retained best.

## Where to find them

* **On a job req:** open the **Hiring Classes** tab to see that job req's classes.
* **Across your company:** select **Classes** in the top navigation to see every class you have access to, with openings and percent filled.

![A job req's Hiring Classes tab, with summary tiles above a list of classes showing each class's status, start and due dates, days left, hires, openings and percent filled](https://mintcdn.com/journeyfront/jgBPyq0oPVTYhwCy/images/hiring-classes/overview/gen-hiring-classes-tab.png?fit=max\&auto=format\&n=jgBPyq0oPVTYhwCy\&q=85\&s=b3467cca7334379ad718b46b8e82435a)

> [!TIP]
>
> Name classes with the role and start month, such as "Customer Care, March 2027". Consistent names make filtering, bulk actions and reports much easier later.

## FAQ

> [accordion] When should I create a new job req instead of a new class?
>
> Create a new class when you're hiring more people for the same role with the same process. Create a new job req when the role, location or hiring process is meaningfully different.

> [accordion] Can a candidate move to a different class?
>
> Yes. You can change a candidate's hiring class from their Candidate Application or with a bulk action on the Candidates page.

> [accordion] Why can't I see a class on the Classes page?
>
> You see classes for the job reqs you're on. Ask your admin about the *All Hiring Classes* permission if you need to see every class.

## Related

> [card] [Workflows overview](https://help.journeyfront.com/workflows/overview.md)
>
> The path candidates follow on each job req.

> [card] [How the pieces connect](https://help.journeyfront.com/getting-started/how-the-pieces-connect.md)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.


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