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

# Getting started for TA leaders

> Own the hiring process end to end: set a job req up from Details to AI Agents, bring candidates to it, then manage the hiring with classes, dashboards and saved views.

> [!NOTE]
>
> **Who this is for:** Talent acquisition leaders, recruiting managers and program owners: the people who decide how hiring runs, not just who gets hired. Most of this page needs the *Manage Job Req Settings* and *Company Dashboard Access* permissions, and some of it needs *Company Settings Access*. Ask your Journeyfront admin if a page or tab below isn't there.

Hiring in Journeyfront runs in three phases, and they happen in order: you **set up a job req**, you **bring candidates to it**, and then you **manage the hiring** that follows. This page follows that order, so you can read it start to finish the first time you build a role and come back to one section later.

## Your first week

**1. Learn the model**

A job req is a role, not an opening; hiring classes are the waves you fill it with; a workflow is the path candidates follow. Start with [How the pieces fit together](#how-the-pieces-fit-together) below, then see the [Job reqs overview](https://help.journeyfront.com/job-reqs/overview.md).

**2. Audit your job reqs**

Open **Job Reqs** and check what's **Active**, **Inactive**, **Closed** or **Archived**. Close what you're no longer hiring for so your dashboards aren't counting dead reqs. See [Job req statuses](https://help.journeyfront.com/job-reqs/statuses.md).

**3. Read one workflow end to end**

Pick your highest-volume job req, open **Setup**, then **Workflow**, and follow it from **START** to **HIRED**. Note every step a candidate waits on a person. See [Workflows overview](https://help.journeyfront.com/workflows/overview.md).

**4. List the automation you already have**

On the same page, the purple bars with a lightning bolt are your automation rules. Know which ones move, message or assign candidates before you change anything. See [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md).

**5. Set your baseline numbers**

Click **Dashboard** and open **Funnel Analytics** and **Time To Hire**. Write down today's drop-off and time to hire so you can tell whether your changes helped. See [Dashboards overview](https://help.journeyfront.com/reporting/dashboards.md).

**6. Check who can do what**

Review your security roles and who holds them, especially *Manage Job Req Settings*, *Hire Candidates* and *All Job Req Access*. See [Security roles and permissions](https://help.journeyfront.com/account-setup/security-roles.md).

## How the pieces fit together

Job profiles, job reqs, job postings, job boards and referral portals each do one job, and their names are close enough to blur together. The short version: a **job profile** is a role your employees hold, a **job req** is a role you're hiring for, a **job posting** is the public ad for that req, and a **job board** or **referral portal** is where the ad is seen. Every applicant, from every channel, lands back in the same job req.

Click any box below to see what it is, where it lives and what it connects to. For each relationship on its own, with examples and the cardinality spelled out, see [How the pieces connect](https://help.journeyfront.com/getting-started/how-the-pieces-connect.md).

How Journeyfront objects connect

**Where:**

**Connects:**

| Object | What it is | Where it lives | How it connects |
| - | - | - | - |
| Job profile | A role your employees hold, with their performance and tenure. | **Profiles** in the top navigation | Many job reqs link to one profile; hires land in it; predictive models are built on it |
| Job req | The role you're hiring for, holding the workflow, attributes, team and candidates | **Job Reqs** in the top navigation | Links to one job profile; holds its hiring classes, postings and candidates |
| Hiring class | A wave of hires from one job req, usually one per start date | The **Hiring Classes** tab on a job req | Belongs to one job req; hires count toward its openings |
| Job posting | The public ad: title, location, pay and description | **Setup**, then **Job Postings**, on a job req | One req can have many postings; each links to one job board |
| Job board | Your own career site, with its branding and job feed | **Settings**, then **Job Boards** | Hosts the postings linked to it; candidates apply from it |
| External job boards | Indeed, JobTarget and Appcast | **External Job Board Posts** on a job posting | Carries a posting outward; applicants still land in the job req |
| Referral portal | A branded portal where employees refer people and share jobs | **Settings**, then **Referral Portals** | Lists active job reqs set to show on it, under the req's **Setup**, then **Configurations** |
| Candidates | Everyone who applied, with their scores and current step | The **Candidates** page, or a job req's **Candidates** tab | Every channel feeds one job req; source links record which one |

## Phase 1: Set up a Job Reqs

Create the job req in **Job Reqs**, then work down the **Setup** menu from top to bottom. Each page is one decision, and the menu is already in a sensible order: what the role is, what you ask candidates, what you measure, how they move, who does the work, and where the job is advertised.

**1. Details**

The role itself: **Job Req Name** for your team, **External Job Title** for candidates, the **Linked to Job Profile** the hires land in, and the description, location and employment type. See [Create a job req](https://help.journeyfront.com/job-reqs/create.md).

**2. Application Form**

What candidates fill in when they apply, including whether a resume or LinkedIn profile is required. Every field here is a field you can later filter and report on, so ask for what you'll use. See [Application form](https://help.journeyfront.com/job-reqs/application-form.md).

**3. Attributes**

The traits and skills this role is measured on. Do this before the workflow: activities score against these attributes, so settling them first means your screening, assessments and interviews all measure the same things. See [Attributes](https://help.journeyfront.com/scoring/attributes.md).

**4. Workflow**

The steps candidates move through, the activities inside each step, and the automation rules that move them. Every new job req starts with a draft, **Workflow 1.0**, which you reshape to your process. Interview activities are set up here too: the interviewers, the length and what goes on the calendar invite. See [Workflows overview](https://help.journeyfront.com/workflows/overview.md), [Build a workflow](https://help.journeyfront.com/workflows/build.md) and [Set up an interview activity](https://help.journeyfront.com/interviews/interview-activity.md).

**5. Team**

The recruiters, hiring managers and interviewers who work on this job req, and what each of them can do on it. Anyone who interviews also needs their own calendar connected and their hours set, under **Interviews**, then **My Profile** and **My Availability**. See [Hiring team](https://help.journeyfront.com/job-reqs/hiring-team.md) and [Your availability and calendar](https://help.journeyfront.com/interviews/availability.md).

**6. Job Postings**

The public ad: the title candidates search for, the location, the pay and the description. One job req can have many postings, each linked to one job board, and you send a posting out to Indeed, JobTarget or Appcast from the posting itself. See [Job postings](https://help.journeyfront.com/sourcing/job-postings.md).

**7. Configurations**

Five cards of per-req settings: **Candidate Assignment** (who owns each candidate), **Interviews** (including interview reminders), **Referrals** (which portals list this job and what a referral earns), **Candidate Experience** and **Scoring & Reporting**. See [Job settings](https://help.journeyfront.com/job-reqs/job-settings.md).

**8. AI Resume Scoring**

Where it's turned on for your account, score resumes against what the role needs. See [AI resume scoring](https://help.journeyfront.com/scoring/ai-resume-scoring.md).

**9. AI Agents**

Where it's turned on, let an agent handle parts of the candidate conversation inside the workflow. See [AI agents](https://help.journeyfront.com/workflows/ai-agents.md).

**10. Publish and activate**

A new job req starts **Inactive** and can't take applications. Publish the workflow, or use **Actions**, then **Activate**, when the rest is ready. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md) and [Job req statuses](https://help.journeyfront.com/job-reqs/statuses.md).

> [!NOTE]
>
> There's no **Interview Scheduling** page in the **Setup** menu. Scheduling is set in three places instead: the interview activity in the **Workflow** (interviewers, length, calendar invite), **Interview Reminders** on the **Configurations** page, and each interviewer's own calendar and hours under **Interviews**. See [Set up an interview activity](https://help.journeyfront.com/interviews/interview-activity.md) and [Interview reminders](https://help.journeyfront.com/interviews/reminders.md).

> [!TIP]
>
> Write your scoring criteria before your questions. When every attribute says plainly what a weak, average and strong answer sounds like, interviewers score the same candidate the same way, and your **Attributes** and **Interview Questions** dashboards start telling you something real. See [Interview guides](https://help.journeyfront.com/interviews/interview-guides.md).

> [!TIP]
>
> Standardize once, then duplicate. Get one job req right, all the way down the **Setup** menu, and use **Actions**, then **Duplicate Job Req** for the next site, shift or client. Postings aren't copied, so create those on the copy. See [Create a job req](https://help.journeyfront.com/job-reqs/create.md#start-from-an-existing-job-req).

### Workflow and automation in more depth

The workflow is your process, written down and enforced. Changes land in a **draft** and only reach candidates when you **publish**, so you can rework a process without disturbing the people already in it.

| What you need to do | Where | Learn more |
| - | - | - |
| See the whole process as a flow | **Setup**, then **Workflow** | [Workflows overview](https://help.journeyfront.com/workflows/overview.md) |
| Add, remove or reorder steps and activities | **Create New Version** or **Edit Draft** | [Build a workflow](https://help.journeyfront.com/workflows/build.md) |
| Know what you can put in a step | The building blocks list in the editor | [Activities you can add](https://help.journeyfront.com/workflows/activities.md) |
| Move, message, reject or assign candidates automatically | Automation rules on a step or activity | [Automation rules](https://help.journeyfront.com/workflows/automation-rules.md) |
| Decide who owns each candidate | **Setup**, then **Configurations** | [Candidate assignment](https://help.journeyfront.com/workflows/candidate-assignment.md) |
| Ship a change on a date you choose | **Publish**, with a scheduled version | [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md) |
| Let AI handle parts of the conversation | AI agent activities, where turned on | [AI agents](https://help.journeyfront.com/workflows/ai-agents.md) |

> [!WARNING]
>
> Candidates already in progress stay on the workflow version they started with. If you need a change to reach people mid-process, plan to move them yourself, or with an automation rule, rather than assuming the new version catches them.

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

## Phase 2: Bring candidates in

With the job req live, the job is getting the right people to it and recording where each one came from. Tag every channel as you go: the source is what later tells you which spending was worth it.

| What you need to do | Where | Learn more |
| - | - | - |
| Send people straight into the application | **Actions**, then **Invite Candidates**, choosing a **Source** before you copy the link | [Invite candidates](https://help.journeyfront.com/sourcing/invite-candidates.md) |
| Advertise the job publicly | **Setup**, then **Job Postings**, on your job boards | [Job postings](https://help.journeyfront.com/sourcing/job-postings.md), [Job boards](https://help.journeyfront.com/sourcing/job-boards.md) |
| Reach the big external boards | **External Job Board Posts** on a posting | [External job boards](https://help.journeyfront.com/sourcing/external-job-boards.md) |
| Tag every place you share the job | **Generate Source Link** on a job board or posting | [Magic links](https://help.journeyfront.com/sourcing/magic-links.md) |
| Keep your source list clean | **Settings**, then **Sources**, each with a **Source Type** | [Sources](https://help.journeyfront.com/sourcing/sources.md) |
| Get your employees referring | Referral portals, and the **Referrals** card on **Configurations** | [Referrals overview](https://help.journeyfront.com/referrals/overview.md), [Rewards on job reqs](https://help.journeyfront.com/referrals/job-req-rewards.md) |
| Load a list from an event or agency | **Actions**, then **Import Candidates**, with a `source` column | [Import candidates](https://help.journeyfront.com/sourcing/import-candidates.md) |
| Re-engage people already in your database | Saved views and bulk actions on the **Candidates** page | [Bulk actions](https://help.journeyfront.com/candidates/bulk-actions.md) |

> [!TIP]
>
> Make a separate source link for every placement, not every channel. "Facebook" tells you little; "Facebook - Tampa Night Shift - Nov" tells you which creative and which market to repeat. Hand this part to your sourcing team with [Getting started for sourcing teams](https://help.journeyfront.com/getting-started/sourcing-team.md).

## Phase 3: Manage the hiring

Setup is done and candidates are arriving. From here your job is filling the classes, watching the funnel and keeping work from sitting still.

### Hiring classes

A hiring class is a wave of hires from one job req, usually one per start date, with its own openings. A job req can have as many classes as you need, which is how one req fills wave after wave without ever being recreated.

| What you need to do | Where | Learn more |
| - | - | - |
| Set up the next wave and its openings | The **Hiring Classes** tab on a job req | [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md), [Create a class](https://help.journeyfront.com/hiring-classes/create.md) |
| Act on everyone starting on the same day | Open the class and work from it | [Working with a hiring class](https://help.journeyfront.com/hiring-classes/working-with-a-class.md) |
| Put a candidate in a class before hiring | **Assign Class**, or the **Hiring Class** field on the **Details** tab | [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md) |

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

### Dashboards

Company dashboards cover every job req; a job req's own **Dashboard** tab covers one.

| Your question | Dashboard |
| - | - |
| Are we getting enough applicants, and where do they stand? | **Candidate Overview** |
| Where are we losing candidates, and how long do steps take? | **Funnel Analytics** |
| How long does it take us to hire, by req and location? | **Time To Hire** |
| Which channels are worth the budget? | **Source Effectiveness** |
| Is the team actually following the process? | **Hiring Process Fidelity** |
| How is each recruiter doing? | **Recruiter Productivity** |
| Are our hiring classes on track? | **Hiring Classes** |
| Do our hires stay, and do they perform? | **Turnover**, **Performance** |
| Does what we measure predict who succeeds? | **Attributes**, **Interview Questions**, **Interviewers** |
| What does our applicant pool look like demographically? | **EEOC Dashboard**, when turned on. See [EEOC reporting](https://help.journeyfront.com/reporting/eeoc.md). |

See [Dashboards overview](https://help.journeyfront.com/reporting/dashboards.md) for what each one holds, how to filter it and how to save your filters as bookmarks, and [Job req dashboards](https://help.journeyfront.com/reporting/job-dashboards.md) for one req at a time.

> [!TIP]
>
> Save a bookmark for the filters you check every week, and make it the default on that dashboard. Then your Monday number is the same number every Monday.

> [!NOTE]
>
> The **Turnover**, **Performance**, **Attributes**, **Interview Questions** and **Interviewers** dashboards only show something once your employee data is in Journeyfront: start dates, separations and performance reviews. Getting that feed in place is what turns hiring reporting into outcome reporting. See [Turnover and performance](https://help.journeyfront.com/reporting/turnover-and-performance.md).

> [!TIP]
>
> Review the funnel and the process together. When **Funnel Analytics** shows a step bleeding candidates, open that step in the workflow before you change the ad spend: a long assessment, a slow hand-off or a missing reminder explains more drop-off than the source usually does.

### Saved views

A saved view is a set of filters on the **Candidates** or **Job Reqs** page that you can come back to, make your default and share with your team. Views are how a leader turns "keep an eye on things" into something checkable in a minute.

| View worth saving | What it catches |
| - | - |
| Candidates with no assigned user | Work nobody owns |
| Candidates whose step hasn't changed in days | People stuck waiting on your team |
| New applicants on your priority job reqs | Whether today's volume arrived |
| Candidates in the offer or onboarding step | Hires at risk of slipping their start date |

See [Saved views](https://help.journeyfront.com/lists-and-exports/saved-views.md), and [Export data](https://help.journeyfront.com/lists-and-exports/export-data.md) when you need the list in a spreadsheet.

### Keep the job req list honest

Close or archive the job reqs you're no longer hiring for, so your dashboards stop counting them, and use a req's **Activity** tab when something changes behaviour unexpectedly: it records who changed the workflow, the steps and the activities, and when. See [Job req statuses](https://help.journeyfront.com/job-reqs/statuses.md) and [Job reqs overview](https://help.journeyfront.com/job-reqs/overview.md#activity-tab).

## FAQ

> [accordion] Who should be allowed to change a workflow?
>
> Anyone with *Manage Job Req Settings* can edit and publish a job req's workflow. Keep that list short, and use the job req's **Activity** tab to see who changed what. See [Security roles and permissions](https://help.journeyfront.com/account-setup/security-roles.md).

> [accordion] Why do two dashboards disagree about the same month?
>
> They don't all count on the same date. Most use the application date, but others use the hire, start, interview or test date. Match the date range and the filters before comparing. See [Dashboards overview](https://help.journeyfront.com/reporting/dashboards.md#filter-a-dashboard).

> [accordion] We're hiring the same role in five locations. One job req or five?
>
> Five, if the workflow, location or client really differs; one, with a hiring class per wave, if the process is the same. Separate reqs are easier to report on by location, but every change has to be made five times.

> [accordion] How do I roll a process change out safely?
>
> Build it as a draft on one job req, publish it there, watch **Funnel Analytics** and **Hiring Process Fidelity** for a couple of weeks, then copy it to the rest. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).

> [accordion] Where do I set up interview scheduling?
>
> In three places, not one. The interview activity in the **Workflow** holds the interviewers, the length and the calendar invite; **Interview Reminders** on the **Configurations** page decides when candidates are reminded; and each interviewer connects their own calendar and sets their hours under **Interviews**. See [Set up an interview activity](https://help.journeyfront.com/interviews/interview-activity.md), [Interview reminders](https://help.journeyfront.com/interviews/reminders.md) and [Your availability and calendar](https://help.journeyfront.com/interviews/availability.md).

> [accordion] Why can't candidates apply to my new job req?
>
> New job reqs start **Inactive**. Publish the workflow, or click **Actions**, then **Activate**, when you're ready. Check the posting too: both **Make job posting page active** and **Post job to job board** have to be on. See [Job req statuses](https://help.journeyfront.com/job-reqs/statuses.md) and [Job postings](https://help.journeyfront.com/sourcing/job-postings.md).

> [accordion] Can I see what a candidate actually went through?
>
> Yes. Their Candidate Application's **Comments & Activities** tab holds their history, and the job req's **Activity** tab holds changes to the process itself.

> [accordion] How do I train the rest of the team?
>
> Send recruiters to [Getting started for recruiters](https://help.journeyfront.com/getting-started/recruiters.md), hiring managers and interviewers to [Getting started for hiring managers](https://help.journeyfront.com/getting-started/hiring-managers.md), your sourcing team to [Getting started for sourcing teams](https://help.journeyfront.com/getting-started/sourcing-team.md), and whoever handles new-hire paperwork to [Getting started for onboarding teams](https://help.journeyfront.com/getting-started/onboarding-team.md).

## Related

> [card] [Admin setup checklist](https://help.journeyfront.com/getting-started/admin-setup-checklist.md)
>
> Everything to put in place before candidates flow.

> [card] [Workflows overview](https://help.journeyfront.com/workflows/overview.md)
>
> Steps, activities, automation and versions.

> [card] [Dashboards overview](https://help.journeyfront.com/reporting/dashboards.md)
>
> Find the dashboard that answers your question.

> [card] [How scoring works](https://help.journeyfront.com/scoring/how-scoring-works.md)
>
> What the scores behind your decisions mean.


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