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

# Job reqs overview

> What a job req is and how it connects workflows, hiring classes and candidates.

> [!NOTE]
>
> **Who can do this:** Users with the *All Job Req Access* permission see every job req. Everyone else sees the job reqs they're on the hiring team for. The **Setup** tab needs the *Manage Job Req Settings* permission.

A **job req** is a role you're hiring for, not a single opening. A customer care role you fill all year is one job req, even if you hire hundreds of people into it. Each job req holds the workflow candidates follow, the people who work on it, the application form, the job postings that bring candidates in, and every candidate who applies.

Because one job req can stay open for as long as you hire into the role, the people you hire are grouped into [hiring classes](https://help.journeyfront.com/hiring-classes/overview.md), usually one per start date.

> [!TIP]
>
> Hiring the same role again next month? Add a hiring class to the job req you already have instead of creating a new job req. Your workflow, postings, dashboards and candidate history stay in one place.

## Open a job req

Click **Job Reqs** in the top navigation and click a job req's name. It opens on the **Candidates** tab. See [The Job Reqs page](https://help.journeyfront.com/job-reqs/job-reqs-page.md) for finding job reqs in a long list.

The header shows the job req's name and, below it, the external job title, created date, location, employment type and [status](https://help.journeyfront.com/job-reqs/statuses.md). The **Actions** menu on the right holds everything you do to the job req as a whole: inviting, adding and importing candidates, exporting data, and changing its status.

## The tabs on a job req

![A job req header: the name Customer Care - Day Shift with its external job title, created date, location, employment type and status below, and the Hiring Classes, Dashboard, Candidates, Setup and Activity tabs next to the Actions button](https://mintcdn.com/journeyfront/jgBPyq0oPVTYhwCy/images/job-reqs/overview/gen-job-req-header.png?fit=max\&auto=format\&n=jgBPyq0oPVTYhwCy\&q=85\&s=4e37ddc8c8535e42062b96b29439af5d)

<table>
  <colgroup>
    <col width="134" />

    <col width="611" />
  </colgroup>

  <thead>
    <tr>
      <th>Tab</th>
      <th>What it's for</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>**Hiring Classes**</td>
      <td>The groups of hires for this job req, each with its own openings and start date. See [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md).</td>
    </tr>

    <tr>
      <td>**Dashboard**</td>
      <td>Reporting for this job req. See [Job req dashboards](https://help.journeyfront.com/reporting/job-dashboards.md).</td>
    </tr>

    <tr>
      <td>**Candidates**</td>
      <td>Everyone who has applied, where they are in the workflow and their scores. See [The Candidates page](https://help.journeyfront.com/candidates/candidates-page.md).</td>
    </tr>

    <tr>
      <td>**Setup**</td>
      <td>How the job req is built. Only shown to users with the *Manage Job Req Settings* permission.</td>
    </tr>

    <tr>
      <td>**Activity**</td>
      <td>A history of changes to the job req's setup.</td>
    </tr>
  </tbody>
</table>

## Setup

The **Setup** tab has a menu down the left side:

* **Details:** the job req's name, external job title, job profile, description, location, employment type and custom fields. See [Create a job req](https://help.journeyfront.com/job-reqs/create.md).
* **Application Form:** the fields candidates fill in when they apply. See [Application form](https://help.journeyfront.com/job-reqs/application-form.md).
* **Attributes:** the traits and skills this job req measures. See [Attributes](https://help.journeyfront.com/scoring/attributes.md).
* **Workflow:** the steps, activities and automation rules candidates move through, and its versions. See [Workflows overview](https://help.journeyfront.com/workflows/overview.md).
* **Team:** who works on the job req. See [Hiring team](https://help.journeyfront.com/job-reqs/hiring-team.md).
* **Predictive Models:** see [Predictive models](https://help.journeyfront.com/scoring/predictive-models.md).
* **Job Postings:** where the job is advertised. See [Job postings](https://help.journeyfront.com/sourcing/job-postings.md).
* **Configurations:** candidate assignment, interview reminders, referral portal visibility, the candidate experience, and scoring and reporting options. See [Job settings](https://help.journeyfront.com/job-reqs/job-settings.md).

Some accounts also see **Lead Ads**, **AI Resume Scoring** or **AI Agents** here, when those features are turned on.

On **Lead Ads**, admins link lead forms from Facebook and Instagram lead ads to the job req, so every form submission becomes a candidate here.

> [card] [Lead ads](https://help.journeyfront.com/sourcing/lead-ads.md#link-a-form-from-the-job-req)
>
> Link lead forms to this job req, map their questions and choose whether candidates get an invitation email.

## Job req name and external job title

Every job req has two names:

* **Job Req Name** is for your team. Make it as specific as you need, for example "US Customer Care - Tampa - Client A", so it's easy to tell apart in lists and filters.
* **External Job Title** is what candidates see, for example "Customer Service Agent". It's used on the candidate's application, in candidate emails and text messages, and on referral portals.

## Activity tab

The **Activity** tab is an audit trail of changes to the job req, newest first. It records:

* The job req being created, or duplicated (with the job req it was copied from)
* Status changes, for example from Active to Closed
* Workflow publishes
* Steps added, deleted or reordered
* Activities added, removed or reordered
* Screening and interview questions added or removed, and screening questions reordered
* Changes to attributes and attribute groups

Each entry shows what changed, who made the change, and the date and time. Reorder entries list the previous order and the updated order. Use **Search activities** at the top to find an entry by keyword or by the person who made it.

![A job req's Activity tab with the Search activities box and entries such as Workflow Published, Activity Order Updated with the previous and updated order, Activity Added and Job Req Status Updated, each showing who made the change and when](https://mintcdn.com/journeyfront/jgBPyq0oPVTYhwCy/images/job-reqs/overview/gen-activity-tab.png?fit=max\&auto=format\&n=jgBPyq0oPVTYhwCy\&q=85\&s=bae318849ae65f1aead0cfeb2f6a3f3b)

> [!TIP]
>
> When a job req suddenly behaves differently, for example candidates stop moving to the next step, check the **Activity** tab first. It shows who changed the workflow and when.

## FAQ

> [accordion] Why can't I find a job req?
>
> You only see job reqs you're on the hiring team for, unless your security role has the *All Job Req Access* permission. Ask someone on the job req's hiring team, or your Journeyfront admin, to add you. Archived job reqs are also hidden from the Job Reqs page until you filter by status.

> [accordion] Why don't I see the Setup tab?
>
> The **Setup** tab needs the *Manage Job Req Settings* permission. Ask your Journeyfront admin to check your security role.

> [accordion] Does the Activity tab show what candidates did?
>
> No. It records changes to the job req itself. Each candidate's history is on their Candidate Application, in the **Comments & Activities** tab.

> [accordion] Can candidates see the Job Req Name?
>
> No. Candidates see the **External Job Title**. The Job Req Name is only shown to your team.

> [accordion] Should I create a new job req for each hiring wave?
>
> Usually not. Keep one job req for the role and add a hiring class for each start date. Create a separate job req when the role itself is different, for example a different workflow, location or client.

## Related

> [card] [Create a job req](https://help.journeyfront.com/job-reqs/create.md)
>
> Set up a new job req and get it ready for candidates.

> [card] [Job req statuses](https://help.journeyfront.com/job-reqs/statuses.md)
>
> Deactivate, close, archive, duplicate or delete a job req.

> [card] [Workflows overview](https://help.journeyfront.com/workflows/overview.md)
>
> The steps and activities every candidate follows.

> [card] [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md)
>
> Fill wave after wave of hires from one job req.


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