# Journeyfront Help Center
> This file is very large and may be truncated. For an index of this content, please refer to https://help.journeyfront.com/llms.txt instead.
> Guides, training and reference for hiring teams using Journeyfront.
> ## 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.
# Add-ons and credits
Source: https://help.journeyfront.com/account-setup/add-ons
See how many credits you have left, what you've used and the full transaction history for each add-on.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission.
>
> **Availability:** Add-ons are purchased separately. To turn one on or buy more credits, contact your Customer Success Manager.
Some Journeyfront features, like language assessments, e-signatures, text messages and AI features, run on prepaid credits. The **Add-Ons** page shows each add-on's balance, how much you've used and every purchase, usage charge and adjustment, so you always know where you stand before you run low.
## See your add-ons
Go to **Settings**, then **Add-Ons**. Each add-on shows:
* Its name and how it's tracked: **credits**, or **dollars** for text messages.
* **Active** or **Not Activated**.
* **Remaining:** your balance. It turns red when you've used everything.

Click an add-on to see its details:
* **Purchased**, **Used** and **Remaining**, with a bar showing the percentage used. The bar turns red once you've used 90%.
* **Transaction History**: every change to your balance, with its **Date**, **Type**, **Amount** and a **Note** from Journeyfront.

| Transaction type | What it means |
| - | - |
| Credit | Credits or funds added to your account, for example a purchase |
| Usage | Credits or funds used |
| Adjustment | A correction to your balance, explained in the note |
> [!TIP]
>
> Check the Add-Ons page before a big hiring push. Buying more credits goes through your Customer Success Manager, so plan ahead rather than waiting until the bar turns red.
## What each add-on covers
| Add-on | Tracked in | What uses it |
| - | - | - |
| Language assessments (shown as **Hallo Assessments** or **Emmersion Assessments**) | Credits | Candidates completing a language assessment |
| **E-Signatures** | Credits | Offers and documents sent for signature. One envelope uses one credit. |
| **Text Messages** | Dollars | Text messages and WhatsApp messages, when Journeyfront provides your texting account |
| **AI Credits** | Credits | AI features, such as AI Agents |
| **System Requirements** | Credits | Device checks before candidates start an activity |
## Text message credits
Text messaging is tracked in **dollars** rather than credits. The same balance covers text messages and WhatsApp messages; there's no separate WhatsApp add-on.
* **If Journeyfront provides your Twilio account,** messages draw from a prepaid messaging balance. You'll see it on the **Text Messages** add-on, on the **Billing** card. **Show transactions** lists your usage history.
* **If you use your own Twilio account or Webex Connect,** your provider bills you directly. The **Billing** card says so, and there's no Journeyfront balance.
Setting up texting, phone numbers and WhatsApp is covered in [Texting providers](/integrations/texting-providers). Sending messages is covered in [Text messages and WhatsApp](/communication/text-messages).
## E-signature credits
E-signature credits are used when you send an offer or document for a candidate to sign. An offer letter and all of its supporting documents go to the candidate as one envelope, and you use one credit per envelope, not per document. See [E-signatures](/offers/e-signatures).
## AI credits
AI credits are one shared pool that Journeyfront's AI features draw from, such as AI Agents. On the **AI Credits** add-on, the **Usage** section shows:
* Credits used over the last **30 days**, **90 days** or **12 months**, as a chart.
* A breakdown **By feature**, or **By agent** when only one feature has used credits.
* **Download CSV** and **Download XLS** from the chart's menu.
AI agents use one credit for each action they line up. When your AI credits run out, agents stop lining up new messages until more credits are added. See [AI agents](/workflows/ai-agents#ai-credits).
## FAQ
> [accordion] How many credits do we have left?
>
> Go to **Settings**, then **Add-Ons**. Each add-on shows its **Remaining** balance. Click one for purchased and used totals and the full transaction history.
> [accordion] How do we buy more credits?
>
> Contact your Customer Success Manager. New credits appear as a **Credit** in the add-on's transaction history.
> [accordion] Why does an add-on say Not Activated?
>
> It hasn't been turned on for your account. Contact your Customer Success Manager to get started.
> [accordion] What happens when we run out of credits?
>
> Contact your Customer Success Manager before your balance runs out so your team isn't interrupted.
> [accordion] Will we get a warning when credits run low?
>
> Keep an eye on the usage bar on each add-on. It turns red once you've used 90% of your credits.
> [accordion] Why don't I see a text message balance?
>
> A balance only appears when Journeyfront provides your Twilio account. If you use your own Twilio account or Webex Connect, your provider bills you directly.
> [accordion] Does an offer with several documents use more than one e-signature credit?
>
> No. The offer letter and all of its documents go to the candidate as one envelope, which uses one credit.
## Related
> [card] [Texting providers](/integrations/texting-providers)
>
> Set up texting and see your messaging balance.
> [card] [E-signatures](/offers/e-signatures)
>
> Send offers and documents for signature.
> [card] [Text messages and WhatsApp](/communication/text-messages)
>
> Message candidates one at a time or in bulk.
> [card] [System requirements](/assessments/system-requirements)
>
> Make sure candidates' devices are ready.
# Company details
Source: https://help.journeyfront.com/account-setup/company-details
Set your company's name, location, logo and the welcome message on your employee landing page.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission.
**Company Details** holds the basics about your company: its name, where it's based, its logo, and the welcome message employees see when you ask them to take assessments. Your company name and logo also appear on the sign-in page candidates see when they apply, so it's worth getting them right before your first job req goes live.
## Edit your company details
**1. Open Company Details**
Go to **Settings** (the gear icon at the top right), then **Company Details**. It's the first page in Settings.

**2. Click Edit Details**

A window titled with your company name, for example **Acme Settings**, opens with every field.
**3. Make your changes**
**Company Name** and **Job Country** are required. Everything else is optional.
| Field in the edit window | What it's for |
| - | - |
| **Company Name** | Your company's name. Candidates see it on the sign-in page when they apply, and it's used in emails Journeyfront sends for you, such as candidate invitations sent from "Your Company via Journeyfront". |
| **Company Description** | A short description of your company, for your own records. Candidates don't see it. |
| **Job Country** and **Location** (**City**, **State**, **Zip Code**) | Where your company is headquartered. The Company Details page shows these under **Headquarters**. |
| **Company Size** | Your company's size range, for your own records. |
| **Time in Job Before Job Assessments Required** | Choose from **Immediately** up to **12 Months**. It's meant for employee assessments: how long someone is in the job before they're asked to take job assessments. |
| **Logo URL** | The web address of your logo image. See [Add your logo](#add-your-logo). |
| **Welcome Text Header** and the message box below it | The title and message on your employee landing page. The Company Details page shows them as **Welcome Message Title** and **Welcome Message**. |
**4. Click Save**
The Company Details page shows your new values.
## Add your logo
**Logo URL** takes the web address of an image that's already online, such as the logo file on your company website. You can't upload a file here. Paste the full address, starting with `https://`.
Your logo appears:
* At the top of the sign-in page candidates see when they open a job req's application link, unless that job req has its own image (see [What candidates see](#what-candidates-see)).
* On the sign-in page your teammates see when they accept their invitation to Journeyfront.
* On your employee landing page.
> [!TIP]
>
> Before you save, paste the address into a new browser tab. If the logo opens on its own, the link will work in Journeyfront. A logo on a white or transparent background looks best on the sign-in pages.
## The employee landing page
The employee landing page is the sign-in page your current employees open when you ask them to take assessments for a job profile. It shows your logo, your company name, and the **Welcome Text Header** and message you set here. See [Job profiles](/employees/job-profiles).
To see it the way your employees do, click **View employee landing page** at the bottom of Company Details.

> [!TIP]
>
> Use the welcome message to tell employees why their participation matters, for example that their results help you find more people who succeed in the role. Employees who understand the reason are more likely to finish.
## What candidates see
When a candidate opens a job req's application link, the sign-in page shows:
* Your logo at the top, or the job req's own image if someone added one.
* The job req's title, with your company name and the job req's city and state underneath.
* The job req's own message, if it has one.
Each job req's image and message are set in its **Invite Candidates** window, not here. See [Customize the sign-in page](/sourcing/invite-candidates#customize-the-sign-in-page). The welcome message on Company Details is only for employees; candidates never see it.
## FAQ
> [accordion] Can I upload our logo instead of using a link?
>
> Not on Company Details. **Logo URL** needs the address of an image that's already online. If your logo isn't online anywhere, ask your web team for a link to it.
> [accordion] Why don't candidates see our logo on one job req?
>
> That job req has its own image. In the job req's **Invite Candidates** window, an **Image to display** replaces your company logo on that job req's sign-in page. Remove the image there to use your company logo again.
> [accordion] Do candidates see the welcome message?
>
> No. The welcome message only appears on the employee landing page. To show candidates a message, write a **Candidate Message** in a job req's **Invite Candidates** window.
> [accordion] Where do the logos on our career site and referral portals come from?
>
> Each has its own logo. Set them in **Settings**, then **Job Boards**, or **Settings**, then **Referral Portals**. See [Job boards](/sourcing/job-boards) and [Set up a referral portal](/referrals/portal-setup).
> [accordion] Can our logo replace the Journeyfront logo at the top of the app?
>
> Yes, but it needs to be turned on for your account. Ask your Customer Success Manager. Once it's on, the top bar shows the logo from **Logo URL**.
> [accordion] Why can't I find Company Details in Settings?
>
> It needs the *Company Settings Access* permission. Ask an admin to check your security role. See [Security roles and permissions](/account-setup/security-roles).
## Related
> [card] [Users](/account-setup/users)
>
> Invite your team to Journeyfront.
> [card] [Security roles and permissions](/account-setup/security-roles)
>
> Decide who can change your company settings.
> [card] [Invite candidates](/sourcing/invite-candidates)
>
> Set the message and image candidates see for a job req.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Brand the job boards candidates browse.
# Custom fields
Source: https://help.journeyfront.com/account-setup/custom-fields
Capture the extra information your team needs on candidates, applications, employees, job reqs and hiring classes.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* create and manage custom fields. Anyone who can edit a record can fill in its fields. Fields marked private are only visible to users with *Private Data Access*.
Custom fields let you track the information your business runs on, beyond what Journeyfront records out of the box. You set them up once for your whole account, and they appear on the records your team already works with: on forms, as columns and filters, in exports, and in offer letters.
All custom fields live in one place: go to **Settings**, then **Custom Fields**.

## The five kinds of custom field
Each kind of field belongs to a different record:
| Field type | Where it lives | Example |
| - | - | - |
| **Personal fields** | The Candidate Profile. About the person, so the value is shared by all of their Candidate Applications. | Languages spoken, bilingual (Yes/No) |
| **Application fields** | One Candidate Application. The person can have a different answer on each application. | Preferred site for this role, available for weekend training |
| **Employee job fields** | An employee's job record, once they're hired | Badge number, uniform size |
| **Job req fields** | A job req | Cost center, client name, contract end date |
| **Hiring class fields** | A hiring class | Program code, trainer, training room |
> [!TIP]
>
> Not sure whether a candidate question should be a personal field or an application field? Ask whether the answer could change from one job req to the next. Languages spoken stays the same, so make it a personal field. Availability for a specific role can change, so make it an application field.
## Value types
Every field has a type, which decides what people can enter:
| Type | What people enter | Example |
| - | - | - |
| **Text** | Free text | Client name, reference number |
| **Number** | A number | Headcount, years of experience |
| **Multiple Choice** | One option from a list you define | Region, shift preference |
| **Date** | A date | Contract end date, target start date |
| **Yes/No** | Yes, No or not set | Bilingual, backfill, billable |
| **User** | Someone on your team | Account manager, requisition owner |
| **Currency** | An amount with a currency | Approved budget, bill rate |
| **URL** | A link | Client portal, internal ticket |
| **File Upload** | A file, up to 10 MB | Signed statement of work, certification |
| **HRIS Object** | A record from your HR system | Work location, department, job code |
Not every type is available on every kind of field:
| Field type | Types you can use |
| - | - |
| Personal fields and application fields | Text, Number, Multiple Choice, Date, Yes/No, User, Currency, URL, File Upload |
| Employee job fields | Text, Number, Multiple Choice |
| Job req fields and hiring class fields | All of the above, plus HRIS Object |
## Personal, application and employee job fields
### Add a field
**1. Open the page**
Go to **Settings**, then **Custom Fields**, then **Personal Fields**, **Application Fields** or **Employee Job Fields**.
**2. Add the field**
Click **+ Field** and fill in the details:
* **Label:** the name people see on forms and records.
* **Internal Name:** a unique name for the field within your account.
* **Merge Key:** optional. Lets you place the field in offer letters and documents. See [Use fields in offer letters](#use-fields-in-offer-letters).
* **Field Type:** what kind of value it holds.
* **Placeholder Text:** optional hint text shown in the empty field.
* **Options:** the choices, for Multiple Choice fields.
**3. Choose who fills it in**
Set **Required**, **Admin Only** or **Private** (see below), then click **Save**.
| Setting | What it does |
| - | - |
| **Required** | Candidates must fill in the field when it's asked. |
| **Admin Only** | Only your team sees and fills in the field. Candidates never see it. |
| **Private** | Only users with the *Private Data Access* permission can see the value. A private field is also Admin Only. |
A field is either filled in by candidates (and can be **Required**) or kept for your team (**Admin Only** or **Private**), so turning one of these on can turn the others off. Application fields only have the **Private** setting: you decide whether they're required on each job req's application form.
> [!TIP]
>
> Use **Private** for sensitive details, such as government ID numbers or background information, so only the people who need them can see them.
To change a field, click its edit icon. To remove one, click its delete icon. Journeyfront's built-in fields can be edited but not deleted.
### Ask candidates on the application form
Personal and application fields can be added to any job req's application form:
1. Open the job req and go to **Setup**, then **Application Form**.
2. Click **Add**, then **Add Field**, and pick the fields you want. Each field is labeled Personal or Application.
3. Set each one to **Optional** or **Required**, and drag the rows into the order you want.
4. Save the application form.
User fields can't be added to application forms, because they would show candidates a list of your team. You can also add personal fields to onboarding forms in **Settings**, then **Onboarding Forms**.
### Where the values show
* **Personal fields** show on the Candidate Profile and on each of the person's Candidate Applications. On the **Candidates** page, add them as columns or filters under **Personal Fields**.
* **Application fields** show on the Candidate Application they belong to. On the **Candidates** page, they're under **Application Fields**.
* **Employee job fields** show on the employee's job record, and you can fill them in when you hire someone.
## Job req fields
Job req fields hold the details you organize your job reqs by, such as client, cost center, headcount or contract end date. You can fill them in on any job req, show them as columns on the **Job Reqs** page, filter by them and include them in exports.
### Add a job req field
**1. Open the page**
Go to **Settings**, then **Custom Fields**, then **Job Req Fields**, and click **Add Field**.
**2. Name it**
Enter a **Label**, such as "Cost Center". Journeyfront suggests a **Merge Key** from the label (for example `COST_CENTER`). You can change the key before you save, but not after.

**3. Choose a type**
Pick a **Field Type**. Add a **Description** if you'd like help text under the field, and **Options** for a Multiple Choice field.
**4. Save**
Click **Save**. The field now appears on every job req in your account.
> [!TIP]
>
> Take a moment over the merge key: it's permanent, because offer letters and documents refer to it. The label can be changed at any time.
### Fill in values on a job req
Open the job req and go to **Setup**, then **Details**. Under **Custom Fields**, the **Custom Job Req Fields** section lists your account's fields. The heading shows how many there are, and you can collapse the section when you don't need it. Fill in whatever applies and click **Save** at the top of the page.
No job req field is ever required, so you can always save a job req before you have every detail. Fields appear in the order you set in **Settings**.

### Work with job req fields on the Job Reqs page
* **Add columns:** click **Edit Columns**. Your fields are under **Custom Job Req Fields**. Tick each one you want. Your columns are listed under **Selected Columns** on the right, where you can drag them to reorder. Click **Save**. Currency values show their currency code, links and files are clickable, and user fields show the person's name.
* **Edit in place:** hover over a cell and click the pencil icon. Change the value and click **Save** (or press **Enter**). Click **Cancel** (or press **Esc**) to close without saving. You'll only see the pencil on job reqs you can edit.
* **Filter:** click **Filters**, then **More**, and tick fields under **Custom Job Req Fields**. Then click a filter to set its value.
* **Export:** click **Export**, select the columns you want (including custom fields), and choose CSV or Excel. Each field becomes a column named after its label.

How you filter depends on the field's type:
| Field type | How you filter |
| - | - |
| Multiple Choice, Yes/No, User | Pick one or more values |
| Text, URL, File Upload | Type a value to match, or choose **Is Set** or **Is Not Set** |
| Number, Currency | Between, equals, does not equal, greater than or less than |
| Date | A date range |
> [!TIP]
>
> Filter a field by **Is Not Set** to find job reqs that are missing information, then click **Save as New View** so you can check again in one click.
## Hiring class fields
Hiring class fields work the same way as job req fields, for your hiring classes. Use them for details like a program code, trainer or training room.
1. Go to **Settings**, then **Custom Fields**, then **Hiring Class Fields**, and click **Add Field**.
2. Enter a **Label**, check the suggested **Merge Key**, pick a **Field Type**, and click **Save**.
Fill in the values in the **Custom Fields** section when you create or edit a hiring class. On the **Classes** page, add them as columns and filters under **Hiring Class Fields**, and include them in exports.
## Manage job req and hiring class fields
On the **Job Req Fields** and **Hiring Class Fields** pages:
* **Reorder:** drag a field by the grip handle on the left. The order you set is the order fields appear on forms, in **Edit Columns** and in filters.
* **Edit:** open the field's menu and choose **Edit**. You can change the label, description and options at any time. The merge key can't change. The type can only change until a job req or hiring class has a value for the field; after that, a value entered as a date can't be reread as a number. If you need a different key or type, create a new field.
* **Archive:** choose **Archive** to remove the field from forms while keeping every value already entered. The values stay visible as a read-only column. Choose **Restore** to use the field again.
* **Delete:** choose **Delete** to remove the field and all of its values permanently. Before you confirm, Journeyfront tells you how many records have a value for it.
> [!TIP]
>
> Archive is almost always the better choice. It's reversible and keeps your history. Renaming a Multiple Choice option is also safe: records that already use it keep their value.
## HRIS Object fields
If your HR system (HRIS) is connected to Journeyfront, job req and hiring class fields can use the **HRIS Object** type. Instead of typing a value, people pick a real record from a list your HRIS keeps, such as a work location, department or job code.
An HRIS Object field carries two values: the record's name and the code your HRIS uses for it. Both appear as columns, in exports and as merge keys.
## Use fields in offer letters
Any field with a merge key can be placed in offer letters and documents as a token like `{{COST_CENTER}}`. When the document is created, the token is replaced with the value for that candidate, job req or hiring class.
* **Job req and hiring class fields** always have a merge key.
* **Personal, application and employee job fields** have one only if you add it. You can add a merge key from the field's edit dialog.
Merge keys use uppercase letters, numbers and single underscores, must be unique in your account, and can't be changed once saved.
## FAQ
> [accordion] Should a candidate question be a personal field or an application field?
>
> Use a personal field when the answer is about the person and stays the same across job reqs, like languages spoken. Use an application field when the answer can be different for each job req they apply to, like availability for that role.
> [accordion] Can I make a custom field required?
>
> Personal and employee job fields have a **Required** setting. Application fields are set to **Optional** or **Required** on each job req's application form. Job req and hiring class fields are never required.
> [accordion] Can candidates see every custom field?
>
> No. Candidates only see fields you ask them to fill in, such as fields on an application or onboarding form. Fields marked **Admin Only** or **Private** are for your team only.
> [accordion] Can I change a job req field's merge key or type later?
>
> The merge key is permanent. The type can change until any job req has a value for the field. If you need either to be different, create a new field.
> [accordion] What happens to custom fields when I duplicate a job req?
>
> The copy keeps every job req field value from the original. If a field holds an uploaded file, the copy gets its own copy of the file, so removing it from one job req never affects the other.
> [accordion] Can I sort the Job Reqs page by a custom field?
>
> Not yet. You can filter by any custom field and save the result as a view, which covers most of the same need.
> [accordion] Is there a limit to how many fields I can create?
>
> No. Keep in mind that every job req field appears on each job req's **Details** page, so a long list takes longer to fill in. The section can be collapsed when your team doesn't need it.
> [accordion] Why can't I edit a value in a column?
>
> Either the field has been archived, which makes its column read-only, or you don't have permission to edit that job req.
## Related
> [card] [Offer letter templates](/offers/templates)
>
> Place custom fields in offer letters with merge keys.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who start and train together.
> [card] [HRIS integrations](/integrations/hris)
>
> Connect your HR system.
> [card] [Lead ads](/sourcing/lead-ads#map-the-forms-questions)
>
> Map lead form answers to personal fields.
# Importing data
Source: https://help.journeyfront.com/account-setup/importing-data
Upload your employee and employee performance data, track each upload, and find where to import candidates.
> [!NOTE]
>
> **Who can do this:** Admins whose security role has both *Company Settings Access* and *Import Data*. Importing candidates into a job req only needs access to that job req.
**Settings**, then **Import Data** is where you send Journeyfront your employee data: who works for you, in which roles, and how they perform. That history powers your employee records, job profiles and turnover reporting. You upload a spreadsheet, and the page tracks each upload until it's imported.
Importing candidates works differently: you import them straight into a job req. See [Import candidates into a job req](#import-candidates-into-a-job-req) below.
## What you can import
**Import Data** has two tabs, each with its own template:
| Tab | What it's for |
| - | - |
| **Employee Data Import** | Your current and former employees: who they are, their job and job profile, their start date, and when and why they left |
| **Employee Performance Data Import** | Performance review results for your employees, by review period |
## Upload a file
**1. Open Import Data**
Go to **Settings**, then **Import Data**, and pick the **Employee Data Import** or **Employee Performance Data Import** tab.
**2. Download the template**
Click **Download Employee Data Import File Template** (or the performance one). Use the template's columns, one row per employee or review.
**3. Choose your file**
Click **Select file** and pick your file. It can be a .csv, .xlsx or .xls file.
**4. Click Upload File**
Your file appears at the top of **History** with the status **Import Pending...**.

Uploads aren't imported instantly. The page notes it can take up to 14 days for your data to appear, and your Customer Success Manager can tell you where an upload stands.
> [!TIP]
>
> Send a small file first, a handful of employees, and check how they look in Journeyfront once it's imported. Fixing the format on 10 rows is much easier than on 10,000.
### The employee data template
The **Employee Data Import** template has these columns:
| Group | Columns |
| - | - |
| Who they are | `email`, `first_name`, `last_name`, `gender`, `dob`, `city`, `state_code`, `country_code` |
| Their job | `employment_type_code`, `job_title`, `profile_title` (the job profile they belong to), `start_date`, `supervisor_email` |
| If they've left | `end_date`, `separation_name` (the reason they left), `separation_note` |
| Your employee job fields | A column for each employee job field (the template shows them as `Custom Job Field "XXX"`) |
For `separation_name`, use a reason from your separation reasons list. See [Rejection and separation reasons](/account-setup/rejection-reasons#separation-reasons). Employee job fields are set up in **Settings**, then **Custom Fields**. See [Custom fields](/account-setup/custom-fields).
### The performance data template
The **Employee Performance Data Import** template has one row per review, with the employee (`first_name`, `last_name`, `email`, `hire_date`), the job (`job_id`), the reviewer and review (`evaluator_email`, `eval_date`, `period_name`, `period_year`), and then a set of columns for each performance question: `account_question_id`, `attribute_id`, `score` and `note`, numbered 1, 2 and so on.
The ID columns refer to the job and performance questions set up in Journeyfront. Ask your Customer Success Manager for the IDs to use. See [Performance reviews](/employees/performance-reviews).
## Check your uploads
The **History** table on each tab lists every upload:
| Column | What it shows |
| - | - |
| **File Uploaded** | The file you uploaded. Click it to open your original. |
| **Date Uploaded** and **Uploaded By** | When, and who uploaded it |
| **Status** | **Import Pending...** until it's processed, then **Import Completed** or **Import Failed** |
| **Result File** | **Results** to download the results file once there is one, or **NA** |
If an upload says **Import Failed**, download the **Results** file to see what went wrong, fix your file and upload it again. Your Customer Success Manager can help if it isn't clear.
## Daily imports from your HR system
Some accounts have employee data imported automatically every day, straight from their HR system. If yours does, a **Daily Importer** section below **History** lists each day's run with its status. Click **View Results** to see what happened to each employee. This needs to be set up for your account; ask your Customer Success Manager.
## Import candidates into a job req
Candidates aren't imported in **Settings**. Import them into the job req they're applying to:
1. Open the job req and click **Actions**, then **Import Candidates**.
2. Click **Download Example File** for the columns: `email`, `first_name`, `last_name`, plus optional columns such as `phone` and `source`.
3. Drag in your .csv or .xlsx file, choose whether to tick **Send new candidates invite email**, and click **Import**.
4. Check the results: how many were imported, how many were duplicates and how many had invalid data. Click **Download Import Results** for the details, then **Done**.
For every column and how to fix rows that didn't import, see [Import candidates](/sourcing/import-candidates).
## FAQ
> [accordion] I see Import Data in my menu, but it won't open.
>
> **Import Data** appears in the menu under your name for everyone, but opening it needs both *Company Settings Access* and *Import Data* in your security role. Ask an admin to check your role. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] How long does an import take?
>
> It can take up to 14 days for an upload to be imported. The **Status** column shows **Import Pending...** until then. Ask your Customer Success Manager if you need it sooner.
> [accordion] Can I import candidates here?
>
> No. **Import Data** only takes employee and performance data. Import candidates from a job req's **Actions** menu. See [Import candidates](/sourcing/import-candidates).
> [accordion] Can I import candidates into several job reqs at once?
>
> No. Each candidate import goes into one job req. Run a separate import from each job req.
> [accordion] Can I undo an import?
>
> Not from this page. If something was imported wrong, ask your Customer Success Manager how best to correct it before you upload again.
> [accordion] What file types can I upload?
>
> .csv, .xlsx and .xls files. Start from the template so the column names match.
## Related
> [card] [Import candidates](/sourcing/import-candidates)
>
> Import a list of candidates into a job req.
> [card] [Employee records](/employees/employee-records)
>
> Where imported employees show up.
> [card] [Rejection and separation reasons](/account-setup/rejection-reasons)
>
> The separation reasons your employee import uses.
> [card] [Turnover and performance](/reporting/turnover-and-performance)
>
> Reports built on your employee data.
# Rejection and separation reasons
Source: https://help.journeyfront.com/account-setup/rejection-reasons
Set the reasons your team picks when rejecting a candidate or recording an employee leaving.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission manage both lists. Anyone rejecting a candidate can also add a rejection reason from the Reject window.
Every rejection in Journeyfront needs a reason, and every employee who leaves can have one too. These reasons are what turn "we lost a lot of people" into something you can act on: candidates who withdrew after the interview, hires who left in their first month for pay. Both lists live under **Settings**, then **Custom Options**.
| List | Used when | Reason types |
| - | - | - |
| **Rejection Reasons** | Rejecting a candidate | **We rejected them**, **They rejected us**, **Other** |
| **Separation Reasons** | Recording that an employee left | **Voluntary**, **Involuntary**, **Other** |
Every reason belongs to one reason type, so your reports can split, for example, candidates you turned down from candidates who turned you down.
> [!NOTE]
>
> **Custom Options** also has **Move Reasons**, the reasons your team picks when moving a candidate to another job req. See [Set up move reasons](/candidates/move-to-another-job#set-up-move-reasons).
## Rejection reasons
Go to **Settings**, then **Custom Options**, then **Rejection Reasons**. The list shows each **Rejection Reason** and its **Reason Type**. Click a column heading to sort by it.

### Add a rejection reason
**1. Click + Rejection Reason**
A new row appears at the top of the list.
**2. Name it and pick a type**
Type the reason, then pick a **Reason Type**.
**3. Click Save**
The reason is available in the Reject window straight away.
### Edit a rejection reason
Click the reason's name or type in the list. The row becomes editable; make your change and click **Save**, or **Cancel** to leave it as it was.
Renaming a reason renames it everywhere, including on candidates who were already rejected with it. Use that to fix a typo or tidy a name. If the meaning really changes, add a new reason instead, so older rejections keep reporting correctly.
### Delete a rejection reason
**1. Click the trash icon**
The **Delete Rejection Reason** window shows the reason you're deleting.
**2. Choose a replacement**
Pick the reason that candidates who currently have this one should get instead. You have to choose one.
**3. Click Delete**
The reason disappears from the list, and those candidates now show the replacement.
### The Auto rejected reason
Candidates who pick a knockout answer on a screening question are rejected with the reason **Auto rejected**. If it's not on your list, Journeyfront adds it the first time it's needed. If you rename or delete it, a new **Auto rejected** reason is added the next time a knockout answer rejects someone, so it's best to leave it as it is. See [Screening questions](/assessments/screening-questions).
### Where rejection reasons are used
* **Rejecting a candidate**, one at a time or in bulk. The Reject window groups reasons by type and lets you search them. See [Reject candidates](/candidates/reject).
* **Automation rules**, where the **Reject candidate** action uses the reason you pick. See [Automation rules](/workflows/automation-rules).
* **The Candidates page**, where you can filter by **Rejection Reasons**. See [The Candidates page](/candidates/candidates-page).
Reasons that anyone adds with **Add Rejection Reason** in the Reject window go on this same list for everyone.
> [!TIP]
>
> A good list is short, specific and doesn't overlap: if two reasons could both fit, recruiters will pick different ones and your reports will split the same problem in two. Name what happened ("Failed typing test", "No-show for interview", "Accepted another offer"), not a vague catch-all. Review the list every few months, and fold in reasons people added on the fly.
## Separation reasons
Separation reasons record why an employee left. Go to **Settings**, then **Custom Options**, then **Separation Reasons**. The list shows each **Separation Reason** and its **Reason Type**: **Voluntary**, **Involuntary** or **Other**.
Adding, editing and deleting work the same way as for rejection reasons:
* **Add:** click **+ Separation Reason**, type the reason, pick a **Reason Type** and click **Save**.
* **Edit:** click the reason's name or type, make your change and click **Save**.
* **Delete:** click the trash icon. In the **Delete Separation Reason** window, pick the reason that records using this one should get instead, and click **Delete**.
### Where separation reasons are used
* **An employee's record:** on the **Job Info** tab, untick **Employee currently works here**, set the **End Date**, and pick the **Reason for Separation**. The reason is required once the employee no longer works there. Add a **Separation Note** for detail. See [Employee records](/employees/employee-records).
* **Turnover reporting:** dashboards show each former employee's separation reason, and let you filter turnover by reason type and reason. See [Turnover and performance](/reporting/turnover-and-performance).
* **Employee imports:** the employee data template has a `separation_name` column for the reason. Use the reason's name exactly as it appears on your list. See [Importing data](/account-setup/importing-data).
> [!TIP]
>
> Keep voluntary and involuntary reasons clearly apart ("Left for higher pay" versus "Attendance"). Early turnover is one of the most useful things to measure in high-volume hiring, and it's only as good as the reasons behind it.
## FAQ
> [accordion] Can a recruiter add a rejection reason without admin access?
>
> Yes. In the Reject window, **Add Rejection Reason** at the bottom of the list adds a reason, with its type, to your account's list. Admins can tidy it up later in **Settings**, then **Custom Options**.
> [accordion] What happens to rejected candidates when I delete their reason?
>
> They get the replacement reason you picked in the **Delete Rejection Reason** window. Their rejection itself doesn't change.
> [accordion] Does changing a reason's name change past rejections?
>
> Yes. A rename shows on every candidate who has that reason. To keep old and new meanings apart in your reports, add a new reason instead.
> [accordion] Does editing the reasons list email anyone or run automations?
>
> No. Changing the lists in **Settings** doesn't change any candidate's status or send anything.
> [accordion] Why is there an Auto rejected reason I didn't add?
>
> Journeyfront adds it automatically the first time a candidate is rejected by a knockout answer. See [The Auto rejected reason](#the-auto-rejected-reason).
> [accordion] Can I change the reason types?
>
> No. The reason types are the same for every account. Name your reasons so they fit one of them clearly.
## Related
> [card] [Reject candidates](/candidates/reject)
>
> Reject one or many candidates with a reason.
> [card] [Automation rules](/workflows/automation-rules)
>
> Reject candidates automatically with a chosen reason.
> [card] [Employee records](/employees/employee-records)
>
> Record when an employee leaves and why.
> [card] [Turnover and performance](/reporting/turnover-and-performance)
>
> See why and when people leave.
# Security roles and permissions
Source: https://help.journeyfront.com/account-setup/security-roles
Control what each person can see and do with security roles, and find out which permission a missing page or button needs.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission.
A security role is a named set of permissions, such as "Recruiter" or "Hiring Manager". Every user in your account has one role, and the role decides what they can see and do: which job reqs they can open, whether they can hire, which settings they can change. Change a role once and everyone who has it gets the change.
Journeyfront hides what a role doesn't allow instead of showing an error. So when someone says they "can't find" a page or button, the answer is almost always a permission in their role. Use the [permissions table](#every-permission) below to find which one.
## The roles you start with
Every account starts with four roles. Your admins may have changed them since.
| Role | Made for |
| - | - |
| **Admin** | Access to all data and functionality |
| **People Manager** | Their direct reports and job profiles |
| **Recruiter** | Every job req and job profile |
| **Hiring Team Member** | Only the job reqs they're on the hiring team for |
**Admin** and **Hiring Team Member** can't be renamed or deleted, but you can change their permissions.
When someone adds an email to a job req's hiring team and that person isn't a user in your account yet, they get the **Hiring Team Member** role. See [Hiring team](/job-reqs/hiring-team).
## Create or edit a role
**1. Open Security**
Go to **Settings**, then **Security**. The **Security Roles** list shows each role's **Role Name** and **Description**.
**2. Start a role**
Click **New Role**, or click **Edit** next to an existing role.
**3. Name and describe it**
Click the name at the top to type a role name. Click **Click to add description** to say who the role is for.
**4. Turn permissions on or off**
Permissions are grouped into sections. Turn each switch **On** to allow it or **Off** to block it.
**5. Click Save**
A **Save** bar appears at the bottom once you change something. Click **Back to All Roles** to return to the list.
A new role starts with every permission turned off, so turn on everything the role needs before you save.

To give someone a role, edit them in **Settings**, then **Users**. See [Users](/account-setup/users#change-someones-security-role).
> [!TIP]
>
> Build roles around jobs, not people: "Recruiter", "Hiring Manager", "Interviewer", "Onboarding Coordinator". Give each one the least access it needs. It's easy to add a permission later, and much harder to notice one that shouldn't be there.
### Delete a role
Click **Delete** next to the role, then **Confirm**. You can only delete a role that no one has. If the role is still in the list afterward, move its users to another role in **Settings**, then **Users**, and try again.
## Every permission
Permissions are listed in the same sections, and the same order, as on the **Security** page.
### People & Candidate Access
| Permission | What it controls |
| - | - |
| *All Employee Access* | Shows the **Employees** tab at the top of the app, listing every employee in your account. Without it, the tab doesn't appear. |
| *Private Data Access* | See custom fields and documents marked private, and switch a document between private and public. See [Custom fields](/account-setup/custom-fields). |
| *Delete Applicants* | Shows **Delete** in the bulk actions bar, which removes Candidate Applications. Deleted applications can be recovered. See [Bulk actions](/candidates/bulk-actions#delete-candidates). |
| *View & Submit Comments* | See and post comments on Candidate Applications and in interview guides. Without it, comments are hidden but the activity history still shows. |
| *Hire Candidates* | **Hire** and **Un-Hire** on a Candidate Application, and **Hire** in bulk actions. See [Hire candidates](/onboarding/hire-candidates). |
| *Send Emails* | Email candidates and employees: **Email** on a Candidate Application and **E-mail** in bulk actions. |
| *Send Messages* | Text and WhatsApp candidates: **Message** on a Candidate Application and in bulk actions, and the message icon next to phone numbers. Only listed when your account has text messaging. |
### Requisitions & Classes
| Permission | What it controls |
| - | - |
| *All Job Req Access* | See every job req and all of its candidates. Without it, people only see the job reqs they're on the hiring team for. Creating a new job req also needs it. |
| *Manage Job Req Settings* | Shows a job req's **Setup** tab, where its details, application form, workflow, team, job postings and settings live. Without it, people can still work with candidates but can't change how the job req is set up. |
| *All Hiring Class Access* | The **Classes** page lists every hiring class. Without it, it only lists classes on job reqs the person is on the hiring team for, even if they have *All Job Req Access*. |
| *Deactivate Job Reqs* | **Deactivate Job Req** and **Activate** in a job req's **Actions** menu. |
| *Close Job Reqs* | **Close Job Req** and **Re-Open**. |
| *Duplicate Job Reqs* | **Duplicate Job Req**. |
| *Archive Job Reqs* | **Archive Job Req** and **Un-archive Job Req**. |
| *Delete Job Reqs* | **Delete Job Req**. |
For what each job req action does, see [Job req statuses](/job-reqs/statuses).
### Scores & Interviews
| Permission | What it controls |
| - | - |
| *Can Unlock Interviews* | Unlock an interviewer's submitted feedback so it can be changed. See [Conduct an interview](/interviews/conduct-an-interview). |
| *Can Delete Scores* | Delete an activity's score on a Candidate Application, for example so a candidate can retake an assessment. See [Retakes](/assessments/retakes). |
| *Edit AI Scores* | Edit or delete the scores AI gave to candidates' answers. |
| *AI Scored Question Control* | Turn on **Score with Ai** for a question and add instructions for the AI. Only listed when AI scoring is on for your account. |
| *AI Score Single Question* | Send one candidate's answer to be scored by AI with the **Generate** button. Only listed when AI scoring is on for your account. |
| *Edit Locked Questions* | Edit a screening or interview question that candidates have already answered, with **Edit Anyway**. The change applies to everyone who already answered it. |
See [AI-scored questions](/scoring/ai-scored-questions) for how the AI scoring permissions work together.
### AI Agents
This section only appears when AI agents are turned on for your account.
| Permission | What it controls |
| - | - |
| *Manage AI Agents* | Create and set up AI agents in **Settings**, then **AI Agents**. |
| *Assign AI Agents* | Turn on AI agents for a job req (**Setup**, then **AI Agents**) and assign agents to candidates. |
| *Approve AI Agent Actions* | Approve or reject what agents propose, on the **AI Agent Tasks** page. |
| *View AI Agent Tasks* | See the **AI Agent Tasks** page, without approving anything. |
See [AI agents](/workflows/ai-agents).
### Dashboards & Reporting
| Permission | What it controls |
| - | - |
| *Company Dashboard Access* | Shows the **Dashboard** tab with your company-wide dashboards. Without it, the tab doesn't appear. Each job req's own **Dashboard** tab doesn't need it. See [Dashboards](/reporting/dashboards). |
| *Performance Access* | See employees' job performance data: the **Job Performance** tab on an employee's record, and the performance comparisons you can open from dashboards. |
### System & Settings
| Permission | What it controls |
| - | - |
| *Company Settings Access* | Opens **Settings** (the gear icon) and nearly every page in it. A few pages need one of the permissions below as well. |
| *Manage Users* | Shows **Settings**, then **Users**, to add, edit and remove users. Needs *Company Settings Access* too. |
| *Import Data* | Shows **Settings**, then **Import Data**. Needs *Company Settings Access* too. See [Importing data](/account-setup/importing-data). |
| *E-Consent Forms* | Manage e-consent forms and see signatures, without *Company Settings Access*. See [E-consent forms](/onboarding/e-consent-forms). |
| *Offer Packages* | Build and edit offer packages, without *Company Settings Access*. See [Offer packages](/offers/offer-packages). |
| *Connect to MCP* | Connect an AI assistant that supports MCP to read your Journeyfront data, from **Personal Settings**, then **AI Connections**. AI connections need to be turned on for your account. |
### Other
| Permission | What it controls |
| - | - |
| *All Job Profile Access* | See every employee job profile on the **Profiles** tab. Without it, people only see the job profiles ticked for them in **Settings**, then **Users**. See [Job profiles](/employees/job-profiles). |
| *View and Send Offers* | See and manage offers on a candidate's **Offer** tab, **Send Offers** in bulk, and create offers while changing a candidate's step. See [Send an offer](/offers/send-offers). |
> [!TIP]
>
> Turn on *Company Settings Access* and *Manage Users* only for the few people who run your account. Anyone with both can change other people's access, including their own.
## FAQ
> [accordion] Why can't a recruiter see a job req?
>
> Unless their role has *All Job Req Access*, people only see the job reqs they're on the hiring team for. Add them to the job req's team (**Setup**, then **Team**), tick the job req for them in **Settings**, then **Users**, or turn on *All Job Req Access* in their role. Also check the job req isn't archived: archived job reqs are hidden from the Job Reqs page until you filter for them. See [Hiring team](/job-reqs/hiring-team).
> [accordion] Why can't someone see the Dashboard tab?
>
> The **Dashboard** tab needs *Company Dashboard Access*. A job req's own **Dashboard** tab only needs access to that job req. Performance details inside dashboards also need *Performance Access*.
> [accordion] Why can't a recruiter see a hiring class?
>
> Without *All Hiring Class Access*, the **Classes** page only lists classes on job reqs the person is on the hiring team for. Turn on *All Hiring Class Access*, or add them to the class's job req team. Anyone who can open a job req sees all of its classes on that job req's **Hiring Classes** tab.
> [accordion] Why can't someone see a job req's Setup tab?
>
> The **Setup** tab needs *Manage Job Req Settings*. Without it, people can still review candidates, move them through steps and submit feedback, but can't change the workflow, application form or postings.
> [accordion] Why don't they see Settings (the gear icon)?
>
> **Settings** appears for people with *Company Settings Access*, or with *Offer Packages* or *E-Consent Forms*, which open just those pages.
> [accordion] Why can't someone delete, hire, email or text candidates?
>
> Each needs its own permission: *Delete Applicants*, *Hire Candidates*, *Send Emails* or *Send Messages*. See [Bulk actions](/candidates/bulk-actions).
> [accordion] Can an interviewer see only the candidates they interview?
>
> Not one candidate at a time. Turn off *All Job Req Access* in their role and add them only to the job reqs they interview for. They'll see the candidates on those job reqs and nothing else.
> [accordion] What's the difference between All Job Req Access and All Job Profile Access?
>
> Job reqs are the jobs you're hiring for. Job profiles describe roles your current employees hold, on the **Profiles** tab. Each has its own "see everything" permission.
> [accordion] Who can fix a score the AI got wrong?
>
> People whose role has *Edit AI Scores*. See [AI-scored questions](/scoring/ai-scored-questions).
> [accordion] I changed a role, but nothing changed for the person.
>
> Ask them to sign out and sign back in. Also check they have the role you changed: their role is in the **Role** column on **Settings**, then **Users**.
## Related
> [card] [Users](/account-setup/users)
>
> Add people and give them a role.
> [card] [Hiring team](/job-reqs/hiring-team)
>
> Give people access to one job req.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> The permissions behind each candidate action.
> [card] [Job req statuses](/job-reqs/statuses)
>
> Deactivate, close, archive, duplicate and delete job reqs.
# Users
Source: https://help.journeyfront.com/account-setup/users
Invite teammates, assign their security role, give them access to job reqs, and fix invitation problems.
> [!NOTE]
>
> **Who can do this:** Admins whose security role has both *Company Settings Access* and *Manage Users*.
Everyone on your team who works in Journeyfront, from recruiters to hiring managers and interviewers, is a user in your account. Each user has one security role, which decides what they can see and do, and a list of the job reqs they work on. You manage all of it from **Settings**, then **Users**.
## The Users page
Go to **Settings**, then **Users**. The list shows every user in your account:
| Column | What it shows |
| - | - |
| **Team Member** | The person's name |
| **Email** | The email they sign in with |
| **Role** | Their security role |
| **Job Reqs** | How many job reqs they're on, or **All** if their role has *All Job Req Access* |
Use the search box to find someone by name, email or role, and click a column heading to sort by it. Each row has an edit icon and a trash icon.

## Add a user
**1. Click + User**
On **Settings**, then **Users**, click **User** (with the plus) at the top right. The **Add New User** window opens.
**2. Enter their email and role**
Enter the **User Email** they'll sign in with, pick a **Security Role**, and click **Add**.
**3. Add their name (new people only)**
If no one in Journeyfront has this email yet, you're asked to **Add a name for this user**. Enter their first and last name (at least two characters each) and click **Add Name**.
The person is added to the list and gets an invitation email right away. See [The invitation email](#the-invitation-email).
If they're already a user in your account, you'll see "This user has already been added as an admin on this account." Find them in the list and edit them instead.
> [!TIP]
>
> Pick the role with the least access the person needs. You can always give more later. See [Security roles and permissions](/account-setup/security-roles) for what each permission controls.
### Other ways people become users
When someone adds an email to a job req's hiring team (on the job req's **Setup** tab, under **Team**) and that person isn't a user in your account yet, Journeyfront adds them as a user with your account's **Hiring Team Member** role and emails them an invitation to the hiring team. See [Hiring team](/job-reqs/hiring-team).
## Give a user access to job reqs
People see the job reqs they're on the hiring team for. People whose role has *All Job Req Access* see every job req.
**1. Edit the user**
Click the edit icon on the person's row. The **Edit User** window opens with their name, email and **Security Role**.
**2. Pick their job reqs**
On the **Available Job Reqs** tab, tick each job req they should work on and untick any they shouldn't. Use **Search** to find a job req, and turn on **Show Archived** to include archived ones.
**3. Pick their job profiles (optional)**
On the **Available Job Profile** tab, tick the employee job profiles they should see.
**4. Click Save**
Ticking a job req adds the person to its hiring team; unticking removes them.
If the person's role has *All Job Req Access*, the tab says **All Job Reqs** and there's nothing to tick. The same goes for **All Job Profiles** with *All Job Profile Access*.
Next to each ticked job req, the edit icon opens **Edit Team Member**, where you choose whether they get an email each time a candidate completes the application. See [Hiring team](/job-reqs/hiring-team#get-an-email-when-a-candidate-finishes-applying).

## Change someone's security role
Click the edit icon on their row, pick a new **Security Role**, and click **Save**. The **Role** column updates.
> [!TIP]
>
> If a change doesn't show up for the person, ask them to sign out and sign back in.
## Remove a user
Click the trash icon on their row. The **Remove User** window asks "Are you sure you want to remove this User?" Click **Confirm**.
Removing someone:
* Takes away their access to your account.
* Takes them off every job req hiring team they were on.
* Keeps their history. Comments, interview feedback and other activity they left stay on your candidates.
There's no separate "deactivate" option: remove the user to turn off their access. If they come back, add them again with **+ User** and choose their job reqs again.
> [!WARNING]
>
> Candidates assigned to the person stay assigned to them after they're removed. Reassign those candidates first, for example with **Assign User** in [Bulk actions](/candidates/bulk-actions).
## The invitation email
When you add a user, Journeyfront emails them:
* **From:** Journeyfront
* **Subject:** "*Your name* has invited you to Journeyfront"
* **What it says:** that you've given them access to Journeyfront for your company, with a **Click here to get started!** link.
The link opens a sign-in page with your company logo and their email already filled in. They set a password and click **Next**. The password needs at least 8 characters, including a capital letter, a number and a symbol. They're then signed in and land on the **Job Reqs** page.
If your company signs in with single sign-on (SSO), the link sends them to your company's sign-in page instead of asking for a password.
The invitation link doesn't expire, so they can use it later.
To change the wording, edit the **Invitation Admin** email in **Settings**, then **Templates**, then **E-mail Template**, on the **System Emails** tab. See [Team emails and system emails](/communication/email-templates).

## Troubleshoot invitations
| What happens | Why | What to do |
| - | - | - |
| The invitation never arrived | It went to spam or junk, or the email address has a typo | Ask them to search for an email from Journeyfront with "has invited you to Journeyfront" in the subject. Check the address in the **Email** column. |
| They lost the invitation | There's no resend button | Send them to the Journeyfront sign-in page. They enter their email, click **Next**, then **Forgot your password?** to get an email with a link to set a password. |
| "Incorrect Email or Password" after setting a password on the invitation page | They already have a Journeyfront password with this email, for example from applying to a job or from another company that uses Journeyfront | Enter that existing password on the invitation page instead. If they don't remember it, go to the regular Journeyfront sign-in page, enter the email and click **Forgot your password?** |
| The **Next** button stays greyed out | The password doesn't meet the rules | Use at least 8 characters with a capital letter, a number and a symbol. |
| They land on a candidate page instead of your account | They signed in with a different email from the one you invited | Sign out and sign in with the invited email, or add the email they use. |
| They sign in but see no job reqs | They're not on any hiring team and their role doesn't have *All Job Req Access* | Tick their job reqs on the **Available Job Reqs** tab. See [Give a user access to job reqs](#give-a-user-access-to-job-reqs). |
> [!TIP]
>
> If the address had a typo, remove the user and add them again with the right email. That sends a fresh invitation to the right inbox.
For more about signing in and passwords, see [Logging in and passwords](/getting-started/logging-in).
## Change a user's email
You can't change a teammate's email from **Settings**, then **Users**. Each person changes their own:
1. Click your name at the top right, then **My Profile**.
2. Next to **Primary Email**, click **Change**.
3. Enter the **New Email** and your current **Password**, then click **Save**.
You're signed out, and from then on you sign in with the new email. Because this asks for their Journeyfront password, people who sign in with SSO should ask your Customer Success Manager instead.
To change a candidate's email, edit **Primary Email** on the **Details** tab of their Candidate Application. See [Edit candidate details](/candidates/edit-details).
## FAQ
> [accordion] Why can't I see Users in Settings?
>
> The **Users** page needs both *Company Settings Access* and *Manage Users* in your security role. Ask another admin to check your role. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] Does a new user get an email?
>
> Yes. Adding a user sends the invitation email straight away. Adding someone to a job req's hiring team also sends them an email about that job req.
> [accordion] Can I add many users at once?
>
> Not from the **Users** page; add them one at a time. If your company signs in with SSO, ask your Customer Success Manager how new people are set up for your account.
> [accordion] Can someone have more than one security role?
>
> No. Each user has one role in your account. If someone needs a mix of permissions, create a role for it. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] A hiring manager can't see a job req. What do I check?
>
> Edit them and make sure the job req is ticked on **Available Job Reqs**, or add them on the job req's **Team** page. Archived job reqs only appear in the list when **Show Archived** is on.
> [accordion] Can I remove myself?
>
> Be careful: removing your own user takes away your access to the account immediately. Ask another admin to make the change instead.
## Related
> [card] [Security roles and permissions](/account-setup/security-roles)
>
> What each permission lets someone see and do.
> [card] [Hiring team](/job-reqs/hiring-team)
>
> Add people to a job req's team and set their notifications.
> [card] [Logging in and passwords](/getting-started/logging-in)
>
> Sign in, reset a password and use SSO.
> [card] [Team emails and system emails](/communication/email-templates)
>
> Edit the invitation email.
# Behavioral assessment
Source: https://help.journeyfront.com/assessments/behavioral-assessment
Measure the work-related traits that predict success and retention in a role, on its own or with a predictive model.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add the assessment to a job req. Anyone who can open a Candidate Application can see the results.
The behavioral assessment measures work-related traits, the kind of preferences and tendencies that shape how someone approaches a job day to day. It's included on every Journeyfront account. It was built to work with [predictive models](/scoring/predictive-models), which learn which traits go with success and retention in your own roles. You can also use it on its own, by telling Journeyfront what an ideal candidate looks like for the job.
## Two ways to use it
| | With a predictive model | On its own |
| - | - | - |
| **How it's scored** | The job req's predictive model uses the candidate's results to produce their Candidate Predictive Score. | You set an **Ideal Value** for each trait, and candidates are scored against it. |
| **What you set up** | A predictive model on the job req, and **Use Predictive Model** under **Setup**, then **Configurations**. See [Predictive models](/scoring/predictive-models). | The ideal value for each trait, and which traits count, on the activity in the workflow. |
| **Good for** | Roles where you have the hiring and turnover history to learn from. | Getting started. The results you collect now can be used later to find which traits go with turnover in your roles. |
With a predictive model turned on, a candidate's overall score combines two roll-ups: the **Attribute Group** roll-up from the job req's attributes, and the **Predictive Model** roll-up. How much each counts is set under **Setup**, then **Configurations**. See [How scoring works](/scoring/how-scoring-works) and [Job settings](/job-reqs/job-settings).
> [!TIP]
>
> Even if you're not ready for a predictive model, add the behavioral assessment early. Every candidate who takes it adds to the history a predictive model learns from later.
## See what the assessment measures
Go to **Settings**, then **Measurements**, then **Personal Assessments**. Each assessment is listed with its version. Expand it to see every trait it measures, with a description of each.
## Add the assessment to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, open **BEHAVIORAL ASSESSMENT** and drag **New Behavioral Assessment** into the step where candidates should take it. You can rename the activity at the top of its settings panel. On the Workflow page, its type shows as **Personal Assessment**.
**3. Choose the assessment**
Click the activity to open its settings on the right. Under **Assessments**, click **Add Assessment**. In the **Add Personal Assessment** window, choose a version and click **Add**.
**4. Set up the traits**
The assessment lists each trait it measures. For each one, turn **Score** on or off to choose whether it counts for this job req, and set its **Ideal Value** from 1 to 5: the level of that trait that best fits the role.
**5. Save, then publish**
Set **Estimated Time (Minutes)** and click **Save Draft**; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

Traits only count toward the candidate's score once they're in an attribute group on the job req's **Attributes** page. See [Attributes](/scoring/attributes).
> [!TIP]
>
> Set ideal values with the people who know the role best, like a team lead or trainer. Think about your strongest current employees in the role, not a generic "good employee".
## What candidates see
* **An Authenticity Pledge.** Before starting, candidates are asked to pledge to answer honestly.
* **Instructions,** with the assessment's name and description, then **Got It - Let's Go**.
* **The questions,** which candidates answer for who they are, as the pledge asks.
* **A finish screen** with **Continue to Next Step**. Candidates can also click **View My Results** to see a short report on their own profile, unless your account is set up to hide results from candidates.
To hide results from candidates, ask your Customer Success Manager.
## See the results
Open the candidate's Candidate Application and select the **Assessments** tab. Under **Behavioral assessments**, expand an assessment to see each trait:
* A slider showing the **Candidate Value**, from **Low (1)** to **High (5)**, next to the **Ideal Value** you set.
* **Score (1-5)**, the candidate's score for that trait, or **Not Scored** if the trait doesn't count for this job req.
* A description of the assessment beside the table.
The assessment's score also appears on the **Score** and **Steps** tabs with the rest of the candidate's results. See [Reading a candidate's scores](/scoring/reading-scores).

## FAQ
> [accordion] Is the behavioral assessment an add-on?
>
> No. It's included on every Journeyfront account.
> [accordion] Do I need a predictive model to use it?
>
> No. Set an ideal value for each trait and it's scored on its own. Adding a predictive model later lets Journeyfront learn which traits go with success and retention in your roles. See [Predictive models](/scoring/predictive-models).
> [accordion] What does Not Scored mean?
>
> The trait was measured, but **Score** is off for it on this job req, so it doesn't count toward the candidate's score.
> [accordion] Can candidates see their results?
>
> By default, candidates can open a short report on their own profile from the finish screen. Your scores and ideal values aren't shown to them. To hide the report, ask your Customer Success Manager.
> [accordion] Can a candidate take the assessment again?
>
> Yes. Someone with *Can Delete Scores* can delete the assessment's score on the **Steps** tab, and the candidate can take it again. See [Retakes and resetting scores](/assessments/retakes).
> [accordion] Can I see the questions?
>
> Use **Preview Activity** (the eye icon) on the activity on the job req's **Workflow** page to see the assessment as a candidate does.
## Related
> [card] [Predictive models](/scoring/predictive-models)
>
> Learn which traits predict success in your roles.
> [card] [Attributes](/scoring/attributes)
>
> Choose which traits count for each job req.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> How scores roll up into the overall score.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Find behavioral results on the Candidate Application.
# Internet speed test
Source: https://help.journeyfront.com/assessments/internet-speed-test
Check that remote candidates have a fast enough connection, and help them when the test won't submit.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add the test to a job req. Anyone who can open a Candidate Application can see the results.
For remote roles, a slow connection can make the job impossible. The Internet Speed Test measures a candidate's **download** and **upload** speed in Mbps, right from their application, so you know before the interview whether their home internet can keep up. It's quick for candidates and needs nothing installed.
## Add the test to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, open **INTERNET SPEED TEST** and drag **Internet Speed Test** into the step where candidates should take it.
**3. Add instructions (optional)**
Click the activity to open its settings on the right. Click **Instructions** to expand it, then add anything candidates should know first, like testing from the place they'll work. If you leave it empty, candidates go straight to the test.
**4. Check the scoring**
Under **Scoring**, the **Download Speed** and **Upload Speed** rows set which speeds earn which 1 to 5 score for this job req, and whether a slow result can knock a candidate out. Adjust them if this job needs a different bar.
**5. Save, then publish**
Set **Estimated Time (Minutes)** and click **Save Draft**; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

> [!TIP]
>
> Ask candidates to run the test from the computer and connection they'll actually work on. A result from a phone on mobile data, or from a coffee shop, doesn't tell you much about their home setup.
## What candidates see
1. **Instructions,** if you added them, then **Begin Internet Speed Test**.
2. **The speed test.** They click **GO** and the test measures their download and upload speed.
3. **Submit Speed Test** (on a phone, **Submit Test**) appears at the top once the test finishes. They click it to send their result.
4. **Completed,** then **Continue to Next Step**.
## See the results
Open the candidate's Candidate Application and select the **Steps** or **Score** tab. The speed test shows a score for **Download Speed** and **Upload Speed**, with the measured speed in Mbps under each. See [Reading a candidate's scores](/scoring/reading-scores).
## Help a candidate whose test won't submit
The most common problem is that **Submit Speed Test** never appears after the test runs. Share these steps with the candidate:
**1. Check the connection**
Make sure the internet connection is stable, and turn off any VPN.
**2. Run the test again**
Open the activity, click **Begin Internet Speed Test**, then **GO**, and wait for the download and upload results to finish.
**3. Submit**
Click **Submit Speed Test** at the top of the page.
**4. Try a private window**
If **Submit Speed Test** still doesn't appear, open the application link in a private (incognito) browser window, sign in and try again.
**5. Contact support**
If it still won't submit, contact Journeyfront support with a link to the candidate's Candidate Application, the browser and device they're using, and a screenshot if they have one.
## FAQ
> [accordion] How is this different from the System Requirements Test?
>
> The Internet Speed Test only measures download and upload speed, and it's available on every account. The [System Requirements Test](/assessments/system-requirements) is an add-on that checks the whole setup, hardware, software and network, against your requirements. You can use both in the same workflow.
> [accordion] Can candidates take the speed test on a phone?
>
> Yes, the test runs in any browser. But the result reflects the device and connection they used, so ask them to test from the setup they'll work on.
> [accordion] A candidate's result looks wrong. Can they take it again?
>
> Yes. Someone with *Can Delete Scores* can delete the speed test's score on the **Steps** tab, and the candidate can take it again from their application. See [Retakes and resetting scores](/assessments/retakes).
> [accordion] Why did the candidate go straight to the test?
>
> The activity has no instructions. Add **Instructions** to the activity in the workflow editor if you want candidates to read something first.
## Related
> [card] [System requirements test](/assessments/system-requirements)
>
> Check the whole computer and connection.
> [card] [Assessments overview](/assessments/overview)
>
> Every assessment and what candidates need.
> [card] [Retakes and resetting scores](/assessments/retakes)
>
> Let a candidate take a test again.
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities to a job req.
# Language assessments
Source: https://help.journeyfront.com/assessments/language-assessments
Measure spoken and written language skills with Journeyfront's assessment partners, and track results by job req or across your company.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add a language assessment to a job req. Anyone who can open a Candidate Application can see the results. The company-wide **Language Assessment** dashboard needs *Company Dashboard Access*.
>
> **Availability:** Language assessments are an add-on that uses credits, from Journeyfront's partners Emmersion and Hallo. They appear in the workflow editor once a partner is turned on for your account. Ask your Customer Success Manager.
When a role depends on how well someone speaks, writes, reads or listens in a language, a language assessment gives you a standard, comparable result for every candidate. Candidates take the test as an activity in their application, and the results, including a CEFR level, land on their Candidate Application without anyone on your team having to run a call.
## What's measured
Results use the **CEFR** (Common European Framework of Reference for Languages), the global standard for describing language proficiency. It has six levels: A1 and A2 for beginners, B1 and B2 for intermediate, and C1 and C2 for proficient speakers. Each partner also gives its own score.
With Hallo, you choose the **Assessment Type** and the **Language** for each test:
| Assessment Type | What candidates do |
| - | - |
| **Speaking** | Answer out loud |
| **Writing** | Write responses |
| **Reading** | Read and answer questions |
| **Listening** | Listen and answer questions |
| **Speaking + Writing** | Both speaking and writing parts |
| **Comprehensive (Speaking, Writing, Reading & Listening)** | All four skills |
With Emmersion, you pick from the list of tests available to your account.
Each test uses add-on credits. See [Add-ons and credits](/account-setup/add-ons) to check your balance.
## Add a language assessment to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, find your partner's group, **HALLO ASSESSMENT** or **EMMERSION ASSESSMENT**, and drag **New Hallo Assessment** or **New Emmersion Assessment** into the step where candidates should take it.
**3. Choose the test**
Click the activity to open its settings on the right. Under **Language Tests**, click **Add Language Test**.
* **Hallo:** in **Add Language Assessment**, choose an **Assessment Type** and a **Language**, click **Add**, then **Done**.
* **Emmersion:** in **Select Assessments to Add**, click **Add** next to a test, then **Close**.
**4. Check the scoring**
Each test lists what it measures, with score settings for this job req: which results earn which 1 to 5 score, and whether a result can knock a candidate out. Adjust them if this job needs a different bar.
**5. Save, then publish**
Set **Estimated Time (Minutes)** and click **Save Draft**; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

> [!TIP]
>
> Match the test to the job. A phone-based role needs speaking and listening; a chat or email role needs writing and reading. A Comprehensive test covers everything but takes candidates longer.
## What candidates see
* **The test opens from their application.** Hallo tests run inside the candidate's Journeyfront application. Emmersion tests take the candidate to Emmersion's site.
* **Device needs:** speaking tests need a microphone, and listening tests need speakers or headphones. Candidates may also be asked to allow camera access.
> [!TIP]
>
> Tell candidates ahead of time that they'll need a quiet place and a working microphone, and that their browser will ask for permission to use it.
## See a candidate's results
Open the candidate's Candidate Application and select the **Language** tab. It appears once the candidate has a language assessment. Depending on the partner, you'll see:
* An **overall score** and **CEFR** level, plus the partner's own score.
* Scores for each skill or part, such as fluency, grammar, pronunciation and vocabulary.
* A description of the candidate's level, and suggestions for what they can do to improve.
* The candidate's spoken and written responses to open questions, so you can listen and read for yourself.
The language assessment's score also appears on the **Score** and **Steps** tabs with the rest of the candidate's results.

### If the scores are missing
If the **Language** tab says the assessment is completed but scores are missing, click **Refresh Score** at the top of the tab to fetch them from the partner. If they still don't appear, contact Journeyfront support with a link to the Candidate Application.
## Language assessment dashboards
To see results across many candidates, use the **Language Assessment** dashboards:
* **For one job req:** open the job req, click the **Dashboard** tab, then **Language Assessment**. See [Job req dashboards](/reporting/job-dashboards).
* **Across your company:** click **Dashboard** in the top navigation and choose **Language Assessment** from the dashboard menu. See [Dashboards overview](/reporting/dashboards).
Each dashboard has two views. **Results Analysis** charts how many tests were taken, scores by partner, and how CEFR levels are spread, including how candidates at each level moved through your hiring process. **Language Results** lists every result, with the candidate, the step and activity where they took the test, the test name, their CEFR level and the partner's detailed scores. Use the **Controls** at the top to filter by dates, job req, step, test, candidate status, CEFR level or source.
> [!TIP]
>
> Use the **Language Results** view to compare CEFR levels with who you hired. If most of your hires sit at one level, that's a good guide for the score settings on your job reqs.
## FAQ
> [accordion] Why don't I see a language assessment in the workflow editor?
>
> No language assessment partner is turned on for your account yet. Language assessments are an add-on; ask your Customer Success Manager.
> [accordion] The candidate finished, but there are no results. What should I do?
>
> Results come from the partner. If the **Language** tab says the assessment is completed but scores are missing, click **Refresh Score**. If they still don't appear, contact support with a link to the Candidate Application.
> [accordion] Which languages can we test?
>
> It depends on the partner. With Hallo, the **Language** list in **Add Language Assessment** shows every language available for the assessment type you choose. With Emmersion, the test list shows what's available to your account.
> [accordion] Can a candidate retake a language assessment?
>
> Language assessment scores can't be deleted from the Candidate Application, so the usual retake option isn't available. Contact your Customer Success Manager if a candidate needs to take it again.
> [accordion] Does each test use a credit?
>
> Yes, language assessments use add-on credits. See [Add-ons and credits](/account-setup/add-ons).
> [accordion] What does CEFR mean?
>
> The Common European Framework of Reference for Languages, the global standard for language proficiency. A1 and A2 are beginner levels, B1 and B2 intermediate, and C1 and C2 proficient.
## Related
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> Check your language assessment credits.
> [card] [Job req dashboards](/reporting/job-dashboards)
>
> Language results for one job req.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Company-wide reporting, including language results.
> [card] [Assessments overview](/assessments/overview)
>
> Every assessment and what candidates need.
# Assessments overview
Source: https://help.journeyfront.com/assessments/overview
Every assessment you can add to a workflow, what it measures, what candidates need and where the results show up.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add assessments to a job req's workflow. Anyone who can open a Candidate Application can see the results.
>
> **Availability:** Language assessments and the System Requirements Test are add-ons, and skills tests are made available to your account by Journeyfront. Everything else is included. Ask your Customer Success Manager about add-ons.
Assessments are the activities in a job req's workflow that tell you whether a candidate can do the job: questions you write, tests of specific skills, and checks of a remote candidate's setup. Candidates complete them online as part of their application, and every result becomes a score your team can sort, filter and automate on. Mix and match them to fit each role.
## Choose an assessment
| Assessment | What it measures | Candidates need | Results | Availability |
| - | - | - | - | - |
| [Screening questions](/assessments/screening-questions) | Answers to your own questions: written, number, multiple choice, video, audio and more | Any device. A camera and microphone for video and audio answers. | **Screenings** tab | Included |
| [Typing test](/assessments/typing-test) | Typing speed (words per minute) and accuracy | A computer with a physical keyboard | **Steps** and **Score** tabs | Included |
| [Skills tests](/assessments/skills-tests) | Job-specific skills, in timed sections | Time to finish each timed section | **Steps** and **Score** tabs | Made available by Journeyfront |
| [Behavioral assessment](/assessments/behavioral-assessment) | Work-related traits, on its own or with a predictive model | No special equipment | **Assessments** tab | Included |
| [Language assessments](/assessments/language-assessments) | Speaking, writing, reading and listening, with a CEFR level | A microphone for speaking, speakers or headphones for listening | **Language** tab | Add-on, uses credits |
| [Internet speed test](/assessments/internet-speed-test) | Download and upload speed | The connection they'll work on | **Steps** and **Score** tabs | Included |
| [System requirements test](/assessments/system-requirements) | Computer hardware, software and connection against your requirements | A computer running Windows, macOS, Chrome OS or Linux | **Assessments** tab | Add-on |
Interviews are activities too, completed by your interviewers rather than the candidate. See [Set up an interview activity](/interviews/interview-activity).

## Add assessments to a workflow
Every assessment is added the same way, in the job req's workflow editor:
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Drag in the assessment**
Find the assessment in the building blocks on the left (use **Search** to find one quickly) and drag it into a step.
**3. Set it up**
Click the activity to set it up in the panel on the right. Each assessment's page covers its settings.
**4. Save, then publish**
Click **Save Draft** to save your changes; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).
Back on the Workflow page, each activity has three icons: the eye (**Preview Activity**) shows it the way a candidate sees it, the bolt (**Add Automation**) adds an automation rule that runs when a candidate completes it, and the bell (**Notify Users**) emails people when a candidate completes it. Partner language assessments can't be previewed. See [Build a workflow](/workflows/build) and [Activities you can add](/workflows/activities).
> [!TIP]
>
> Put quick, decisive assessments first and longer ones later. A short set of screening questions before a 30-minute test 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.
## How candidates take assessments
* **In their application.** Candidates see the activities in their current step and work through them in order, unless the job req allows them to take activities out of order. Your team, or an automation rule, moves them to the next step. (This is the job req's **Gate Steps** setting, on by default. See [Job settings](/job-reqs/job-settings).)
* **At their own pace.** Candidates can come back to their application between activities. If they leave screening questions partway, their answers are saved so they can pick up where they left off.
* **In their language.** Candidates can switch the page between English, Spanish and French. Your own questions and text appear as you wrote them.
> [!TIP]
>
> Tell candidates up front what they'll need: a computer and keyboard for a typing test, a quiet place and a microphone for a speaking test, the computer they'll work on for a speed or system test. A line in your invitation email saves a lot of "I'm stuck" messages later.
## Supported browsers
Candidates and your team should use an up-to-date version of **Chrome**, **Edge**, **Firefox** or **Safari**. Older browsers, such as Internet Explorer, aren't supported.
* **On an iPhone or iPad,** candidates need to use **Safari** to record video answers.
* **For video and audio answers and speaking tests,** the browser needs permission to use the camera and microphone. Candidates should allow it when asked.
## FAQ
> [accordion] A candidate says they're stuck. What should I check?
>
> * **Have they finished their current step?** Candidates only see the activities in their current step. Once those are done, they wait for your team or an automation rule to move them on. See [Move candidates through steps](/candidates/move-through-steps).
> * **Are they on the right device?** The typing test needs a physical keyboard, and the System Requirements Test needs a computer.
> * **Did they allow the camera and microphone?** Video and audio answers and speaking tests need both. On an iPhone or iPad, video answers need Safari.
> * **Is their browser up to date?** Ask them to update it, or try Chrome, Edge or Firefox, and refresh the page.
> * **Get Help:** if it's turned on for your account, candidates can click **Get Help** on their application, then **Scan & Fix Technical Issues**, to check their connection, camera, microphone and browser.
>
> If they're still stuck, contact Journeyfront support with the candidate's **Application ID** (on the Candidate Application's **Details** tab), the activity's name, the device and browser they're using, and a screenshot if they have one.
> [accordion] Why do screening questions keep coming back for a candidate?
>
> If some answers didn't save, for example a video that didn't upload, the candidate sees **Oops, something went wrong** and is asked to answer those questions again. If a video won't record, they should fully restart their browser and try again, or switch browsers.
> [accordion] A candidate finished, but their score is missing. What should I check?
>
> * **Answers waiting to be scored:** written, video, audio and some other answers are scored by your team unless the question uses AI scoring. Look for a **Score** button on the **Screenings** tab.
> * **Language assessments:** if the **Language** tab says scores are missing, click **Refresh Score**.
> * **System requirements:** **Error Getting Results** means Journeyfront is still retrying. After 48 hours, click **Retry**.
> * **Attribute scores:** an attribute only shows a score once it's in an attribute group on the job req. See [Attributes](/scoring/attributes).
>
> If a score is still missing, contact support with the candidate's **Application ID** and the activity's name.
> [accordion] Can a candidate take an assessment again?
>
> For most assessments, yes: someone with *Can Delete Scores* deletes the activity's score, and the candidate takes it again. See [Retakes and resetting scores](/assessments/retakes).
> [accordion] Can candidates see their results?
>
> Candidates see their typing speed and accuracy when they finish a typing test, and can open a report of their results after a skills test. After the behavioral assessment they can open a report on their own profile, unless your account is set up to hide it. They don't see the 1 to 5 scores your team uses.
> [accordion] Which assessments use credits?
>
> Language assessments use add-on credits. The System Requirements Test is also an add-on. See [Add-ons and credits](/account-setup/add-ons).
## Related
> [card] [Activities you can add](/workflows/activities)
>
> Every activity type, including interviews and offers.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw results and the Job Adaptive Score.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Where each result appears on the Candidate Application.
> [card] [Retakes and resetting scores](/assessments/retakes)
>
> Let a candidate take an assessment again.
# Retakes and resetting scores
Source: https://help.journeyfront.com/assessments/retakes
Let a candidate take an activity again by deleting its score, and how that differs from letting candidates re-apply to a job req.
> [!NOTE]
>
> **Who can do this:** Deleting an activity's score needs the *Can Delete Scores* permission. Turning on re-applying for a job req needs *Manage Job Req Settings*.
Sometimes a candidate deserves a second try: their connection dropped halfway through a timed question, their typing test glitched, or they started on the wrong device. Deleting the activity's score clears their results so they can take that activity again, on the same Candidate Application. That's different from letting someone **re-apply** to a job req later, which starts a whole new application.
## Two different kinds of retake
| | Delete an activity's score | Allow Re-Takes (re-applying) |
| - | - | - |
| **What it does** | Clears one activity's results so the candidate can take it again | Lets someone apply to the same job req again after a waiting period |
| **Where** | The Candidate Application's **Steps** tab | The job req's **Setup**, then **Configurations** |
| **Who** | *Can Delete Scores* | *Manage Job Req Settings* |
| **Result** | The same Candidate Application, with that activity starting over | A new Candidate Application |
| **Use it when** | Something went wrong during an activity | A past applicant should be able to try again in the future |
## Delete an activity's score
You can delete the score of screening questions, typing tests, behavioral assessments, internet speed tests and system requirements tests. Language assessment and skills test scores can't be deleted.
**1. Open the Steps tab**
Open the candidate's Candidate Application and select the **Steps** tab. Expand the step with the activity.
**2. Hover over the activity's score**
On the activity's row, hover over its score in the **Assessments** or **Screening Questions** column. It changes to **Delete Score**.
**3. Confirm**
Click **Delete Score**, then click **Yes** at **Delete?** (or **No** to keep the score).

### What happens when you delete a score
* **The activity's results are cleared.** Its scores show **NA**, and the candidate's other scores, including the overall score, are recalculated.
* **The activity starts over.** It goes back to not started, and the candidate can take it again from their application. They answer every question in the activity again, not just the one that went wrong, and any time limit starts fresh.
* **The application's status changes to Incomplete** until they finish.
* **It's recorded.** An **Activity Score Deleted** entry, with who did it, appears in the Candidate Application's activity history on the **Comments & Activities** tab.
Deleting a score doesn't send the candidate a message.
> [!TIP]
>
> Let the candidate know they can take the activity again, and what to do differently, like using a computer or a wired connection. Without a heads-up, most won't go back and look.
> [!WARNING]
>
> Deleting a score can't be undone. The candidate's answers and results for that activity are gone, so only delete a score when you want them to take the whole activity again.
### Give someone permission to delete scores
Go to **Settings**, then **Security**, edit the security role and turn on **Can Delete Scores** (in **Scores & Interviews**). See [Security roles](/account-setup/security-roles).
### Other ways to change a result
* **A single answer you scored by hand:** change or remove it on the **Screenings** tab, without resetting the activity. See [Reading a candidate's scores](/scoring/reading-scores#score-an-answer-yourself).
* **AI scores:** users with *Edit AI Scores* can change them. See [AI-scored questions](/scoring/ai-scored-questions).
* **Interview feedback:** someone with *Can Unlock Interviews* unlocks it so the interviewer can resubmit. See [Conduct an interview](/interviews/conduct-an-interview).
* **System requirements results that didn't arrive:** click **Retry** on the **Assessments** tab. See [System requirements test](/assessments/system-requirements).
## Let candidates re-apply to a job req
**Allow Re-Takes** lets someone who already applied to a job req apply to it again, after a waiting period you choose. It's off by default.
**1. Open the job req's configurations**
Open the job req and go to **Setup**, then **Configurations**.
**2. Turn on Allow Re-Takes**
In the **Candidate Experience** card, turn on **Allow Re-Takes**.
**3. Set the waiting period**
Enter **Days before re-apply**: how many days someone must wait after applying before they can apply again. It doesn't limit their first application.
**4. Save**
Click **Save** at the top of the page.

Once the waiting period has passed, the candidate sees a **Re-apply** link on that job's card in their applications. When they click it and confirm, a new application to the job req starts. Their earlier Candidate Application stays as it was. See [Job settings](/job-reqs/job-settings).
> [!TIP]
>
> Choose a waiting period long enough for someone to have actually built new skills or experience, so a quick re-apply doesn't just repeat the same result.
## FAQ
> [accordion] Can I delete the score for just one question?
>
> No. Deleting a score resets the whole activity, and the candidate answers all of its questions again. To change one answer's score instead, edit it on the **Screenings** tab if it was scored by hand.
> [accordion] Why don't I see Delete Score?
>
> Check three things: your security role needs *Can Delete Scores*; you need to hover over the activity's own score on the **Steps** tab, not a question or attribute row; and language assessments and skills tests can't be deleted.
> [accordion] Can a candidate retake an activity on their own?
>
> No. Once an activity is complete, the candidate can't restart it themselves. Deleting its score is what reopens it.
> [accordion] How do I let a candidate retake a language assessment or skills test?
>
> Their scores can't be deleted from the Candidate Application. Contact your Customer Success Manager.
> [accordion] Is Allow Re-Takes the same as deleting a score?
>
> No. **Allow Re-Takes** is about applying to the job req again after a waiting period, which starts a new Candidate Application. Deleting a score lets a candidate redo one activity on their current application.
> [accordion] Can I see who deleted a score?
>
> Yes. Every deletion is recorded as **Activity Score Deleted** in the activity history on the **Comments & Activities** tab, with who made the change.
## Related
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> The Steps, Score, Screenings and Assessments tabs.
> [card] [Job settings](/job-reqs/job-settings)
>
> Allow Re-Takes and other candidate experience settings.
> [card] [Security roles](/account-setup/security-roles)
>
> Give a role the Can Delete Scores permission.
> [card] [Assessments overview](/assessments/overview)
>
> Every assessment and what candidates need.
# Screening questions
Source: https://help.journeyfront.com/assessments/screening-questions
Ask candidates your own questions, score their answers consistently, and reuse questions with templates.
> [!NOTE]
>
> **Who can do this:** Adding screening questions to a job req needs the *Manage Job Req Settings* permission. Managing your company-wide question library and templates in **Settings** needs *Company Settings Access*. Editing a question candidates have already answered needs *Edit Locked Questions*. Anyone who can open a Candidate Application can score answers by hand.
Screening questions are the questions you write for candidates to answer online, like "How many hours a week can you work?" or "Tell us about a time you helped an upset customer." Each question measures an [attribute](/scoring/attributes), so every answer turns into a score you can sort, filter and automate on. Build a question once, and reuse it across job reqs on its own or as part of a template.
## Where screening questions live
| Where | What it's for |
| - | - |
| **Settings**, then **Measurements**, then **Screening Questions** | Your company-wide question library. Create, edit, clone and delete questions here. |
| **Settings**, then **Templates**, then **Screening Questions** | Saved sets of questions, with instructions, that you can drop into a job req in one go. |
| **Settings**, then **Templates**, then **Scoring Criteria** | Reusable answer options and scores, so similar questions are scored the same way. |
| A job req, under **Setup**, then **Workflow** | The screening questions activity candidates actually complete, in the step where it belongs. |
The same **Measurements** menu holds your other question and test libraries: **Interview Questions**, **Personal Assessments** (the [behavioral assessment](/assessments/behavioral-assessment)), **Typing Test** (see [Typing test](/assessments/typing-test)), and **Employee Questions**, **Job Assessments** and **Employee Performance**, which are used for current employees rather than candidates (see [Job profiles](/employees/job-profiles) and [Performance reviews](/employees/performance-reviews)).
## Create a screening question
**1. Open the question library**
Go to **Settings**, then **Measurements**, then **Screening Questions**, and click **Question**.
**2. Write the question**
Type the question as candidates will see it, then give it a short **Question Name** so your team can find it later.
**3. Choose the attribute**
Pick the attribute the question measures, such as *Availability* or *Customer Focus*. If it doesn't exist yet, click **Add Attribute** at the bottom of the list to create it.
**4. Choose the response type and scoring**
Pick how candidates answer (see the table below) and set up the answer options or scoring criteria. The **Live Preview** on the right shows the question the way candidates will see it.
**5. Set a time limit (optional)**
Turn on **Time Limit** and enter minutes and seconds to limit how long candidates have to answer. Time limits aren't available for video or audio answers.
**6. Save**
Click **Save**. The question is now in your library, ready to add to any job req or template.

### Response types
| Response type | Candidates... | How it's scored |
| - | - | - |
| **Multiple Choice** | Pick one option | Automatically, from the score you give each option (1 to 5). Options can be marked as knockouts. |
| **Number** | Enter a number | Turn on **AutoScore** to score answers automatically from the ranges you set, or leave it off to score them by hand. |
| **Ordering** | Put options in order | Automatically, by comparing their order with the **Ideal Order** you set |
| **Text** | Type a written answer | By your team, using your scoring criteria, or by [AI](/scoring/ai-scored-questions) |
| **Multi-Select** | Pick every option that applies | By your team |
| **Video Response** | Record a video answer | By your team, using your scoring criteria, or by [AI](/scoring/ai-scored-questions) |
| **Audio Response** | Record an audio answer | By your team, using your scoring criteria, or by [AI](/scoring/ai-scored-questions) |
| **File Upload** | Upload a file, such as a document or image | By your team. The question window lists the accepted file types. |
For **Number** answers you can also add **Placeholder Text**, the hint candidates see in the empty answer box.
### Scoring criteria and knockouts
For multiple choice questions, each option gets a **Score (1 - 5)** and a **Label**. For text, video and audio questions, the same table becomes your **scoring criteria**: a description of what a 1, a 3 or a 5 answer looks like, which your team (or AI) uses to score each answer consistently.
* Click **+ Option** to add a row, or drag rows to reorder them.
* Click **Templates** to fill the table from a saved scoring criteria template.
* On multiple choice questions, tick **Knockout** next to any option that rules a candidate out. Candidates who choose it are marked **KO** and rejected automatically, with the rejection reason *Auto rejected*.
> [!TIP]
>
> Use knockouts only for true requirements, like a required certification or the ability to work the shifts the job needs. Anything that's a preference rather than a deal-breaker works better as a low score, so a strong candidate isn't removed over one answer.
If your account has AI scoring, text, video and audio questions also show **Score with Ai**. See [AI-scored questions](/scoring/ai-scored-questions).
## Scoring criteria templates
Scoring criteria templates save a set of options and scores you use often, like a 1 to 5 comfort scale, so you don't rebuild it for every question.
**1. Open scoring criteria templates**
Go to **Settings**, then **Templates**, then **Scoring Criteria**, and click **Scoring Criteria**.
**2. Build the template**
Enter a **Template Name**. Click **+ Option** for each answer, then give it a **Score (1 - 5)** and a **Label**. Tick **Knockout** on any option that should rule a candidate out.
**3. Save**
Click **Save**. To use it, click **Templates** in a question's options table, then **Use Template**.
Templates provided by Journeyfront can be used but not edited or deleted. Use the edit and trash icons on your own templates to change or remove them.
## Edit, clone or delete a question
In **Settings**, then **Measurements**, then **Screening Questions**, each question has icons to **Clone**, **Edit** and **Delete** it. Search the list, or sort it by **Question Name** or **Question**. Expand a question to see its attribute and scoring criteria; knockout options are marked **KO**.
* **Edit:** opens the question window. Change it and click **Save**.
* **Clone:** confirm, and a copy named "(question name) - CLONE" opens, ready to change and save as a new question.
* **Delete:** confirm to remove the question from your library. The trash icon only appears on questions candidates haven't answered yet.
### Locked questions
Once candidates have answered a question, it's **locked**. The question window shows "question has been locked", and the question can't be changed or deleted. Locking keeps scores fair: every candidate on a job req answers the same question, scored the same way.
To change a locked question, clone it instead:
**1. Clone the question**
Click the **Clone** icon on the locked question and confirm. The copy isn't locked.
**2. Make your changes**
Edit the copy and click **Save**.
**3. Swap it into your job reqs**
On each job req that should use the new version, open the workflow editor, add the copy to the screening questions activity, remove the old question, then save and publish.
### Edit a locked question anyway
Users with the *Edit Locked Questions* permission can change a locked question in place, for small fixes like a typo. Open the question and click **Edit Anyway**. You can change the wording, name and scoring, but not the attribute or response type. When you click **Save**, Journeyfront asks you to confirm, because the change applies to everyone who has already answered and can't be undone. Click **Yes - Proceed** to save it.
> [!WARNING]
>
> Editing a locked question changes it for every candidate who already answered it. For anything more than a spelling or punctuation fix, clone the question instead.
To give someone this permission, go to **Settings**, then **Security**, edit their security role and turn on **Edit Locked Questions**. See [Security roles](/account-setup/security-roles).
## Screening question templates
A screening question template is a saved activity: a set of questions in order, plus the instructions and supporting content candidates see. Templates make it quick to set up job reqs that screen the same way.
**1. Create the template**
Go to **Settings**, then **Templates**, then **Screening Questions**, and click **Question Template**. Type a name and save it.
**2. Add instructions (optional)**
Expand the template. Under **Instructions** and **Supporting Content**, type what candidates should see, then click **Save**. See [Instructions and supporting content](#instructions-and-supporting-content).
**3. Add questions**
Click **Add Question to Template**. Search for a question and click **Add**, or click **Create New Question** to write one. Drag questions to put them in order.
To rename a template, click its name. To remove a question from a template, or delete the whole template, use its trash icon.
## Add screening questions to a job req
You add screening questions in the job req's workflow editor.
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft) to open the editor.
**2. Add the activity**
In the building blocks on the left, open **SCREENING QUESTIONS**. Drag **New Screening Questions** into the step where candidates should answer the questions to start from scratch, or click **Templates** to see your saved templates and drag one in instead. Click the eye icon on a template to preview its instructions and questions first.
**3. Add or change questions**
Click the activity to open its settings on the right. Under **Questions**, click **Add Question**, search for a question and click **Add**, or click **Create New Question**. Drag questions by their handle to change the order; use the pencil to edit a question or the trash icon to remove it.
**4. Name the activity and set the time**
Type the activity's name at the top of the panel, and set **Estimated Time (Minutes)** so candidates know how long it takes.
**5. Save, then publish**
Click **Save Draft** to save your changes; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

Turn on **Time Limit** in the activity's settings to give candidates only the **Estimated Time (Minutes)** to finish the whole activity. Anything unanswered when time runs out is submitted as not answered.
> [!TIP]
>
> Keep each screening activity short and focused. A handful of well-chosen questions early in the workflow does more than a long questionnaire, and candidates are far more likely to finish it, especially on a phone.
### Instructions and supporting content
A screening questions activity has two kinds of text, both in its settings panel in the editor. Both use a rich-text editor, so you can format them.
* **Instructions** are shown to candidates on their own page before they start. Candidates click **I'm Ready - Begin** to start answering. If you don't add instructions, candidates go straight to the first question.
* **Supporting Content** is shown alongside the questions while candidates answer, for anything they need to refer to, like a short scenario or policy.
Teams use instructions to explain how to answer, what kind of questions are coming, and whether there's a time limit. When you start from a template, its instructions and supporting content come with it, and you can change them for this job req.
## Score answers by hand
Text, multi-select, video, audio and file upload answers, and number answers without AutoScore, wait for someone on your team to score them, unless the question uses AI scoring.
**1. Open the Screenings tab**
Open the candidate's Candidate Application and select the **Screenings** tab.
**2. Compare the answer with the criteria**
Find the answer. The **Attributes and Scoring Criteria** column shows the attribute and what each score means.
**3. Enter the score**
Click **Score**, enter a number from 1 to 5 and click **Save**. The candidate's scores, including the overall score, update right away.
To change or remove a score you entered, use the edit or trash icon under it. For more on this tab, see [Reading a candidate's scores](/scoring/reading-scores#score-an-answer-yourself).
> [!TIP]
>
> When several people score the same question, agree on what a 3 looks like before you start. Clear scoring criteria on the question do most of this work for you.
## What candidates see
* **Instructions first,** if you added them, then **I'm Ready - Begin**.
* **One question at a time,** with your supporting content alongside. A timer shows when the activity or question has a time limit.
* **Video and audio questions** ask for camera and microphone access. On an iPhone or iPad, candidates need to use Safari to record video.
* **A final check** before they submit their answers.
* **Leave and come back:** if they leave partway, their answers are saved so they can pick up where they left off.
* **Their language:** candidates can switch the page between English, Spanish and French. Your questions appear as you wrote them.
## FAQ
> [accordion] Why can't I edit or delete a question?
>
> It's locked because candidates have already answered it. Clone it and edit the copy, or, if you have *Edit Locked Questions*, click **Edit Anyway** for a small fix. Locked questions can't be deleted.
> [accordion] Why did a candidate skip straight to the questions?
>
> The activity has no **Instructions**. Open the workflow editor (**Setup**, then **Workflow**, then **Create New Version** or **Edit Draft**), click the activity, add **Instructions**, then save and publish. Candidates will see them before the first question.
> [accordion] Can one screening question measure more than one attribute?
>
> No. Each screening question measures one attribute. To measure several, write a question for each.
> [accordion] Why is an answer showing NA or a Score button?
>
> It's waiting for someone to score it. Text, multi-select, video, audio and file upload answers are scored by your team unless the question uses AI scoring. Open the **Screenings** tab and click **Score**.
> [accordion] What happens when a time limit runs out?
>
> With a time limit on the activity, anything the candidate hasn't answered when time runs out is submitted as not answered. Set the limit with the activity's **Estimated Time (Minutes)** and **Time Limit** switch in the workflow editor.
> [accordion] Can a candidate answer the questions again?
>
> Yes, if someone with *Can Delete Scores* deletes the activity's score. The candidate then answers every question in the activity again. See [Retakes and resetting scores](/assessments/retakes).
> [accordion] Where do I find interview questions?
>
> In **Settings**, then **Measurements**, then **Interview Questions**, with interview templates under **Settings**, then **Templates**. See [Interview guides](/interviews/interview-guides).
## Related
> [card] [AI-scored questions](/scoring/ai-scored-questions)
>
> Let AI score video, audio and written answers.
> [card] [Attributes](/scoring/attributes)
>
> What each question measures, and how much it counts.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Find answers and scores on the Candidate Application.
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities to a job req.
# Skills tests
Source: https://help.journeyfront.com/assessments/skills-tests
Check the job-specific skills a role needs, with timed tests built and maintained by Journeyfront.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add a skills test to a job req. Anyone who can open a Candidate Application can see the results.
>
> **Availability:** Skills tests are made available to your account by Journeyfront. Ask your Customer Success Manager which tests you can use, or to request one.
Skills tests check whether a candidate can do specific parts of the job, before anyone spends time on an interview. Journeyfront builds and maintains each test, so you don't write questions or answer keys yourself. Each test is split into timed sections, and candidates get a short report of their results when they finish.
## How a skills test is organized
* **Type and version:** each skills test has a type, the skill it covers, and one or more versions. When you add a test, its latest version is used unless you choose another.
* **Sections:** the test is split into sections. Each section has its own instructions and time limit.
* **Practice questions:** some sections start with practice questions, so candidates can get used to the format before the timed part begins.
* **Difficulty and estimated time:** shown for each test, so you can pick the right one and tell candidates how long it takes.
## Add a skills test to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Preview the tests available to you**
In the building blocks on the left, open **SKILLS TESTS**. Each skills test type available to your account is listed. Click its eye icon to see the version, difficulty, description, instructions and sections before you add it.
**3. Add the test**
Drag the skills test into the step where candidates should take it. Its latest version is added.
**4. Check the details**
Click the activity to open its settings on the right. You can rename it at the top; the name stays if you switch versions. You'll also see the **Skills Test Type**, the version (labeled **Version 1**, **Version 2** and so on; choose another here if you need to), the **Difficulty**, the **Estimated Time**, the test's instructions (click to expand) and a list of its sections with their time limits. Under **Scoring**, each section has score settings for this job req.
**5. Preview the questions (optional)**
Click **Preview questions** under the sections. A panel slides out with each section's questions as cards, the correct answers marked. Click **Show instructions** to read a section's instructions.
**6. Save, then publish**
Click **Save Draft** to save your changes; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

If the **SKILLS TESTS** group is empty, no skills tests are available to your account yet. Ask your Customer Success Manager.
> [!TIP]
>
> Check the **Estimated Time** before you add a skills test, and put it in a step on its own if it's long. Candidates are more likely to finish a longer test when they know how much time to set aside.
## What candidates see
1. **Section instructions,** with the section's time limit.
2. **Practice questions,** if the section has them: **Start Practice Question**, then **I'm Ready - Begin** when they're ready for the real thing.
3. **The timed section.** When it ends, they see **Section Completed** and **Continue to Next Section**.
4. **A finish screen** after the last section, with **View Report** and **Continue to Next Step**. The report shows their overall test score and how they did in each section.
> [!TIP]
>
> Tell candidates how long the test takes and that sections are timed, in the step name or in the message that invites them. A quiet place and a steady internet connection give them the best chance to show what they can do.
## See the results
Open the candidate's Candidate Application and select the **Steps** or **Score** tab. The skills test's score appears with the rest of the candidate's results, in the **Assessments** column. See [Reading a candidate's scores](/scoring/reading-scores).
## FAQ
> [accordion] Can we write our own skills test?
>
> Skills tests are built and maintained by Journeyfront. For your own questions, use [screening questions](/assessments/screening-questions). To ask about a new skills test for your roles, contact your Customer Success Manager.
> [accordion] Why don't I see any skills tests in the editor?
>
> None have been made available to your account yet. Ask your Customer Success Manager which skills tests fit your roles.
> [accordion] Can a candidate retake a skills test?
>
> Skills test scores can't be deleted from the Candidate Application, so the usual retake option isn't available. Contact your Customer Success Manager if a candidate needs to take a skills test again.
> [accordion] Which version should I use?
>
> The latest version, unless you need to match results from an older job req. You can switch versions in the activity's settings in the workflow editor.
> [accordion] Do candidates see their results?
>
> Yes. When they finish, they can open a report with their overall score and how they did in each section.
## Related
> [card] [Assessments overview](/assessments/overview)
>
> Every assessment and what candidates need.
> [card] [Screening questions](/assessments/screening-questions)
>
> Write your own questions and score the answers.
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities to a job req.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw results and the Job Adaptive Score.
# System requirements test
Source: https://help.journeyfront.com/assessments/system-requirements
Confirm a remote candidate's computer and internet connection meet your requirements before they go further.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add the test to a job req. Anyone who can view a candidate's Candidate Application can see the results.
>
> **Availability:** The System Requirements Test is an add-on. Ask your Customer Success Manager to turn it on and set up your requirement sets.
For remote and bring-your-own-device roles, the System Requirements Test checks a candidate's computer and connection for you. The candidate runs a short diagnostic, and you get a pass or fail on every requirement, using real values from their machine instead of screenshots or self-reported answers. Turn on knockout, and candidates whose setup can't do the job leave the process before they spend time on assessments or interviews.
[System Requirements Test overview](https://www.youtube.com/embed/5R05ljw9-i0)
## What it checks
The checks depend on the requirement set you choose. They can include:
* Operating system and version
* Processor, memory (RAM) and free disk space
* Graphics card, video memory and sound card
* Number of monitors
* Internet download and upload speed, latency, and whether the candidate is on Wi-Fi or a wired connection
* Country and state or region
Once the add-on is on your account, there's no limit on how many tests you can run.
## Requirement sets
A requirement set defines what to check and what counts as good enough. A single set can:
* Cover several operating systems (Windows, macOS, Chrome OS and Linux), with its own values for each.
* Have a **Minimum** level, what the job needs, and a **Recommended** level, the ideal setup.
* Mark each requirement as **Pass/Fail**, which counts toward the score and knockout, or **Information Only**, which is collected for visibility but doesn't affect the score.
You can use a **standard** requirement set with common defaults for Windows, macOS and Chrome OS, or have a **custom** set built for your roles. Many teams have several sets, such as one for entry-level customer service roles and a higher-spec one for video-heavy work.
### Request a custom requirement set
**1. Ask your Customer Success Manager**
Let them know which roles need a custom set.
**2. Fill in the Configuration Worksheet**
Your Customer Success Manager shares a worksheet. For each requirement, give the minimum and recommended values and say whether it's **Pass/Fail** or **Information Only**.
**3. Wait for the set to go live**
Your Customer Success Manager lets you know when it's on your account. This usually takes one to two weeks.
**4. Add it to your job reqs**
Follow the steps below to start using it.
> [!TIP]
>
> Request custom sets early in your rollout so they're ready before your first hiring push. To change a set later, ask your Customer Success Manager. Changes apply to future tests only; candidates who already took the test keep their results.
## Add the test to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, drag **System Requirements Test** into the step where you want to check candidates' tech. The **Choose a requirement set** panel slides out.
**3. Choose a requirement set**
Your account's requirement sets are listed on the left, with the operating systems each supports. Click a set to see its **Minimum** and **Recommended** values, using the tabs to switch between operating systems, then click **Use this set**. The draft can't be saved until you choose one.
Later, the activity's **Requirement Set** section shows the set you picked. Click **View or change** to open the panel again. Once a version is saved with the activity, you can view its set but not switch it; to use a different set, add a new System Requirements Test.

**4. Set scoring and knockout**
Check the **Instructions** (click to expand) and the **Scoring** section, and adjust scoring and knockout (below).
**5. Save and publish**
Click **Save Draft**, then **Publish** when you're ready. See [Publish workflow changes](/workflows/publish).
The default candidate instructions already tell candidates to take the test on a computer, not a phone. You can add anything specific to your process on the activity.
> [!TIP]
>
> Put the test early in the workflow, right after the application. Candidates whose setup won't work find out quickly, before they invest time in longer assessments or interviews.
## Set scoring and knockout
After you choose a requirement set, the activity's **Scoring** section shows a row for each result: **Requirements Not Met**, **Minimum Requirements Met** and **Recommended Requirements Met**. Each result gives the candidate a Job Adaptive Score on the 1 to 5 scale, so it sits alongside the rest of the workflow. You can change the score for **Minimum Requirements Met** if this job needs a different bar.
The **Knockout** checkbox on a row decides what happens to candidates with that result:
* **Checked:** they're rejected automatically, with the rejection reason **Auto rejected**.
* **Unchecked:** they're scored and stay in the process for your team to review.
> [!TIP]
>
> New to the test? Leave **Knockout** off for a few weeks and watch how candidates score. Turn it on once you're confident the requirements fit your roles.
The score counts toward the candidate's overall score and works with filters and automation rules, just like any other activity.
## Review a candidate's results
**1. Open the Assessments tab**
Open the candidate's Candidate Application and select the **Assessments** tab.
**2. Expand the test**
Expand the System Requirements Test. You'll see the overall result, **PASS RECOMMENDED**, **PASS MINIMUM** or **FAIL**, and the Job Adaptive Score.
**3. Check each requirement**
The table lists every requirement checked. The candidate's actual values, their raw results, appear under **Your System**, next to your minimum values (**Requirements**) and recommended values (**Recommendations**). The **Min** and **Rec** columns show a pass, fail or information-only mark for each level.

> [!TIP]
>
> The breakdown makes follow-up easy. A candidate who failed only because they're on Wi-Fi when the role needs a wired connection may be one cable away from passing. **Information Only** requirements appear in the table but never affect the score.
If results don't come back right away, the test shows **Error Getting Results**. Journeyfront keeps trying automatically for 48 hours, and you can click **Retry** to fetch the results again at any time.
## What candidates see
* **Instructions first.** The test appears as an activity in their application, with instructions to use a computer rather than a phone.
* **A quick scan.** They click **Continue**, download and open a small file that checks their computer, and a short diagnostic runs, usually in under two minutes. There's nothing to type.
* **A clear finish.** They come back to Journeyfront, see the test marked complete, and can continue to the next step.
* **No waiting around.** If results are still processing, they're told their test was received and they can carry on. Journeyfront keeps checking for the results.
* **A way to retry.** If the score can't be calculated, they see a message asking them to try again, with a **Try Again** button.

## FAQ
> [accordion] Can candidates take the test on a phone or tablet?
>
> No. The test only runs on a computer with Windows, macOS, Chrome OS or Linux. The default instructions tell candidates this before they start.
> [accordion] A candidate sees "Failed to calculate score." What should they do?
>
> Ask them to click **Try Again** on the same computer and let the scan finish without closing the window. Until a scan completes, the activity stays **In Progress**, so they can retry as many times as they need. If it keeps failing, contact support with a link to the candidate's Candidate Application.
> [accordion] What if a candidate closes the window before the scan finishes?
>
> The activity stays **In Progress**. They can open it again and restart the test. Only a completed scan produces a score.
> [accordion] The results say Error Getting Results. What does that mean?
>
> The candidate finished the test, but the results haven't come back yet. Journeyfront retries automatically for 48 hours. If retries stop, click **Retry** on the Candidate Application.
> [accordion] How is this different from the Internet Speed Test?
>
> The Internet Speed Test only checks download and upload speed. The System Requirements Test checks the whole setup, hardware, software and network, against a requirement set. You can use both in the same workflow.
> [accordion] Can one requirement set cover several operating systems?
>
> Yes. One set can hold separate values for Windows, macOS, Chrome OS and Linux. Most teams keep all their supported systems in one set.
> [accordion] What happens if we change a requirement set after candidates have taken the test?
>
> Candidates who already took the test keep their results. The new values apply to tests taken after the change goes live.
> [accordion] Is there a limit on how many tests we can run?
>
> No. Once the add-on is on your account, run it on as many candidates and job reqs as you like.
## Related
> [card] [Add-ons](/account-setup/add-ons)
>
> Turning on add-ons for your account.
> [card] [Workflows overview](/workflows/overview)
>
> Where activities like this fit in a job req's workflow.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores and the Job Adaptive Score.
# Typing test
Source: https://help.journeyfront.com/assessments/typing-test
Measure typing speed and accuracy with your own text. Candidates need a computer and a physical keyboard.
> [!NOTE]
>
> **Who can do this:** Creating typing tests in **Settings** needs *Company Settings Access*. Adding a typing test to a job req needs the *Manage Job Req Settings* permission. Anyone who can open a Candidate Application can see the results.
The typing test measures how fast and how accurately a candidate types, in words per minute and percent accuracy. You write the text candidates type and choose how long the test runs, so the test reflects the work. Results arrive as soon as the candidate finishes, alongside the rest of their scores.
## Create a typing test
Your typing tests live in your company settings, ready to add to any job req.
**1. Open your typing tests**
Go to **Settings**, then **Measurements**, then **Typing Test**. The list shows each test's **Name**, **Duration**, **Used On** and **Is Active**.
**2. Add a test**
Click **Test**. A new row appears. Type a **Name** and set the **Duration** in minutes and seconds.
**3. Add the text**
Expand the row and type or paste the passage into **Text to Type**.
**4. Turn it on and save**
Set **Is Active** to **Yes**, then click **Save**. Only active tests can be added to job reqs.

To change a test, edit its row and click **Save**. To remove one, click its trash icon and confirm. You can only delete a test that isn't used on any job req; otherwise, set **Is Active** to **No** so it can't be added anywhere new.
> [!TIP]
>
> Use text that looks like the job: a customer note, an order summary or a short email, rather than random words. Candidates who'll type that kind of text all day give you a more realistic result, and they get a preview of the work. Make the passage long enough that your fastest typists won't reach the end before time runs out, since the test also ends when the text does.
## Add a typing test to a job req
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, open **TYPING TEST** and drag **New Typing Test** into the step where candidates should take it.
**3. Choose the test**
Click the activity to open its settings on the right. Under **Typing Tests**, click **Add Typing Test**, then click **Add** next to the test you want in **Select Typing Test to Add**. You can add more than one; candidates take them one after another.
**4. Check the scoring**
Each test shows **Typing Speed** and **Typing Accuracy**, with score settings for this job req: which results earn which 1 to 5 score, and whether a result can knock a candidate out. Adjust them if this job needs a different bar.
**5. Save, then publish**
Set **Estimated Time (Minutes)** and click **Save Draft**; you stay in the editor. When you're ready for candidates to see it, click **Publish**. See [Publish workflow changes](/workflows/publish).

The raw results stay the same on every job req; how they turn into a score depends on what each job needs. See [How scoring works](/scoring/how-scoring-works).
## What candidates see
* **A computer check.** On a phone or small tablet, candidates first see **Mobile Device Detected**: the test is meant for a computer with a full keyboard, and the on-screen keyboard doesn't work for it. They can **Go Back** or **Continue Anyway** with an attached keyboard.
* **Instructions,** then **Begin Typing Test**. The text appears in light grey and they type over it, pressing the space bar to move to the next word. Correct letters turn black, mistakes turn red, and they can use backspace to fix errors as they go.
* **A timer that starts when they start typing,** and runs for the duration you set.
* **Their result.** When time runs out, or they reach the end of the text, they see their **WPM** and **Accuracy**, then **Next Typing Text** if there's another test, or **Continue to Next Step**.
> [!TIP]
>
> Mention the computer and keyboard requirement in the message that invites candidates to apply, and in the step's name or instructions. It's the most common reason candidates get stuck on a typing test.
## See the results
Open the candidate's Candidate Application and select the **Steps** or **Score** tab. The typing test shows a score for **Typing Speed** and **Typing Accuracy**, with the raw result under each: words per minute and percent accuracy. See [Reading a candidate's scores](/scoring/reading-scores).
## FAQ
> [accordion] Can candidates take the typing test on a phone?
>
> Only with a physical keyboard attached. The on-screen keyboard is turned off for the test, and phones and small tablets show a warning before it starts. A computer works best.
> [accordion] When does the timer start?
>
> When the candidate starts typing, not when the page opens. They can read the instructions first without losing time.
> [accordion] A candidate had a problem during the test. Can they take it again?
>
> Yes. Someone with *Can Delete Scores* can delete the typing test's score on the **Steps** tab, and the candidate can then take it again from their application. See [Retakes and resetting scores](/assessments/retakes).
> [accordion] Why can't I delete a typing test in Settings?
>
> It's used on at least one job req (see **Used On**). Set **Is Active** to **No** instead, so it can't be added to new job reqs.
> [accordion] Why isn't my typing test in the Add Typing Test list?
>
> Only active tests are listed. In **Settings**, then **Measurements**, then **Typing Test**, set its **Is Active** to **Yes** and click **Save**.
> [accordion] Do candidates see their score?
>
> They see their words per minute and accuracy when they finish each text. They don't see the 1 to 5 score your team uses.
## Related
> [card] [Assessments overview](/assessments/overview)
>
> Every assessment, what it measures and what candidates need.
> [card] [Retakes and resetting scores](/assessments/retakes)
>
> Let a candidate take a test again.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw results and the Job Adaptive Score.
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities to a job req.
# Add a candidate to another job req
Source: https://help.journeyfront.com/candidates/add-to-another-job
Consider a candidate for a different role, and reuse the results they've already earned.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the candidate. You can add candidates to the job reqs you have access to: the ones you're on, or every job req if your security role has *All Job Req Access*.
A strong candidate who wasn't the right fit for one role may be perfect for another. **Add to Job Req** gives them a new Candidate Application on a different job req without them having to apply again. You can also bring over their screening answers and test results, so they don't repeat work they've already done.
The original application stays exactly as it is. Details about the person, like contact information, personal fields and resume, are shared automatically because they belong to the [Candidate Profile](/candidates/profiles-and-applications).
## Add or move?
Adding is for starting something new, outside the candidate's current hiring process. Both applications stay on file, each with its own status. Teams add candidates to:
* Invite past candidates, including rejected or withdrawn ones, to apply for a new opening.
* Consider someone for a second role while they stay in the first.
* Keep a rejection on record: reject the candidate on the first job req, then add them to one that fits better.
If the new job req is the next step in the candidate's current process and they should only be in one place, [move them](/candidates/move-to-another-job) instead. Moving closes the original application with a **Moved** status, which isn't counted as a rejection, and places them at the step you choose. For a side-by-side comparison, see [Move or add to another job req?](/candidates/move-to-another-job#move-or-add-to-another-job-req)
> [!TIP]
>
> After you add someone, remember both applications are open. Once they're hired or placed on one job req, close the other one yourself, since Journeyfront doesn't close it for you.
## Add one candidate
**1. Open Add to Job Req**
On the Candidate Application or the Candidate Profile, click **Actions**, then **Add to Job Req**. The **Add Candidates to Other Job Req** window opens.
**2. Choose the job req**
Pick a job req under **Add to Job Req**. The list shows the job reqs you have access to, newest first. Inactive and archived job reqs aren't listed.
**3. Choose whether to email them**
Tick **Send email inviting candidates to complete the application steps** to send the candidate a link to continue.
**4. Transfer results (optional)**
Under **Transfer Data**, click **Check for Transferrable Data** and choose what to bring over. See [Transfer results to the new application](#transfer-results-to-the-new-application).
**5. Click Add to Job Req**
Click **View in Job Req** to open the new Candidate Application.

## Add several candidates at once
**1. Select the candidates**
On the **Candidates** page or a job req's **Candidates** tab, tick the boxes next to the candidates. They can come from different job reqs.
**2. Click Add to Other Req**
**Add to Other Req** is in the actions bar above the list.
**3. Choose the job req and options**
Pick the job req, and tick **Send email inviting candidates to complete the application steps** if you want to email them. To bring over everyone's earlier results, tick **Transfer all applicable data from each candidate's previous applications**.
**4. Click Add to Job Req**
If some candidates were already on that job req, the results list them under **Already in Job Req** next to the ones under **Added Candidates successfully**.
If you selected two rows for the same person (two of their applications), they're added once.
## Transfer results to the new application
Journeyfront looks at the activities in the new job req's workflow and finds results the candidate already has from their other applications in your account. Matching results can be copied over, so those activities are complete on the new application from the start.
| Activity | What counts as a match |
| - | - |
| **Screening Questions** | An answer to the same question from your question library |
| **Typing Test** | A result from the same typing test |
| **Language Test** | A result from the same language assessment |
| **Internet Speedtest** | A result from the same internet speed test |
| **System Requirements Test** | A result from the same system requirements test |
**For one candidate**, you choose exactly what to copy:
1. Click **Check for Transferrable Data**. If nothing matches, you'll see "No candidate information is available to transfer to this job req."
2. Matching results are listed under each step of the new workflow, grouped by activity. Each one shows when it was completed and which job req it came from, plus the result, such as typing speed and accuracy, a language level, or download and upload speeds.
3. The most recent result for each item is ticked for you. If the candidate has more than one, the item shows how many **Older Options Found**; click it to expand and pick a different one.
4. Untick anything you want the candidate to do again.
**For several candidates**, **Transfer all applicable data from each candidate's previous applications** copies every matching result for each person, using their most recent result.
Activities that aren't in the table, like interviews, offers and onboarding forms, start fresh on the new application. Skills tests the candidate already completed are marked complete for them.
> [!TIP]
>
> Transfer results when the requirement really is the same, like a typing test for two similar roles. When a role needs a fresh look, such as a different language level or a newer version of a test, untick it and let the candidate take it again.
## What the new application looks like
* It starts at the beginning of the new job req's workflow, with its own step, status and scores.
* Transferred activities are already complete, and their scores count toward the new job req.
* Your team can see both applications from the candidate's **Currently Viewing** menu and on their Candidate Profile.
* If you ticked the email option, the candidate gets an email with a link to continue the new application.
## Add candidates automatically
An automation rule can add candidates to another job req for you, for example sending everyone from one region to that region's job req, with or without their results. See the **Add to Other Job Req** action in [Automation rules](/workflows/automation-rules).
## FAQ
> [accordion] Should I add this candidate or move them?
>
> Add them when you're starting something new, like inviting a past candidate to a new opening, or when you want both applications on file. Move them when the new job req is the next step in their current process and the first application should close. See [Move or add to another job req?](/candidates/move-to-another-job#move-or-add-to-another-job-req)
> [accordion] Can I add a candidate who was rejected?
>
> Yes. Adding works whatever the status of their earlier application, and that application keeps its rejection. This is how teams invite past candidates to new openings.
> [accordion] The candidate was hired on one job req. What happens to their other application?
>
> Nothing changes automatically. It stays open on the other job req, so close it if they're no longer being considered there.
> [accordion] Why isn't a job req in the list?
>
> The list only shows job reqs you have access to, and leaves out inactive and archived ones and the job req the candidate is already on. Ask your Journeyfront admin to add you to the job req's team, or activate it first.
> [accordion] What happens to the candidate's original application?
>
> Nothing. It keeps its step, status and scores. Each application moves through its own workflow from here on.
> [accordion] Why were some candidates listed under Already in Job Req?
>
> They already have an application on that job req, so a second one wasn't created. Open their existing application on that job req instead.
> [accordion] Can I pick which results to transfer when I add several candidates?
>
> No. For a group, it's all matching results or none. To choose item by item, add candidates one at a time.
> [accordion] Why didn't a screening answer transfer even though the question looks the same?
>
> Answers transfer when both job reqs use the same question from your question library. A question that was written separately on each job req, even with identical wording, doesn't match.
> [accordion] Can a candidate I add this way see their earlier answers?
>
> Transferred activities show as complete for the candidate, so they don't see them as tasks to do again.
> [accordion] Can I transfer results when I add someone with Add New Candidate?
>
> Yes. When the email belongs to someone already in Journeyfront who isn't on this job req, the **Add New Candidate** window shows the same **Transfer Data** section. See [Add candidates](/sourcing/add-candidates).
## Related
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> One person, many applications.
> [card] [Move a candidate to another job req](/candidates/move-to-another-job)
>
> Close the first application and continue on the new job req.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to a group of candidates.
> [card] [Automation rules](/workflows/automation-rules)
>
> Add candidates to other job reqs automatically.
> [card] [Assessments overview](/assessments/overview)
>
> The tests whose results can transfer.
# Bulk actions
Source: https://help.journeyfront.com/candidates/bulk-actions
Act on many candidates at once: change step, email, assign, hire and more.
> [!NOTE]
>
> **Who can do this:** Anyone who can see the candidates. Some actions need a permission in your security role, listed below.
When you're hiring at volume, you rarely want to open candidates one at a time. Select a group on the **Candidates** page or a job req's **Candidates** tab, and an actions bar appears above the list with everything you can do to all of them at once.
## Select candidates
Tick the box next to each candidate, or tick the box in the header to select every candidate on the current page. The actions bar shows how many you've selected. Click the box on the left of the bar, or the **x** on the right, to clear your selection.

> [!TIP]
>
> Filter first, then select. A saved view like "Completed assessments, not yet moved" turns a daily task into: open the view, tick the header box, click **Change Step**. See [The Candidates page](/candidates/candidates-page).
## All bulk actions
| Action | What it does | Permission needed | Shows when |
| - | - | - | - |
| **Compare** | Opens a side-by-side comparison of scores. See [Compare and merge](/candidates/compare-and-merge). | None | 2 to 5 candidates, same job req and workflow version |
| **Merge** | Combines two records of the same person. See [Compare and merge](/candidates/compare-and-merge). | None | Exactly 2 candidates |
| **E-mail** | Emails everyone, from scratch or with a template. See [Email candidates](/communication/email-candidates). | *Send Emails* | Any selection |
| **Delete** | Removes the selected Candidate Applications. See [Delete candidates](#delete-candidates). | *Delete Applicants* | Any selection |
| **Reject** | Rejects everyone with one reason. See [Reject candidates](/candidates/reject). | None | Same job req |
| **Change Step** | Moves everyone to a step, with optional invites, onboarding forms and offers. See [Move candidates through steps](/candidates/move-through-steps). | None | Same job req and workflow version |
| **Send Offers** | Creates and sends offers for the group. See [Send offers in bulk](/offers/bulk-send). | *View and Send Offers* | Same job req and workflow version |
| **Hire** | Hires the group in one go. See [Bulk hire](/onboarding/bulk-hire). | *Hire Candidates* | Up to 100 candidates, from any job reqs |
| **Mark as New** | Sets everyone's status to **New**. | None | Every selected candidate is **Active** |
| **Add to Other Req** | Adds everyone to another job req, with or without their results. See [Add a candidate to another job req](/candidates/add-to-another-job). | None | Any selection |
| **Assign User** | Assigns everyone to a user who can be assigned on that job req, or unassigns them. See [Candidate assignment](/workflows/candidate-assignment). | None | Same job req |
| **Message** | Texts everyone. Needs text messaging set up for your account. See [Text messages](/communication/text-messages). | *Send Messages* | Any selection |
| **Assign Class** | Puts everyone in a hiring class, or removes them from one. See [Hiring classes](/hiring-classes/overview). | None | Same job req |
When you message a group, candidates without a phone number, or who aren't opted in to texts, are skipped. Journeyfront offers to email them instead.
### Assign AI agents in bulk
To assign an AI agent to a group of candidates, switch the job req's **Candidates** tab to the classic layout with **Back to Classic**, select the candidates and click **Assign AI Agent**. It appears when AI agents are turned on for your account, your security role has *Assign AI Agents*, and at least one agent is active. See [AI agents](/workflows/ai-agents).
## Why some actions disappear
The actions bar only shows what you can do to *everyone* you selected.
* **Across job reqs.** On the **Candidates** page you can select candidates from different job reqs. **Reject**, **Change Step**, **Send Offers**, **Compare**, **Assign User** and **Assign Class** then disappear, because each job req has its own workflow, team and hiring classes. Narrow your selection to one job req, or work from that job req's **Candidates** tab.
* **Across workflow versions.** When a job req's workflow changes, candidates who applied earlier stay on the version they started with. **Change Step**, **Send Offers** and **Compare** need everyone on the same version. Add the **Job Version** column with **Edit Columns** to see who's on which, and act on each group separately.
* **Over the bulk hire limit.** **Hire** stays visible but is greyed out when you select more than 100 candidates. Hover over it to see why.
* **Permissions.** Actions that need a permission don't appear at all without it. Ask your Journeyfront admin to check your security role. See [Security roles](/account-setup/security-roles).
> [!TIP]
>
> On the **Candidates** page, add the **Job Req** column and filter to one job req before selecting. Every action is then available, and you can't accidentally mix candidates from different roles.
## Delete candidates
> [!WARNING]
>
> Delete is for applications that shouldn't exist, like test records or duplicates added by mistake. To turn a real candidate down, **Reject** them instead, so the decision and its reason stay in your reports.
**1. Select the candidates**
Tick the candidates whose applications you want to remove.
**2. Click Delete**
The **Remove Candidate(s)** window asks you to confirm.
**3. Click Yes**
The applications disappear from the job req and from your candidate lists.
Deleting removes the Candidate Application, not the person. Their Candidate Profile and any applications to other job reqs stay. If you delete an application by mistake, open that job req's **Actions** menu, click **Add New Candidate**, enter the person's email and click **Recover deleted application**. See [Recover a deleted application](/sourcing/add-candidates#recover-a-deleted-application).
## On a hiring class
The candidate list on a hiring class has a shorter actions bar: **E-mail**, **Delete**, **Reject**, **Change Step**, **Hire**, **Assign User** and **Message**, with the same permissions as above.
## FAQ
> [accordion] Why don't I see Reject or Change Step?
>
> Your selection probably includes candidates from more than one job req, or from different versions of the workflow. See [Why some actions disappear](#why-some-actions-disappear).
> [accordion] Why don't I see Delete, E-mail, Message, Send Offers or Hire?
>
> Each of these needs a permission in your security role: *Delete Applicants*, *Send Emails*, *Send Messages*, *View and Send Offers* or *Hire Candidates*. Ask your Journeyfront admin.
> [accordion] How do I select more than one page of candidates?
>
> The header checkbox selects the candidates on the current page. Show more rows per page at the bottom of the list, or narrow your filters so everyone fits on one page.
> [accordion] What happens to hired candidates in a bulk reject?
>
> They're skipped. To reverse a hire, use **Un-Hire** on the Candidate Application. See [Hire candidates](/onboarding/hire-candidates#un-hire-a-candidate).
> [accordion] Can I undo a bulk action?
>
> Most bulk actions can be reversed one candidate at a time: un-reject, change the step back, reassign, or remove from a class. Merges can't be undone. Deleted applications can be recovered one at a time, as described in [Delete candidates](#delete-candidates).
## Related
> [card] [The Candidates page](/candidates/candidates-page)
>
> Filter, sort and save views before you act.
> [card] [Move candidates through steps](/candidates/move-through-steps)
>
> Change Step and its moving actions.
> [card] [Bulk hire](/onboarding/bulk-hire)
>
> Hire a whole group at once.
> [card] [Security roles](/account-setup/security-roles)
>
> The permissions behind each action.
# The Candidate Application
Source: https://help.journeyfront.com/candidates/candidate-application
Everything about one candidate in one job req, tab by tab.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team, or anyone whose security role has *All Job Req Access*. Some actions need their own permission, noted below.
>
> **Availability:** The **Fraud** and **AI Tasks** tabs only appear when those features are turned on for your account. Ask your Customer Success Manager.
The Candidate Application is one candidate's progress through one job req: their scores, answers, interviews, offer and history, all on one screen. It's where you review a candidate, move them forward and take action. If the same person applies to another job req, that's a separate Candidate Application, and all of them roll up into their [Candidate Profile](/candidates/profiles-and-applications).
## Open a Candidate Application
* **From a list:** on the **Candidates** page or a job req's **Candidates** tab, click the candidate's name. The Candidate Application opens in a side panel, so you can review candidate after candidate without losing your place. See [The Candidates page](/candidates/candidates-page#open-a-candidate).
* **In its own page:** in the side panel, click the **Open in a new tab** icon, or Ctrl-click (Cmd-click on a Mac) the candidate's name in the list.
* **From the Candidate Profile:** click a row on the **Applications** tab.
In the side panel, use the up and down arrows (or Alt or Option plus the up or down arrow key) to move to the previous or next candidate in your list, and press Esc to close it.

## The header
The top of the Candidate Application tells you who the candidate is and where they stand.

* **Name and contact details.** The LinkedIn icon next to the name opens the candidate's LinkedIn profile, when they gave one. Icons next to the phone number open text messages and calling, if your team uses them.
* **Currently Viewing.** Switch to the person's [Candidate Profile](/candidates/profiles-and-applications) or to any of their other Candidate Applications and jobs.
* **Applied** date and **status**, such as Active, Hired (with the start date) or Rejected (with the date and rejection reason), and the candidate's fraud risk level. See [Fraud flags](/candidates/fraud-flags).
* **Score.** The candidate's overall score for this job req. See [How scoring works](/scoring/how-scoring-works).
* **Current Step.** The step the candidate is in. Pick another step to move them. See [Move candidates through steps](/candidates/move-through-steps).
If the person is flagged, or matches someone flagged, a red banner appears above the header. See [Do Not Hire](/candidates/do-not-hire).
## The Actions menu

| Action | What it does |
| - | - |
| **Hire** | Hires the candidate. Needs the *Hire Candidates* permission. See [Hire candidates](/onboarding/hire-candidates). |
| **Reject** | Rejects the candidate with a reason. Rejected candidates show **Un-reject** instead. See [Reject candidates](/candidates/reject). |
| **Move** | Moves the candidate to another job req. See [Move a candidate to another job req](/candidates/move-to-another-job). |
| **Un-Hire** | Reverses a hire. Needs the *Hire Candidates* permission. |
| **Email** | Emails the candidate. Needs the *Send Emails* permission. See [Email candidates](/communication/email-candidates). |
| **Message** | Texts the candidate, when they have a phone number. Needs the *Send Messages* permission. See [Text messages](/communication/text-messages). |
| **Call** | Calls the candidate, when your account has calling set up. See [Calling](/communication/calling). |
| **Interview** | Opens the candidate's interviews so you can start or continue an interview guide. See [Conduct an interview](/interviews/conduct-an-interview). |
| **Share** | Emails a link to this Candidate Application to teammates. See [Share and print](/candidates/share-and-print). |
| **Add to Job Req** | Adds the candidate to another job req. See [Add a candidate to another job req](/candidates/add-to-another-job). |
| **Send to** your ATS | Appears when your account is connected to another applicant tracking system. See [ATS integrations](/integrations/ats). |
| **Mark Do Not Hire** | Flags the person so your team doesn't hire them again. On someone already flagged, it reads **Remove Do Not Hire**. See [Do Not Hire](/candidates/do-not-hire). |
| **Print All Data** | Prints the candidate's scores, steps, screenings, notes, resume and assessments. See [Share and print](/candidates/share-and-print). |
## The tabs
The tabs appear in this order. When the window is too narrow to show them all, the rest move into a **More** menu at the end of the row.
| Tab | What you'll find | When it appears |
| - | - | - |
| **Score** | Scores by attribute, so you can see the candidate's strengths and gaps for this job. | Always |
| **Steps** | Every step and activity in the job req's workflow, with the candidate's progress and scores. | Always |
| **Screenings** | Each screening question, the candidate's response and its score. You can score questions that aren't scored automatically. | Always |
| **Notes** | Interviewers' notes and scores from each interview. | Always |
| **Resume** | The candidate's resume, with **Download**, print and full-screen options. If there's no resume, click **Upload Resume**. | Always |
| **Assessments** | Behavioral assessment results and system requirements check results. | Always |
| **Language** | Language assessment results. | When the candidate has a language assessment |
| **Comments & Activities** | Your team's comments and the full history: emails, texts, calls, step changes and more. | Always |
| **Details** | Application details, contact details, custom fields, documents, work and education history, and the **Application ID** and **User ID**. | Always |
| **Offer** | The candidate's offer, documents and e-signature status. | Always. It shows an offer card for each Offer activity in the workflow. |
| **Onboarding** | The candidate's onboarding forms, and background checks when the job req has a background check activity. | Always. It lists the Onboarding activities in the workflow. |
| **Fraud** | What fraud detection found for this application. | When fraud detection is on for your account |
| **AI Tasks** | AI agents assigned to this candidate and the tasks waiting for your review. | When AI agents are on for your account and set up |
Click through the tabs below to see each one on a sample candidate. This candidate has no language assessment, so the **Language** tab doesn't appear.
> [tab] Score
>
> 
> [tab] Steps
>
> 
> [tab] Screenings
>
> 
> [tab] Notes
>
> 
> [tab] Resume
>
> 
> [tab] Assessments
>
> 
> [tab] Comments & Activities
>
> 
> [tab] Details
>
> 
> [tab] Offer
>
> 
> [tab] Onboarding
>
> 
> [tab] Fraud
>
> 
> [tab] AI Tasks
>
> 
Each tab has its own guide:
* **Score**, **Steps** and **Screenings:** [Reading scores](/scoring/reading-scores) and [How scoring works](/scoring/how-scoring-works).
* **Notes:** [Interview notes](/interviews/interview-notes).
* **Comments & Activities:** [Comments and activity](/candidates/comments-and-notes).
* **Resume:** [AI resume scoring](/scoring/ai-resume-scoring), if your account uses it.
* **Assessments** and **Language:** [Assessments overview](/assessments/overview) and [Language assessments](/assessments/language-assessments).
* **Details:** [Edit candidate details](/candidates/edit-details).
* **Offer:** [Send an offer](/offers/send-offers).
* **Onboarding:** [Onboarding forms](/onboarding/onboarding-forms).
* **Fraud:** [Fraud flags](/candidates/fraud-flags).
* **AI Tasks:** [AI agents](/workflows/ai-agents#review-and-approve), for reviewing and approving what agents do, and [assigning agents](/workflows/ai-agents#assign-candidates) to the candidate.
> [!TIP]
>
> Review a new candidate from left to right: **Score** for the big picture, **Steps** for where they are, then **Screenings** and **Resume** for the detail. Leave a comment with your decision so the next person doesn't start from scratch.
> [!NOTE]
>
> Users whose security role has *Can Delete Scores* can delete an activity's score on the **Steps** tab with **Delete Score**. Language assessment and skills test scores can't be deleted.
## FAQ
> [accordion] How do I see a candidate's LinkedIn profile?
>
> Click the LinkedIn icon next to the candidate's name at the top of the Candidate Application or Candidate Profile. It only appears when the candidate gave a LinkedIn URL. To ask every candidate for one, go to the job req's **Setup**, then **Application Form**, and set the LinkedIn field to **Required**. See [Application form](/job-reqs/application-form).
> [accordion] Why don't I see the Fraud or AI Tasks tab?
>
> Those tabs only appear when the feature is turned on for your account. The **AI Tasks** tab also needs at least one AI agent set up, or tasks for this candidate. Ask your Customer Success Manager.
> [accordion] Why don't I see the Language tab?
>
> It appears when the candidate has language assessment results. For some language assessments, it appears as soon as the assessment is part of the candidate's workflow, and shows a **Refresh Score** button if a completed assessment's scores haven't arrived yet.
> [accordion] Where did some of the tabs go?
>
> On a narrower screen, tabs that don't fit move into the **More** menu at the end of the tab row. A number on **More** means a tab inside it has something waiting, such as AI tasks to review.
> [accordion] Where do I find the Application ID?
>
> On the **Details** tab, in the **Application Details** card. The **User ID** is in the **Personal Details** card. Both have a copy button. See [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications#user-id-and-application-id).
> [accordion] Why can't I hire this candidate?
>
> **Hire** only appears in **Actions** for users whose security role has *Hire Candidates*, and only while the candidate isn't already hired or rejected.
> [accordion] Can candidates see any of this?
>
> No. The Candidate Application, including scores, comments and notes, is only visible to your team.
## Related
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> The person versus their application to one job req.
> [card] [The Candidates page](/candidates/candidates-page)
>
> Find candidates and open them in the side panel.
> [card] [Edit candidate details](/candidates/edit-details)
>
> Update contact details and custom fields.
> [card] [Share and print](/candidates/share-and-print)
>
> Send a Candidate Application to a teammate or print it.
# The Candidates page
Source: https://help.journeyfront.com/candidates/candidates-page
Search, filter, edit and export candidates across every job req you can access, all from one list.
> [!NOTE]
>
> **Who can do this:** Everyone on your hiring team. You see candidates on the job reqs you're on, or on every job req if your security role has *All Job Req Access*.
The Candidates page is where you work your pipeline. Every row is one Candidate Application, so you can search, filter, sort and act on candidates without opening them one at a time. Save the views you use every day and they're one click away.
## Open the Candidates page
Click **Candidates** in the top navigation. The page opens on **All Candidates**: every Candidate Application on the job reqs you can access. Your saved views sit in tabs next to it.

Each job req also has its own **Candidates** tab with the same list and tools, showing only that job req's candidates.
> [card] [The tabs on a job req](/job-reqs/overview#the-tabs-on-a-job-req)
>
> Open a job req to work its candidates by status and step.
## Search
Type in the search box (**Search by name, email, or phone**) and press Enter. Search works together with your filters and the tab you're on.
## Filter
Click **Filters** (1) to open the filter bar (2). These filters are always there:
* **Job Req**
* **Current Step**
* **Activity Status**
* **Status**
* **Hiring Class**
* **Assigned User**
* **Rejection Reasons**

Click **More** (3) to add any other filter. You can search the list, which includes:
* **Default Fields:** **Sources**, **Source Types**, **Fraud Risk Levels**, **Country**, **State/Region**, **City**, **Zip/Postal Code**, **Date Applied**, **Overall score**, **Time in Current Step**, **Unread Messages**, **Do Not Hire**, **Hired Date**, **Start Date**, **Date of Birth**, and **AI Resume Score** when AI resume scoring is on for your account.
* **Personal Fields** and **Application Fields:** your account's [custom fields](/account-setup/custom-fields#personal-application-and-employee-job-fields).
* Scores: **Activity Score**, **Attribute Score**, **Attribute Groups**, **Assessment Raw Score** and **Predictive Model Scores**.
* **Screening Questions:** filter by how candidates answered a specific question.
The **Date Applied** filter has quick ranges, like the past 7 days, that keep rolling forward in a saved view. The **Filters** button shows how many filters are applied. Open a filter to change it, click **Clear Filter** to empty it, or click **Remove Filter From Bar** to take it off the bar.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Set up the personal and application fields you filter and sort by.
## Choose your columns
Click **Edit Columns** to choose what the list shows.

**1. Open Edit Columns**
The left side lists every column you can add, grouped into sections you can expand. The right side, **Selected Columns**, shows what's in the list now.

**2. Add or remove columns**
Tick a column on the left to add it, or click the **x** next to a column on the right to remove it. Use **Search Columns** to find one quickly.
**3. Reorder**
Drag columns up or down in **Selected Columns**. **Name** and **Email** always come first and can't be moved or removed.
**4. Save**
Click **Save**. The list updates right away.
The list starts with **Name**, **Email**, **Phone Number**, **Job Req**, **Assigned User**, **Date Applied**, **Activity Status**, **Step**, **Status** and **Overall Score**. You can also add:
* **Default Fields** such as **Source**, **Source Type**, **Time in Step**, **Other Applications**, **Hiring Class**, **Job Version**, **Interview**, **Date Completed**, **Rejection Reason**, **Fraud Risk Level**, address and location fields, **Hired Date**, **Start Date**, **Date of Birth**, **Do Not Hire** and **Do Not Hire Reason**.
* **Personal Fields** and **Application Fields** from your account's [custom fields](/account-setup/custom-fields#personal-application-and-employee-job-fields).
* Scores: **Attributes Scores**, **Activities Scores**, **Attribute Group**, **Assessment Raw Score** (such as typing speed) and **Predictive Model Scores** when your job reqs use them.
* **Screening Questions:** one column per question, showing each candidate's answer.
* **Job Req Fields** and **Hiring Class Fields:** values from the candidate's job req or hiring class.
* **Offer Fields:** values from the candidate's offer details.
Some columns only appear when the feature is on for your account, like **AI Resume Score**.
You can also drag a column header to move it, drag its edge to resize it, and click a sortable header to sort.
> [!TIP]
>
> Fields marked private only show their values to users whose security role has *Private Data Access*.
## Saved views
A saved view remembers your filters, columns and sort order as a tab across the top of the list. Set up the list, click **Save as New View**, name it and click **Save**. You can share a view with your whole organization or with specific people, and add views your teammates shared from the **+** at the end of the tabs. See [Saved views](/lists-and-exports/saved-views) for everything you can do with them.
Changed the columns or filters on **All Candidates** itself? Click **Save Changes** and that tab keeps your layout. Click **Reset to Default** to go back to the standard one.
> [card] [Saved views](/lists-and-exports/saved-views)
>
> Create, share and organize views, including views on a job req.
> [!TIP]
>
> When you're hiring at volume, build a view for each part of your day: for example "New today" (filtered on **Date Applied**), "Ready to interview" (filtered on **Current Step**) and "Waiting on me" (filtered on **Assigned User**). Make the one you check first your default, and share the ones your whole team works from.
## Open a candidate
Click a candidate's name (1) to open their Candidate Application in a side panel without leaving the list.
* Use the up and down arrows (2) on the side of the panel to move to the previous or next candidate in your list. With the keyboard, hold Alt (Option on a Mac) and press the up or down arrow. The number below the buttons shows where you are in the list.
* Click the **Open in a new tab** icon (3) to open the full page.
* Press Esc or click the **x** (4) to close the panel. The list refreshes with any changes you made.

To skip the panel, Ctrl-click (Cmd-click on a Mac) a name to open the Candidate Application in a new browser tab. See [The Candidate Application](/candidates/candidate-application).
## Edit right in the list
You can change some values without opening the candidate. Hover over a cell and click the pencil to edit it, for example **Phone Number**, **Source**, **Hiring Class**, **Step**, the location columns and most custom field columns. Make the change and click **Save**.

* Changing **Step** or **Hiring Class** opens the same window you'd use for a group of candidates.
* Personal values like phone number and location update the person on all of their Candidate Applications.
* **Name** and **Email** can't be edited in the list. Change them on the Candidate Application's **Details** tab. See [Edit candidate details](/candidates/edit-details).
## Act on a group of candidates
Tick the boxes next to candidates to show the actions bar: **Compare**, **Merge**, **E-mail**, **Reject**, **Change Step**, **Send Offers**, **Hire**, **Assign User**, **Message** and more. Some actions need a permission or only work when everyone you selected is on the same job req.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Every action in the bar, and when it appears.
## Export
Click **Actions**, then **Export Data**, to download the list exactly as you see it: your current tab, search, filters and columns.
**1. Click Actions, then Export Data**
The **Export Data** window shows the view, and how many rows and columns the file will have (1).
**2. Name the file and choose a format**
Change the **Export File Name** if you like, then choose **CSV** or **Excel** under **File Format** (2).
**3. Click Start Export**
Click **Start Export** (3). Most files download right away.

Excel exports are limited to 10,000 rows. For more than that, choose CSV: Journeyfront prepares the file in the background and emails you when it's ready. See [Export data](/lists-and-exports/export-data) for other reports.
## FAQ
> [accordion] Why does the same person appear more than once?
>
> Each row is a Candidate Application, so someone who applied to two job reqs has two rows on the Candidates page. Add the **Other Applications** column to see who has applied elsewhere. See [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications).
> [accordion] Why can't I find a candidate?
>
> Check the tab you're on and your filters first; **All Candidates** with no filters shows everything you can access. You only see candidates on job reqs you're on, unless your security role has *All Job Req Access*.
> [accordion] Can my teammates see my saved views?
>
> Only if you share them. Views start as **Only me**. To share one, open it and click **Actions**, then **Edit View**, and change **Who can see this**. See [Share a view](/lists-and-exports/saved-views#share-a-view).
> [accordion] How do I change which view opens first?
>
> Open the view, click **Actions**, then **Edit View**, turn on **Make Default** and click **Save**.
> [accordion] How do I find candidates flagged Do Not Hire?
>
> Add the **Do Not Hire** filter from **More**, or add the **Do Not Hire** and **Do Not Hire Reason** columns with **Edit Columns**. See [Do Not Hire](/candidates/do-not-hire).
> [accordion] Why did my export arrive by email?
>
> Exports over 10,000 rows are prepared in the background, and Journeyfront emails you when the file is ready. Exports this large are CSV only.
> [accordion] Can I filter by how candidates answered a screening question?
>
> Yes. Click **Filters**, then **More**, and choose the question under **Screening Questions**. You can also add the question as a column with **Edit Columns**.
## Related
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Everything about one candidate in one job req.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Act on many candidates at once.
> [card] [Compare and merge candidates](/candidates/compare-and-merge)
>
> Side-by-side scores, and cleaning up duplicates.
> [card] [Export data](/lists-and-exports/export-data)
>
> Get your hiring data out of Journeyfront.
# Comments and activity
Source: https://help.journeyfront.com/candidates/comments-and-notes
Leave comments for your team and see a candidate's full activity history.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team. To see and add comments, your security role needs *View & Submit Comments*.
Comments keep your team on the same page about a candidate: why you moved them forward, what to ask in the interview, what you decided. Journeyfront also records everything that happens to a candidate, like emails, texts, calls and step changes, so you never have to piece the story together. Candidates never see comments or the activity history.
There are two places to look:
| Where | What it shows |
| - | - |
| The Candidate Application's **Comments & Activities** tab | Comments and activity for this application |
| The Candidate Profile's **Activity Feed** tab | Comments and activity from all of the person's applications in one timeline |
## Add a comment
**1. Open the Comments & Activities tab**
Open the Candidate Application and click **Comments & Activities**.
**2. Write your comment**
Type in the **Make a comment** box.
**3. Click Publish**
Your comment appears at the top of the list with your name and the time.

Everyone on the job req's hiring team with *View & Submit Comments* can read it. Each comment shows where it was added: on the Candidate Application, or during an interview, labeled with the interview's name.
> [!TIP]
>
> When you make a call on a candidate, like moving them past a fraud flag or rejecting them after an interview, add a one-line comment saying why. The next recruiter sees your reasoning instead of starting over.
## Edit, hide or delete your comment
Click the **...** menu next to a comment you wrote:
* **Edit Comment:** change the text and click **Update**.
* **Hide on Interview Guide:** comments you add on the Candidate Application also show to interviewers on the candidate's interview guides. Hide a comment to keep it on the Candidate Application only. An eye icon marks hidden comments. Click **Show on Interview Guide** to undo.
* **Delete Comment:** removes it after you confirm. This can't be undone.
You can only change your own comments.
## Comments during an interview
Interviewers can leave comments while they conduct an interview, in the **Comments** panel on the right side of the interview guide. Click the comment icon to open or close the panel. Comments added there appear on the Candidate Application's **Comments & Activities** tab, labeled with the interview's name. See [Conduct an interview](/interviews/conduct-an-interview).
## The activity history
The **Comments & Activities** tab also lists everything that happened on this application, newest first, such as:
* Emails sent, with the template, sender, recipient, subject and message (click **Read More** for the full email)
* Text messages and calls, including call recordings and transcripts when your calling provider supplies them
* Step changes, shown as the old step and the new step
* Source, assigned user and hiring class changes
* Rejections, hires and Do Not Hire flags
* Documents uploaded or deleted
Use the **All**, **Comments** and **Activities** buttons to narrow the list, and **Search activities** to find something by person or text. Actions taken by an AI agent are marked with the agent's avatar.
## The Candidate Profile's Activity Feed
The Candidate Profile's **Activity Feed** tab brings together comments and activity from every one of the person's Candidate Applications. Each item is labeled with the job req it came from.
Comments you add on the **Activity Feed** belong to the person, not to one application, and are labeled "Candidate Profile". Use them for notes that matter for every role, like "Prefers evening shifts". See [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications).
## FAQ
> [accordion] Can candidates see comments?
>
> No. Comments and the activity history are only visible to your team.
> [accordion] Why can't I see or add comments?
>
> Your security role needs *View & Submit Comments*. Without it, the **Comments & Activities** tab only shows activity. Ask an admin to check your role. See [Security roles](/account-setup/security-roles).
> [accordion] Can I edit or delete someone else's comment?
>
> No. Only the person who wrote a comment can edit, hide or delete it.
> [accordion] Where do interviewers' comments go?
>
> Comments added in an interview guide's **Comments** panel show on the Candidate Application's **Comments & Activities** tab, labeled with the interview's name. Interviewers' notes on each question are on the **Notes** tab. See [Interview notes](/interviews/interview-notes).
> [accordion] Do comments carry over to the candidate's other applications?
>
> No. A comment on a Candidate Application stays with that application. To read comments from all of the person's applications in one place, open their Candidate Profile's **Activity Feed**.
## Related
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
> [card] [Interview notes](/interviews/interview-notes)
>
> What interviewers recorded on each interview guide.
> [card] [Email candidates](/communication/email-candidates)
>
> Emails you send are logged in the activity history.
> [card] [Share and print](/candidates/share-and-print)
>
> Send a Candidate Application to a teammate.
# Compare and merge candidates
Source: https://help.journeyfront.com/candidates/compare-and-merge
Compare candidates side by side, and merge duplicate records into one.
> [!NOTE]
>
> **Who can do this:** Anyone who can see the candidates on the Candidates page or a job req's **Candidates** tab. You can only compare or merge candidates on job reqs you have access to.
**Compare** puts two to five candidates for the same job req side by side, so you can see who's strongest at a glance. **Merge** cleans up duplicates: when one person ends up with two records, for example because they applied with two different email addresses, you combine them into one.
## Compare candidates
**1. Select the candidates**
On the **Candidates** page or a job req's **Candidates** tab, tick the boxes next to two to five candidates on the same job req.
**2. Click Compare**
**Compare** appears in the actions bar above the list.
**3. Review the comparison**
The comparison shows each candidate's **Overall Score**, then a table of scores. Use the dropdown above the table to switch between **Scores By Attributes Measured** and **Scores By Screening Steps**, and expand a row for more detail.

Click **Back to All Candidates** when you're done.
**Compare** only appears when:
* You've selected at least two and no more than five candidates.
* They're all on the same job req.
* They're all on the same version of the job req's workflow. If the workflow changed after some candidates applied, they may be on an older version. Add the **Job Version** column with **Edit Columns** to check.
> [!TIP]
>
> Compare the finalists for a role before your hiring decision meeting. Switching to **Scores By Screening Steps** shows where each candidate did well or struggled in your process, which makes for a sharper conversation.
## Merge duplicate candidates
> [!WARNING]
>
> A merge can't be undone. Check that the two records really are the same person before you start.
**1. Select the two records**
On the **Candidates** page, search by name or phone number to find both records, then tick one row for each. Each row is a Candidate Application, so make sure the two rows come from the two different records, not two applications of the same record.
**2. Click Merge**
**Merge** appears in the actions bar when exactly two candidates are selected.
**3. Read the warning and click I understand**
The **Merge Users** window explains what will happen.
**4. Choose the primary record**
The **Primary User** column is the record you keep. The **Duplicate User** column is merged into it. Click **Switch Users** if they're the wrong way round. The primary record's email address is the one that stays.
**5. Review each application and job**
Each row shows how a job req application or employee job will be handled:
* **MERGE:** both records have one for the same job req or job, so they're combined into the primary's.
* **MOVE:** only the duplicate has one, so it moves to the primary as it is.
For employee jobs, you can switch a row between **Merge** and **Move**.
**6. Click Merge Users**
Journeyfront merges the records and recalculates the primary's scores.

> [!TIP]
>
> Make the record with the email address the candidate uses now the primary. That's the address they'll sign in with, and the one your emails go to.
### What a merge keeps
| | What happens |
| - | - |
| Email address | The primary's email stays. The duplicate's email isn't copied. |
| Other personal details | The primary's details stay. Anything the primary is missing, like a phone number, secondary email or date of birth, is filled in from the duplicate. |
| Custom personal fields | Same rule: the primary's values stay, and empty fields are filled in from the duplicate. |
| Resume | If the primary has no resume, the duplicate's resume moves over. Otherwise the primary's is kept. |
| Applications to job reqs only the duplicate applied to | They move to the primary, unchanged. |
| Applications to the same job req | They're combined into the primary's application. Interviews, screening question answers, interview answers, typing tests and language results that the primary's application doesn't have are copied over. When both have the same interview, the primary's is kept. The duplicate's application is then removed. |
| Assessments | Assessments the primary hasn't taken are copied from the duplicate. |
| Employee jobs set to **Merge** | Combined into the primary's job record. Job fields and performance records the primary doesn't have are copied over, and the duplicate's job record is removed. |
| Employee jobs set to **Move** | Moved to the primary as they are. The primary may end up with two job records in the same job profile. |
Only records in your account are merged. Anything the person has with another company that uses Journeyfront isn't touched.
## Merge employee records
You can also merge two employee records:
**1. Open the job profile**
Click **Profiles** in the top navigation and open the job profile. The **Employees** tab lists its employees.
**2. Select the two records and click Merge**
Tick the boxes next to the two records, then click **Merge**.
**3. Follow the same steps**
Read the warning, click **I understand**, check the **Primary User** and **Duplicate User**, and click **Merge Users**.
If the two rows are two job records of the same person, the window is titled **Merge Employee Job Records** and combines the job records instead. See [Employee records](/employees/employee-records).
## FAQ
> [accordion] Why don't I see Compare?
>
> Compare needs two to five candidates, all on the same job req and the same version of its workflow. Check how many you selected, and add the **Job Req** and **Job Version** columns to spot the odd one out.
> [accordion] Why don't I see Merge?
>
> Select exactly two candidates. **Merge** doesn't appear for one, or for three or more.
> [accordion] Can I undo a merge?
>
> No. Merging is permanent, so check both records carefully before you click **Merge Users**.
> [accordion] How do duplicates happen?
>
> Most often a candidate applies again with a different email address, or a teammate adds or imports someone who's already in Journeyfront under another email. Searching by phone number is a quick way to find them.
> [accordion] What if both records have an interview for the same job req?
>
> If both have the same interview, only the primary's is kept. Interviews only the duplicate has are copied to the primary's application.
> [accordion] Does merging affect the candidate's applications at other companies?
>
> No. Only records in your account are merged.
## Related
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> One person, many applications.
> [card] [The Candidates page](/candidates/candidates-page)
>
> Find, select and act on candidates.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Every action you can take on a group of candidates.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What the scores in a comparison mean.
# Do Not Hire
Source: https://help.journeyfront.com/candidates/do-not-hire
Flag a person your company shouldn't hire, so everyone on your team sees the warning.
> [!NOTE]
>
> **Who can do this:** Anyone on your team who can open the candidate or employee can set or remove the flag.
The **Do Not Hire** flag marks a candidate or employee as not eligible to be hired again. Once someone is flagged, a red banner appears on their Candidate Profile, on every one of their Candidate Applications and on their employee profile, so no one on your team misses it. Journeyfront also warns you when a new applicant's email or phone number matches someone you flagged, even if they apply with a different account.
It's built for teams that rehire often, through seasonal peaks, program changes and people moving between roles, and need one reliable record of who shouldn't come back. No spreadsheets, no relying on memory.
[Do Not Hire flag](https://www.youtube.com/embed/WaUQP6GlXPs)
## Flag a candidate or employee
**1. Open the record**
Open the person's Candidate Application, Candidate Profile or employee profile.
**2. Choose Mark Do Not Hire**
Click **Actions**, then **Mark Do Not Hire**.

**3. Add a reason and confirm**
Enter a **Reason** if you'd like, then click **Confirm**.

> [!TIP]
>
> Add a reason every time, even a short one. It shows on the banner and in the hire warning, so the next recruiter understands the decision without having to track you down.
When you confirm, Journeyfront:
* Shows a red **Do Not Hire** banner at the top of the person's records, with the reason, who set the flag and when.
* Saves the person's email addresses and phone number so it can recognize them if they apply again.
* Records the change in their activity history.

The flag belongs to the person, not to a single application, so it appears on every Candidate Application they have in your account.
If a reason is longer than 80 characters, the banner shortens it. Click **View full note** to read the whole reason along with who set the flag and when.
## Remove the flag
Open any of the person's records and click **Actions**, then **Remove Do Not Hire**. Click **Remove Flag** to confirm.
The banner disappears, the saved email addresses and phone number are cleared, and the removal is recorded in the activity history.
## Catch people who reapply
When you flag someone, Journeyfront saves their primary email, their secondary email (if they have one) and their phone number. When anyone in your account applies with one of those details, their banner shows which detail matched (email or phone number), links to the person you flagged, and shows who flagged them and when. The reason appears in the hire warning.
Because both email addresses are saved, a former employee whose main email was changed to a work address is still recognized if they reapply from their personal email.

## The hire warning
When you click **Hire** on the Candidate Application of someone who is flagged, or who matches a flagged person, a **Warning: Do Not Hire** message appears before the hire starts. It shows the reason and links to the matching record.
Click **Proceed** to continue with the hire or **Cancel** to stop. The warning makes sure the hire is reviewed; it doesn't block it.
> [!NOTE]
>
> The warning appears only when you hire from a Candidate Application. Hiring several candidates at once from a candidate list doesn't show it, so check the **Do Not Hire** column first.

> [!TIP]
>
> Decide ahead of time who is allowed to approve hiring a flagged person. A recruiter who sees the warning then knows exactly who to ask before clicking **Proceed**.
## Find flagged people on the Candidates page
On the **Candidates** page, or a job req's **Candidates** tab, click **Edit Columns** to add the **Do Not Hire** and **Do Not Hire Reason** columns, or filter by **Do Not Hire**. The filter includes people you flagged directly and people whose contact details match someone you flagged.
## Import flags in bulk
When you import candidates into a job req (**Actions**, then **Import Candidates**), your file can include two optional columns. See [Import candidates](/sourcing/import-candidates#columns).
| Column | Values | What it does |
| - | - | - |
| `do_not_hire` | `true`, `yes` or `1` | Flags the person during the import |
| `do_not_hire_reason` | Any text | The reason shown on the banner |
Each flagged row saves the person's contact details for matching and adds an activity entry under the name of the person who ran the import. If someone is already flagged, or their contact details already match a flagged person, the import leaves things as they are. Files without these columns import exactly as before.
## Activity history
Every flag and removal is recorded. You'll find it on the Candidate Application's **Comments & Activities** tab and the Candidate Profile's **Activity Feed** tab. Each entry shows the action (Marked Do Not Hire or Do Not Hire Removed), who made the change (for an import, the person who ran it), and the reason when one was given.
## FAQ
> [accordion] Does the flag stop someone from applying?
>
> No. Flagged people can still apply. Your team sees the banner on their records and a warning if anyone tries to hire them.
> [accordion] Is a reason required?
>
> No, but it's strongly recommended. The reason is what tells the rest of your team why the person was flagged.
> [accordion] Can the flag be removed?
>
> Yes. Anyone who can set the flag can remove it with **Actions**, then **Remove Do Not Hire**. The removal is recorded in the activity history.
> [accordion] Does the flag carry across job reqs?
>
> Yes. The flag is on the person, so it shows on every Candidate Application they have in your account.
> [accordion] What if the person's email was changed to a work email?
>
> Journeyfront saves both the primary and the secondary email when you set the flag. If their personal email was moved to the secondary email field, it's still used to recognize them.
> [accordion] Can candidates see that they're flagged?
>
> No. The flag, the banner and the reason are only visible to your team.
> [accordion] Can I flag many people at once?
>
> Yes. Add a `do_not_hire` column to your CSV import file, with an optional `do_not_hire_reason` column. See [Import flags in bulk](#import-flags-in-bulk).
## Related
> [card] [Fraud flags](/candidates/fraud-flags)
>
> Spot applications that need a closer look.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
# Edit candidate details
Source: https://help.journeyfront.com/candidates/edit-details
Update a candidate's name, contact details and custom fields.
> [!NOTE]
>
> **Who can do this:** Anyone with access to the candidate's job req. Fields marked private only show to users whose security role has *Private Data Access*.
A candidate's details live on the **Details** tab of their Candidate Application. Change a value right where you see it; there's no separate edit mode and no **Save** button for most fields. You can also fix common fields straight from the Candidates list.
## Edit on the Details tab
**1. Open the Details tab**
Open the Candidate Application and click the **Details** tab.
**2. Click the value you want to change**
The value turns into a box, a dropdown or a date picker.
**3. Make your change**
Type or pick the new value, then press Enter or click away. The change saves on its own.

## What's on the Details tab
| Card | What's in it | Belongs to |
| - | - | - |
| **Application Details** | **Application Date**, **Assigned User**, **Source**, **Hiring Class**, **Job Board**, **Job Post** and the **Application ID** | This application |
| **Custom Application Fields** | Your account's application fields | This application |
| **Job Req Details** and **Hiring Class Details** | Values from the job req and the candidate's hiring class, read only | The job req or hiring class |
| **Documents** | Files for this application. Click **Upload** to add one, or **Generate Document** to create one from a template. | This application |
| **Work History** and **Education History** | Past jobs and education. Click **Add** to add an entry. | The person |
| **Personal Details** | **First Name**, **Last Name**, **Primary Email**, **Secondary Email**, **Phone Number**, **Opt-in to text messages**, the **User ID**, and **LinkedIn URL** and **Date of Birth** when the job req's application form includes them | The person |
| **Location** | **Country**, **State/Region**, **City**, **Zip/Postal Code**, **Address Line 1** and **Address Line 2** | The person |
| **Custom Personal Fields** | Your account's personal fields | The person |
Anything that belongs to the person, like contact details and personal fields, is the same on every one of their Candidate Applications and on their Candidate Profile. Change it once and it changes everywhere. Application fields only change for this application. See [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications).
You can also edit personal details on the Candidate Profile's **Details** tab. Admins set up custom fields under account settings. See [Custom fields](/account-setup/custom-fields).
> [!TIP]
>
> Need to give a candidate's ID to another system, like your HRIS? Click the copy icon next to **Application ID** or **User ID** instead of retyping it.
## Edit from the Candidates list
On the **Candidates** page or a job req's **Candidates** tab, click a cell to edit it without opening the candidate. This works for **Phone Number**, **Source**, **Hiring Class**, **Step**, the location columns and most custom field columns. **Name** and **Email** can only be changed on the **Details** tab. See [The Candidates page](/candidates/candidates-page#edit-right-in-the-list).
## Documents
* **Upload:** add a file up to 15 MB, such as a PDF, Word or Excel file, or an image.
* **Generate Document:** pick a **Document Template**, check the merge keys it fills in, and give the file a name. See [Offer and document templates](/offers/templates).
* Each document's menu lets you **Download** or **Delete** it. Users with *Private Data Access* can also **Change to Private** so only users with that permission can see it, or **Change to Public**.
## FAQ
> [accordion] Why won't a new email address save?
>
> An email address can only belong to one person in Journeyfront. If the address is already used by another candidate record, the change can't be saved and the old email comes back. That usually means the person has a duplicate record: merge the two instead. See [Compare and merge candidates](/candidates/compare-and-merge).
>
> Also check the format. A primary or secondary email that isn't a valid address shows an error and isn't saved.
> [accordion] Why won't a name change save?
>
> First and last names need at least two letters or numbers. If the field shows an error, fix the name and click away again.
> [accordion] Why can't I edit this candidate's details at all?
>
> If the candidate is also a member of your team in Journeyfront, only users whose security role has *All Employee Access* can change their details. You also need access to the candidate's job req.
> [accordion] Does changing the email change how the candidate signs in?
>
> Yes. The **Primary Email** is the address the candidate uses to sign in to Journeyfront. Let them know when you change it.
> [accordion] Can I opt a candidate in to text messages?
>
> Yes. Turn on **Opt-in to text messages** in **Personal Details**. Journeyfront asks you to confirm that you received the candidate's consent first. See [Text messages](/communication/text-messages).
> [accordion] Why can't I change the Source?
>
> Sources set by an integration, like a job board, can't be changed by hand.
> [accordion] Why can't I see some custom fields?
>
> Fields marked private only show to users whose security role has *Private Data Access*.
> [accordion] Do my changes carry over to the employee record after the candidate is hired?
>
> Yes. Contact details and personal fields belong to the person, so their employee record shows the same values.
## Related
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Set up personal and application fields.
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> What belongs to the person and what belongs to one application.
> [card] [Compare and merge candidates](/candidates/compare-and-merge)
>
> Fix duplicate records.
# Fraud flags
Source: https://help.journeyfront.com/candidates/fraud-flags
How Journeyfront flags applications that need a closer look, and what to do about them.
> [!NOTE]
>
> **Who can do this:** Everyone on a job req can see fraud flags. Admins with *Company Settings Access* choose which checks run in **Settings**, then **Fraud Detection**.
>
> **Availability:** Fraud detection needs to be turned on for your account. Ask your Customer Success Manager.
Remote, high-volume hiring attracts fraudulent applications. Journeyfront checks applications for warning signs automatically and gives each one a **fraud risk level**, so your team can spot the ones that need a closer look before they take up interview time.
## Risk levels
| Level | What it means | What to do |
| - | - | - |
| None | No warning signs found | Continue as normal |
| Low | Minor activity worth noting | Usually fine; glance at the details |
| Medium | Activity that may warrant review | Review before advancing |
| High | Strong warning signs | Review carefully before any next step |
| NA | Not enough information to set a risk level | Continue as normal |
## Where you'll see it
* **The Candidates page and a job req's Candidates tab:** add the **Fraud Risk Level** column with **Edit Columns**, or filter by **Fraud Risk Levels**.
* **The Candidate Application:** open the **Fraud** tab to see what was found.

## Turn fraud checks on or off
Admins choose which checks run for your whole account.
**1. Open Fraud Detection**
Go to **Settings**, then **Fraud Detection**.
**2. Choose your Fraud Indicators**
Under **Network & Location**, switch each check on or off:
* **Location Change During Application**: whether the candidate's location changes while they work through the application.
* **IP Address Matches Other Candidates**: whether other candidates applied from the same network address.
* **VPN and Proxy Detection**: whether the candidate is hiding their location behind a VPN or another privacy service.
**3. Save**
Click **Save**. The button appears once you change a switch.

If the page says fraud detection is not enabled for your account, ask your Customer Success Manager to turn it on. A change to the switches applies to activity from then on. Earlier activity isn't checked again, except that a new candidate on a shared network address can raise the shared-address level on the candidates who used it before.
## How the risk level is set
Each time a candidate applies, completes an activity, books an interview or submits an onboarding form, Journeyfront records the network address they used and its approximate location. When someone on your team schedules an interview for a candidate, your team member's network isn't recorded against the candidate.
Each check you've turned on looks at those records and gives itself a level:
| Check | What it looks for | How the level is set |
| - | - | - |
| **Location Change During Application** | The candidate's location moving between steps of the same application | The bigger the move, the higher the level. A different city is lower than a different state, and a different country is highest. |
| **IP Address Matches Other Candidates** | Other candidates in your account who applied from the same network address | The more other candidates share the address, the higher the level. |
| **VPN and Proxy Detection** | Signs the connection is anonymized, such as a VPN, a proxy or a hosting provider | Based on how strongly the connection looks anonymized. |
The application's **fraud risk level** is the highest level among its checks. One High check makes the application High, even if the other checks find nothing. Levels only go up as new activity is checked: a later clean step doesn't lower an earlier flag. A level can also rise after the fact: when a new candidate applies from an address an earlier candidate used, both applications are flagged.
Common, innocent reasons for a flag:
* **Shared networks.** Family members, roommates, a library, a college campus or your own hiring event's Wi-Fi can put several real candidates on one address.
* **Moving between networks.** A candidate who starts on a phone and finishes on home Wi-Fi can show a different city.
* **Work or privacy VPNs.** Some candidates apply from a work laptop or use a VPN by habit.
> [card] [Candidate Application](/candidates/candidate-application)
>
> The slide-out panel where the Fraud tab and the risk level appear.
## Reviewing a flagged application

**1. Spot the risk level**
The candidate's level shows in the header of the Candidate Application (1), next to their status.
**2. Open the Fraud tab**
Click **Fraud** (2). **Fraud Indicators** lists each check with its own level (3). Click a check to see what was found.
**3. Read the details**
Each check shows an **Overview** and **Details** (4):
* **IP Address Matches Other Candidates:** the shared IP address, the **Number of other candidates**, the location and a table of those candidates with the job req they applied to. Click a job req to open that candidate's application. When the list is long, click **Export All** to download it.
* **Location Change During Application:** each location detected, with the activity and time it was recorded.
* **VPN and Proxy Detection:** the network provider and type, and what was detected.
Below the checks, the **Network & Location Log** lists every recorded activity with its IP address. Click **Get IP Details** on a row to look up its network and location.
**4. Look at the whole application**
Compare the flag with the candidate's answers, resume and contact details. Several candidates on one address who applied minutes apart, with similar answers, is a stronger sign than one household.
**5. Decide**
Advance, ask follow-up questions in the interview, or reject with a reason.
> [!TIP]
>
> Instead of rejecting High-risk applications automatically, use an automation rule (with the **Fraud Risk Level** condition) to move them to a review step. A reviewer clears the false alarms and you don't lose good candidates. Leave a comment with what you decided so the rest of your team knows it's been reviewed.
> [!WARNING]
>
> A risk level is a reason to review, not proof of fraud. Always look at the details before rejecting a candidate.
## FAQ
> [accordion] Can candidates see their fraud risk level?
>
> No. Fraud flags are only visible to your team.
> [accordion] Why don't some candidates have a risk level?
>
> Checks run as candidates apply and work through their activities, using the checks that are on at that moment. Earlier activity isn't checked again later, so a candidate who applied before fraud detection was turned on has no risk level until they do something new. One exception: when a new candidate applies from a network address other candidates already used, those earlier candidates' **IP Address Matches Other Candidates** level can go up too. A candidate shows NA when there isn't enough information to set a level.
> [accordion] Can I change the levels or the rules behind them?
>
> No. You choose which checks run in **Settings**, then **Fraud Detection**. How each check sets its level is the same for every account.
> [accordion] Why don't I see fraud flags at all?
>
> Fraud detection needs to be turned on for your account, and your admins choose which checks run. Ask your Customer Success Manager.
> [accordion] Does Journeyfront reject candidates for fraud on its own?
>
> No. Journeyfront flags applications for review. Your team, or automation rules your team sets up, decide what happens next.
## Related
> [card] [Automation rules](/workflows/automation-rules)
>
> Move flagged applications to a review step automatically.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What candidate scores mean.
# Move candidates through steps
Source: https://help.journeyfront.com/candidates/move-through-steps
Advance a candidate to the next step, or move one or many candidates to any step in the workflow.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the candidate's job req. Creating offers while you move candidates needs the *View and Send Offers* permission.
Every job req's workflow is a series of steps, like Application, Screening, Interview and Offer. Candidates work on the activities in their current step. Your team moves them to the next step with **Change Step**, or an automation rule does it for you. (This is the job req's **Gate Steps** setting, under **Setup**, then **Configurations**, which is on by default.)
Moving a candidate is also your chance to set them up for what comes next: email them a link to continue, assign their onboarding form, or create their offer, all in the same window.
The steps, and the activities in each one, come from the job req's workflow, under **Setup**, then **Workflow**. See [Workflows overview](/workflows/overview).
## Move one candidate
**1. Open the Current Step menu**
On the Candidate Application, click **Current Step** at the top right.
With **Gate Steps** on, steps the candidate hasn't reached yet have an outlined number. Hover over a step to see when it was unlocked and by whom.

**2. Pick the step**
Choose the step to move them to. The **Change Candidate Step** window opens with that step selected.
**3. Work through the moving actions**
The window shows a part for each activity in the new step that needs something from you. See [Moving actions](#moving-actions) below. If the step has none, you go straight to the review.
**4. Move the candidate**
Check the summary on **Review & Execute** and click **Move Candidate**. Click **Done** to close the window.
You can also move a candidate from the list: on the **Candidates** page or a job req's **Candidates** tab, click the candidate's **Step** cell. The same window opens.
## Move several candidates at once
**1. Select the candidates**
On the **Candidates** page or a job req's **Candidates** tab, tick the boxes next to the candidates (1). They need to be on the same job req.
**2. Click Change Step**
**Change Step** (2) is in the actions bar above the list. The **Change Candidate Step** window opens.

**3. Choose the step**
On **Select Step**, pick the step to move everyone to, then click **Next**.
**4. Work through the moving actions**
Your choices apply to everyone in this move.
**5. Move the candidates**
On **Review & Execute**, click **Move Candidates**, then **Done**.
**Change Step** only appears when everyone you selected is on the same job req and the same version of its workflow. If the workflow changed after some candidates applied, they may be on an older version. Add the **Job Version** column with **Edit Columns** to check, and move each group separately.

## Moving actions
The **Change Candidate Step** window adds a part to its progress bar for each of these activities in the step you're moving to:
| Part | When it appears | What you choose |
| - | - | - |
| **Step Invites** | The step has an activity candidates complete themselves, such as screening questions, an assessment, or a typing, skills, speed or language test | Turn on **Send email inviting user to complete the next step**, and add an optional message |
| The onboarding activity's name | The step has an Onboarding Form activity | Which **Onboarding form** to assign, and whether to **Send Invite Email**. A form is required to move candidates into this step. See [Onboarding forms](/onboarding/onboarding-forms). |
| The offer activity's name | The step has an Offer activity, and you have the *View and Send Offers* permission | Turn on **Create Offer** (or **Bulk Create Offers**) to create offers as part of the move. See [Send offers in bulk](/offers/bulk-send). |
The step invite email uses the **User is moved to a new step notification** system email, with your message added. You can edit it in **Settings**, then **Templates**, then **E-mail Template**, on the **System Emails** tab. See [Email templates](/communication/email-templates).
> [!TIP]
>
> Turn the email on whenever candidates have something to do in the new step. Most candidates won't sign back in on their own, and a short personal message ("Great job on the screening, here's your typing test") gets more of them to finish.
Interviews in the new step don't add a part here. Candidates get a scheduling invite through the interview's own settings. See [Self-scheduling](/interviews/self-scheduling).
## Move candidates automatically
Automation rules can move candidates for you, for example when they score well on screening questions. Use the **Change candidate step to** action, and tick **Send email inviting user to complete the next step** to email them. See [Automation rules](/workflows/automation-rules).
Moving a candidate by hand also starts any rule with the **Candidate Moved to Step** trigger for that step.
## What candidates see
If you turned on the email, the candidate gets a message with a link to continue. When they sign in, they see the activities in their new step on their progress page. Without the email, they see the new step the next time they sign in.
## FAQ
> [accordion] Why don't I see Change Step?
>
> Everyone you select needs to be on the same job req and the same version of its workflow. Add the **Job Req** and **Job Version** columns to spot the candidates that don't match, then select a smaller group.
> [accordion] Can I skip a step or move a candidate back?
>
> Yes. You can pick any step in the workflow, ahead or behind the candidate's current step.
> [accordion] Does the candidate get an email when I change their step?
>
> Only if you turn on **Send email inviting user to complete the next step**, which appears when the new step has something for them to do.
> [accordion] Why can't I click Next on the onboarding part?
>
> A step with an Onboarding Form activity needs a form assigned. Choose one under **Onboarding form**, then click **Next**.
> [accordion] Can I move a candidate and create their offer at the same time?
>
> Yes. Move them to the step with the Offer activity and turn on **Create Offer** in the window. See [Send offers in bulk](/offers/bulk-send).
> [accordion] Why didn't a candidate move to the next step after finishing?
>
> With the job req's **Gate Steps** setting on, which is the default, candidates stay in their step until your team or an automation rule moves them. Set up a rule with the **Candidate Completes Step** trigger to move candidates as soon as they finish.
## Related
> [card] [Workflows overview](/workflows/overview)
>
> The steps and activities candidates move through.
> [card] [Automation rules](/workflows/automation-rules)
>
> Move candidates automatically.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to a group of candidates.
> [card] [Reject candidates](/candidates/reject)
>
> When a candidate isn't moving forward.
# Move a candidate to another job req
Source: https://help.journeyfront.com/candidates/move-to-another-job
Close a candidate's application on one job req and continue it on another, with a reason, without rejecting them.
> [!NOTE]
>
> **Who can do this:** Anyone who can manage both job reqs: job req managers and users whose security role includes job req access. Managing the list of move reasons needs *Company Settings Access* or full access.
**Move** takes a candidate out of one job req and puts them into another, at the step you choose. Their original Candidate Application closes with a **Moved** status, and a new Candidate Application opens on the new job req. Both applications show the move, so anyone can see where the candidate came from, where they went and why.
Moving isn't the same as rejecting. A moved candidate isn't counted as rejected, doesn't get a rejection email, and doesn't have to apply again.
## When to move a candidate
Teams move candidates for two main reasons.
### From an evergreen job req to a job-specific one
For many high-volume teams, moving candidates is a planned part of the hiring process. You keep one evergreen job req always open, often one per role or location, so candidates can apply any time. Your team screens everyone there. When a specific opening is ready, like a new hiring class, site, shift or start date, you move the qualified candidates into that job req, where interviews, offers and hiring happen.
* The evergreen job req stays a clean list of people still waiting, because moved candidates leave it.
* You can place candidates at a later step, like Interview or Offer, since they already passed screening.
* **Transfer Data** brings their screening answers and test results over, so they don't repeat them.
* Keeping the **Original Application Date** means time-to-hire is counted from when they first applied.
### When a candidate is a better fit for a different job
Sometimes a candidate doesn't qualify for the job they applied to but would be a good match for another one. They might not meet one role's language, schedule or skills requirements but suit a different role well. Instead of rejecting them and hoping they apply again, move them to the job req that fits.
* Your rejection numbers stay accurate, because the candidate isn't rejected.
* You pick the step that makes sense, so they don't redo steps that still apply.
* A move reason and a note tell the team on the new job req why the candidate is there.
## Move or add to another job req?
Journeyfront has two ways to get a candidate onto another job req: **Move** and [Add to Job Req](/candidates/add-to-another-job). Both create a new Candidate Application and can bring over results the candidate already has. The difference is what happens to the application they're on now.
* **Move when the new job req is the next step in the candidate's current hiring process.** They're partway through, and the right place to continue is a different job req. Their journey carries on there, and the first application closes as **Moved**.
* **Add when you're starting something new, outside their current process.** For example, you're reaching out to past candidates about a new opening, or you want someone considered for a second role while they stay in the first. Each application keeps its own status and runs through its own workflow.
| | Move | Add to Job Req |
| - | - | - |
| **The original application** | Closes with a **Moved** status | Stays as it is, with its own step, status and scores |
| **Applications afterward** | One open application, on the new job req | Two applications, one on each job req |
| **Works on** | Open applications only | Any candidate, including ones whose earlier application was rejected or withdrawn |
| **Where they start** | Any step you choose | The first step of the new workflow |
| **Application date** | Today's date, or their original application date | Today's date |
| **Reason and notes** | A move reason (required if your account has them) and notes, shown on both applications | None |
| **How many at once** | One candidate at a time | One, a selected group, or automatically with an automation rule |
| **Rejection numbers** | The original isn't counted as rejected | Unchanged. A rejected original stays rejected |
| **Transfer results** | Yes, on by default | Yes, when you choose to |
| **Email the candidate** | Optional | Optional |
### Tips for choosing
> [!TIP]
>
> Ask yourself: is this the same hiring journey continuing, or a new one? If the candidate would naturally keep going on the other job req, move them. If you're inviting them to something new, add them.
* **Keep a real rejection on record.** If the candidate didn't pass the first job req and you want that rejection and its reason to stay on their history, reject them there and then add them to the other job req. Moving would replace the rejection with **Moved**.
* **Re-engage past candidates with Add.** Move only works on open applications. To invite earlier applicants to a new opening, filter the [Candidates page](/candidates/candidates-page) (for example by status or applied date), select them, and use **Add to Other Req** with the invitation email turned on.
* **Don't use Add as a stand-in for Move.** If the candidate should only be in one place, adding leaves the first application open, so they show as an active candidate on both job reqs and each application keeps running through its workflow.
* **Close the leftover application after an add.** Once someone is hired or placed on one job req, nothing closes their other application automatically. Close it yourself so it doesn't sit in that job req's pipeline.
* **Use Original Application Date for planned moves.** When moving from an evergreen job req, keeping the original date means time-to-hire counts from when they first applied.
## Move a candidate
**1. Open Move**
On the Candidate Application, click **Actions**, then **Move**. The **Move Candidate to Another Job Req** window opens.
**Move** is only available on open applications. It doesn't show for candidates who are hired, rejected, withdrawn or already moved.

**2. Check who you're moving**
**Who to move** shows the candidate's name, their current job req and their current step.
**3. Choose where they go**
Under **Where to?**:
* **Job Req:** pick the job req to move them to. The list shows the other open job reqs you have access to.
* **Step:** pick the step to place them at. Steps are listed in the order of that job req's workflow.
* **Application Date on New Job Req:** choose **Today's Date**, or **Original Application Date** to keep the date they first applied.
**4. Say why**
Under **Why?**, pick a move reason and add **Notes** if they help. If your account has move reasons set up, a reason is required. If you have access to manage move reasons, you can click **Add Move Reason** to add one without leaving the window.

**5. Choose the options**
Under **Options**:
* **Email Candidate:** turn it on to email the candidate a link to complete the new job req's application steps. It's off by default.
* **Transfer Data:** on by default. Journeyfront checks what the candidate has already completed that matches the new job req, and ticks it for you. Untick anything you want them to do again, or turn the switch off to start fresh. If the check doesn't finish, click **Try again**.

**6. Click Move to Job Req**
The button turns on once you've picked a job req, a step and (if required) a reason. When the move is done, click **View in Job Req** to open the new Candidate Application, or **Close**.

For what counts as matching data, see [Transfer results to the new application](/candidates/add-to-another-job#transfer-results-to-the-new-application). It works the same way when you move a candidate.
## After the move
**On the original application:**
* The status shows **Moved on** the move date, followed by the move reason.
* The application is closed. Its status can't be changed, and bulk reject, **Mark as New**, reminder emails and automatic rejections all skip it.
* **Comments & Activities** shows **Moved to Another Job Req**, with the new job req, the step, the reason and the notes.

**On the new application:**
* The candidate is at the step you chose, with any transferred results already complete.
* **Comments & Activities** shows **Moved from Another Job Req**, with the same details.

* It's a normal open application, so it moves through the new workflow like any other, and can be moved again later if needed.
Both applications stay on the candidate's [Candidate Profile](/candidates/profiles-and-applications), so you can follow their path from one job req to the next.
## Edit a move's reason or notes
**1. Open the original application**
Open the Candidate Application the candidate was moved out of.
**2. Click the pencil next to Moved**
The **Edit Move Reason** window opens and shows where the candidate was moved to.
**3. Change the reason or notes and click Save**
The change is recorded in **Comments & Activities** on both applications, showing the old and new values.

## Find moved candidates on the Candidates page
On the [Candidates page](/candidates/candidates-page), moved applications have the status **Moved**. Hover over it to see the move date, the job req and step they moved to, the reason and the notes.
Three columns are available from **Edit Columns**:
| Column | Shows |
| - | - |
| **Moved Date** | When the candidate was moved |
| **Moved To** | The job req a moved application went to |
| **Moved From** | The job req a new application came from |
You can sort and filter by all three, and they're included when you [export data](/lists-and-exports/export-data).

## Set up move reasons
Move reasons keep your team's moves consistent and make it easy to see later why candidates moved. Go to **Settings**, then **Custom Options**, then **Move Reasons**.

* **Add:** click **+ Move Reason**, type the reason and click **Save**.
* **Rename:** click the reason, change it and click **Save**.
* **Delete:** click the trash icon and confirm. The reason is no longer offered when moving a candidate. Moves that already used it keep it.
Two reasons can't have the same name. Once your account has at least one move reason, every move needs one.
> [!TIP]
>
> Keep the list short and name what happened, for example "Placed in open class", "Assigned to site" or "Better fit for another role". If you move candidates out of an evergreen job req as part of your normal process, give that its own reason so you can tell planned moves from case-by-case ones.
## FAQ
> [accordion] What's the difference between Move and Add to Job Req?
>
> **Move** closes the candidate's current application as **Moved** and continues their hiring process on the new job req. **Add to Job Req** leaves the current application as it is and gives them a second one, so both are on file. Move when the new job req is the next step in their journey; add when you're starting something new. See [Move or add to another job req?](#move-or-add-to-another-job-req)
> [accordion] The candidate didn't pass this job req. Should I move them or reject them?
>
> If you want the rejection on their record, reject them, then [add them to the other job req](/candidates/add-to-another-job). Move them only when the new job req is simply a better place for them to continue, and a rejection wouldn't tell the real story.
> [accordion] Can I move a rejected or past candidate?
>
> No. Move only works on open applications. To bring a past candidate into a new job req, use [Add to Job Req](/candidates/add-to-another-job), which works whatever the status of their earlier application.
> [accordion] I added a candidate when I meant to move them. Can I fix it?
>
> You can't turn an add into a move, and Move won't work now because they already have an application on that job req. Their original application is still open, so close it the way your team normally would.
> [accordion] Does a moved candidate count as rejected?
>
> No. **Moved** is its own status, separate from **Rejected**, so your rejection numbers aren't affected.
> [accordion] Does the candidate get an email?
>
> Only if you turn on **Email Candidate**. That email invites them to continue on the new job req. Moving never sends a rejection email.
> [accordion] Why isn't a job req in the list?
>
> The list only shows open job reqs you have access to, and leaves out the job req the candidate is already on. Inactive, closed and archived job reqs aren't listed.
> [accordion] Why can't I move this candidate to a job req?
>
> A candidate can't be moved to a job req they already have an application on, including one they were moved out of. If that job req has **Allow Re-Takes** with a waiting period and the candidate applied there recently, the move is blocked until the waiting period passes.
> [accordion] Why don't I see Move in the Actions menu?
>
> The application is already closed (hired, rejected, withdrawn or moved), or you don't have access to manage this job req.
> [accordion] Can I move several candidates at once?
>
> Not with **Move**. You move one candidate at a time from their Candidate Application. To add a group to another job req without closing their current applications, use **Add to Other Req** in [Bulk actions](/candidates/bulk-actions).
> [accordion] Can I undo a move?
>
> No. A moved application's status can't be changed, and the candidate can't be moved back to the job req they came from, because they still have an application there. If the move was a mistake, you can move them on to a different job req, or reject the new application.
> [accordion] Which date does the new application use?
>
> The one you chose under **Application Date on New Job Req**: today's date, or the date of their original application. That date is used on the Candidates page, in exports and in reports.
## Related
> [card] [Add a candidate to another job req](/candidates/add-to-another-job)
>
> Consider a candidate for a second role and keep both applications open.
> [card] [Reject candidates](/candidates/reject)
>
> Close an application with a rejection reason.
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> One person, many applications.
> [card] [Hiring classes overview](/hiring-classes/overview)
>
> Group hires who start together.
# Working with candidates
Source: https://help.journeyfront.com/candidates/overview
What a candidate is in Journeyfront, where you work with them, and the everyday jobs you'll do, with links to each.
> [!NOTE]
>
> **Who can do this:** Everyone on your hiring team. You see candidates on the job reqs you're on, or on every job req if your security role has *All Job Req Access*.
Candidates are at the center of most of your day in Journeyfront. This page explains how Journeyfront keeps track of a candidate, where you find them, and the everyday jobs you'll do with them, with a link to the full guide for each.
## Candidate Profiles and Candidate Applications
Journeyfront keeps two kinds of record for every candidate:
* The **Candidate Profile** is the person: contact details, location, resume, work and education history, and every job req they've applied to. There's one per person, identified by their **User ID**.
* A **Candidate Application** is that person in one job req: their step, status, scores, screening answers, interviews, offer and onboarding. There's one for each job req they're in, identified by its **Application ID**.
Someone who applies to three job reqs has one Candidate Profile and three Candidate Applications. Most of your work, like scoring, moving through steps, rejecting and hiring, happens on a Candidate Application and only affects that one job req.
> [card] [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications)
>
> What lives on each record, and how to open a Candidate Profile.
## Where you work with candidates
* **The Candidates page.** Click **Candidates** in the top navigation to see Candidate Applications on every job req you can access, with search, filters, columns and saved views.
* **A job req's Candidates tab.** Open a job req to see only its candidates, grouped by status and by step. It has the same list and tools as the **Candidates** page.
* **The Candidate Application.** Click a candidate's name in either list. Their Candidate Application opens in a side panel over the list, so you can move from one candidate to the next without losing your place.

> [card] [The Candidates page](/candidates/candidates-page)
>
> Search, filter, choose columns and save views.
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Everything about one candidate in one job req, tab by tab.
## Everyday jobs
| Job | How it works | Guide |
| - | - | - |
| Review and score | Read a candidate's scores on the **Score**, **Steps**, **Screenings** and **Assessments** tabs. | [Reading a candidate's scores](/scoring/reading-scores) |
| Move through steps | Advance a candidate to the next step, or move one or many to any step in the workflow. | [Move candidates through steps](/candidates/move-through-steps) |
| Email and text | Email or text one candidate or many, from a template or from scratch. | [Email candidates](/communication/email-candidates), [Text messages](/communication/text-messages) |
| Comment and review activity | Leave comments for your team and see everything that has happened to the application. | [Comments and activity](/candidates/comments-and-notes) |
| Reject | Close an application with a reason. A rejection can always be undone. | [Reject candidates](/candidates/reject) |
| Hire | Mark a candidate as hired and record their job details. | [Hire candidates](/onboarding/hire-candidates) |
| Do Not Hire | Flag a person your company shouldn't hire, so everyone sees the warning on every application. | [Do Not Hire](/candidates/do-not-hire) |
| Check fraud flags | See each application's fraud risk level and review the ones that need a closer look. | [Fraud flags](/candidates/fraud-flags) |
| Consider for another role | Add a candidate to another job req, or move them to one. | [Add a candidate to another job req](/candidates/add-to-another-job), [Move a candidate to another job req](/candidates/move-to-another-job) |
| Act on a group | Tick candidates in the list to change step, email, reject, hire, assign and more in one go. | [Bulk actions](/candidates/bulk-actions) |
| Save your lists | Save the filters and columns you use every day as a tab, and share it with your team. | [Saved views](/lists-and-exports/saved-views) |
> [!TIP]
>
> When you're hiring at volume, set up a saved view for each part of your day, such as new applicants, candidates ready to interview and candidates assigned to you. Then filter, tick and use a bulk action instead of opening candidates one at a time.
## Related
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to a group of candidates.
> [card] [Add candidates](/sourcing/add-candidates)
>
> Add a candidate to a job req yourself, or invite them to apply.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> What each score means and where to find it.
> [card] [Reject candidates](/candidates/reject)
>
> Reject with a reason, and undo a rejection.
# Candidate Profiles and Candidate Applications
Source: https://help.journeyfront.com/candidates/profiles-and-applications
The difference between the person and their application to one job req.
> [!NOTE]
>
> **Who can do this:** Everyone on your hiring team can open a Candidate Profile. You can open the Candidate Applications on job reqs you have access to; the others show greyed out.
Journeyfront keeps two kinds of record for every candidate. The **Candidate Profile** is the person. A **Candidate Application** is that person's progress through one job req. Someone who applies to three job reqs has one Candidate Profile and three Candidate Applications, so you always see their whole history in one place.
## The difference at a glance
| | Candidate Profile | Candidate Application |
| - | - | - |
| What it is | The person, across your whole account | The person in one job req |
| How many | One per person | One per job req they're in |
| Holds | Contact details, location, custom personal fields, resume, work and education history, the Do Not Hire flag, and a list of every application and job | Step, status, scores, screening answers, interviews, offer, onboarding, assigned user, source, hiring class, custom application fields and documents |
| ID | **User ID** | **Application ID** |
| Where you work | Reviewing the person's history, updating their details, adding them to another job req | Screening, interviewing, moving through steps, offers and hiring |
Changes to the person, like a new phone number, show on every one of their Candidate Applications. Changes to one application, like a step change or an application field, stay with that application.

## Open a Candidate Profile
From any Candidate Application, click the **Currently Viewing** dropdown at the top and choose **Candidate Profile**. The same dropdown lists all of the person's applications and jobs, so you can jump between them.
You can also reach a Candidate Profile from the link in a Do Not Hire match banner. See [Do Not Hire](/candidates/do-not-hire).
## What's on the Candidate Profile
The header shows the person's name, contact details and location, the **Currently Viewing** dropdown and the **Created Date** of their record. The **Actions** menu has **Add to Job Req** and **Mark Do Not Hire**.

| Tab | What you'll find |
| - | - |
| **Applications** | Every Candidate Application in your account, with **Job Req**, **Application Date**, **Status**, **Current Step**, **Assigned User**, **Source** and **Overall Score**. Click a row to open it. |
| **Jobs** | The person's employment records after they were hired: **Job Profile**, **Position Title**, **Start Date**, **End Date**, **Separation Reason**, **Type** and **Status**. Click a row to open their employee record. |
| **Details** | **Personal Details**, **Location** and **Custom Personal Fields**, plus work and education history and e-consent records. Click a value to change it. |
| **Resume** | The person's resume, with download and print. Upload one if none is on file. |
| **Activity Feed** | Comments and activity from all of the person's applications in one timeline. Each item shows which job req it came from, or "Candidate Profile". |
Comments you add on the **Activity Feed** belong to the person rather than to one application, which is handy for notes that apply to every role, like "prefers evening shifts". See [Comments and activity](/candidates/comments-and-notes).
Applications and jobs on job reqs or job profiles you can't access still appear, greyed out, so you know they exist. You can't open them.
## User ID and Application ID
Journeyfront shows two IDs, and both are on the Candidate Application's **Details** tab with a copy button:
* **User ID** identifies the person. It's the same on every one of their Candidate Applications. Find it in the **Personal Details** card.
* **Application ID** identifies one Candidate Application. Find it in the **Application Details** card.
> [!TIP]
>
> When you contact support about a specific candidate, include the **Application ID**. It points straight to the right application, even when the person has applied to several job reqs.
## FAQ
> [accordion] Why does a candidate show up twice on the Candidates page?
>
> The Candidates page lists Candidate Applications, so a person who applied to two job reqs has two rows. If the same person has two separate Candidate Profiles, for example because they applied with two email addresses, merge them. See [Compare and merge candidates](/candidates/compare-and-merge).
> [accordion] If I change a candidate's phone number on one application, does it change everywhere?
>
> Yes. Contact details, location and custom personal fields belong to the person, so the change shows on their Candidate Profile and every Candidate Application.
> [accordion] Is the User ID the same as the candidate ID in our HRIS or other systems?
>
> No. The **User ID** is Journeyfront's own ID for the person. Your HRIS and other systems keep their own IDs.
> [accordion] Can I see applications a candidate made to other companies?
>
> No. A Candidate Profile only shows applications and jobs in your account.
> [accordion] How do I add an existing candidate to another job req?
>
> On the Candidate Profile or a Candidate Application, click **Actions**, then **Add to Job Req**. See [Add a candidate to another job req](/candidates/add-to-another-job).
## Related
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Everything about one candidate in one job req.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
> [card] [Compare and merge candidates](/candidates/compare-and-merge)
>
> Combine duplicate records.
> [card] [Edit candidate details](/candidates/edit-details)
>
> Update a candidate's details and custom fields.
# Reject candidates
Source: https://help.journeyfront.com/candidates/reject
Reject one or many candidates with a reason, let them know, and undo a rejection if you need to.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the candidate's job req.
Rejecting a candidate closes their Candidate Application on that job req and records why. Every rejection needs a reason, so your reports can show where and why candidates drop out of your process. A rejection can always be undone.
Rejecting only affects one Candidate Application. If the person has applied to other job reqs, those applications aren't touched.
## Before you start
Rejection reasons come from your account's list, so set that list up first with the reasons your team actually uses. Your admins manage it in **Settings**, then **Custom Options**, then **Rejection Reasons**.
> [card] [Rejection reasons](/account-setup/rejection-reasons)
>
> Set up the reasons your team chooses from when rejecting a candidate.
## Reject one candidate
**1. Open the Reject window**
On the Candidate Application, click **Actions**, then **Reject**. The **Reject Candidate** window shows the candidate's name and the job req they applied for.
**2. Choose a rejection reason**
Pick a **Rejection Reason**. Reasons are grouped by type, and you can type to search the list. It's required.
**3. Add notes (optional)**
Add **Rejection Notes** with any detail your team should know.
**4. Click Reject**
The header now shows **Rejected**, the date and the reason.

**Reject** only appears in **Actions** while the candidate isn't already hired or rejected. To reverse a hire instead, see [Un-Hire a candidate](/onboarding/hire-candidates#un-hire-a-candidate).
## Reject several candidates at once
**1. Select the candidates**
On the **Candidates** page or a job req's **Candidates** tab, tick the boxes next to the candidates. They need to be on the same job req.
**2. Click Reject**
**Reject** is in the actions bar above the list. The **Reject Candidates** window lists everyone you selected.

**3. Choose a reason and click Reject**
The reason and notes apply to everyone in the group.
Hired candidates in your selection are skipped. Use **Un-Hire** on them first if they really shouldn't be hired.
> [!TIP]
>
> Filter the list before you select, for example by **Current Step** and **Activity Status**, so you only reject candidates who all fit the same reason. One accurate reason per group keeps your rejection reports meaningful.
## Rejection reasons
Reasons are grouped by type, so your reports can separate, for example, candidates you turned down from candidates who withdrew. Your admins manage the list in **Settings**, then **Custom Options**, then **Rejection Reasons**. See [Rejection reasons](/account-setup/rejection-reasons).
If the reason you need isn't there, click **Add Rejection Reason** at the bottom of the list in the Reject window. Type the reason, pick its type and click **Save**. It's added to your account's list for everyone.

## Change the reason or notes
On a rejected Candidate Application, click the edit icon next to **Rejected** in the header. The Reject window opens with the current reason and notes. Change them and click **Reject** to save.
## Let candidates know
Rejecting a candidate doesn't send them anything. To tell them:
* **Email them yourself.** Use **Actions**, then **Email** on the Candidate Application, or **E-mail** for a group. Save your rejection wording as an email template so it's ready each time. See [Email candidates](/communication/email-candidates) and [Email templates](/communication/email-templates).
* **Email them automatically.** Set up an automation rule with the **Candidate is Rejected** trigger and a **Send Email to Candidate** action. Add a delay of a day or so if you'd rather the email didn't arrive the moment you reject. See [Automation rules](/workflows/automation-rules).
## Automatic rejections
Candidates can also be rejected without anyone clicking **Reject**:
* **Knockout answers.** A candidate who picks a knockout option on a screening question is rejected with the reason **Auto rejected**. See [Screening questions](/assessments/screening-questions).
* **Automation rules.** A rule with the **Reject candidate** action rejects candidates who match its conditions, with the reason you chose.
Every rejection, and every un-reject, is recorded on the candidate's **Comments & Activities** tab. When an automation rule acted, an **Automation Ran** entry names the rule.
## Un-reject a candidate
**1. Choose Un-reject**
On the rejected Candidate Application, click **Actions**, then **Un-reject**.
**2. Confirm**
The **Undo Candidate Rejection?** window asks you to confirm. Click **Confirm**.
The candidate's status goes back to **Active** (or **Incomplete**, if they haven't been scored on anything yet), in the same step they were in. If they were rejected for a knockout answer, Journeyfront won't reject them for it again automatically.
## FAQ
> [accordion] Why don't I see Reject in the actions bar?
>
> Everyone you select needs to be on the same job req. Add the **Job Req** column to spot candidates from other job reqs, or work from the job req's **Candidates** tab.
> [accordion] Can I reject without choosing a reason?
>
> No. A reason is required. If none fits, add one with **Add Rejection Reason**, or ask your admin to add it to your account's list.
> [accordion] Does rejecting email the candidate?
>
> No. Send an email yourself, or set up an automation rule to send one. See [Let candidates know](#let-candidates-know).
> [accordion] Can I un-reject several candidates at once?
>
> No. Un-reject them one at a time from each Candidate Application.
> [accordion] Is a rejected candidate removed from Journeyfront?
>
> No. Their Candidate Application stays on the job req with the **Rejected** status, and you can filter for them by **Status** or **Rejection Reasons**. To remove an application completely, see **Delete** in [Bulk actions](/candidates/bulk-actions).
> [accordion] Does rejecting a candidate affect their other applications?
>
> No. Each Candidate Application has its own status. To flag someone your company shouldn't hire for any role, use [Do Not Hire](/candidates/do-not-hire).
## Related
> [card] [Rejection reasons](/account-setup/rejection-reasons)
>
> Set up the reasons your team chooses from.
> [card] [Automation rules](/workflows/automation-rules)
>
> Reject or notify candidates automatically.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to a group of candidates.
> [card] [Do Not Hire](/candidates/do-not-hire)
>
> Flag someone your company shouldn't hire again.
# Share and print
Source: https://help.journeyfront.com/candidates/share-and-print
Share a Candidate Application with teammates by email, or print everything about a candidate.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the Candidate Application. The people you share with need a Journeyfront login and access to the job req.
When a hiring manager or another recruiter needs to weigh in on a candidate, send them a link to the Candidate Application instead of describing it. If you need a copy on paper or as a PDF, print one tab or everything at once.
## Share by email
**1. Open Actions, then Share**
On the Candidate Application, click **Actions**, then **Share**. The share panel opens under the header.
**2. Add recipients**
Type each teammate's email address under **Emails**. Press Enter, Space or a comma after each one. An address that isn't valid is highlighted.
**3. Add a message**
Under **Message (optional)**, tell them what you need, for example "Can you review before Thursday's interviews?"
**4. Click Share**
Each recipient gets an email with the candidate's name, the job req, your message and a link to the Candidate Application.

When a recipient clicks the link, they sign in to Journeyfront and land on the Candidate Application. Only people with a Journeyfront login and access to the job req can open it.
> [!TIP]
>
> Hiring managers who review candidates regularly should be on the job req's hiring team, so every link you share just works. See [Hiring team](/job-reqs/hiring-team).
### Copy the link instead
In the share panel, click **Copy Link** to copy the address of the Candidate Application. Paste it into a chat or a calendar invite. The same access rules apply: only signed-in teammates with access to the job req can open it.
## Print
### Print everything
Click **Actions**, then **Print All Data**. Journeyfront loads every tab it prints and opens your browser's print window with:
* **Score**, **Steps** and **Screenings**
* **Notes** (all interviews, expanded)
* **Resume**
* **Assessments**, and **Language** when the candidate has language results
**Comments & Activities**, **Details**, **Offer**, **Onboarding**, **Fraud** and **AI Tasks** aren't included.
### Print one tab
On the **Score**, **Steps**, **Screenings**, **Notes**, **Assessments** or **Language** tab, click the print icon at the top right of the tab. Only that tab prints.
There are two more print buttons:
* **Resume** tab: click the print icon next to **Download** to print just the resume.
* **Notes** tab: click the print icon on an interview's row to print only that interview.
> [!TIP]
>
> To save a PDF instead of printing, choose **Save as PDF** (or **Microsoft Print to PDF**) as the printer in your browser's print window.
## FAQ
> [accordion] Who can open a link I share?
>
> Only people with a Journeyfront login who have access to the candidate's job req: people on its hiring team, or anyone whose security role has *All Job Req Access*. Anyone else can't open it.
> [accordion] Can I share a candidate with someone who doesn't use Journeyfront?
>
> Not with a link. Shared links only open for signed-in teammates. Ask an admin to add the person as a user and to the job req's hiring team. See [Users](/account-setup/users).
> [accordion] Does the person I share with get notified?
>
> Yes. **Share** sends each recipient an email with the link and your message. **Copy Link** doesn't send anything.
> [accordion] Why aren't comments in my printout?
>
> **Print All Data** prints the candidate's results, notes and resume. It leaves out **Comments & Activities**, **Details** and the offer. Open those tabs to review them on screen.
> [accordion] Can I share several candidates at once?
>
> Not with **Share**. To review several candidates side by side, select them on the Candidates page and use **Compare**. See [Compare and merge candidates](/candidates/compare-and-merge).
## Related
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
> [card] [Comments and activity](/candidates/comments-and-notes)
>
> Discuss a candidate with your team.
> [card] [Hiring team](/job-reqs/hiring-team)
>
> Give teammates access to a job req.
> [card] [Compare and merge candidates](/candidates/compare-and-merge)
>
> Review candidates side by side.
# Calling candidates
Source: https://help.journeyfront.com/communication/calling
Call a candidate from Journeyfront, log how the call went and find every call on the Candidate Application.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the Candidate Application. Anyone with a role on your account can play call recordings.
>
> **Availability:** Automatic call logging needs Webex Contact Center or QUO connected for your company and for you. See [Calling](/integrations/calling).
Call a candidate straight from their Candidate Application, with no copying numbers between windows. When your company uses a calling integration, every call is written to the candidate's record automatically: who called, when, how long you spoke, how it went and the recording. The next person who opens the candidate can see, and hear, what happened without anyone writing it down.

[Calling candidates with Webex Contact Center](https://www.youtube.com/embed/n-70AJ9R-Og)
## Call a candidate
Open the Candidate Application and click the **phone icon** in the header, or open **Actions** and choose **Call via Webex** (or **Call**). You can also call from the Candidate Profile. What happens next depends on how your company calls candidates.

> [tab] Webex Contact Center
>
> **1. Get ready in Webex**
>
> Sign in to the **Webex Agent Desktop** and set yourself to **Available**.
>
> 
>
> **2. Click the phone icon**
>
> Open the candidate in Journeyfront and click the **phone icon**. The tooltip reads "Waiting for you to answer in Webex."
>
> **3. Answer in your Agent Desktop**
>
> Webex rings you first. Answer in the Agent Desktop, and Webex then dials the candidate. The phone icon shows the call is in progress.
>
> **4. Log how it went**
>
> When the call ends, choose how it went and add a note if you like. See [Log the call outcome](#log-the-call-outcome).
>
> You can move to another page while the call is in progress. The call is still logged on the candidate.
> [tab] QUO
>
> **1. Click the phone icon**
>
> Click the **phone icon**, or the candidate's phone number. The number opens in your QUO app.
>
> **2. Make the call in QUO**
>
> Call the candidate in QUO as usual.
>
> **3. Let Journeyfront log it**
>
> When the call ends, it's logged on the candidate automatically, with QUO's summary, transcript and recording added as they become available. There's nothing to fill in.
>
> Calls you dial directly in the QUO app are logged too, as long as the number matches a candidate in your account.
> [tab] No calling integration
>
> Click the **phone icon** or the candidate's phone number, and the call opens in your computer's default calling app. These calls aren't logged in Journeyfront.
>
> > [!TIP]
> >
> > If your company doesn't use a calling integration, add a comment on the Candidate Application after each call so your team knows what happened.
## Log the call outcome
With Webex Contact Center, the **Log call outcome** window opens when a call ends and asks how the call went:
* **Reached:** you spoke with the candidate.
* **Left voicemail:** you left a message.
* **No answer:** nobody picked up.
Add a note if you like, then click **Save**. Click **Skip** to leave it out.

> [!TIP]
>
> Always pick an outcome. Webex can tell that a call connected, but not whether a person or a voicemail greeting answered, so your answer is the only record of what really happened.
If you chose a wrap-up code in the Agent Desktop, it's kept too, as the **Webex code**, alongside your outcome.
## Find calls on the Candidate Application
Calls appear on the Candidate Application's **Comments & Activities** tab, newest first. Each entry is titled by what happened, such as **Called via Webex**, **Called via QUO**, **Answered Call via Webex** for a call from the candidate, or **Webex Call Failed** for a call that didn't reach anyone.
Depending on your provider, an entry can show:
| Detail | What it shows |
| - | - |
| **To** or **From** | The candidate's number |
| **Shown as** or **Received on** | Your number: the caller ID the candidate saw, or the number they called |
| **Duration** | How long you spoke |
| **Answered by** | Who picked up a call from the candidate, when they don't use Journeyfront |
| **Rang for** | How long the phone rang before someone answered |
| **Outcome** | What the recruiter chose, plus their note |
| **Webex code** | The wrap-up code chosen in the Webex Agent Desktop |
| **Ended** | Why a call that didn't connect ended |
| **Summary** | QUO's summary of the conversation |
Below the details, **Play recording** and **View transcript** appear when they're available.

## Calls from candidates
When a candidate calls you back, that call is logged on their record too, including when a different member of your team answers. A call is only logged when the caller's number matches a candidate in your account, so personal and internal calls never appear.
If the candidate has applied to more than one job req, the call goes on one Candidate Application: the one you most recently called them about. If there wasn't a recent call to that number, it goes on the application with the most recent activity. Either way, it's on the right candidate.

## Recordings and transcripts
* **Recordings:** click **Play recording** and the audio plays in place. Anyone with a role on your account can play it, not only the recruiter who made the call. Recordings stay with your calling provider and are streamed when you play them.
* **Transcripts:** click **View transcript** to read the conversation. Transcripts come from QUO. Webex Contact Center doesn't provide them.
## FAQ
> [accordion] Do I need the Webex Agent Desktop open to make a call?
>
> Yes. Webex rings you first and connects the candidate only after you answer, so you need to be signed in and set to **Available**.
> [accordion] Why am I asked how the call went?
>
> Webex can tell that a call connected, but not whether a person or a voicemail greeting answered. Your answer records what actually happened.
> [accordion] I clicked the phone icon and nothing happened. Why?
>
> With Webex, make sure you're signed in to the Agent Desktop and set to **Available**. If the call rings for a few seconds and then ends, ask your admin to check the Webex setup on [Webex Contact Center](/integrations/calling/webex-contact-center#set-up-webex-first).
> [accordion] Who can hear a call recording?
>
> Anyone with a role on your Journeyfront account, from the candidate's record.
> [accordion] Why is there no recording on a call?
>
> Recording is a setting in your calling provider. Ask your admin to check that call recording is turned on. If a recording won't load, it may have expired or been removed in your provider.
> [accordion] A call landed on a different job req than I expected. Why?
>
> When a candidate has more than one application, a call from them goes on the job req you most recently called them about, or else the one with the most recent activity. The call is still on the right candidate.
> [accordion] What if I haven't connected my calling account?
>
> The phone icon opens your computer's default calling app instead, and the call isn't logged. Connect your account in **Personal Settings**, then **Integrations**.
## Related
> [card] [Calling setup](/integrations/calling)
>
> Connect Webex Contact Center or QUO.
> [card] [Text messages](/communication/text-messages)
>
> Message candidates by SMS or WhatsApp.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
> [card] [Finding your way around](/getting-started/navigating)
>
> Where everything lives in Journeyfront.
# Email candidates
Source: https://help.journeyfront.com/communication/email-candidates
Send an email to one candidate or many, from a template or from scratch, now or later.
> [!NOTE]
>
> **Who can do this:** Users with the *Send Emails* permission. Creating and editing the email templates you pick from needs *Company Settings Access*.
Email reaches every candidate, whether or not they've opted in to texts. You can email one candidate from their Candidate Application, or a whole group at once from any candidate list. Start from a team email template or write your own, personalize it with template variables, and send it right away or schedule it. Every email you send is saved in the candidate's activity history.
## Email one candidate
**1. Open the Candidate Application**
Click the candidate's name on the **Candidates** page or a job req's **Candidates** tab.
**2. Choose Email**
Click **Actions** (1), then **Email** (2). The **Email** window opens with the candidate already in **To**.

**3. Pick a template or write your own**
Choose a **Template** to fill in the sender, subject and body for you, or fill in the fields yourself. Anything you change applies to this email only; the template stays as it is.
**4. Send**
Click **Send**. To send it later instead, see [Schedule an email](#schedule-an-email).
## Email many candidates at once
**1. Select the candidates**
On the **Candidates** page or a job req's **Candidates** tab, tick the candidates you want to email. You can also select candidates on a hiring class's candidate list.
**2. Click E-mail**
Click **E-mail** in the actions bar. The **Email** window opens with everyone you selected in **To**.

**3. Write and send**
Pick a template or write your own, then click **Send** or **Schedule**.
Each candidate gets their own copy of the email, with the template variables filled in with their own details. Candidates never see who else received it. On the **Candidates** page you can email candidates from different job reqs in one go; each email uses the details of that candidate's own job req.
> [!TIP]
>
> Filter your list first, for example to everyone in one step who hasn't finished an activity, then tick the header box to select them all. See [Bulk actions](/candidates/bulk-actions).
## The Email window
The **Email** window opens on the right, over the page you're on.

| # | Field | What it's for |
| - | - | - |
| 1 | **Template** | A team email template. Choosing one fills in the fields below. See [Email templates](/communication/email-templates). |
| 2 | **From** | The address the email is sent from. Choose one of Journeyfront's sending addresses. |
| 2 | **From Name** | The sender name candidates see, such as your company or recruiting team. Required. |
| 2 | **Reply To** | Where candidate replies go. Use an inbox your team checks. |
| 3 | **To** | The candidates you selected, with a count. Click the **x** on a candidate to leave them out. |
| 4 | **Subject** | The subject line. Template variables work here too. Required. |
| 4 | **Body** | The message, with a formatting toolbar for headings, lists, colors, links and images. Required. |
| 5 | **Attachment** | Click **Choose File** to attach files, up to 15 MB in total. |
| 5 | **Insert Variable Field** | Copies a template variable so you can paste it into the subject or body. |
| 6 | **Delay Message** | **Now** sends right away. **Later** schedules the email. |
> [!TIP]
>
> Choosing a template fills in **Reply To** for you. If you write an email from scratch, fill it in yourself so replies land in your team's inbox.
## Personalize with template variables
Template variables are placeholders that Journeyfront replaces with each candidate's details when the email goes out. Type them in double curly braces, or click **Insert Variable Field**, choose one to copy it, and paste it where you want it.
| Variable | Replaced with |
| - | - |
| `{{first_name}}` | The candidate's first name |
| `{{last_name}}` | The candidate's last name |
| `{{job_name}}` | The job req's title (its External Job Title, if it has one) |
| `{{job_invite_link}}` | A link to the job req's application, where the candidate can pick up where they left off |
| `{{current_step_name}}` | The name of the candidate's current step |
| `{{company_name}}` | Your company name |
`{{company_name}}` isn't in the **Insert Variable Field** list, but it works the same way. See [Template variables](/communication/template-variables) for the full list, including the variables in system emails.
> [!TIP]
>
> Include `{{job_invite_link}}` whenever you're asking a candidate to finish something. It takes them straight back to their application, so there's nothing for them to search for.
## Schedule an email
**1. Choose Later**
Under **Delay Message**, set **When** to **Later**.

**2. Pick the date and time**
Choose the date in **On** and the time in **At**, in 15-minute steps. Journeyfront suggests 8:15 AM tomorrow.
**3. Click Schedule**
The **Send** button changes to **Schedule**. Click it to schedule the email.
The email goes out at the time you chose, with the variables filled in at that point.
## Where sent emails show up
Every email you send is recorded on the candidate's Candidate Application, on the **Comments & Activities** tab, as **Email Sent**. The entry shows the template (if you used one), who it was from, who it went to, the subject and the body, with the candidate's details filled in. Click **Read More** to see a long email in full. Scheduled emails appear there once they're sent.

Replies don't come back into Journeyfront. Candidates who reply are writing to the **Reply To** address, so their answer arrives in that inbox.
## Send emails automatically
* **From your workflow:** an automation rule with the **Send Email to Candidate** action sends a team email template when something happens, like a candidate being moved to a step or rejected, with an optional delay. See [Automation rules](/workflows/automation-rules).
* **When you change a candidate's step:** tick **Send email inviting user to complete the next step** in the **Change Step** window. See [Move candidates through steps](/candidates/move-through-steps).
* **Reminders:** Journeyfront reminds candidates who haven't finished their application, and before their interviews. See [Reminder emails](/communication/reminder-emails).
## FAQ
> [accordion] Why don't I see Email or E-mail?
>
> Both need the *Send Emails* permission in your security role. Ask your Journeyfront admin. See [Security roles](/account-setup/security-roles).
> [accordion] Can I add other people, or CC a colleague?
>
> No. **To** only holds the candidates you selected. You can remove a candidate with the **x** on their name, but you can't add other addresses, and there's no CC or BCC.
> [accordion] Can candidates see who else got the email?
>
> No. Each candidate gets their own email, addressed only to them.
> [accordion] Where do candidate replies go?
>
> To the **Reply To** address on the email. They don't appear in Journeyfront, so use an inbox your team checks.
> [accordion] Can I change a template's wording just for this email?
>
> Yes. Choosing a template fills in the fields, and you can edit any of them before you send. The template itself doesn't change. To change it for everyone, edit it in **Settings**, then **Templates**, then **E-mail Template**.
> [accordion] How big can attachments be?
>
> Up to 15 MB in total per email.
> [accordion] Does rejecting a candidate email them?
>
> No. Email them yourself, or set up an automation rule to do it. See [Reject candidates](/candidates/reject).
> [accordion] Should I email or text?
>
> Texts get read faster, but candidates have to opt in to them. Email reaches everyone with an email address. Many teams send both for important steps. See [Text messages](/communication/text-messages).
## Related
> [card] [Email templates](/communication/email-templates)
>
> Create team emails and edit the emails Journeyfront sends.
> [card] [Template variables](/communication/template-variables)
>
> Every variable you can use in emails and texts.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Act on many candidates at once.
> [card] [Text messages](/communication/text-messages)
>
> Text candidates one at a time or in bulk.
# Team emails and system emails
Source: https://help.journeyfront.com/communication/email-templates
Create the emails your team sends, and edit the emails Journeyfront sends for you.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission.
Journeyfront has two kinds of email templates, both under **Settings**, then **Templates**, then **E-mail Template**:
| | Team Emails | System Emails |
| - | - | - |
| **What they are** | Templates your team writes | The emails Journeyfront sends automatically |
| **Who sends them** | Your team, from the **Email** window, or your automation rules | Journeyfront, when something happens, like a candidate applying or booking an interview |
| **Create or delete** | Yes | No, the list is fixed |
| **Edit** | Everything | Subject, body, sender and reply-to |
| **Undo your changes** | Edit again | **Restore to Default** |

## Create a team email
**1. Open the Team Emails tab**
Go to **Settings**, then **Templates**, then **E-mail Template**. **Team Emails** is the first tab.
**2. Click E-mail Template**
Click **E-mail Template** at the top right. The **Email Editor** opens on a **New Email Template**.
**3. Write the email**
On the **Email Body** tab, write the email. The toolbar has headings, font size, lists, bold and other text styles, text and background color, alignment, links, images, video and **Edit HTML**.
**4. Fill in the details**
On the **Details** tab, enter the **Template Name** and **Subject**, choose the **From Email**, and fill in **From Name**, **Reply To** and an optional **Description**. See [Template details](#template-details).
**5. Save**
Click **Save** at the top right. The **Save** and **Cancel** buttons appear once you've made a change.
Your new template is now in the **Template** list of the **Email** window, and in the **Send Email to Candidate** action of automation rules. See [Email candidates](/communication/email-candidates) and [Automation rules](/workflows/automation-rules).
> [!TIP]
>
> Write team emails for the moments your recruiters repeat every day: interview follow-ups, "we're still reviewing" updates, start-date details. One good template saves hundreds of hand-typed emails, and keeps everyone's wording consistent.
## Template details
| Field | What it's for |
| - | - |
| **Template Name** | Your name for the template. Candidates never see it. |
| **Subject** | The subject line candidates see. Template variables work here. |
| **From Email** | The address the email is sent from: one of Journeyfront's two sending addresses. |
| **From Name** | The sender name candidates see, such as your company or recruiting team. |
| **Reply To** | Where candidate replies go. Use an inbox your team checks. |
| **Description** | A note for your team about what the template is for. Candidates never see it. |
## Add template variables
Template variables, like `{{first_name}}`, are replaced with each candidate's details when the email is sent. Click **Insert Variable Field** above the editor and choose a variable to copy it, then paste it into the body or subject.
The list shows the variables that template supports. Team emails all share the same set; each system email has its own. See [Template variables](/communication/template-variables).
## Preview and test data
The **Preview** panel on the right shows the email as candidates will see it: the subject, the sender and the body. It updates as you type.
To see variables filled in, open the **Test Data** tab and enter a sample value for each variable, like a first name and job title. The preview swaps them in. Test data is only for the preview, and it's saved in your browser, not with the template.

> [!TIP]
>
> Before you save, put in test data and read the preview once. A misspelled variable stays as `{{...}}` in the preview, which is the easiest way to catch it.
## Edit or delete a team email
On the **Team Emails** tab, click the edit icon on a template's row to open it in the **Email Editor**. Make your changes and click **Save**.
To delete a template, click its trash icon, then confirm in the **Remove E-mail Template** window.
> [!WARNING]
>
> Deleting a team email can't be undone. Automation rules that send it stop sending that email, so check your job reqs' automation rules before you delete one.
## System emails
The **System Emails** tab lists the emails Journeyfront sends for you. Each row shows the template's name with a short description, and **Last Updated** shows **System Default** until someone edits it.
| System email | When it's sent |
| - | - |
| **Invitation Admin** | Someone on your team adds a new user to your account. |
| **Invitation Applicant** | A candidate comes in from a connected system, like another ATS, and is invited to complete their application. |
| **Invitation Hiring Manager** | Someone is added to a job req's hiring team. |
| **Invitation Applicant Manual Add** | Your team adds a candidate, or imports candidates, and invites them to apply. |
| **User is moved to a new step notification** | You change a candidate's step and tick **Send email inviting user to complete the next step**. |
| **Scorecard Share Link** | You share a Candidate Application with a colleague. |
| **User Reminder** | A candidate hasn't finished their application. See [Reminder emails](/communication/reminder-emails). |
| **Interview Reminder Notification** | Before a booked interview. See [Interview reminders](/interviews/reminders). |
| **Interview Schedule Invite** | A candidate is invited to book an interview. |
| **Interview Invite Notification** | The app describes it as the email a candidate gets when an interview is scheduled for them. |
| **Interview Schedule Confirmation** | A candidate books an interview. |
| **Easy Apply Invite** | A candidate applies through Indeed Easy Apply and is invited to finish their application. |
| **Onboarding Form** | A candidate is sent an onboarding form. |
| **Offer E-Signature Candidate** | A candidate is sent their offer to sign. See [E-signatures](/offers/e-signatures). |
| **Referral Invitation** | Someone refers a candidate. |
| **Lead Ad Invite** | A candidate submits a lead ad form and is invited to complete their application. |
A few standard emails, such as password resets and some notifications to your own team, aren't in the list and can't be changed.
### Edit a system email
**1. Open the System Emails tab**
Go to **Settings**, then **Templates**, then **E-mail Template**, and click **System Emails**.
**2. Open the template**
Click the edit icon on the template's row.
**3. Make your changes**
Edit the **Email Body**, and on the **Details** tab, the **Subject**, **From Email**, **From Name** and **Reply To**. The **Template Name** and **Description** of a system email can't be changed. On the **Plain Text** tab, update the unformatted version of the email that's sent along with it, for email apps and screen readers that don't show formatting.
**4. Save**
Click **Save**. Your version is used from now on, for every job req in your account.
> [!TIP]
>
> Set **Reply To** to an inbox your team checks. Until you do, replies to a system email go to Journeyfront's support address instead of to your team.
### Restore a system email
To go back to Journeyfront's original version, open the template and click **Restore to Default**, then **Restore**. All of your changes to that template are lost and can't be recovered.
## FAQ
> [accordion] Can I send myself a test email?
>
> Not from the editor. Use the **Preview** panel with the **Test Data** tab to check the email with sample values before you save.
> [accordion] Does editing a system email change it for every job req?
>
> Yes. Each system email has one version for your whole account.
> [accordion] Can different job reqs send different invite or reminder emails?
>
> Not with system emails, which are shared across your account. For job-specific messages, create a team email and send it from that job req's automation rules.
> [accordion] Why can't I find the Save button?
>
> **Save** appears once you've changed something. If it's greyed out, a required field is empty: the body, the **Subject**, or **Reply To** on the **Details** tab, and the **Template Name** for a team email.
> [accordion] I changed a system email and want the original back. What do I do?
>
> Open it and click **Restore to Default**. Your changes are replaced with Journeyfront's original.
> [accordion] Can I add our logo or links?
>
> Yes. Use the image and link buttons in the editor toolbar, or **Edit HTML** for full control.
## Related
> [card] [Email candidates](/communication/email-candidates)
>
> Send team emails to one candidate or many.
> [card] [Template variables](/communication/template-variables)
>
> Every variable, for team and system emails.
> [card] [Reminder emails](/communication/reminder-emails)
>
> When Journeyfront reminds candidates to finish.
> [card] [Automation rules](/workflows/automation-rules)
>
> Send team emails automatically.
# Message templates
Source: https://help.journeyfront.com/communication/message-templates
Save the texts your team sends most, with variables for each candidate's details, and use them in the message panel, bulk messages and automations.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission create and edit message templates. Anyone with the *Send Messages* permission can send them.
>
> **Availability:** Uses the Text Messages add-on. See [Texting providers](/integrations/texting-providers).
A message template is a saved text message your whole team can send. Write it once, with variables like the candidate's first name and the job title, and recruiters pick it instead of typing the same message again and again. Every candidate still gets a personal message, because Journeyfront fills in their own details.
Message templates live in **Settings**, then **Templates**, then **Message Template**. The list shows each template's **Channels**, its **WhatsApp Status** if your company uses WhatsApp, and when it was last updated. Use the pencil to edit a template and the trash can to delete it.

## Create a message template
**1. Open message templates**
Go to **Settings**, then **Templates**, then **Message Template**, and click **Add Message Template**.
**2. Name it**
Enter a **Template Name** (1). Recruiters pick templates by this name, so make it say what the message is for, like "Phone Screen Invite". Candidates never see it.
**3. Write the text message**
On the **SMS** tab (2), write the **Message** (3), up to 1,600 characters. Add variables for the candidate's details (see below).
**4. Save**
Click **Save**. The template is ready to use right away. Text message templates don't need approval.

> [!TIP]
>
> Keep templates short and specific: who you are, what the candidate should do next, and by when. Long texts get split into several messages and are easier to ignore.
## Add variables
Variables are placeholders in double curly braces that Journeyfront replaces with each candidate's details when the message sends. To add one, choose it from **Insert Variable Field** (4). It's copied, so paste it where you want it in the message.
| Variable | Replaced with |
| - | - |
| `{{first_name}}` | The candidate's first name |
| `{{last_name}}` | The candidate's last name |
| `{{job_name}}` | The job req's title |
| `{{job_invite_link}}` | A link back to the candidate's application |
| `{{current_step_name}}` | The name of the candidate's current step |
For example, "Hi `{{first_name}}`, do you have 15 minutes tomorrow for a quick phone screen for `{{job_name}}`?" reaches Erin Luna as "Hi Erin, do you have 15 minutes tomorrow for a quick phone screen for Billing Support Specialist?"
> [card] [Template variables](/communication/template-variables)
>
> Every variable you can use in emails and texts.
## Add a WhatsApp version
If your company has connected WhatsApp, the same template can also hold a WhatsApp version on its **WhatsApp** tab. Journeyfront sends the version that matches the channel you send on. Unlike text messages, WhatsApp versions have to be approved by WhatsApp before you can send them, and the **WhatsApp Status** column shows where each one stands. Until WhatsApp is connected, the **WhatsApp** tab is greyed out.
> [card] [WhatsApp templates](/communication/whatsapp#whatsapp-templates)
>
> Write a WhatsApp version, submit it for approval and track its status.
## Where templates are used
* **The message panel.** On a Candidate Application, open the message panel and click the bookmark icon (**Message Template**). **Select Template** lists your templates with a preview of each. Click **Use Template** to put it in the message box, where you can still edit it before you send.
* **Bulk messages.** When you select candidates and click **Message**, choose a **Template** to send the same message to everyone, each with their own details filled in.
* **Automation rules.** The **Send SMS to Candidate** and **Send WhatsApp Message to Candidate** actions send one of your templates automatically, for example when a candidate reaches a step.
* **AI agents.** Agents that send WhatsApp messages use your approved WhatsApp templates.

> [card] [Text messages](/communication/text-messages)
>
> Send texts one at a time or in bulk, and follow each conversation.
> [card] [Automation rules](/workflows/automation-rules)
>
> Send a template automatically when something happens in your workflow.
## FAQ
> [accordion] Why can't I see Message Template in Settings?
>
> Creating and editing templates needs the *Company Settings Access* permission. Ask your Journeyfront admin. See [Security roles](/account-setup/security-roles).
> [accordion] Can I change a template's wording just for one message?
>
> Yes. In the message panel, **Use Template** puts the text in the message box, and you can edit it before you send. The template itself doesn't change.
> [accordion] Do text message templates need approval?
>
> No. Only WhatsApp versions are reviewed by WhatsApp. A text message template is ready as soon as you save it.
> [accordion] If I edit a template, does it change messages already sent?
>
> No. Messages already sent stay as they were. The change applies to messages sent from then on.
> [accordion] Are message templates the same as email templates?
>
> No. Message templates are for texts and WhatsApp. Emails use team email templates. See [Team emails and system emails](/communication/email-templates).
## Related
> [card] [Text messages](/communication/text-messages)
>
> Text candidates one at a time or in bulk.
> [card] [WhatsApp](/communication/whatsapp)
>
> Message candidates on WhatsApp.
> [card] [Template variables](/communication/template-variables)
>
> Every variable you can use in emails and texts.
> [card] [Team emails and system emails](/communication/email-templates)
>
> Templates for the emails your team sends.
# Reminder emails
Source: https://help.journeyfront.com/communication/reminder-emails
How Journeyfront reminds candidates to finish their application, and when the reminders stop.
> [!NOTE]
>
> **Who can do this:** Reminders go out automatically. Changing the reminder email needs the *Company Settings Access* permission.
Candidates who start an application and don't finish it are easy to lose. Journeyfront emails them a reminder to come back and complete it, with a link straight to their application, so you don't have to chase every one of them yourself. This page covers the application reminder. Journeyfront also sends [interview reminders](/interviews/reminders), and you can add your own follow-ups with automation rules or [AI agents](/workflows/ai-agents).
## Who gets application reminders
A candidate gets reminders for a Candidate Application when all of these are true:
* **The application isn't 100% complete.** Reminders are for applications that are still incomplete.
* **It's been at least a day.** The first reminder goes out about 24 hours after they started.
* **It's within the first 7 days.** No reminders are sent after that.
* **They haven't been rejected**, and the job req hasn't been archived or deleted.
Each Candidate Application gets its own reminders. A candidate who applied to two job reqs, or applied to the same one twice, can get reminders for each one.
## When reminders go out
| Reminder | When |
| - | - |
| First | About 24 hours after the candidate started their application |
| Second | About 24 hours after the first |
| Third and last | About 24 hours after the second |
A candidate gets **at most three** reminders per application, all within the first 7 days. Journeyfront checks for candidates who are due a reminder every 15 minutes.
The timing and the number of reminders are the same for every account and can't be changed. Reminders can be turned off for your whole account; ask your Customer Success Manager.
## How "complete" is worked out
The percentage complete counts the activities in the steps a candidate has reached, including the application form. Interviews aren't counted. (This assumes the job req's **Gate Steps** setting is on, which is the default. With it off, every step counts.)
When a candidate finishes every counted activity, their application reaches 100% and the reminders stop. If you move them to a new step, the new step's activities count too, so the percentage can drop below 100% again. If that happens within the first 7 days and they haven't had three reminders yet, they can get another one.
> [!TIP]
>
> Keep activities that your team completes, like an offer or a background check, in a later step than the activities candidates complete themselves. That way, candidates who've done everything that's theirs to do reach 100% and stop getting reminders.
## What the reminder email says
The reminder uses the **User Reminder** system email. By default, the subject is "Reminder - Complete your application", and the email names the job title and your company, says what percentage of the application the candidate has completed, and links them back to it.
### Change the reminder email
**1. Open the template**
Go to **Settings**, then **Templates**, then **E-mail Template**, click **System Emails**, and click the edit icon on **User Reminder**.
**2. Edit it**
Change the body on the **Email Body** tab, and the **Subject**, **From Name** and **Reply To** on the **Details** tab.
**3. Save**
Click **Save**. Every reminder from now on uses your version.

The reminder can use `{{user_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{assessment_link}}` and `{{percent_complete}}`. See [Template variables](/communication/template-variables) and [Email templates](/communication/email-templates).
> [!TIP]
>
> Set **Reply To** to an inbox your team checks. Candidates often reply to reminders with questions, or to say they're done, and until you set it, those replies go to Journeyfront's support address.
## Send your own reminders
The application reminder is the same for every job req. For reminders that fit a particular step, set up an automation rule on the job req's workflow:
* **Trigger:** **Candidate Time in Step Reaches**, with the number of days and hours.
* **Action:** **Send Email to Candidate** with a team email template, or **Send SMS to Candidate** for a text.
See [Automation rules](/workflows/automation-rules). To remind candidates who were invited to book an interview but haven't, see [See who hasn't booked](/interviews/who-hasnt-booked).
## FAQ
> [accordion] A candidate finished but still got a 'complete your application' reminder. Why?
>
> Check these, in order:
>
> 1. **Which job req is it for?** The reminder names the job title and company. If the candidate has another Candidate Application, for a different job req or from applying again, the reminder is for that one. Their Candidate Profile shows all of their applications.
> 2. **Is the application really at 100%?** The percentage counts every activity in the steps they've reached except interviews. An activity your team completes, like an offer, keeps it below 100%.
> 3. **Did they finish right after it was sent?** Reminders are checked every 15 minutes, so one can go out shortly before the candidate finishes.
> [accordion] A candidate replied 'I'm done' to the reminder. Where did it go?
>
> To the **Reply To** address on the **User Reminder** template. If you haven't set one, it went to Journeyfront's support address. Set **Reply To** to your team's inbox so you see these replies.
> [accordion] Who is 'Cody at Journeyfront'?
>
> It's the reminder's default sender name. Change it in **From Name** on the **User Reminder** template's **Details** tab, for example to your company's name.
> [accordion] Can I stop reminders for one candidate?
>
> Not on their own. Reminders stop when the application reaches 100%, after three reminders, after 7 days, or when you reject the candidate.
> [accordion] Can I change how often reminders go out?
>
> No, the schedule is fixed. Use automation rules for extra reminders on your own schedule, or ask your Customer Success Manager to turn the application reminders off for your account.
> [accordion] Why didn't a candidate get a reminder?
>
> More than 7 days may have passed since they started, or they've already had three. Also ask them to check their spam or junk folder.
> [accordion] Do reminders go out by text?
>
> No, application reminders are emails. To text candidates, use an automation rule with **Send SMS to Candidate**. See [Text messages](/communication/text-messages).
## Related
> [card] [Interview reminders](/interviews/reminders)
>
> Remind candidates before their interview.
> [card] [Email templates](/communication/email-templates)
>
> Edit the User Reminder email.
> [card] [Automation rules](/workflows/automation-rules)
>
> Send your own follow-ups at any step.
> [card] [AI agents](/workflows/ai-agents)
>
> Personal follow-ups for candidates who stall.
# Template variables
Source: https://help.journeyfront.com/communication/template-variables
Personalize emails and texts with each candidate's name, job and links.
> [!NOTE]
>
> **Who can do this:** Anyone who writes emails (*Send Emails*) or texts (*Send Messages*) can use variables. Editing templates needs *Company Settings Access*.
Template variables are placeholders in double curly braces, like `{{first_name}}`. When an email or text goes out, Journeyfront replaces each one with that candidate's details, so one template can greet hundreds of candidates by name and send each of them their own link.
> [!NOTE]
>
> Template variables are for **emails and texts**. Offer letters and documents use **merge keys**, like `{{SALARY}}` or `{{CANDIDATE_NAME}}`, which are a separate list. See [Offer fields and merge keys](/offers/offer-fields).
## How to add a variable
* **Type it** in double curly braces, exactly as it's spelled below, in the subject or the body.
* **Or click Insert Variable Field** and choose a variable. It's copied for you; paste it where you want it.
**Insert Variable Field** is in the **Email** window, the **Email Editor**, and the message template and bulk message windows for texts. In each place, it lists the variables that template can use.

## Team emails, texts and automations
These variables work in everything your team sends: emails from the **Email** window, team email templates, text message and WhatsApp templates, bulk messages, and the **Send Email to Candidate** and **Send SMS to Candidate** automation actions.
| Variable | Replaced with |
| - | - |
| `{{first_name}}` | The candidate's first name |
| `{{last_name}}` | The candidate's last name |
| `{{job_name}}` | The job req's title (its External Job Title, if it has one) |
| `{{job_invite_link}}` | A link to the job req's application, where the candidate can sign in and pick up where they left off |
| `{{current_step_name}}` | The name of the candidate's current step on that job req |
| `{{company_name}}` | Your company name |
`{{company_name}}` isn't in the **Insert Variable Field** list, but it works the same way.
When you email or text candidates from different job reqs at once, each candidate's `{{job_name}}`, `{{job_invite_link}}` and `{{current_step_name}}` come from their own job req.
WhatsApp templates use the same variables, which are turned into numbered placeholders when the template is submitted for approval. See [WhatsApp](/communication/whatsapp).
## System emails
Each system email has its own set of variables, which you'll see in **Insert Variable Field** when you edit it. They're filled in by Journeyfront from whatever triggered the email, so a variable from one system email won't work in another, and the team email variables above don't work in system emails.
| System email | Variables |
| - | - |
| **Invitation Admin** | `{{inviter_name}}`, `{{company_name}}`, `{{link_to_profile}}` |
| **Invitation Applicant** | `{{user_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{assessment_link}}` |
| **Invitation Hiring Manager** | `{{inviter_name}}`, `{{company_name}}`, `{{smartreq_name}}`, `{{link_to_profile}}` |
| **Invitation Applicant Manual Add** | `{{user_first_name}}`, `{{inviter_name}}`, `{{job_title}}`, `{{company_name}}`, `{{assessment_link}}` |
| **User is moved to a new step notification** | `{{user_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{job_link}}`, `{{message}}` |
| **Scorecard Share Link** | `{{recipient_name}}`, `{{inviter_name}}`, `{{candidate_name}}`, `{{job_title}}`, `{{scorecard_link}}`, `{{message}}` |
| **User Reminder** | `{{user_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{assessment_link}}`, `{{percent_complete}}` |
| **Interview Reminder Notification** | `{{invitee_name}}`, `{{company_name}}`, `{{interviewers}}`, `{{interview_date}}`, `{{interview_type}}`, `{{invite_link}}`, `{{address}}`, `{{link_to_reschedule}}` |
| **Interview Schedule Invite** | `{{invitee_name}}`, `{{company_name}}`, `{{link_to_schedule}}`, `{{message}}` |
| **Interview Invite Notification** | `{{invitee_name}}`, `{{company_name}}`, `{{date_time}}`, `{{message}}` |
| **Interview Schedule Confirmation** | `{{invitee_name}}`, `{{company_name}}`, `{{date_time}}`, `{{event_details}}`, `{{conferencing_link}}`, `{{address}}`, `{{link_to_reschedule}}` |
| **Easy Apply Invite** | `{{user_first_name}}`, `{{company_name}}`, `{{assessment_link}}` |
| **Onboarding Form** | `{{user_first_name}}`, `{{company_name}}`, `{{onboarding_link}}` |
| **Offer E-Signature Candidate** | `{{candidate_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{signing_link}}`, `{{custom_message}}`, `{{expire_date}}` |
| **Referral Invitation** | `{{user_first_name}}`, `{{job_title}}`, `{{company_name}}`, `{{job_invite_link}}`, `{{referrer_name}}`, `{{referrer_message}}` |
| **Lead Ad Invite** | `{{user_first_name}}`, `{{company_name}}`, `{{assessment_link}}` |
### What each system email variable means
| Variable | Replaced with |
| - | - |
| `{{user_first_name}}`, `{{candidate_first_name}}` | The candidate's first name |
| `{{candidate_name}}`, `{{invitee_name}}` | The candidate's full name |
| `{{job_title}}`, `{{smartreq_name}}` | The job req's title |
| `{{company_name}}` | Your company name |
| `{{assessment_link}}`, `{{job_link}}`, `{{job_invite_link}}` | The candidate's link to start or continue their application |
| `{{percent_complete}}` | How much of their application the candidate has completed, as a percentage |
| `{{message}}`, `{{custom_message}}`, `{{referrer_message}}` | The optional message written by the person who triggered the email |
| `{{inviter_name}}` | The person on your team who sent the invite or shared the Candidate Application |
| `{{recipient_name}}` | The colleague a Candidate Application was shared with |
| `{{referrer_name}}` | The person who referred the candidate |
| `{{link_to_profile}}` | The new user's link to sign in to Journeyfront |
| `{{scorecard_link}}` | The link to the shared Candidate Application |
| `{{link_to_schedule}}` | The candidate's link to book their interview |
| `{{link_to_reschedule}}` | The candidate's link to reschedule or cancel their interview |
| `{{interview_date}}`, `{{date_time}}` | The interview's date and time |
| `{{interview_type}}` | The interview format, such as video, phone or in person |
| `{{interviewers}}` | Who the candidate is interviewing with |
| `{{invite_link}}`, `{{conferencing_link}}` | The video meeting link, for video interviews |
| `{{address}}` | The location, for in-person interviews |
| `{{event_details}}` | The interview's details |
| `{{onboarding_link}}` | The candidate's link to their onboarding form |
| `{{signing_link}}` | The candidate's link to sign their offer |
| `{{expire_date}}` | When the signature request expires, if it does |
## Add a fallback
If a candidate's detail is empty, its variable is left blank. To show something else instead, add a fallback with `default`, the way Journeyfront's own templates do:
```text theme={null}
Hi {{first_name | default:'there'}},
```
A candidate with no first name on file reads "Hi there," instead of "Hi ,".
## FAQ
> [accordion] Why did a variable come out blank?
>
> Either the candidate doesn't have that detail, or the variable isn't one that template supports, for example a team email variable in a system email. Check the spelling against the lists above, and add a fallback for details that can be empty.
> [accordion] Why does my email show \{\{first_name}} instead of a name?
>
> In the editor's **Preview**, variables stay as they are until you enter sample values on the **Test Data** tab. In a sent email they're always filled in.
> [accordion] Can I use variables in the subject line?
>
> Yes, in team and system emails alike.
> [accordion] Can I use custom fields as variables?
>
> No. Emails and texts use the variables on this page. Custom fields can go into offer letters and documents as merge keys. See [Offer fields and merge keys](/offers/offer-fields).
> [accordion] Is \{\{job_invite_link}} the same for every candidate?
>
> It points to the same job req's application, set up for each candidate's own email address. Send it to the candidate it's meant for, not to a group.
## Related
> [card] [Email templates](/communication/email-templates)
>
> Team emails and system emails.
> [card] [Email candidates](/communication/email-candidates)
>
> Send emails one at a time or in bulk.
> [card] [Message templates](/communication/message-templates)
>
> Message templates for texts and WhatsApp.
> [card] [Offer fields and merge keys](/offers/offer-fields)
>
> The placeholders for offer letters and documents.
# Text messages
Source: https://help.journeyfront.com/communication/text-messages
Text candidates one at a time, in bulk or automatically, and keep every conversation on the Candidate Application.
> [!NOTE]
>
> **Who can do this:** Users with the *Send Messages* permission. Creating message templates needs the *Company Settings Access* permission.
>
> **Availability:** Uses the Text Messages add-on. Your admin sets up a texting provider and a sending number first (see [Texting providers](/integrations/texting-providers)).
Candidates read texts much faster than email, so a quick text keeps them moving through screening, assessments and interviews. Message one candidate, a whole list at once, or let your workflow send messages for you. Every message and reply is saved on the Candidate Application, so anyone who picks up a candidate sees the full conversation.
If your company has connected WhatsApp, you send WhatsApp messages from the same places. See [WhatsApp](/communication/whatsapp) for what's different.

## Send a message to one candidate
**1. Open the message panel**
Open the Candidate Application and click the **message icon** next to the candidate's phone number. The message panel opens with your conversation so far. You can also click **Actions**, then **Message**.

**2. Choose the number to send from**
In **From**, choose a number. Text numbers are labeled "SMS:" followed by the number. Your WhatsApp number, if you have one, is labeled "WhatsApp".

**3. Write your message**
Type a message, or click the bookmark icon (**Message Template**) and choose **Use Template** on a saved message. The template's text goes into the message box, where you can edit it, and its variables are filled in with the candidate's details when it sends. See [Message templates](/communication/message-templates).
**4. Send**
Click send. The message goes out right away.
> [!TIP]
>
> Only numbers that can send on a channel appear in **From**. If your number is missing, ask your admin to check it in **Settings**, then **Phone Numbers**.
## Message many candidates at once
**1. Select candidates**
On the **Candidates** page, or a job req's **Candidates** tab, select the candidates you want to message.
**2. Click Message**
Click **Message** in the actions bar.

**3. Choose a number and write your message**
Pick a number in **Text From**, then write a message or choose a **Template**.
**4. Send now or schedule it**
Send right away, or tick **Delay sending message** and pick a date and time.
> [!TIP]
>
> You don't need to clean up your list before a scheduled send. Anyone who opts out before the message goes out is skipped automatically.
## Send messages automatically
An automation rule on a job req's workflow can text candidates for you when they reach a step, with the **Send SMS to Candidate** action (or **Send WhatsApp Message to Candidate**) and one of your message templates.
> [card] [Automation rules](/workflows/automation-rules)
>
> Set up rules that send messages when candidates reach a step.
## Where conversations show up
* **The message panel** shows the full conversation for the number you pick in **From**.
* **The Comments & Activities tab** on the Candidate Application logs messages alongside the candidate's other history, such as comments and calls.
* **Unread badges** tell you a candidate has replied. Open the message panel to read the reply and answer it.
Replies go to the candidate your team messaged. Sometimes one phone number belongs to more than one record in your account, for example someone who applied twice. Journeyfront then picks, in order:
1. The candidate your team texted from that number in the last 30 days.
2. Otherwise, the candidate whose application changed most recently.
3. Otherwise, any candidate in your account with that phone number.
A reply from a number that doesn't belong to anyone in your account is kept on that number's conversation and shown as an unknown number.
## Track delivery
Each text shows the time it was sent. If a message can't be delivered, **Not delivered** appears under it. Hover over it to see why. Common causes, like a landline or a candidate who opted out, are explained in plain words. For anything else, you see the provider's error message and code.

## Message templates
Save your common messages as templates so anyone on your team can send them, with each candidate's details filled in. Admins create them in **Settings**, then **Templates**, then **Message Template**.
> [card] [Message templates](/communication/message-templates)
>
> Create text and WhatsApp templates, add variables, and see where they're used.
## Opt-in and opt-out
* Candidates opt in to texts on your application form. If a candidate hasn't opted in, the message panel shows a warning at the top.
* A candidate who replies **STOP** (or STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT) stops getting texts from your account. Replying **START**, **YES** or UNSTOP opts them back in.
* An opt-out applies to every record in your account with that phone number.
* Messages scheduled before a candidate opted out aren't sent.
## Credits and billing
If Journeyfront provides your texting account, texts draw from a prepaid messaging balance. Admins can see the balance in **Settings**, then **Add-Ons**, then **Text Messages**. If your company uses its own Twilio or Webex Connect account, your provider bills you directly and there's no Journeyfront balance. See [Add-ons and credits](/account-setup/add-ons).
## What candidates see
Text messages come from your sending number. Candidates can reply, and can reply STOP at any time to opt out.
## FAQ
> [accordion] Why don't I see our number in the From list?
>
> Only numbers that can send on that channel appear. A number connected only to WhatsApp won't show for SMS, and a removed number won't show at all. Ask your admin to check **Settings**, then **Phone Numbers**.
> [accordion] Can I schedule a message for later?
>
> Yes, when you message several candidates at once with the **Message** action.
> [accordion] Why was my message not delivered?
>
> Hover over **Not delivered** on the message to see the reason. Common causes are an invalid or landline number, or a candidate who opted out.
> [accordion] A candidate says they replied, but I don't see it. Why?
>
> First check whether the reply landed on another record with the same phone number. If replies aren't arriving at all, ask your admin to check the **Candidate replies** step in **Settings**, then **Add-Ons**, then **Text Messages**. It shows whether replies are reaching Journeyfront.
> [accordion] Does it matter which provider our numbers use?
>
> No. The message panel, templates, replies and delivery updates work the same for every provider.
## Related
> [card] [WhatsApp](/communication/whatsapp)
>
> Message candidates on WhatsApp.
> [card] [Texting providers](/integrations/texting-providers)
>
> Set up your provider and phone numbers.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> See your messaging balance and usage.
> [card] [Calling candidates](/communication/calling)
>
> Call candidates and log every call.
> [card] [Message templates](/communication/message-templates)
>
> Saved messages for texts and WhatsApp.
# WhatsApp
Source: https://help.journeyfront.com/communication/whatsapp
Message candidates on WhatsApp with approved templates, and keep every conversation on the Candidate Application.
> [!NOTE]
>
> **Who can do this:** Users with the *Send Messages* permission send WhatsApp messages. Creating WhatsApp templates needs *Company Settings Access*.
>
> **Availability:** WhatsApp is part of the Text Messages add-on. Your admin connects your company's WhatsApp Business number first (see [WhatsApp setup](/integrations/texting-providers/whatsapp)).
In many countries, candidates live on WhatsApp more than on text messages. Once your company's WhatsApp Business number is connected, you can message candidates on WhatsApp from the same places you text them: the message panel on a Candidate Application, the bulk **Message** action and workflow automations. Every message and reply is saved on the Candidate Application.
WhatsApp has a few rules that SMS doesn't, mostly around **templates**: WhatsApp only lets a business start a conversation with a message it has approved in advance.
## Send a WhatsApp message
* **To one candidate:** open the Candidate Application, click the **message icon**, and choose your WhatsApp number in **From** (it's labeled "WhatsApp"). To start a conversation, pick an approved template. You'll see a preview with the candidate's details filled in before you send.
* **To many candidates:** select candidates on the **Candidates** page or a job req's **Candidates** tab, choose **Message**, pick your WhatsApp number and an approved template. You can send now or schedule it.
* **Automatically:** on a job req's workflow, add an automation with the **Send WhatsApp Message to Candidate** action and an approved template.


Everything else works the same as text messages. See [Text messages](/communication/text-messages).
## WhatsApp rules
* **Templates start conversations.** To message a candidate first, use an approved template.
* **Free-form replies for 24 hours.** Once the candidate replies, you can type free-form messages for 24 hours. After that, you need a template again.
* **Candidates must be on WhatsApp** on the phone number you have for them.
* **Daily limits.** WhatsApp limits how many new conversations your business can start each day. See [WhatsApp limits and quality](/integrations/texting-providers/whatsapp#whatsapp-limits-and-quality).
While the 24-hour window is open, a green bar above the message box shows how long you have left to reply freely.

## Connect WhatsApp
An admin connects your company's WhatsApp Business number once. WhatsApp goes through the same provider you text through, so set up texting first.
**1. Open the Text Messages add-on**
Go to **Settings**, then **Add-Ons**, then **Text Messages**, and click **Connect WhatsApp**.
**2. Choose the number and display name**
Choose the phone number candidates will message you on and confirm the display name candidates will see. Then click **Connect your WhatsApp Business Account**.

**3. Finish in Facebook**
In the Facebook window, select **your own** business account. When asked about the phone number, choose **"Use a display name only."** The number is ready to message once its status shows **Online**.
For every step, or if your WhatsApp number sends through Webex Connect, see [WhatsApp setup](/integrations/texting-providers/whatsapp).
## WhatsApp templates
Create your templates ahead of time so they're approved and ready when you need them. A message template can hold both an SMS version and a WhatsApp version, and Journeyfront uses the right one for the channel you send on. The **WhatsApp** tab on a template appears once your WhatsApp number is connected.
If your WhatsApp number sends through Twilio (Journeyfront's account or your own):
**1. Open the template**
Go to **Settings**, then **Templates**, then **Message Template**. Open a template, or click **Add Message Template**, and select the **WhatsApp** tab.
**2. Choose a category**
Choose **Utility** for messages about the candidate's application, such as confirmations, reminders and next steps. Choose **Marketing** only for promotional messages.
**3. Write the message**
Write the **Body**. You can add bold or italic text and insert variables, like the candidate's first name, from the menu. Optionally add a header, a footer and up to three buttons.
**4. Check the preview**
The live **preview** shows exactly what the candidate will receive.
**5. Submit for approval**
Click **Submit for Approval**. WhatsApp usually reviews templates within minutes to a few hours, and the status updates on its own. Once it shows **Active**, the template is approved and ready to send.

> [!TIP]
>
> Pick **Utility** and keep the wording specific to the candidate's application. WhatsApp doesn't deliver Marketing templates to U.S. (+1) numbers, and it can reclassify a promotional-sounding Utility template as Marketing.
If your WhatsApp number sends through Webex Connect, templates are written and approved in Webex Connect, then linked in Journeyfront. See [Link a WhatsApp template from Webex Connect](/integrations/texting-providers/whatsapp#link-a-whatsapp-template-from-webex-connect).
The template list shows each template's WhatsApp status:
| Status | What it means |
| - | - |
| Draft | The WhatsApp version hasn't been sent to WhatsApp yet |
| In Review | WhatsApp is reviewing it |
| Active | Approved and ready to send. The dot next to it shows WhatsApp's quality rating for the template. Templates linked from Webex Connect also show Active |
| Rejected | WhatsApp declined it. Open the template to see the reason at the top of its WhatsApp tab, then edit the wording and resubmit |
| Paused or Disabled | WhatsApp has restricted it, usually for quality or policy reasons |

## Track delivery
WhatsApp messages show a clock while sending, a check when sent, and double checks when delivered or read. If a message can't be delivered, **Not delivered** appears under it. Hover over it to see the reason.

## Consent
Once WhatsApp is connected, your application form asks candidates for WhatsApp consent alongside text message consent. The two are tracked separately, and the message panel shows whether a candidate has opted in to WhatsApp.

## Billing
There's no separate WhatsApp add-on. If Journeyfront provides your texting account, WhatsApp messages use the same prepaid messaging balance as your texts. If your company uses its own Twilio or Webex Connect account, your provider bills you directly. See [Add-ons and credits](/account-setup/add-ons).
## What candidates see
WhatsApp messages come from your company's WhatsApp display name and number, like any WhatsApp business message, with any formatting and buttons from your template.
## FAQ
> [accordion] Why do I need a template to message a candidate?
>
> WhatsApp requires businesses to use a pre-approved template for the first message in a conversation. It's their policy to prevent spam. After the candidate replies, you can send free-form messages for 24 hours.
> [accordion] Why was my WhatsApp message not delivered?
>
> Hover over **Not delivered** to see the reason. The most common cause is a Marketing template sent to a U.S. number; rewrite it as a Utility template and resubmit it. Other causes include a candidate who isn't on WhatsApp, or a free-form message sent more than 24 hours after the candidate's last reply.
> [accordion] Can we use more than one WhatsApp number?
>
> No. Each account connects one WhatsApp number.
> [accordion] Does it matter which provider our WhatsApp number uses?
>
> Not for sending. The message panel, replies and delivery updates work the same. The one difference is where templates are written: in Journeyfront for Twilio, and in Webex Connect for Webex Connect.
> [accordion] Does WhatsApp cost extra?
>
> There's no separate WhatsApp add-on. If Journeyfront provides your texting account, WhatsApp uses the same messaging balance as your texts. If you use your own Twilio or Webex Connect account, your provider bills you directly.
## Related
> [card] [Text messages](/communication/text-messages)
>
> Text candidates by SMS.
> [card] [WhatsApp setup](/integrations/texting-providers/whatsapp)
>
> Connect your WhatsApp Business number.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> See your messaging balance and usage.
> [card] [Workflows overview](/workflows/overview)
>
> Steps, activities and automation.
# Employee records
Source: https://help.journeyfront.com/employees/employee-records
Find your employees, keep their job details up to date, and record when someone leaves.
> [!NOTE]
>
> **Who can do this:** The **Employees** page needs the *All Employee Access* permission. People without it can still open the employees in the job profiles they have access to, from **Profiles**. Emailing employees needs *Send Emails*, and the **Job Performance** tab needs *Performance Access*.
Journeyfront keeps a record for every employee: who they are, which job profile they belong to, their job title, start date, supervisor and, when they leave, why. These records are what connect hiring to what happens next. Once you know who stayed, who left and how people performed, you can see which scores, sources and steps lead to your best hires.
## How employees get into Journeyfront
| Way in | What happens |
| - | - |
| **You hire a candidate** | Hiring creates their employee record in the job profile you choose in the Hire window. See [Hire candidates](/onboarding/hire-candidates). |
| **Your HR system syncs** | With an HRIS connection and employee sync turned on, employees are added and updated on a schedule. See [HRIS integrations](/integrations/hris#sync-employees-from-your-hr-system). |
| **You import a file** | Admins upload employee data in **Settings**, then **Import Data**. See [Importing data](/account-setup/importing-data). |
| **You add one by hand** | On a job profile, click **Actions**, then **Add New Employee**. See [Job profiles](/employees/job-profiles#add-employees-to-a-profile). |
## The Employees page
Click **Employees** in the top navigation. The page lists every employee in your account, with a count at the top ("Showing 1,240 employees").

### Search and filter
* **Search** finds employees by name, email, job title, department, supervisor, employment type or job profile.
* **Filters** on the left narrow the list. Open a group and tick the values you want; each value shows how many employees have it. The groups are **Completed** (how much of their job profile's assessments they've finished), **Department**, **Title**, **Supervisor**, **Employment Type** and **Job Profile**.
* Ticked filters stack, and each one shows as a chip above the search box. Click the **x** on a chip to remove it.
### Choose your columns
Click the table icon above the list. In **Choose which fields you want to see**, tick the columns you want under **Personal Fields** and **Job Fields**, then click **Save**. **Reset to default** brings back the standard set.
The list starts with **Name**, **Primary Email**, **Job Title**, **Tenure** (in months), **Supervisor**, **Department** and **Job Profile**. You can add columns such as **Email (secondary)**, **Date of Birth**, **Percentage Complete**, **Start Date**, **End Date**, **Employment Type**, **Supervisor Email**, **Created Date** and **Last Performance Date**. Click a column heading to sort by it.
### Export the list
Click **Actions**, then **Export Data**, then **Export**. Journeyfront downloads a CSV file of your employees, with their details, their job information and your employee job fields. To export the employees of one job profile only, export from the profile instead. See [Job profiles](/employees/job-profiles#export-employee-data).
## Open an employee's record
Click an employee's name or any other value in their row. The record opens with their name, email, phone number and location at the top.
* **Currently Viewing** shows the job you're looking at, with its start date, its end date if they've left, and an **Active** or **Inactive** label. Open it to jump to the person's Candidate Profile, one of their Candidate Applications, or another of their jobs.
* **Actions** has **Email**, and **Mark Do Not Hire** (or **Remove Do Not Hire**). See [Do Not Hire](/candidates/do-not-hire).
The record has four tabs:
| Tab | What's on it |
| - | - |
| **Personal Info** | **Personal Details** (name, primary and secondary email, date of birth, phone number and address) and **Personal Custom Fields** |
| **Job Info** | This job's details and your employee job fields. See [Edit job details](#edit-job-details). |
| **Job Performance** | Their performance review scores. Only shown with *Performance Access*. See [Performance reviews](/employees/performance-reviews). |
| **Applications** | Every job req they applied to before they were hired: **Applied Date**, **Job Title Applied For**, **Screening Step Reached**, **Application Status** and **Overall Score**, with a link to open each Candidate Application |
> [!TIP]
>
> An employee's record and their Candidate Profile are the same person. The **Jobs** tab of their Candidate Profile lists every job they've held with you, and clicking a row opens this record. See [Candidate Profiles and Candidate Applications](/candidates/profiles-and-applications).
## Edit personal details
On the **Personal Info** tab, change what you need. **Cancel** and **Save** appear at the bottom once you change something. Click **Save**; you'll see "Saved Successfully".
Your account's personal fields appear on the right under **Personal Custom Fields**. They're the same fields that show on the person's Candidate Profile. See [Custom fields](/account-setup/custom-fields).
## Edit job details
The **Job Info** tab holds this job's details:
| Field | What it's for |
| - | - |
| **Job Profile Link** | The job profile this job belongs to (read only). To change it, move the employee from the profile. See [Job profiles](/employees/job-profiles#move-or-remove-employees). |
| **External Employee Identifier** | Your own ID for the person, such as an employee ID or employee number. An HRIS employee sync can use it to match people. |
| **Job Title** | Required. |
| **Job Location** and **Job Country** | Where they work. |
| **Employment Date(s)** | The **Start Date** (required), the **End Date**, and **Employee currently works here**. |
| **Reason for Separation** and **Separation Note** | Why they left. See [Record that an employee left](#record-that-an-employee-left). |
| **Supervisor Email** | Who they report to. |
| **Employment Type** | Required. |
Your account's employee job fields appear on the right under **Custom Job Fields**. Change what you need and click **Save**.
### Change an employee's supervisor
On the **Job Info** tab, enter the new supervisor's email in **Supervisor Email** and click **Save**. The **Supervisor** column and filter on the Employees page use it.
Supervisor Email records who the employee reports to. It doesn't change who can see the employee in Journeyfront: that comes from each person's security role and the job profiles they have access to. See [Security roles and permissions](/account-setup/security-roles).
## Record that an employee left
**1. Open the Job Info tab**
Open the employee's record and click **Job Info**.
**2. Untick Employee currently works here**
The **End Date** becomes required.
**3. Enter the end date and reason**
Enter the **End Date** (it has to be after the start date) and pick a **Reason for Separation**. Add a **Separation Note** if you want more detail.
**4. Click Save**
The record now shows the end date and **Inactive**.

The reasons in the list are your separation reasons, set up in **Settings**, then **Custom Options**, then **Separation Reasons**. See [Rejection and separation reasons](/account-setup/rejection-reasons#separation-reasons).
> [!TIP]
>
> Record the real reason every time, even when it's awkward. Turnover reports are only as useful as the reasons behind them, and early, voluntary turnover is one of the clearest signals of what to change in your hiring.
## Email employees
* **One employee:** open their record and click **Actions**, then **Email**.
* **Several employees:** open their job profile's **Employees** tab, tick the employees, and click the envelope icon above the list.
Write your message or pick an email template, then click **Send**, or schedule it for later. See [Email candidates](/communication/email-candidates) for the options in the email window.
## FAQ
> [accordion] Why don't I see Employees in the top navigation?
>
> It needs *All Employee Access* in your security role. Without it, you can still reach employees through **Profiles**, for the job profiles you have access to. Ask your Journeyfront admin to check your role. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] Why can't I see the Job Performance tab?
>
> It needs *Performance Access* in your security role.
> [accordion] Can I bring an employee back after they left?
>
> Yes. On the **Job Info** tab, tick **Employee currently works here** again and click **Save**.
> [accordion] Why can't I change some fields?
>
> **Job Profile Link** is read only; move the employee from their job profile to change it. If your account syncs employees from your HR system, the next sync can also overwrite values that came from it, so change those in your HR system.
> [accordion] Where did someone's application go after they were hired?
>
> It's still there. Open the employee's **Applications** tab, or use **Currently Viewing** to jump to it.
> [accordion] Why is my Separation Reasons list empty?
>
> Your admins haven't added any yet. They're set in **Settings**, then **Custom Options**, then **Separation Reasons**. See [Rejection and separation reasons](/account-setup/rejection-reasons).
## Related
> [card] [Job profiles](/employees/job-profiles)
>
> Group employees by role and measure what success looks like.
> [card] [Performance reviews](/employees/performance-reviews)
>
> Score how employees are doing.
> [card] [Importing data](/account-setup/importing-data)
>
> Upload employee and performance data in bulk.
> [card] [Turnover and performance](/reporting/turnover-and-performance)
>
> See who stays, who leaves and why.
# Job profiles
Source: https://help.journeyfront.com/employees/job-profiles
Group your employees by role, measure what success looks like in it, and see which parts of your hiring predict it.
> [!NOTE]
>
> **Who can do this:** Everyone sees the job profiles they have access to under **Profiles**: all of them with the *All Job Profile Access* permission, otherwise the ones ticked for them in **Settings**, then **Users**. Creating a job profile needs *All Job Profile Access*. Company outcomes need *Company Settings Access*.
A **job profile** is a role your employees hold, such as "Customer Care Agent" or "Team Lead". It groups the people who do that job and the data about them: the assessments they took, how they perform and how long they stay. That data is what tells you what success looks like in the role.
Job profiles connect to hiring in two ways:
* **Every job req is linked to a job profile.** You choose it in **Linked to Job Profile** when you create the job req, and it's where the job req's hires go unless you pick another profile in the Hire window. See [Create a job req](/job-reqs/create).
* **Predictive models are built on job profiles.** Journeyfront learns from a profile's employee outcomes which candidates are likely to perform and stay, and job reqs linked to the profile can use that model in their scores. See [Predictive models](/scoring/predictive-models).
## The Profiles page
Click **Profiles** in the top navigation. **Job Profiles** shows a card for each profile you have access to, with its description, **Created Date** and **Total Employees**. Click a card to open the profile.
Every account has a **Default Profile**. It can't be renamed or deleted.
## Create a job profile
**1. Click New Profile**
On the **Profiles** page, click **New Profile**. The **Job Profile** window opens.
**2. Fill in the details**
Enter a **Profile Name**, a **Profile Description** and the **Employment Type**, all required. **O\*NET Code** is optional: the standard occupation code for the role, which you can look up on O\*NET OnLine from the info icon.
**3. Click Create**
The new profile opens. Profile names must be unique in your account.
To change these details later, open the profile, go to **Setup**, then **Details**, and click **Edit**.
> [!TIP]
>
> Create one profile per role that's measured the same way, not one per site or client. A "Customer Care Agent" profile with hundreds of employees tells you far more than ten small ones, and predictive models need that volume.
## Inside a job profile
A job profile's tabs are **Dashboard**, **Employees** and **Setup**, and it opens on **Employees**. Click **All Job Profiles** at the top to go back.
The **Actions** menu has **Invite New Employees**, **Add New Employee**, **Export Data** and **Delete Profile**.
## The Employees tab
The **Employees** tab lists everyone in the profile. It works like the [Employees page](/employees/employee-records#the-employees-page): search, filters on the left (including your multiple choice custom fields), and the table icon to choose your columns. Click a name to open the employee's record.
Tick one or more employees to act on them:
* **Move** them to another job profile. See [Move or remove employees](#move-or-remove-employees).
* **Merge**, when you tick exactly two, to combine duplicate records of the same person. See [Compare and merge candidates](/candidates/compare-and-merge).
* **Email** them, with the envelope icon. Needs *Send Emails*.
* **Delete** them from the profile.

## Add employees to a profile
Employees join a profile when you hire them into it, when your HR system syncs them, or when you import them. See [Employee records](/employees/employee-records#how-employees-get-into-journeyfront). To add one person yourself:
**1. Open Add New Employee**
Open the profile and click **Actions**, then **Add New Employee**.
**2. Check the email**
Enter their **Email** and click **Check Email**. For someone new to Journeyfront, enter their first and last name.
**3. Click Add To Profile**
They appear on the **Employees** tab. No email is sent.
### Invite employees to take the assessments
To learn what success looks like in a role, invite the people already doing it well to take the same assessments you give candidates.
**1. Copy the invite link**
Open the profile and click **Actions**, then **Invite New Employees**. In the **Invite New Participants** window, click **Copy**, then **Done**.
**2. Send it yourself**
Paste the link into your own email or chat message. Journeyfront doesn't email it for you.
The link opens your **employee landing page**, with your logo and the welcome message from **Settings**, then **Company Details**. Employees enter their email, sign in or create a password, click **Add Position To My Profile**, and then work through the assessments. See [Company details](/account-setup/company-details#the-employee-landing-page) to change the welcome message.
> [!TIP]
>
> Tell employees why you're asking and how long it takes, in your own email and in the welcome message. People who understand that their answers help you hire great teammates are far more likely to finish.
### Track who has finished
On the **Employees** tab, open the **Completed** filter. Each value is a percentage of the profile's assessments finished, with the number of employees at that point. For example, "40%" next to 6 means six people have finished 40% of the assessments. Tick a value to list those employees, or add the **Percentage Complete** column.
### See an employee's assessment results
Click the chart icon at the start of an employee's row. **Assessment Values** lists each assessment they took, with each attribute and their **Value (1-5)**. Click the document icon next to an assessment's name to open its full report.
If the window is empty, the employee hasn't taken the assessments yet.
## Move or remove employees
* **Move to another profile:** on the **Employees** tab, tick the employees and click **Move**. Choose the new profile under **Select a Job Profile** and click **Move**. If they answered questions that the new profile doesn't ask, **Delete Questions?** lists them. Click **Delete Questions** to remove those answers and finish the move, or **Cancel**, add the questions to the new profile first, and move them again.
* **Remove from the profile:** tick the employees and click **Delete**, then confirm. The person's record stays in Journeyfront; only their job in this profile is removed.
## Export employee data
Open the profile and click **Actions**, then **Export Data**, then **Export**. Journeyfront downloads a CSV file of the profile's employees with their details, job information, assessment completion, last performance and satisfaction dates, and your employee job fields. To export every employee in your account, use the [Employees page](/employees/employee-records#export-the-list).
## Profile dashboards
The **Dashboard** tab shows how the employees in this profile are doing, and which parts of your hiring go with success. Pick a view from the menu at the top:
| View | What it shows |
| - | - |
| **Attributes** | The attributes most closely related to **Overall Performance** or **Employee Retention** |
| **Activities** | The same, for the activities in your hiring process |
| **Interview Questions** | The same, for individual interview questions |
| **Interviewers** | How each interviewer's scores compare with the overall performance of the people they interviewed |
| **Turnover** | Turnover by hire date, by time since hire and by time of year |
| **Performance** | Performance by hire date, for the performance type and period you choose |
| **Resume Analytics** | How work experience and education relate to your hires |
| **Satisfaction Analytics** | Employee satisfaction, by type, supervisor and turnover |
On **Attributes**, **Activities** and **Interview Questions**, choose what to compare against, narrow it with the filters (for retention, by separation reason), and set **From Date** and **To Date**. Each row shows the **Correlation**, its **Statistical Significance** and how many **Employees** it's based on. Click the chart icon at the end of a row to see the data points and the employees behind them.
> [!TIP]
>
> Look for strong relationships that are also statistically significant and based on plenty of employees. A strong result from a dozen people is a hint to keep watching, not a reason to change your workflow.
These views fill up as you collect outcomes: performance reviews, separation reasons and satisfaction results. See [Performance reviews](/employees/performance-reviews) and [Employee records](/employees/employee-records#record-that-an-employee-left).
## Set up a profile
The **Setup** tab has four pages:
| Page | What it's for |
| - | - |
| **Details** | The profile's name, description, employment type and O\*NET code. Click **Edit** to change them. |
| **Outcomes** | What success means in this role, grouped into **Performance**, **Culture Fit** and **Satisfaction**. Click the plus icon on **Performance** or **Culture Fit** to add an outcome to that group. |
| **Attributes** | The attributes measured for employees in this role, in attribute groups. It works like a job req's attributes. See [Attributes](/scoring/attributes). |
| **Measurement Plan** | The **Employee Measurement Plan**: what employees in the profile complete (the assessments and employee questions under **Attribute Assessment Plan**) and how their outcomes are collected (performance evaluations and satisfaction under **Outcome Measurement Plan**). |
Your Customer Success Manager can help you set up a profile's outcomes and measurement plan, especially before your first performance reviews.
### Company outcomes
Outcomes are the results you track for employees, such as quality, attendance or teamwork. Your company's list lives in **Settings**, then **Outcomes**, and job profiles and performance questions pick from it.
**1. Open Outcomes**
Go to **Settings**, then **Outcomes**. The list shows each outcome's **Name**, **Description** and **Type**. Use the search box or **Filter By** to narrow it.
**2. Click + Outcome**
The **Add New Outcome** window opens.
**3. Fill it in**
Choose the **Outcome Group** (**Performance** or **Culture Fit**) and enter an **Outcome Name**. Add an **Outcome Description**; the more specific, the more consistently managers will score it.
**4. Click Create**
The outcome is added to the list.
To change an outcome, click its edit icon, then **Edit**. Outcomes your company added also have a trash icon to delete them.
### Predictive models
Journeyfront builds predictive models on job profiles, from the outcomes of the profile's employees. You don't set them up in the profile. To get a model for a role, ask your Customer Success Manager. Then add it to the job reqs linked to the profile. See [Predictive models](/scoring/predictive-models).
The [behavioral assessment](/assessments/behavioral-assessment) is made to go with predictive models. Giving it to candidates now builds the history a model can learn from later.
## FAQ
> [accordion] Why can't I see a job profile?
>
> Without *All Job Profile Access*, you only see the profiles ticked for you on the **Available Job Profile** tab when an admin edits you in **Settings**, then **Users**. See [Users](/account-setup/users#give-a-user-access-to-job-reqs).
> [accordion] Why don't I see New Profile?
>
> Creating a job profile needs *All Job Profile Access* in your security role.
> [accordion] What's the difference between a job profile and a job req?
>
> A job req is a job you're hiring for. A job profile is a role your employees hold. Many job reqs can link to one job profile, for example one job req per site, all hiring Customer Care Agents.
> [accordion] Does inviting employees send them an email?
>
> No. **Invite New Employees** gives you a link to send yourself, in an email, a chat message or anywhere your employees will see it.
> [accordion] Can I delete a job profile?
>
> Yes, except the **Default Profile**. Open it and click **Actions**, then **Delete Profile**, then **Confirm**.
> [accordion] Can we build our own predictive model?
>
> No. Journeyfront builds predictive models from your outcome data. Ask your Customer Success Manager about a model for a role.
## Related
> [card] [Predictive models](/scoring/predictive-models)
>
> Use what a profile's employees teach you in candidates' scores.
> [card] [Behavioral assessment](/assessments/behavioral-assessment)
>
> The assessment made to go with predictive models.
> [card] [Employee records](/employees/employee-records)
>
> Each employee's details, job and history.
> [card] [Performance reviews](/employees/performance-reviews)
>
> Collect the outcomes that show what success looks like.
# Performance reviews
Source: https://help.journeyfront.com/employees/performance-reviews
Have managers score how employees are doing, so your hiring data connects to real performance.
> [!NOTE]
>
> **Who can do this:** Anyone on your team can start a review from **Start**, then **Performance Review**. Finding employees in that list needs the *All Employee Access* permission. Reviewing from an employee's record, and seeing their scores, needs *Performance Access*.
A performance review is a short evaluation a manager fills in for one employee and one review period. Each review scores the outcomes that matter in the employee's role, such as quality or attendance. Over time, those scores show which candidates became your strongest performers, and which scores, steps and sources predicted it.
## Before you start
Performance reviews use two things that are set up for each job profile:
* **The questions.** Your performance questions live in **Settings**, then **Measurements**, then **Employee Performance**. Each one measures one or more of your company outcomes (**Settings**, then **Outcomes**). See [Job profiles](/employees/job-profiles#company-outcomes).
* **The review periods.** How often employees in a profile are reviewed is part of the profile's measurement plan, under **Outcome Measurement Plan**.
If you see **Unable to add Performance Evaluation** ("You are unable to add a performance evaluation for this position due to incomplete setup"), the employee's job profile isn't set up for reviews yet. Contact your Customer Success Manager or Journeyfront support to set it up.
## Review an employee
**1. Click Start, then Performance Review**
**Start** is at the top right of every page. **Who are you reviewing?** lists your employees with their email, **Job Title**, **Start Date** and **Last Performance Date**. Use **Search** to find someone.
**2. Click the employee**
The review period window opens.
**3. Choose the period**
Under **Which performance period would you like to evaluate?**, pick an **Evaluation Period**. Each period shows who completed the last review for it and when. Periods you've already reviewed for this employee are greyed out. Click **Next**.
**4. Score each question**
The **Performance Evaluation** opens with the employee's name, **Position**, you as the **Evaluator** and today's **Evaluation Date**. For each question, add **Notes** if you like (up to 4,000 characters) and enter a score from 1 to 5 in each **Score (1-5)** box.
**5. Click Submit - I'm all done**
You'll see **Performance Evaluation Saved**.

You can also start a review from the employee's record: open the **Job Performance** tab and click **Performance Evaluation** (with the plus). The same period window opens. See [Employee records](/employees/employee-records).
### Scoring rules
* **Score a whole question or skip it.** If you score anything on a question, score every box on it. If you can't judge a question, leave all of its boxes empty.
* **Notes need scores.** A question with a note but no scores can't be submitted.
* If something's missing, the question is marked in red. Fix it and click **Submit - I'm all done** again.
> [!TIP]
>
> Review against the outcome descriptions, not your overall impression of the person. If two managers would score the same employee differently, the descriptions need to be clearer: update them in **Settings**, then **Outcomes**.
To leave without saving, click **Cancel - discard scores**. **Leave Performance Evaluation?** warns that all answers will be lost. Reviews can't be saved part way.
## See an employee's scores
Open the employee's record and click the **Job Performance** tab. **Performance Scores** shows their reviews, with each evaluator's scores side by side.
* Switch between **Scores by Review** and **Scores by Outcome**.
* Pick a review period, or **All Periods**.
* Click **Print** for a copy.
The **Last Performance Date** column on the Employees page and a job profile's **Employees** tab shows when each employee was last reviewed. Add it with the table icon. See [Employee records](/employees/employee-records#choose-your-columns).
## Where reviews are used
* **Job profile dashboards:** the **Performance** view, and the **Attributes**, **Activities**, **Interview Questions** and **Interviewers** views when compared with **Overall Performance**. See [Job profiles](/employees/job-profiles#profile-dashboards).
* **Company dashboards:** performance across your account. See [Turnover and performance](/reporting/turnover-and-performance).
* **Predictive models:** performance outcomes are what Journeyfront learns from when it builds a model for a job profile. See [Predictive models](/scoring/predictive-models).
## Bring in reviews from another system
If your reviews happen in another system, admins can upload them in bulk from **Settings**, then **Import Data**, on the **Employee Performance Data Import** tab. See [Importing data](/account-setup/importing-data#the-performance-data-template).
## FAQ
> [accordion] Why is a review period greyed out?
>
> You've already reviewed this employee for that period. Someone else can still review them for it.
> [accordion] Why is the employee list empty under Start, then Performance Review?
>
> Finding employees there needs *All Employee Access*. You can also review someone from the **Job Performance** tab of their record, if you can open it from **Profiles**.
> [accordion] Why don't I see the Job Performance tab?
>
> It needs *Performance Access* in your security role. Ask your Journeyfront admin.
> [accordion] Can I save a review and finish later?
>
> No. Fill it in and submit it in one go. **Cancel - discard scores** throws away what you entered.
> [accordion] Can employees see their reviews?
>
> No. Performance reviews are only visible to your team.
> [accordion] Why can't I un-hire someone who has reviews?
>
> Once an employee record has performance data, the hire is part of their employment history and can't be undone. Record a separation instead. See [Employee records](/employees/employee-records#record-that-an-employee-left).
## Related
> [card] [Employee records](/employees/employee-records)
>
> Each employee's details, job and scores.
> [card] [Job profiles](/employees/job-profiles)
>
> Outcomes, review periods and profile dashboards.
> [card] [Turnover and performance](/reporting/turnover-and-performance)
>
> Connect hiring data to how people perform.
> [card] [Predictive models](/scoring/predictive-models)
>
> Learn which candidates are likely to perform.
# Admin setup checklist
Source: https://help.journeyfront.com/getting-started/admin-setup-checklist
Everything to set up before your team starts hiring, in the order that works best.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission. Adding users also needs *Manage Users*, and creating job reqs needs *All Job Req Access*.
Whether Journeyfront's team sets your account up with you or you're doing it yourself, the same things need to be in place before your team starts hiring. Work through this list in order: each step builds on the ones before it. Steps marked **Recommended** are worth doing before your first candidate applies; the rest depend on how you hire.
Settings live behind the gear icon at the top right. See [Finding your way around](/getting-started/navigating).
## The checklist
**1. Company details (Recommended)**
Go to **Settings**, then **Company Details**, and click **Edit Details**. Add your company name, location and **Logo URL**. Candidates see your name and logo when they sign in to apply.
See [Company details](/account-setup/company-details).
**2. Security roles, then users (Recommended)**
First review your roles in **Settings**, then **Security**. Every account starts with **Admin**, **People Manager**, **Recruiter** and **Hiring Team Member**; adjust them or add roles that match how your team works. Then add your team in **Settings**, then **Users**, and give each person a role. Each person gets an invitation email.
See [Security roles and permissions](/account-setup/security-roles) and [Users](/account-setup/users).
> [!TIP]
>
> Set up the roles before you invite people. Each role is a set of permissions, so getting them right first means nobody starts with more access than they need.
**3. Sources and rejection reasons (Recommended)**
In **Settings**, then **Sources**, list the places your candidates come from. In **Settings**, then **Custom Options**, then **Rejection Reasons**, set the reasons your team picks when rejecting someone, and add **Separation Reasons** for employees who leave.
See [Sources](/sourcing/sources) and [Rejection and separation reasons](/account-setup/rejection-reasons).
> [!TIP]
>
> These lists drive your reports from day one. A short, clear list your team uses consistently beats a long one, and it's much harder to clean up after hundreds of candidates.
**4. Email templates (Recommended)**
In **Settings**, then **Templates**, then **E-mail Template**, write the emails your team sends most, such as interview invitations and rejections. On the **System Emails** tab, review the emails Journeyfront sends for you, like candidate invitations and interview reminders.
See [Email templates](/communication/email-templates) and [Template variables](/communication/template-variables).
**5. Career site and job boards (Recommended)**
In **Settings**, then **Job Boards**, set up and brand the career site where candidates find your jobs. To advertise on outside job boards, connect them in **Settings**, then **Integrations**.
See [Job boards](/sourcing/job-boards) and [Job board integrations](/integrations/job-boards).
**6. Your first job req and its workflow (Recommended)**
Every job req is linked to a job profile, the role your hires join. Your account starts with a **Default Profile**; to measure a role on its own, create a profile for it under **Profiles** first. See [Job profiles](/employees/job-profiles).
Then go to **Job Reqs** and click **New Job Req**. A new job req starts **Inactive**, with a draft workflow called **Workflow 1.0**. Shape it to your process under **Setup**, then **Workflow**, with **Edit Draft** (or **Create New Version** if there's no draft), and work through the rest of the **Setup** tab: the application form, the hiring team, the settings and the job posting. Publishing the workflow makes the job req **Active**.
See [Create a job req](/job-reqs/create), [Build a workflow](/workflows/build) and [Publish workflow changes](/workflows/publish).
> [!WARNING]
>
> The starter workflow includes automation rules on its **Pre-screen** step, including one that rejects candidates with low scores. Review them, and change or remove them, before candidates start applying. See [Automation rules](/workflows/automation-rules).
**7. A hiring class (if you hire in groups)**
If your hires start together, open the job req's **Hiring Classes** tab and create a class with its openings and start date.
See [Create a hiring class](/hiring-classes/create).
**8. Integrations (as you need them)**
Connect the tools your team already uses, in **Settings**, then **Integrations**: your HR system, outside job boards, background checks, e-signature and calling. Interviewers connect their own calendars under **Interviews**, then **My Profile**.
See [Integrations overview](/integrations/overview) and [Calendars](/integrations/calendars).

> [!TIP]
>
> Before you share a job req's link, open its **Workflow** page and click the eye icon (**Preview Activity**) on each activity to see it the way candidates will. Nothing you enter in a preview is saved.
## When you're ready for more
Set these up when your hiring process needs them:
| What | Where | Learn more |
| - | - | - |
| Custom fields for candidates, applications, employees, job reqs and hiring classes | **Settings**, then **Custom Fields** | [Custom fields](/account-setup/custom-fields) |
| Reusable screening and interview questions | **Settings**, then **Measurements** and **Templates** | [Screening questions](/assessments/screening-questions), [Interview guides](/interviews/interview-guides) |
| Offer letters, documents and offer packages | **Settings**, then **Offers** | [Offers overview](/offers/overview) |
| Onboarding and e-consent forms | **Settings**, then **Onboarding Forms** and **E-Consent Forms** | [Onboarding forms](/onboarding/onboarding-forms), [E-consent forms](/onboarding/e-consent-forms) |
| Text messaging and WhatsApp | **Settings**, then **Add-Ons** and **Phone Numbers** | [Text messages](/communication/text-messages), [WhatsApp](/communication/whatsapp) |
| Employee referrals | **Settings**, then **Referral Portals** | [How referrals work](/referrals/overview) |
| Employee data for turnover and performance | **Settings**, then **Import Data**, or an HRIS connection | [Importing data](/account-setup/importing-data) |
| Add-ons such as language assessments and e-signatures | **Settings**, then **Add-Ons** | [Add-ons and credits](/account-setup/add-ons) |
Some features, like AI resume scoring, AI agents, fraud detection and referrals, need to be turned on for your account. Ask your Customer Success Manager. See [How Journeyfront uses AI](/getting-started/ai).
## FAQ
> [accordion] Do I have to do every step before we start?
>
> No. The steps marked **Recommended** are the ones that are hard to change once candidates are flowing. The rest can wait until you need them.
> [accordion] Why don't I see some of these Settings pages?
>
> Most of **Settings** needs *Company Settings Access*, and **Users** also needs *Manage Users*. Some pages only appear when the feature is on for your account. See [Security roles and permissions](/account-setup/security-roles).
> [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. See [Job req statuses](/job-reqs/statuses).
> [accordion] We have a lot of roles. Do we set each one up from scratch?
>
> No. Get one job req working well, then use **Actions**, then **Duplicate Job Req** to copy it for the next site or shift. See [Create a job req](/job-reqs/create#start-from-an-existing-job-req).
> [accordion] How do we train the rest of the team?
>
> Send recruiters to [Getting started for recruiters](/getting-started/recruiters), and hiring managers to [Getting started for hiring managers](/getting-started/hiring-managers).
## Related
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
> [card] [Workflows overview](/workflows/overview)
>
> How a job req's workflow drives the candidate's path.
> [card] [Security roles and permissions](/account-setup/security-roles)
>
> Decide who can see and do what.
> [card] [Integrations overview](/integrations/overview)
>
> Connect Journeyfront to your other tools.
# How Journeyfront uses AI
Source: https://help.journeyfront.com/getting-started/ai
Where AI helps in Journeyfront, and the guardrails that keep your team in charge of every hiring decision.
> [!NOTE]
>
> **Availability:** Each AI feature needs to be turned on for your account, and some also need a permission or a setting on each job req. Ask your Customer Success Manager. AI agents use AI credits.
When you're hiring at volume, a lot of the work is reading: hundreds of resumes, hours of recorded answers, and follow-ups with candidates who stalled halfway through. Journeyfront uses AI to take on that first read and the routine follow-up, so your team can spend its time on the candidates and decisions that need a person. AI gives you a head start; your team makes the call.
## Where you'll find AI
> [card] [AI resume scoring](/scoring/ai-resume-scoring)
>
> Scores each resume against the attributes you set for the job, explains every score and highlights the lines behind it.
> [card] [AI-scored questions](/scoring/ai-scored-questions)
>
> Scores video, audio and written screening answers from 1 to 5 against your scoring criteria, with its reasoning.
> [card] [AI agents](/workflows/ai-agents)
>
> Follow up with candidates who stalled, by email, text or WhatsApp, with your team approving messages when you choose.
> [card] [AI Connections](#ai-connections)
>
> Connect your own AI assistant to read your Journeyfront data.
| Feature | What it does | What it never does | Who's in control |
| - | - | - | - |
| **AI resume scoring** | Gives each resume a score per attribute, with reasoning and highlighted evidence | Hire, reject or move a candidate | Turned on per job req. Your team can edit any score, and edits are marked. |
| **AI-scored questions** | Scores free-form answers against your criteria, with reasoning | Hire, reject or move a candidate | Turned on per question. Permissions decide who can turn it on, run it and edit AI scores. |
| **AI agents** | Writes and sends short follow-up messages to stalled candidates | Move, reject, score or assign anyone; message hired, rejected or withdrawn candidates; text people who haven't opted in | You choose the candidates, the channels and whether each message needs approval. Every action is logged with its reasoning. |
| **AI Connections** | Lets an assistant you connect read your Journeyfront data | Change anything in Journeyfront | Each user connects their own assistant and can revoke it at any time. |
## Our principles
### People make the decisions
AI in Journeyfront informs decisions; it doesn't make them. AI scores are one input alongside your assessments, interviews and your team's judgment. AI doesn't hire, reject or move candidates, and AI agents can only send messages.
Your automation rules are yours to design. If a rule acts on scores, those scores can include AI scores, so build rules that send borderline candidates to a person for review rather than rejecting them outright. See [Automation rules](/workflows/automation-rules).
### People can review and change every AI result
* **Every AI score shows its reasoning,** and resume scores highlight the evidence in the resume.
* **Your team can change any AI score.** For resume scores, edited attributes are marked as edited by a person.
* **AI agents can wait for approval.** For each channel, choose whether an agent sends on its own, asks when it's unsure, or always asks first.
### AI only sees what the task needs
Each AI feature works from the information it needs for its job: the resume and the job's attributes, a candidate's answer and your scoring criteria, or a candidate's progress and message history. AI agents work only from hiring workflow data, never from protected characteristics like age, gender or race.
### Your data isn't used to train AI models
Your candidates' and employees' data isn't used to train the AI models that Journeyfront's features use.
### Security
AI features run inside the same security program as the rest of Journeyfront, which is SOC 2 compliant.
## AI Connections
With **AI Connections**, you can connect an AI assistant that supports MCP (Model Context Protocol) to your Journeyfront account, and ask it about your candidates and applications in plain language. The assistant reads your data; it can't change anything in Journeyfront.
**1. Open AI Connections**
Click your name at the top right, then **Personal Settings**, then **AI Connections**.
**2. Copy the connection URL**
Click **Copy** next to **Connection URL**, and follow **How to set this up** for your assistant.
**3. Approve access**
Your assistant sends you to Journeyfront to sign in and approve access. Once approved, it appears under **Active connections**.

The assistant only sees data from the account you're working in, and only what you could see yourself. To disconnect it, click **Revoke** next to it under **Active connections**.
To have your assistant answer how-to questions from this Help Center as well, see [Use the Help Center with your AI assistant](/getting-started/use-docs-with-ai).
AI Connections needs to be turned on for your account, and your security role needs the *Connect to MCP* permission. What a connected assistant does with your data is governed by your agreement with that assistant's provider, so check your company's AI policy before connecting one.
## Automation that isn't AI
Some features do work for you without AI:
* **Automation rules** follow exactly the rules your team sets. See [Automation rules](/workflows/automation-rules).
* **Fraud flags** come from automated checks on each application and give it a risk level for your team to review. See [Fraud flags](/candidates/fraud-flags).
* **Predictive models** are statistical models Journeyfront builds from your own employees' outcomes. See [Predictive models](/scoring/predictive-models).
## FAQ
> [accordion] Is AI deciding who gets hired?
>
> No. AI scores and agent messages support your team. People review the results, can change them, and make every hiring decision.
> [accordion] Can we use Journeyfront without AI?
>
> Yes. Each AI feature is turned on for your account only when you ask, and AI resume scoring and AI-scored questions are also turned on per job req or per question. Everything else in Journeyfront works without them.
> [accordion] Can we see why the AI gave a score?
>
> Yes. Every AI score comes with its reasoning, and resume scores highlight the lines of the resume behind them.
> [accordion] Can the AI get it wrong?
>
> Yes, which is why people stay in the loop. AI only judges what's in front of it: it can't confirm a claim is true, and it can't credit experience a candidate left out. Treat a low AI score as a reason to look closer, not a verdict, and change any score you disagree with.
> [accordion] Is our data used to train AI models?
>
> No. Your candidates' and employees' data isn't used to train AI models.
> [accordion] Do we need to tell candidates we use AI?
>
> Rules about using AI in hiring differ by location, and some require notice to candidates. Check with your legal team about the places you hire.
> [accordion] How do we turn on an AI feature?
>
> Ask your Customer Success Manager to turn it on for your account. Then give the right people the permissions in **Settings**, then **Security**, and turn the feature on where you want it: on a job req for AI resume scoring and AI agents, or on a question for AI scoring. See [Security roles and permissions](/account-setup/security-roles).
## Related
> [card] [AI resume scoring](/scoring/ai-resume-scoring)
>
> Score resumes against the job's attributes.
> [card] [AI-scored questions](/scoring/ai-scored-questions)
>
> Score video, audio and written answers.
> [card] [AI agents](/workflows/ai-agents)
>
> Follow up with stalled candidates.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> How AI scores fit into a candidate's overall score.
# Glossary
Source: https://help.journeyfront.com/getting-started/glossary
Journeyfront terms in plain language.
| Term | What it means |
| - | - |
| **Activity** | Something a candidate completes inside a workflow step, such as screening questions, a typing test, an interview or an offer. |
| **Application fields** | Custom fields that belong to one Candidate Application, such as the shift or location a candidate wants for that job req. |
| **Application form** | The form candidates fill in when they apply to a job req. |
| **Application ID** | The unique ID of one Candidate Application. |
| **Attribute** | The trait or skill being measured, such as typing ability or customer focus. Every skills test, screening question and interview question measures an attribute. |
| **Automation rule** | A rule that acts on candidates automatically when something happens, such as moving them to the next step. |
| **Candidate assignment** | The recruiter who owns a candidate. Journeyfront can assign new candidates automatically. |
| **Candidate Application** | One candidate's progress through one job req: their steps, scores, interviews and offer. |
| **Candidate Profile** | The person. Journeyfront rolls all of a candidate's Candidate Applications up into one Candidate Profile. |
| **Career site** | A branded job board Journeyfront hosts for you, where candidates find and apply to your jobs. |
| **Hidden step** | A step only your team sees. Candidates never see hidden steps. |
| **Hiring class** | A group of hires who usually share a start date and go through training together. Also called a wave or batch. |
| **Hiring team** | The people working on a job req. |
| **Interview guide** | The questions and instructions an interviewer follows. Interviewers submit their feedback through the guide. |
| **Job Adaptive Score** | A score from 1 to 5 that standardizes a raw result based on what the job requires, so different activities can be compared side by side. |
| **Job posting** | How a job req appears to candidates on your career sites and on outside job boards. |
| **Job profile** | A profile used to measure current employees in a role, to define what success looks like. |
| **Job req** | A job you're hiring for, not just a single opening. One job req can fill many hiring classes. |
| **Offer package** | A bundle of an offer letter and documents that goes out together. |
| **Personal fields** | Custom fields that belong to the person and appear on their Candidate Profile, the same across every job req. |
| **Raw score** | The actual result of an activity in its own units, such as words per minute on a typing test. |
| **Saved view** | A list's filters, columns and sort order saved as a tab, on pages like Candidates, Job Reqs and Classes. You can keep it to yourself or share it with your team. See [Saved views](/lists-and-exports/saved-views). |
| **Security role** | A set of permissions that controls what a user can see and do. Every user has one. |
| **Source** | Where a candidate came from, such as a job board, a referral or a tracking link. |
| **Status** | Where a Candidate Application stands overall, such as in progress, hired or rejected. |
| **Step** | A stage in a workflow, such as Screening or Interview. |
| **User ID** | The unique ID of a person in Journeyfront, shared by all their Candidate Applications. |
| **Workflow** | The path candidates follow on a job req, made of steps and activities. |
# Getting started for hiring managers and interviewers
Source: https://help.journeyfront.com/getting-started/hiring-managers
Set your availability, run interviews, submit feedback and review the candidates your recruiters share with you.
> [!NOTE]
>
> **Who this is for:** Hiring managers, team leads and anyone who interviews candidates. You need a Journeyfront user account; ask your Journeyfront admin if you don't have one. What you can see depends on your security role and the job reqs you're on.
As a hiring manager or interviewer, you'll mostly do three things in Journeyfront: make yourself available for interviews, interview candidates with a structured guide, and weigh in on the candidates your recruiters send you. This page gets you set up and points to the details for each.
## Get set up
**1. Sign in**
Accept your invitation email and set your password, or sign in with your company's SSO. See [Logging in and passwords](/getting-started/logging-in).
**2. Connect your calendar**
Go to **Interviews**, then **My Profile**. Connect your calendar under **Synced Calendar**, and set your **Time Zone** and default **Conferencing** service. Booked interviews then land on your calendar, and candidates only see times you're free. See [Your availability and calendar](/interviews/availability).
**3. Set your interview hours**
Go to **Interviews**, then **My Availability**, and choose the hours candidates can book with you.
**4. Check your job reqs**
Open **Job Reqs** and make sure you see the job reqs you hire for. If one's missing, ask your recruiter or admin to add you to its hiring team. See [Hiring team](/job-reqs/hiring-team).
## Your interviews
Go to **Interviews**, then **My Interviews**. **Upcoming** lists the interviews booked with you, with the time, the candidate, the interview and job req, and the interviewers. **Past** lists earlier interviews with their status and your score.
Each row has icons to start the interview, open the candidate's Candidate Application and copy the interview link. The **â‹®** menu has the same actions. See [My Interviews](/interviews/conduct-an-interview#my-interviews).

## Run an interview and submit feedback
**1. Open the interview guide**
Click the start icon in **My Interviews**, use the link on your calendar event, or click **Start**, then **Interview**, at the top of any page.
**2. Ask, take notes and score**
For each question, type what the candidate said in **Notes** and score each attribute from 1 to 5 against the scoring criteria. If an answer didn't give you enough to judge, click **Unable to score**.
**3. Submit**
Click **Submit - I'm all done**. Your scores and notes appear on the candidate's Candidate Application for the rest of the team. To stop and come back, click **Save - I'll finish later**.
See [Conduct an interview and submit feedback](/interviews/conduct-an-interview) for every option, including interviewing a walk-in candidate and correcting submitted feedback.
> [!TIP]
>
> Score each question right after the candidate answers, and write down what they actually said or did. Specific, evidence-based notes are what make your scores useful to the rest of the team.
## Review candidates
Your recruiter can send you a candidate with **Share**. You'll get an email with their message and a link to the Candidate Application. You need to be signed in, and on the job req's hiring team (or have access to every job req), to open it. See [Share and print](/candidates/share-and-print).
On the Candidate Application, start with these tabs:
| Tab | What it tells you |
| - | - |
| **Score** | The candidate's strengths and gaps for this job, by attribute |
| **Steps** | Where they are in the process and how they did on each activity |
| **Notes** | What other interviewers wrote and how they scored |
| **Resume** | Their resume |
| **Comments & Activities** | Your team's comments and the candidate's history |
Leave your view as a comment on **Comments & Activities**, so the recruiter and the rest of the team see it in one place. Comments need the *View & Submit Comments* permission. See [Comments and activity](/candidates/comments-and-notes).
To learn what the scores mean, see [Reading a candidate's scores](/scoring/reading-scores).
> [!TIP]
>
> Want an email when a candidate finishes applying to one of your job reqs? Ask your admin to turn on **Candidate completes application** emails for you on the job req's team. See [Hiring team](/job-reqs/hiring-team#get-an-email-when-a-candidate-finishes-applying).
## If you manage employees
If your company tracks performance in Journeyfront, you may be asked to review the people on your team: click **Start**, then **Performance Review**, pick the employee and the review period, and score each question. See [Performance reviews](/employees/performance-reviews).
## FAQ
> [accordion] Why can't I open a candidate someone shared with me?
>
> Shared links only open for signed-in users who have access to the candidate's job req. Ask the recruiter or your admin to add you to the job req's hiring team.
> [accordion] Why isn't an interview in My Interviews?
>
> **My Interviews** shows interviews booked with you as an interviewer, plus guides you've opened. If the candidate hasn't booked yet, or someone else was picked as the interviewer, it won't be there. Open the guide from **Start**, then **Interview**, instead.
> [accordion] Why can't I submit my feedback?
>
> Every attribute on every question needs a score from 1 to 5, or **Unable to score**. Fix the questions marked in red and submit again.
> [accordion] I submitted by mistake. Can I change it?
>
> Yes, once it's unlocked by someone with the *Can Unlock Interviews* permission. See [Conduct an interview](/interviews/conduct-an-interview#unlock-submitted-feedback).
> [accordion] Why don't candidates see my open times?
>
> Check that your calendar is connected in **My Profile** and that **My Availability** has hours set. See [Your availability and calendar](/interviews/availability).
> [accordion] Can candidates see my notes or scores?
>
> No. Interview notes, scores and comments are only visible to your team.
## Related
> [card] [Conduct an interview](/interviews/conduct-an-interview)
>
> The interview guide, step by step.
> [card] [Your availability and calendar](/interviews/availability)
>
> Connect your calendar and set your hours.
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
# How the pieces connect
Source: https://help.journeyfront.com/getting-started/how-the-pieces-connect
Job reqs, workflows, postings, job boards, referral portals, candidates, hiring classes and job profiles, one relationship at a time.
Journeyfront's pieces are easy to mix up: a job req and a job profile sound alike, a job board and a referral portal both show jobs, and most setup mistakes come from treating two of them as one. This page takes them a pair at a time: what the relationship is, how many of one go with the other, and what that means when you set things up.
Everything hangs off the **job req**, so that's where this starts. For all of it in one diagram, see the map on [Getting started for TA leaders](/getting-started/ta-leaders#how-the-pieces-fit-together).
## Job reqs and workflows
A job req's **workflow** is your hiring process, written down: **steps** in the order candidates move through them, **activities** inside each step, and automation rules that act on candidates along the way. One job req has one workflow, and every candidate who applies to that req follows it.
Job req
one workflow, many steps
Its workflow
Every job req has its own workflow, so a customer care role and a technical support role can be screened completely differently. This is why the job req is the center of everything: change the workflow and you've changed what every candidate in that req does next.
Workflows have versions. You build changes in a **draft**, and candidates only see them once you **publish**. Candidates already in progress stay on the version they started with, keeping their scores, interviews and offers. See [Workflows overview](/workflows/overview) and [Publish workflow changes](/workflows/publish).
## Job reqs and job postings
A **job posting** is the public ad for a job req: the title, location, pay and description candidates read before they apply. One job req can carry many postings.
Job req
one to many
Job postings
Use that to advertise the same job in different ways: a different title per city, a different language, or a posting aimed at one board. Whichever posting someone applies through, they land in the same job req and the same workflow, and the **Job Post** they came from is recorded on their Candidate Application's **Details** tab.
Two things to know when you reorganize job reqs:
* Deactivating, closing or archiving a job req turns all of its postings off and takes them down. Reactivating the req doesn't turn them back on; you reopen each posting yourself.
* Duplicating a job req doesn't copy its postings. Create new ones on the copy.
See [Job postings](/sourcing/job-postings) and [Job req statuses](/job-reqs/statuses).
## Job postings and job boards
In Journeyfront your career site is called a **job board**: a branded page, hosted by Journeyfront, that lists open postings. Each posting is linked to exactly one board, in **Link to Job Board**.
Job postings
each posting to one board
Job board
This is the one place in the chain where you don't get a free many-to-many. To list the same job on two boards, for example a global careers site and a country site, create a second posting and link it to the other board. Both postings still feed the same job req.
A posting appears on its board only when **Make job posting page active** and **Post job to job board** are both on, and the board itself is enabled. See [Job boards](/sourcing/job-boards).
## Job reqs and referral portals
**Referral portals** break the pattern: they list **job reqs** directly, not postings. A job req can appear on several portals at once.
Job req
one to many
Referral portals
You choose this per job req, under **Setup**, then **Configurations**, in **Show on Referral Portals**:
| Option |
What it does |
| **All Portals** |
The job req is listed on every referral portal. This is the default. |
| **No Portals** |
The job req isn't listed on any portal. |
| **Specific Portals** |
The job req is listed only on the portals you pick. |
Archived job reqs are never listed on a portal, whatever this is set to.
The same screen sets the **Reward Program** a referral to this job req earns, and the program has to cover every portal the job req is on. See [Rewards on job reqs](/referrals/job-req-rewards).
## Candidate profiles and applications
When someone applies to a job req, Journeyfront creates a **Candidate Application**: their progress through that job req's workflow, with their scores, interviews and offer. Apply to three job reqs and you have three applications.
All of a person's applications roll up into one **Candidate Profile**.
Candidate applications
many to one
Candidate profile
That's what stops the same person being worked twice by two recruiters without anyone noticing: open their profile and every application is there, whichever job req it belongs to. Where a person has ended up with two records, you can compare and merge them. See [Candidate profiles and applications](/candidates/profiles-and-applications) and [Compare and merge candidates](/candidates/compare-and-merge).
Scores, interviews and offers belong to the application, not the person, because each job req measures its own attributes. The person is what ties them together.
## Job reqs and hiring classes
Because a job req can stay open all year, the people you hire are grouped into **hiring classes**: usually one per start date, each with its own number of openings.
Job req
one to many
Hiring classes
A class belongs to one job req, and a hire counts toward its class's openings. Once a class has as many hires as openings, it's marked filled. That's what lets you answer "how is the March class doing" without creating a new job req every month.
> [!WARNING]
>
> Set a candidate's class before you hire them. The Hire window doesn't ask for it: use **Assign Class** on the Candidates list, or the **Hiring Class** field on the Candidate Application's **Details** tab. See [Hiring classes](/hiring-classes/overview).
## Job reqs and job profiles
A **job profile** is a role as your company measures it: the people who do that job, the assessments they took, how they perform and how long they stay. It's the level Journeyfront builds [predictive models](/scoring/predictive-models) at, because a model needs the outcomes of many employees doing the same work.
A **job req** is one hiring effort. Many job reqs feed a single profile.
Job reqs
many to one
Job profile
You might run "Customer Service Tier 1 MX" and "Customer Service Tier 1 PH" as separate job reqs, because they hire in different countries with different languages and teams. Both link to one **Customer Service** job profile, so everything you learn about customer service agents pools in one place instead of splitting into a dozen thin samples.
Each job req links to exactly one job profile, chosen in **Linked to Job Profile** when you create it. See [Create a job req](/job-reqs/create).
> [!TIP]
>
> Create one profile per role that's measured the same way, not one per site, shift or client. A Customer Service profile with hundreds of employees tells you far more than ten small ones, and predictive models need that volume. See [Job profiles](/employees/job-profiles).
### What the link does when you hire
The link isn't only for reporting. When you hire someone, Journeyfront creates their **employee record** in a job profile, and the job req's profile is the default:
**1. The Hire window opens**
**Job Profile** is already filled in with the job req's linked profile.
**2. The recruiter can change it**
Pick a different profile in that field when this particular hire belongs somewhere else, for example someone hired into a team lead role off a Tier 1 req.
**3. The hire lands where you chose**
Their employee record is created in that profile, and it shows on the **Jobs** tab of their Candidate Profile and on the **Employees** page.
So the job req sets the default, and the person doing the hiring has the final say. Changing it for one candidate doesn't change the job req. See [Hire candidates](/onboarding/hire-candidates).
> [!NOTE]
>
> Journeyfront builds predictive models from your outcome data rather than you configuring them. To get a model for a role, ask your Customer Success Manager, then add it to the job reqs linked to that profile. See [Predictive models](/scoring/predictive-models).
## The shape of it
| Relationship |
How many |
| Job req to workflow |
One job req to one workflow, with many steps and activities |
| Job req to job postings |
One job req to many postings |
| Job posting to job board |
Each posting to exactly one board |
| Job req to referral portals |
One job req to many portals |
| Candidate applications to candidate profile |
Many applications to one person |
| Job req to hiring classes |
One job req to many classes |
| Job reqs to job profile |
Many job reqs to one profile |
Everything above funnels back to the same place: whichever posting, board or portal someone came through, their application is created in the job req and follows its workflow.
## Related
> [card] [The whole map](/getting-started/ta-leaders#how-the-pieces-fit-together)
>
> Every piece in one diagram, on the TA leaders guide.
> [card] [Workflows overview](/workflows/overview)
>
> Steps, activities, automation and versions.
> [card] [Glossary](/getting-started/glossary)
>
> Every term, in plain language.
# Logging in
Source: https://help.journeyfront.com/getting-started/logging-in
Accept your invitation, sign in, reset or change your password, and help a candidate who can't log in.
> [!NOTE]
>
> **Who can do this:** Everyone. If your company signs in with single sign-on (SSO), your password is managed by your company, not by Journeyfront.
Everyone signs in to Journeyfront with their email address. Your team signs in with a work email and either a Journeyfront password or your company's single sign-on. Candidates and employees sign in with the email they applied or were invited with. This page covers each of those, plus what to do when someone can't get in.
## Accept your invitation
When an admin adds you as a user, you get an email with the subject "*Name* has invited you to Journeyfront".
**1. Open the invitation**
Click **Click here to get started!** in the email. A sign-in page opens with your company's logo and your email already filled in.

**2. Set your password**
Under "Please set a password for your profile", enter a password and click **Next**. It needs at least 8 characters, with an uppercase letter, a number and a special character. A checklist shows what's still missing.
**3. Start working**
You're signed in and land on the **Job Reqs** page.
If your company uses SSO, the invitation sends you to your company's sign-in page instead of asking for a password.
The invitation link doesn't expire. If it's lost, go to the sign-in page and use **Forgot your password?** (see [Reset a forgotten password](#reset-a-forgotten-password)). For more invitation problems, see [Users](/account-setup/users#troubleshoot-invitations).
## Sign in
**1. Go to the sign-in page**
Open [app.journeyfront.com](https://app.journeyfront.com). Bookmark it.
**2. Enter your work email**
Under "Enter your email to continue.", type the email you were invited with and click **Next**. If your company uses SSO, you're sent to your company's sign-in page here instead (see [Single sign-on](/integrations/single-sign-on)).
**3. Enter your password**
Under "Please enter your password", enter it and click **Next**.

You land on the **Job Reqs** page. If you signed in from an interview guide link, you go straight to the guide.
To sign out, click your name at the top right, then **Sign Out**.
### Single sign-on (SSO)
With SSO, you sign in to Journeyfront with the same account you use for your other work tools. Journeyfront recognizes your company's email domain after you enter your email and click **Next**, and sends you to your company's sign-in page. Once you're signed in there, you come back to Journeyfront.
SSO is set up for your company by Journeyfront. To set it up, or to add an email domain, ask your Customer Success Manager. If you use SSO, change or reset your password with your company's IT team, not in Journeyfront.
> [card] [Single sign-on (SSO)](/integrations/single-sign-on)
>
> How SSO sign-in works, what it changes, and how it gets set up for your company.
## Reset a forgotten password
**1. Start from the sign-in page**
Enter your email, click **Next**, then click **Forgot your password?**.

**2. Request the email**
On **Reset your password**, check your email address and click **Reset password**. You'll see "If the provided account was found, an email will be sent to reset the password."
**3. Open the email**
Look for an email from **Journeyfront System** with the subject "Reset Your Journeyfront Password", and click **Click here to reset your password**.
**4. Choose a new password**
Enter it in **New Password** and **Confirm New Password**, then click **Submit**. You'll see "Your password has been changed successfully."
**5. Sign in**
Sign in with your new password.
The reset link works once and expires after three days.
> [!TIP]
>
> No email after a few minutes? Check your spam or junk folder, and make sure you entered the email you sign in with. For security, the page looks the same whether or not an account exists, so a typo doesn't show an error.
## Change your password
**1. Open Change Password**
Click your name at the top right, then **Change Password**.

**2. Enter your passwords**
Enter your **Current Password**, then your **New Password** twice. The new password has to be different from the current one and meet the password rules.
**3. Click Submit**
You'll see **Password Changed**.
## Password rules
Every Journeyfront password needs:
* At least 8 characters
* An uppercase letter
* A number
* A special character, such as `!`, `@`, `#`, `$`, `%` or `&`
When you set a new password, a checklist shows what's still missing, and **Next** stays greyed out until the password meets every rule.
## How candidates and employees sign in
Candidates sign in from the link they apply through: a job posting, your career site, an invitation email or a text. They enter their email and click **Next**. The first time, they enter their name and create a password; after that, they enter their password. Then they click **Continue** to go to their application. Employees you invite to take assessments sign in the same way from their invite link. See [Job profiles](/employees/job-profiles#invite-employees-to-take-the-assessments).
Candidates can switch the sign-in page to English, Spanish or French with the language menu at the top right.
### Help a candidate who can't sign in
Work through these with the candidate:
1. **Use the same email.** Their account is tied to the email they applied with. A different email starts a new account.
2. **Reset the password.** On the sign-in page, enter the email, click **Next**, then **Forgot your password?**. The email comes from **Journeyfront System**; ask them to check spam.
3. **Try a private window.** Open the application link in a private (incognito) window, or another browser, and sign in again.
4. **Update the browser.** Use an up-to-date version of Chrome, Edge, Firefox or Safari. See [Supported browsers](/assessments/overview#supported-browsers).
Your team can't see or set a candidate's password. If they still can't get in, contact your Customer Success Manager or Journeyfront support with the candidate's email and **Application ID** (on the **Details** tab of their Candidate Application).
> [!TIP]
>
> If a candidate needs to change the email they sign in with, update **Primary Email** on the **Details** tab of their Candidate Application. They sign in with the new email from then on. See [Edit candidate details](/candidates/edit-details).
## FAQ
> [accordion] The sign-in page says "Invalid Email".
>
> There's no Journeyfront account with that email. Check for typos, and use the email you were invited with. If you've never been invited, ask your Journeyfront admin to add you. See [Users](/account-setup/users).
> [accordion] I set a password on my invitation, and it says "Incorrect Email or Password".
>
> You already have a Journeyfront password for this email, for example from applying to a job or from another company that uses Journeyfront. Enter that password instead, or use **Forgot your password?** on the sign-in page.
> [accordion] My reset link shows an error.
>
> The link has expired or was already used. Reset links work once and expire after three days. Request a new one with **Forgot your password?**.
> [accordion] The reset email never arrives.
>
> Check spam and junk for an email from **Journeyfront System** with the subject "Reset Your Journeyfront Password", and make sure you entered the email you sign in with. If your company uses SSO, there's no Journeyfront password to reset: use your company's password reset instead.
> [accordion] The sign-in page keeps coming back after I sign in.
>
> Open Journeyfront in a private (incognito) window and sign in again. If that works, clear your browser's cookies for Journeyfront and try your normal window. If your company uses SSO, also sign out of your company's sign-in page and back in. Still stuck? Contact your Customer Success Manager or Journeyfront support.
> [accordion] I signed in, but I see a candidate page instead of our job reqs.
>
> You signed in with an email that isn't a user in your company's account, for example a personal email you once applied with. Sign out and sign in with the email you were invited with.
> [accordion] Can an admin reset someone's password?
>
> Not from the app. The person resets it themselves with **Forgot your password?** on the sign-in page. If your company uses SSO, your IT team manages passwords.
> [accordion] An interview guide link asks me to sign in, but I don't have an account.
>
> Interviewers need a Journeyfront user account to open an interview guide. Ask your Journeyfront admin to add you. See [Users](/account-setup/users).
> [accordion] Which browsers can I use?
>
> An up-to-date version of Chrome, Edge, Firefox or Safari. Internet Explorer isn't supported. See [Supported browsers](/assessments/overview#supported-browsers).
## Related
> [card] [Users](/account-setup/users)
>
> Invite teammates and fix invitation problems.
> [card] [Finding your way around](/getting-started/navigating)
>
> What's where once you're signed in.
> [card] [Getting started for recruiters](/getting-started/recruiters)
>
> Your first day in Journeyfront.
> [card] [Getting started for hiring managers](/getting-started/hiring-managers)
>
> Review candidates and run interviews.
# Finding your way around
Source: https://help.journeyfront.com/getting-started/navigating
A quick tour of the Journeyfront navigation: what lives where.
Journeyfront's main navigation runs across the top of every page. What you see depends on your security role and the features your account uses, so your menu may not show every item below.

## The top navigation
| Item | What you'll find there |
| - | - |
| **Dashboard** | Company-wide hiring dashboards and reports |
| **Employees** | Your employee records |
| **Profiles** | Job profiles, used to measure current employees and define what success looks like in a role |
| **Job Reqs** | Every job req you have access to, with saved views and filters |
| **Candidates** | Candidates across all your job reqs, with search, filters and bulk actions |
| **Classes** | Hiring classes across your job reqs, with openings and percent filled |
| **Interviews** | Your upcoming interviews, your availability and your calendar connection |
| **Referrals** | Candidates referred by your employees |
## Inside a job req
Open any job req to see its own tabs:
* **Hiring Classes:** the waves of hires for this job req.
* **Dashboard:** how this job req is performing.
* **Candidates:** everyone who has applied to this job req.
* **Setup:** the job req's details, application form, workflow, team, postings and settings.
* **Activity:** a log of changes made to the job req.

### The job req Actions menu
The **Actions** button at the top right of a job req holds the things you do to the job req as a whole: **Invite Candidates**, **Add New Candidate**, **Import Candidates**, **Export Data**, **Duplicate Job Req**, and the status changes (**Deactivate**, **Close**, **Archive** and **Delete Job Req**, or **Activate** and **Re-Open** when it isn't active). Which items you see depends on the job req's status and your security role. See [Job req statuses](/job-reqs/statuses).

## The right side of the header
* **Help:** opens this Help Center.
* **Settings** (gear icon): company-wide settings such as users, security roles, templates, custom fields and integrations. Only people with settings access see it.
* **Start:** quick ways to start an interview or a performance review.
* **Your name:** **Personal Settings**, **My Profile**, **My Progress**, **Change Password** and **Sign Out**. Admins also see **Company Settings** and **Import Data** here. See [Logging in](/getting-started/logging-in#change-your-password) to change your password.

> [!TIP]
>
> Most of your day happens on the **Candidates** page and inside each **Candidate Application**. Set up a few saved views there for the candidates you work most, and you'll rarely need to search.
## FAQ
> [accordion] Why don't I see some of these menu items?
>
> Menu items depend on your security role and on which features your account uses. If you think you should see something, ask your Journeyfront admin to check your role.
> [accordion] Where do I change my password?
>
> Select your name in the top right, then **Change Password**.
# Getting started for onboarding teams
Source: https://help.journeyfront.com/getting-started/onboarding-team
Take candidates from signed offer to first day: hire them, collect their paperwork, clear their background check and hand them off to your HR system.
> [!NOTE]
>
> **Who this is for:** Onboarding specialists, HR coordinators and anyone who gets new hires ready for day one. **Hire** and **Un-Hire** need the *Hire Candidates* permission, building onboarding and consent forms needs *Company Settings Access*, adding them to a workflow needs *Manage Job Req Settings*, and seeing private fields needs *Private Data Access*. Ask your Journeyfront admin if an action below isn't there.
Your part of the process starts when an offer is signed and ends when a prepared new hire walks in. In Journeyfront that means four things: **hiring** the candidate, **collecting** their information and documents, **clearing** anything that has to clear, and **handing off** a clean record to your HR system.
## Your first week
**1. Find your hires**
On the **Candidates** page, filter to the job reqs you support and the onboarding step, and save it as a view you can open every morning. See [Saved views](/lists-and-exports/saved-views).
**2. Learn the Onboarding tab**
Open a recent hire's Candidate Application and click **Onboarding**. Forms and background checks both live here, each with a status. See [Onboarding forms](/onboarding/onboarding-forms).
**3. Look at your hiring classes**
Most onboarding work is by start date, not by person. See which classes are filling and which are short. See [Hiring classes](/hiring-classes/overview).
**4. Walk through one hire**
Follow a single person from signed offer to employee record so you know every window you'll see. See [Hire candidates](/onboarding/hire-candidates).
**5. Check the hand-off**
If your HR system is connected, find out what Journeyfront sends it and what your team still types by hand. See [HRIS integrations](/integrations/hris).
## The path from offer to day one
**1. Offer accepted**
The signed offer lands on the candidate's **Offer** tab. See [Send an offer](/offers/send-offers) and [E-signatures](/offers/e-signatures).
**2. Onboarding form sent**
The candidate reaches the onboarding step and gets their form, automatically or because you sent it. See [Onboarding forms](/onboarding/onboarding-forms).
**3. Paperwork and consents returned**
They fill in their details, upload documents and sign consent forms. See [E-consent forms](/onboarding/e-consent-forms).
**4. Background check cleared**
Where your process includes one, it runs and comes back on the same tab. See [Background checks](/onboarding/background-checks).
**5. Hired**
You record their job title and start date, and create them in your HR system in the same step. See [Hire candidates](/onboarding/hire-candidates).
**6. Employee record**
They become an employee in Journeyfront, which is what later feeds turnover and performance reporting. See [Employee records](/employees/employee-records).
## Your day to day
| What you need to do | Where | Learn more |
| - | - | - |
| Send someone their onboarding form | The **Onboarding** tab, then **Select Form** | [Onboarding forms](/onboarding/onboarding-forms#send-a-form-to-candidates) |
| Chase what's missing | The form's status: **Not Sent**, **Sent To Candidate**, **In Progress**, **Submitted**, **Complete** | [Onboarding forms](/onboarding/onboarding-forms#review-and-complete-a-form) |
| Fill in the parts your team owns | Expand the form row, including fields hidden from the candidate | [Onboarding forms](/onboarding/onboarding-forms) |
| Close out a finished form | The row's menu, then **Set To Complete** | [Onboarding forms](/onboarding/onboarding-forms) |
| Check a background check | The **Onboarding** tab | [Background checks](/onboarding/background-checks), [Checkr](/integrations/background-checks/checkr) |
| Hire one person | **Actions**, then **Hire** | [Hire candidates](/onboarding/hire-candidates) |
| Hire a whole class at once | **Bulk hire** from the class or the Candidates list | [Bulk hire](/onboarding/bulk-hire) |
| Put a hire into the right start-date group | **Assign Class**, or the **Hiring Class** field on the **Details** tab | [Working with a hiring class](/hiring-classes/working-with-a-class) |
| Reverse a hire that didn't stand | **Actions**, then **Un-Hire**, with a reason | [Hire candidates](/onboarding/hire-candidates#un-hire-a-candidate) |
| Keep the group informed | **Email** and **Message**, including bulk | [Email candidates](/communication/email-candidates), [Text messages](/communication/text-messages) |
> [!WARNING]
>
> Set the hiring class **before** you hire. The Hire window doesn't ask for it, and the class is what counts the hire toward its openings. See [Hiring classes](/hiring-classes/overview).
> [!TIP]
>
> Enter a **Company Email** only once the account really exists. It becomes the address the person signs in with and the one your emails go to, so a typo here sends every message to nowhere.
## Make it run itself
> [!TIP]
>
> Send the onboarding form the moment the offer is accepted, not the week before the start date. Candidates have time to find their documents, and you have time to chase what's missing before training starts.
> [!TIP]
>
> Let automation do the chasing. An automation rule on the **Activity Status Changes To** trigger can assign a coordinator or move the candidate on as soon as a form is **Submitted**, so nobody is checking tabs one by one. See [Automation rules](/workflows/automation-rules).
> [!TIP]
>
> Collect a field once. Onboarding form answers save into your personal and application fields, so they show on the candidate's **Details** tab and can be columns and filters on the **Candidates** page. Ask for a document or a uniform size on the form rather than in an email thread. See [Custom fields](/account-setup/custom-fields).
> [!TIP]
>
> Work by class, not by person. Open the hiring class, act on everyone in it, and your start-date group stays in step. See [Working with a hiring class](/hiring-classes/working-with-a-class).
## FAQ
> [accordion] Why can't I see Hire in the Actions menu?
>
> You need the *Hire Candidates* permission, and the candidate can't already be hired or rejected. To hire someone who was rejected, un-reject them first. See [Reject candidates](/candidates/reject#un-reject-a-candidate).
> [accordion] Why can't I move a candidate into the onboarding step?
>
> The **Change Candidate Step** window needs an onboarding form chosen before it lets you continue. Pick one under **Onboarding form**.
> [accordion] A new hire never started. What do I do?
>
> **Actions**, then **Un-Hire**, with the reason **No-show**. Their employee record for that hire is removed, pending automation from the hire is canceled, and they stop counting toward the class's openings. See [Hire candidates](/onboarding/hire-candidates#un-hire-a-candidate).
> [accordion] I hired someone without sending them to our HR system. Can I send them now?
>
> Yes. Click the edit icon next to **Hired** in the header, tick **Create Employee in** your HR system, and click **Hire** again. See [HRIS integrations](/integrations/hris).
> [accordion] Why is a form missing from the list when I try to send it?
>
> Only active forms can be chosen. An admin can edit it under **Settings**, then **Onboarding Forms**, and turn **Activate Onboarding Form** to **Yes**.
> [accordion] Why can't I see a field a candidate filled in?
>
> Fields marked private only show to users whose security role has *Private Data Access*. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] Is a signed consent form the same as an e-signature?
>
> No. Consent forms are signed with a checkbox and a typed name. Offer letters and documents needing a full e-signature go through offers. See [E-signatures](/offers/e-signatures).
## Related
> [card] [Onboarding forms](/onboarding/onboarding-forms)
>
> Build, send, review and complete new-hire forms.
> [card] [Hire candidates](/onboarding/hire-candidates)
>
> The Hire window, field by field.
> [card] [Bulk hire](/onboarding/bulk-hire)
>
> Hire a whole class in one pass.
> [card] [Employee records](/employees/employee-records)
>
> Where your hires go next.
# Getting started for recruiters
Source: https://help.journeyfront.com/getting-started/recruiters
Your first day in Journeyfront: the pages and actions recruiters use most, with links to the details.
> [!NOTE]
>
> **Who this is for:** Recruiters, recruiting coordinators and anyone who works candidates day to day. What you can see and do depends on your security role, so you may not have every action below. Ask your Journeyfront admin if something's missing.
As a recruiter, most of your day happens in two places: the **Candidates** page, where you work your whole pipeline, and each candidate's **Candidate Application**, where you see their scores, move them forward and stay in touch. This page walks you through your first day and points to the details for everything you'll do after that.
## Your first day
**1. Sign in**
Accept your invitation email and set your password, or sign in with your company's SSO. See [Logging in and passwords](/getting-started/logging-in).
**2. Learn the big ideas**
Five minutes on job reqs, workflows, Candidate Applications and scores makes everything else click. See [How the pieces connect](/getting-started/how-the-pieces-connect).
**3. Find your way around**
Take the tour of the top navigation and a job req's tabs. See [Finding your way around](/getting-started/navigating).
**4. Check your job reqs**
Open **Job Reqs** and make sure you see the job reqs you work on. If one's missing, ask your admin to add you to its hiring team. See [The Job Reqs page](/job-reqs/job-reqs-page).
**5. Save your first views**
On the **Candidates** page, filter to the candidates you work most and click **Save as New View**. Your team lead may already have shared views for you: click **+** at the end of the tabs to add them. See [Saved views](/lists-and-exports/saved-views).
**6. Connect your calendar (if you interview)**
Go to **Interviews**, then **My Profile** to connect your calendar, then **My Availability** to set the hours candidates can book. See [Your availability and calendar](/interviews/availability).
## Your day to day
| What you need to do | Where | Learn more |
| - | - | - |
| Find candidates and work your pipeline | **Candidates** page, or a job req's **Candidates** tab | [The Candidates page](/candidates/candidates-page) |
| Review one candidate | Click their name to open their Candidate Application | [The Candidate Application](/candidates/candidate-application) |
| Decide who to talk to first | The **Overall Score** column and the **Score** tab | [Reading a candidate's scores](/scoring/reading-scores) |
| Move candidates to the next step | **Current Step** on a Candidate Application, or **Change Step** for a group | [Move candidates through steps](/candidates/move-through-steps) |
| Reject candidates, with a reason | **Reject** | [Reject candidates](/candidates/reject) |
| Act on many candidates at once | Tick them to open the actions bar | [Bulk actions](/candidates/bulk-actions) |
| Email or text candidates | **Email** and **Message** | [Email candidates](/communication/email-candidates), [Text messages](/communication/text-messages) |
| Get interviews booked | Scheduling links, booking a time yourself, and the people who haven't booked | [Self-scheduling](/interviews/self-scheduling), [Schedule for a candidate](/interviews/schedule-for-a-candidate), [Who hasn't booked](/interviews/who-hasnt-booked) |
| Get a hiring manager's opinion | **Share** the Candidate Application, or leave a comment | [Share and print](/candidates/share-and-print), [Comments and activity](/candidates/comments-and-notes) |
| Add someone who didn't apply online | **Invite Candidates**, **Add New Candidate** or **Import Candidates** on the job req | [Invite candidates](/sourcing/invite-candidates), [Add candidates](/sourcing/add-candidates), [Import candidates](/sourcing/import-candidates) |
| Fill a start date | Put candidates in a hiring class and act on the whole class | [Working with a hiring class](/hiring-classes/working-with-a-class) |
| Send offers | The **Offer** tab, or **Send Offers** for a group | [Send an offer](/offers/send-offers), [Send offers in bulk](/offers/bulk-send) |
| Hire | **Hire**, on one candidate or a whole class | [Hire candidates](/onboarding/hire-candidates), [Bulk hire](/onboarding/bulk-hire) |
| Spot applications that need a closer look | Fraud flags and Do Not Hire warnings | [Fraud flags](/candidates/fraud-flags), [Do Not Hire](/candidates/do-not-hire) |
Many of these actions, such as **Hire**, **Reject**, **Email**, **Message** and **Interview**, are in the **Actions** menu at the top right of a Candidate Application.

## Work smarter
> [!TIP]
>
> Know what your job reqs do automatically. Automation rules can move candidates forward, assign them or message them when something happens, so you can spend your time on the candidates who need a person. Ask your admin which rules each of your job reqs uses. See [Automation rules](/workflows/automation-rules).
> [!TIP]
>
> Use scores to decide who to look at first, not who to hire. A score tells you where to start; your review, the interview and your judgment decide the outcome. See [How scoring works](/scoring/how-scoring-works).
> [!TIP]
>
> Build a saved view for each part of your day, such as new applicants, candidates waiting on you and candidates ready to interview, and make the one you check first your default.
## FAQ
> [accordion] Why can't I see a job req or its candidates?
>
> You see the job reqs you're on the hiring team for, or every job req if your security role has *All Job Req Access*. Ask your admin to add you to the job req's team. See [Hiring team](/job-reqs/hiring-team).
> [accordion] Why can't I hire, email or text candidates?
>
> Each of those needs its own permission in your security role: *Hire Candidates*, *Send Emails* or *Send Messages*. See [Security roles and permissions](/account-setup/security-roles).
> [accordion] A candidate says they're stuck. What do I check?
>
> Start with their current step: candidates only see the activities in their current step, and wait for your team or an automation rule to move them on. See [Assessments overview](/assessments/overview) for a checklist, and [Logging in and passwords](/getting-started/logging-in#help-a-candidate-who-cant-sign-in) if they can't sign in.
> [accordion] Why don't I see the Setup tab on a job req?
>
> Changing a job req's workflow, application form and settings needs *Manage Job Req Settings*. You can still work with its candidates without it.
## Related
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> Send scheduling links so candidates book their own interview.
> [card] [Schedule an interview for a candidate](/interviews/schedule-for-a-candidate)
>
> Pick a time from your interviewers' calendars and book it yourself.
> [card] [Getting started for hiring managers](/getting-started/hiring-managers)
>
> Share this with the hiring managers you work with.
> [card] [Glossary](/getting-started/glossary)
>
> Every term, in plain language.
> [card] [How Journeyfront uses AI](/getting-started/ai)
>
> Where AI helps, and how your team stays in charge.
# Getting started for sourcing teams
Source: https://help.journeyfront.com/getting-started/sourcing-team
Get the job in front of the right people, tag every channel so you can prove what worked, and bring candidates in by link, import or referral.
> [!NOTE]
>
> **Who this is for:** Sourcers, recruitment marketers and anyone responsible for filling the top of the funnel. Posting a job and generating posting source links needs the *Manage Job Req Settings* permission; career site and company-wide source settings need *Company Settings Access*; source reporting needs *Company Dashboard Access*. Ask your Journeyfront admin if something below isn't there.
Sourcing in Journeyfront is three jobs: **publish** the job where candidates are, **tag** every place you share it so the credit lands in the right bucket, and **bring in** people directly. Do the tagging part properly and the reporting answers your budget questions for you.
## Your first week
**1. See your career site**
Open your company's career site the way a candidate does, and check that the jobs you expect are live on it. See [Job boards](/sourcing/job-boards).
**2. Check a job req's postings**
Open a job req, go to **Setup**, then **Job Postings**, and see where that job is advertised today. See [Job postings](/sourcing/job-postings).
**3. Agree on your source list**
Sources come from your account's list under **Settings**, then **Sources**, each with a **Source Type** such as **Job Board**, **Social Media**, **Referral**, **Event** or **Agency**. Agree the naming before you start making links. See [Sources](/sourcing/sources).
**4. Make your first source links**
Generate a separate link for every place you post: the Facebook ad, the job fair flyer, the newsletter. See [Magic links](/sourcing/magic-links).
**5. Open Source Effectiveness**
Click **Dashboard**, open **Source Effectiveness**, and look at what the last quarter's channels actually produced. See [Dashboards overview](/reporting/dashboards).
## Publish the job
| Channel | Where | Learn more |
| - | - | - |
| Your own career site | **Settings**, then **Job Boards** | [Job boards](/sourcing/job-boards) |
| A posting for one job req | **Setup**, then **Job Postings** | [Job postings](/sourcing/job-postings) |
| External job boards | **Settings**, then your job board integrations | [Job board integrations](/integrations/job-boards) |
| Indeed, including Easy Apply | The Indeed integration | [Indeed](/integrations/job-boards/indeed) |
| JobTarget | The JobTarget integration | [JobTarget](/integrations/job-boards/jobtarget) |
| Appcast | The Appcast integration | [Appcast](/integrations/job-boards/appcast) |
| Paid social lead ads | Lead ads, where turned on | [Lead ads](/sourcing/lead-ads) |
| Your own employees | Referral portals and reward programs | [Referrals overview](/referrals/overview) |
> [!TIP]
>
> Candidates judge the job by its posting. Keep the **External Job Title** the words a candidate would actually search for, and keep the first lines of the description about the work, the shift and the pay rather than the company boilerplate.
## Tag everything: source links
A source link is your normal career site, posting or invite link with the source added to the end. Anyone who applies after opening it is tagged automatically, so nobody has to remember to pick "where did you hear about us".
| Link | Where you generate it | Use it for |
| - | - | - |
| Job board source link | **Settings**, then **Job Boards**, then the **â‹®** menu, then **Generate Source Link** | Links to your whole career site |
| Job posting source link | **Setup**, then **Job Postings**, then the **â‹®** menu, then **Generate Source Link** | Promoting one job |
| Invite link with a source | The job req's **Actions**, then **Invite Candidates**, choosing a **Source** before you copy | Texts, emails and outreach into one job req |
See [Magic links](/sourcing/magic-links) for the full walkthrough, and for how to see or correct a candidate's source afterward.
> [!WARNING]
>
> A source link records the source by its name, so renaming or deleting a source under **Settings**, then **Sources**, stops the old links recording it. Generate fresh links after any rename, and keep source names to letters, numbers and spaces.
> [!TIP]
>
> One link per placement, not one per channel. "Facebook" tells you little; "Facebook - Tampa Night Shift - Nov" tells you which creative and which market to repeat.
## Bring candidates in
| What you need to do | Where | Learn more |
| - | - | - |
| Send someone straight into a job req's application | **Actions**, then **Invite Candidates** | [Invite candidates](/sourcing/invite-candidates) |
| Add one person who didn't apply online | **Actions**, then **Add New Candidate** | [Add candidates](/sourcing/add-candidates) |
| Load a list from an event, agency or spreadsheet | **Actions**, then **Import Candidates**, with a `source` column | [Import candidates](/sourcing/import-candidates) |
| Re-engage people already in your database | The **Candidates** page, saved views and bulk actions | [Bulk actions](/candidates/bulk-actions), [Saved views](/lists-and-exports/saved-views) |
| Email or text a group | **Email** and **Message** | [Email candidates](/communication/email-candidates), [Text messages](/communication/text-messages) |
| Get employees referring | The referral portal and its rewards | [Referral portals](/referrals/portal-setup), [Reward programs](/referrals/reward-programs) |
| Put a job in front of referrers first | Featured jobs and notifications | [Featured jobs and notifications](/referrals/featured-and-notifications) |
> [!TIP]
>
> Your best source is often the database you already have. Build a saved view of strong candidates who were rejected for timing or location, and work it before you spend on ads.
## Prove what worked
| Where | What it tells you |
| - | - |
| **Source Effectiveness** dashboard | Which sources and source types bring in candidates, interviews and hires, how they score, and, with employee data, how long their hires stay. See [Dashboards overview](/reporting/dashboards). |
| **Source Effectiveness** on a job req's **Dashboard** tab | The same view for one job req. See [Job req dashboards](/reporting/job-dashboards). |
| **Candidates** page | Add the **Source** and **Source Type** columns, or filter by them. See [The Candidates page](/candidates/candidates-page). |
| **Referrals** dashboard | What your referral program is producing. See [Referrals dashboard](/referrals/dashboard). |
| Automation rules | Treat candidates differently by where they came from, using the **Source** condition. See [Automation rules](/workflows/automation-rules). |
> [!TIP]
>
> Judge a channel on hires and retention, not applicants. A board that floods you with applications who never finish screening costs your recruiters more than it saves you in spend.
## FAQ
> [accordion] Why do so many candidates have no source?
>
> They applied through a link with no source on it: a plain career site or posting link, or an invite link copied without choosing a **Source**. Replace the links you share, and set the source yourself for anyone you add by hand. See [Magic links](/sourcing/magic-links).
> [accordion] A candidate used my source link but no source was recorded.
>
> The source name in the link has to match a source in your account. That breaks when a source was renamed or deleted after the link was made, or when the link was cut short. Generate a fresh link.
> [accordion] Someone already in our database used my new source link. Does their source change?
>
> No. A source link only sets the source when their application to that job req is created.
> [accordion] Can I tell which posting a candidate applied through?
>
> Yes. The **Job Post** and **Job Board** fields on the **Details** tab of their Candidate Application show it, next to the source.
> [accordion] Why isn't my job showing on the career site?
>
> Check the job req's status and its postings: a job req that is **Inactive** or whose workflow hasn't been published doesn't take applications. See [Job req statuses](/job-reqs/statuses) and [Job postings](/sourcing/job-postings).
> [accordion] How do I add a new source, like a specific job fair?
>
> An admin adds it under **Settings**, then **Sources**, with a **Source Type**. It's then available when you generate links. See [Sources](/sourcing/sources).
## Related
> [card] [Magic links](/sourcing/magic-links)
>
> Magic links, step by step.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> The site your links point to.
> [card] [Referrals overview](/referrals/overview)
>
> Turn employees into your biggest channel.
> [card] [Getting started for recruiters](/getting-started/recruiters)
>
> What happens to candidates after you bring them in.
# Getting started for TA leaders
Source: https://help.journeyfront.com/getting-started/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](/job-reqs/overview).
**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](/job-reqs/statuses).
**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](/workflows/overview).
**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](/workflows/automation-rules).
**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](/reporting/dashboards).
**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](/account-setup/security-roles).
## 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](/getting-started/how-the-pieces-connect).
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](/job-reqs/create).
**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](/job-reqs/application-form).
**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](/scoring/attributes).
**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](/workflows/overview), [Build a workflow](/workflows/build) and [Set up an interview activity](/interviews/interview-activity).
**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](/job-reqs/hiring-team) and [Your availability and calendar](/interviews/availability).
**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](/sourcing/job-postings).
**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](/job-reqs/job-settings).
**8. AI Resume Scoring**
Where it's turned on for your account, score resumes against what the role needs. See [AI resume scoring](/scoring/ai-resume-scoring).
**9. AI Agents**
Where it's turned on, let an agent handle parts of the candidate conversation inside the workflow. See [AI agents](/workflows/ai-agents).
**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](/workflows/publish) and [Job req statuses](/job-reqs/statuses).
> [!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](/interviews/interview-activity) and [Interview reminders](/interviews/reminders).
> [!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](/interviews/interview-guides).
> [!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](/job-reqs/create#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](/workflows/overview) |
| Add, remove or reorder steps and activities | **Create New Version** or **Edit Draft** | [Build a workflow](/workflows/build) |
| Know what you can put in a step | The building blocks list in the editor | [Activities you can add](/workflows/activities) |
| Move, message, reject or assign candidates automatically | Automation rules on a step or activity | [Automation rules](/workflows/automation-rules) |
| Decide who owns each candidate | **Setup**, then **Configurations** | [Candidate assignment](/workflows/candidate-assignment) |
| Ship a change on a date you choose | **Publish**, with a scheduled version | [Publish workflow changes](/workflows/publish) |
| Let AI handle parts of the conversation | AI agent activities, where turned on | [AI agents](/workflows/ai-agents) |
> [!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](/sourcing/invite-candidates) |
| Advertise the job publicly | **Setup**, then **Job Postings**, on your job boards | [Job postings](/sourcing/job-postings), [Job boards](/sourcing/job-boards) |
| Reach the big external boards | **External Job Board Posts** on a posting | [External job boards](/sourcing/external-job-boards) |
| Tag every place you share the job | **Generate Source Link** on a job board or posting | [Magic links](/sourcing/magic-links) |
| Keep your source list clean | **Settings**, then **Sources**, each with a **Source Type** | [Sources](/sourcing/sources) |
| Get your employees referring | Referral portals, and the **Referrals** card on **Configurations** | [Referrals overview](/referrals/overview), [Rewards on job reqs](/referrals/job-req-rewards) |
| Load a list from an event or agency | **Actions**, then **Import Candidates**, with a `source` column | [Import candidates](/sourcing/import-candidates) |
| Re-engage people already in your database | Saved views and bulk actions on the **Candidates** page | [Bulk actions](/candidates/bulk-actions) |
> [!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](/getting-started/sourcing-team).
## 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](/hiring-classes/overview), [Create a class](/hiring-classes/create) |
| Act on everyone starting on the same day | Open the class and work from it | [Working with a hiring class](/hiring-classes/working-with-a-class) |
| Put a candidate in a class before hiring | **Assign Class**, or the **Hiring Class** field on the **Details** tab | [Hiring classes](/hiring-classes/overview) |
> [!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](/reporting/eeoc). |
See [Dashboards overview](/reporting/dashboards) for what each one holds, how to filter it and how to save your filters as bookmarks, and [Job req dashboards](/reporting/job-dashboards) 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](/reporting/turnover-and-performance).
> [!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](/lists-and-exports/saved-views), and [Export data](/lists-and-exports/export-data) 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](/job-reqs/statuses) and [Job reqs overview](/job-reqs/overview#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](/account-setup/security-roles).
> [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](/reporting/dashboards#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](/workflows/publish).
> [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](/interviews/interview-activity), [Interview reminders](/interviews/reminders) and [Your availability and calendar](/interviews/availability).
> [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](/job-reqs/statuses) and [Job postings](/sourcing/job-postings).
> [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](/getting-started/recruiters), hiring managers and interviewers to [Getting started for hiring managers](/getting-started/hiring-managers), your sourcing team to [Getting started for sourcing teams](/getting-started/sourcing-team), and whoever handles new-hire paperwork to [Getting started for onboarding teams](/getting-started/onboarding-team).
## Related
> [card] [Admin setup checklist](/getting-started/admin-setup-checklist)
>
> Everything to put in place before candidates flow.
> [card] [Workflows overview](/workflows/overview)
>
> Steps, activities, automation and versions.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Find the dashboard that answers your question.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What the scores behind your decisions mean.
# Use the Help Center with your AI assistant
Source: https://help.journeyfront.com/getting-started/use-docs-with-ai
Connect Claude, ChatGPT or another AI assistant to the Journeyfront Help Center so it answers how-to questions from the latest articles.
Your AI assistant can read this Help Center for you. Connect it once, then ask questions like "How do I move a candidate to another job req?" or "What's the difference between a hiring class and a job req?" and it answers from our articles, with links to the pages it used.
The Help Center updates the moment we publish a change, so a connected assistant always reads the current version. There's nothing to download or keep in sync.
## Connect the Help Center (recommended)
The Help Center has its own MCP (Model Context Protocol) server. Any assistant that supports MCP connectors can use it to search the Help Center and open the full text of the articles it needs.
```text Help Center connection URL theme={null}
https://help.journeyfront.com/mcp
```
No sign-in is needed, because the Help Center is public.
> [tab] Claude
>
> **1. Open Connectors**
>
> In Claude, go to **Settings**, then **Connectors**.
>
> **2. Add a custom connector**
>
> Click **Add custom connector**, name it **Journeyfront Help Center** and paste the connection URL.
>
> **3. Turn it on in a chat**
>
> In a new chat, make sure the connector is turned on, then ask your question.
>
> On a Claude Team or Enterprise plan, an owner can add the connector once for the whole organization.
> [tab] ChatGPT
>
> **1. Open custom connectors**
>
> In ChatGPT, open **Plugins** and click **+**. On some plans, custom connectors are under **Settings**, then **Connectors** (or **Apps**), and you turn on **Developer mode** first.
>
> **2. Add the Help Center**
>
> Choose to add a custom MCP server, name it **Journeyfront Help Center**, paste the connection URL and set authentication to **None**.
>
> **3. Use it in a chat**
>
> In a new chat, turn on the Help Center from the tools menu, then ask your question.
>
> Custom connectors depend on your ChatGPT plan, and on Business and Enterprise workspaces an admin may need to allow them.
> [tab] Claude Code
>
> Run this in your terminal:
>
> ```bash theme={null}
> claude mcp add --transport http journeyfront-help https://help.journeyfront.com/mcp
> ```
>
> Or paste this prompt into Claude Code, Cursor or another coding agent and let it do the setup:
>
> Connect your coding agent to the Journeyfront Help Center.
>
> Add the Journeyfront Help Center as an MCP server named journeyfront-help, using the HTTP transport and the URL [https://help.journeyfront.com/mcp](https://help.journeyfront.com/mcp). Then search it for "move a candidate to another job req" to confirm it works, and tell me which article you found.
> [tab] Other assistants
>
> In your assistant's settings, look for an option to add a custom connector, app or MCP server, and paste the connection URL. The exact steps depend on the assistant and your plan with that provider.
> [!TIP]
>
> Tell your assistant to check the Journeyfront Help Center when your question is about Journeyfront. Assistants use connectors more reliably when you ask them to.
You can also copy the connection URL from the menu next to any article's title: choose **Copy MCP Server** or **Copy MCP install command**.
## Prompts to try
Once you're connected, start with one of these. Each one asks the assistant to use the Help Center and show its sources.
Plan your first week as a recruiter.
Using the Journeyfront Help Center, walk me through what a recruiter should learn in their first week in Journeyfront, in order. Link each article you use.
Get a setup plan for a new account.
Using the Journeyfront Help Center admin setup checklist, make me a step-by-step setup plan for a new Journeyfront account, and note which steps are recommended before the first candidate applies.
Pick the right action for a candidate.
Using the Journeyfront Help Center, explain when I should move a candidate to another job req and when I should add them instead, and give me an example of each.
Turn an article into a team handout.
Using the Journeyfront Help Center, find the article about \[topic] and turn it into a one-page handout for my team, with the key steps and tips. Link the article at the bottom.
## Teach your agent what Journeyfront does
The Help Center also publishes a skill file, [`/skill.md`](https://help.journeyfront.com/skill.md), that summarizes what Journeyfront does, its key concepts and how its features fit together. Agents connected to the Help Center can read it automatically. To install it into a coding agent yourself:
```bash theme={null}
npx skills add https://help.journeyfront.com
```
## Other ways to give an assistant our docs
| Option | Best for | How |
| - | - | - |
| **One article** | Asking about a single page | On any article, open the menu next to the page title and choose **Copy page**, **Open in ChatGPT** or **Open in Claude**. You can also add `.md` to the end of any article's address for a plain-text version. |
| **Page index** | Tools that read `llms.txt` | [`/llms.txt`](https://help.journeyfront.com/llms.txt) lists every article with a one-line summary and a link to its plain-text version. |
| **The whole Help Center** | Loading everything into a project or knowledge base | [`/llms-full.txt`](https://help.journeyfront.com/llms-full.txt) has every article in one file. It's large, so a copy you upload goes out of date as articles change. |
## The Help Center vs. AI Connections
Connecting the Help Center and using [AI Connections](/getting-started/ai#ai-connections) are two different things, and many teams use both.
| | Help Center connection | AI Connections |
| - | - | - |
| **What the assistant reads** | Our public how-to articles | Your account's candidates and applications |
| **Answers questions like** | "How do I set up move reasons?" | "Which candidates applied to the Dallas job req this week?" |
| **Sign-in** | None | Each user signs in and approves access |
| **Needs** | Nothing | AI Connections turned on for your account, and the *Connect to MCP* permission |
## FAQ
> [accordion] Does the assistant see my Journeyfront data?
>
> Not through the Help Center connection. It only reads the public articles here. To let an assistant read your account's data, use [AI Connections](/getting-started/ai#ai-connections).
> [accordion] Will the assistant's answers stay up to date?
>
> Yes, when it's connected. It reads the live Help Center each time. A copy of `llms-full.txt` you uploaded somewhere stays as it was the day you uploaded it.
> [accordion] Is there a cost?
>
> No. The Help Center connection is free. Whether your assistant supports custom connectors depends on your plan with that provider.
> [accordion] Can candidates do the same with the Candidate Help Center?
>
> Yes. The Candidate Help Center has its own connection URL: `https://candidatehelp.journeyfront.com/mcp`.
> [accordion] The assistant gave an answer that doesn't match the Help Center. What should I do?
>
> Ask it which article it used and open that page to check. If the article itself is wrong or unclear, let your Customer Success Manager know so we can fix it.
## Related
> [card] [How Journeyfront uses AI](/getting-started/ai)
>
> AI features in Journeyfront and the guardrails around them.
> [card] [Glossary](/getting-started/glossary)
>
> The terms used across the Help Center.
# Create and manage classes
Source: https://help.journeyfront.com/hiring-classes/create
Create a hiring class, set its openings and dates, make it active, and keep it up to date.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team, or with the *All Job Req Access* permission. Setting up custom hiring class fields needs *Company Settings Access*.
A hiring class is one group of hires for a job req: a name, how many people you need, when they start and, optionally, the offer package they get. Create a class for each wave you're filling, make it active, and the job req's **Hiring Classes** tab tracks how close every class is to full. See the [Hiring classes overview](/hiring-classes/overview) for when to use them.
## Create a class
**1. Open the job req's Hiring Classes tab**
Open the job req and click the **Hiring Classes** tab.
**2. Click Create Class**
Click **Create Class** at the right of the toolbar. The **Create Hiring Class** window opens.
**3. Fill in the details**
Enter a **Class Name**, which is the only required field, and anything else you know now. See [Class details](#class-details).

**4. Click Create Class**
The class is created as a **Draft**.
**5. Make it active**
Click the class's **Draft** status and choose **Active**, or open the menu next to its name and click **Set To Active**. Candidates can only be added to active classes.

You can also create a class from **Classes** in the top navigation: click **Create Class** and choose the **Job Req** first.
> [!TIP]
>
> Name classes with the role and start month, like "Customer Care, March 2027". The name is what recruiters pick from when they assign candidates, so make it obvious which wave is which.
## Class details
| Field | What it's for |
| - | - |
| **Class Name** | The name everyone sees when assigning candidates and in reports. Required. |
| **Description** | Anything else your team should know, like the trainer or shift. |
| **Job Title** | The title for this class's hires. |
| **Number of Openings** | How many people you need. **Filled %** is hires divided by openings. |
| **Hiring Start Date** | When hiring started for this class. It's what **Days Given**, **Days to Fill** and **Days to Complete** are counted from. Leave it empty to use the date you created the class. |
| **Due Date** | When the class needs to be full. |
| **Candidate Start Date** | The class's first day of work. When you hire candidates in this class with **Hire**, it's filled in as their start date. |
| **External Reference ID** | The class's ID in another system, for integrations and exports. |
| **Location** | Where the class works or trains. |
| **Client Account** | The client this class is hiring for, if you hire on behalf of clients. |
| **Offer Package** | The [offer package](/offers/offer-packages) this class's offers start from. **Use the job's offer package** keeps the job req's own package. |
| **Custom Fields** | Your company's own hiring class fields, if you've set any up. See [Custom hiring class fields](#custom-hiring-class-fields). |
> [!NOTE]
>
> A class's **Offer Package** is only used when the job req's Offer activity allows it, with **Use the candidate's hiring class offer package** turned on in the workflow. See [Offer packages](/offers/offer-packages).
## Class statuses
| Status | What it means |
| - | - |
| **Draft** | Set up but not open yet. New classes start here. Candidates can't be added. |
| **Active** | Open for candidates. Only active classes appear when you assign candidates to a class. |
| **Complete** | Finished. No more candidates can be added, and the class counts toward **Completed Classes** and **Completed Class Fill Rate**. Candidates already in it stay. |
To change a status, click the status on the class's row and pick another one, or use **Set To Active**, **Set To Complete** or **Set To Draft** in the menu next to the class name.
## Edit or delete a class
Open the menu next to the class's name:
* **Edit** opens the **Edit Hiring Class** window with every field. Click **Update Class** to save.
* **Delete Class** deletes it, after you confirm. You can only delete a class with no candidates in it; remove or move its candidates first. Deleting can't be undone.
> [!TIP]
>
> Rather than deleting a finished class, set it to **Complete**. It keeps its history, and your fill rate and time-to-fill numbers stay accurate.
## The Hiring Classes tab
The tab shows the job req's classes, with summary tiles above the list:
| Tile | What it shows |
| - | - |
| **Total Hiring Classes** | Classes that match your current filters |
| **Active Classes** | Classes with **Active** status |
| **Completed Classes** | Classes marked **Complete** |
| **Completed Class Fill Rate** | Average share of openings filled across completed classes |
| **Avg. Days Given to Fill** | Average days from hiring start date to due date |
| **Avg. Days to Fill Class** | Average days from hiring start date to every opening being filled |
| **Avg. Class Size** | Average number of openings |
Each class's row shows its **Status**, **Created** date, **Hiring Start Date**, **Due Date**, **Days Given**, **Days Left**, **Candidates**, **Hired**, **Openings** and **Filled %**, and you can edit **Client Account** right in the list. Use **Edit Columns** to add more, like **Candidate Start Date**, **Date Filled**, **Days to Fill**, **Rejected**, **Offer Package** or your custom hiring class fields.
**Filters** and [saved views](/lists-and-exports/saved-views) work the same way as on the Candidates page, including sharing views with your team. To download the list, click **Actions**, then **Export Data**. **Classes** in the top navigation shows the same list for every job req at once, with a **Job Req** column.
## Custom hiring class fields
To track something every class needs, like a training room or a client's cost center, add a hiring class field: go to **Settings**, then **Custom Fields**, then **Hiring Class Fields**. Your active fields appear in the **Custom Fields** section of the create and edit windows, as columns and filters on the hiring classes list, and as merge keys for offer documents. See [Custom fields](/account-setup/custom-fields).
## FAQ
> [accordion] Why can't I add candidates to my new class?
>
> New classes start as **Draft**. Set the class to **Active**, and it appears when you assign candidates.
> [accordion] Why is Delete Class greyed out?
>
> The class still has candidates in it. Remove them, or move them to another class, first.
> [accordion] What's the difference between Hiring Start Date and Candidate Start Date?
>
> **Hiring Start Date** is when you started recruiting for the class, and drives the time-to-fill numbers. **Candidate Start Date** is the hires' first day of work, and is used as their start date when you hire them.
> [accordion] Does a class close itself when it's full?
>
> No. When hires reach the number of openings, the class records its **Date Filled**, but it stays **Active** until you set it to **Complete**.
> [accordion] Why can't I see some classes on the Classes page?
>
> Without the *All Hiring Class Access* permission, you see classes for the job reqs you're on. Ask your Journeyfront admin.
## Related
> [card] [Working with a class](/hiring-classes/working-with-a-class)
>
> Add candidates, message them and hire the class.
> [card] [Hiring classes overview](/hiring-classes/overview)
>
> When to use classes, and where to find them.
> [card] [Offer packages](/offers/offer-packages)
>
> Give each class its own offer terms.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Add your own hiring class fields.
# Hiring classes overview
Source: https://help.journeyfront.com/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.

> [!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](/workflows/overview)
>
> The path candidates follow on each job req.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
# Working with a class
Source: https://help.journeyfront.com/hiring-classes/working-with-a-class
Add candidates to a class, act on the whole class at once, hire them, and track how full it is.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team, or with the *All Job Req Access* permission, can add and remove candidates. Bulk actions like **E-mail**, **Message** and **Hire** need the same permissions as anywhere else.
>
> **Availability:** Each class's own page (opened by clicking the class name) needs to be turned on for your account. Ask your Customer Success Manager. Everything else on this page works on every account.
Once a class is [created and active](/hiring-classes/create), you fill it by putting candidates in it. From then on, the class keeps count: how many candidates are in it, how many you've hired and rejected, and how close you are to filling every opening. When the class is ready to start, you can hire everyone in it in one go.
## Add candidates to a class
Candidates can only be added to **Active** classes, and only to classes on their own job req. A candidate is in one class at a time on each Candidate Application.
### Several candidates at once
**1. Select the candidates**
On the job req's **Candidates** tab, tick the candidates. On the **Candidates** page, select candidates from a single job req.
**2. Click Assign Class**
Click **Assign Class** in the actions bar. The **Assign to Hiring Class** window lists the job req's active classes, with how many have been hired out of the openings.
**3. Pick the class**
Choose the **Hiring Class** and click **Assign Class**.

### One candidate
Open the Candidate Application, click the **Details** tab, and choose a class in the **Hiring Class** field of the **Application Details** card.
### Automatically
Add the **Set Hiring Class** action to an automation rule, for example to put every candidate who reaches the **Offer** step into the current class. See [Automation rules](/workflows/automation-rules).
### From the class's page
On the class's page, click **Add Candidate**, search by name or email, and click **Add** next to each candidate. Only candidates on the class's job req who aren't already in the class are listed. Click **Close** when you're done.

> [!TIP]
>
> Assign candidates to a class as soon as you know which wave they're headed for, not just at the offer stage. The class's counts then show you early whether you have enough people in the pipeline to fill it.
## Move or remove a candidate
* **Move to another class:** assign them to the new class in any of the ways above. They leave their old class, and both classes' counts update.
* **Remove from a class:** choose **No Hiring Class** in the **Assign to Hiring Class** window or the **Hiring Class** field. On the class's page, click the trash icon on the candidate's row, then **Remove**.
## The class's page
Click a class's name on the **Hiring Classes** tab, or on **Classes** in the top navigation, to open it.
The top of the page shows the class's name and status, its job title, and **Hiring Start Date**, **Created**, **Due Date**, **Offer Package**, **Candidates**, **Rejected**, **Hired**, **Openings** and **Filled %**, with a progress bar. The menu at the top right has **Edit**, the **Set To** status options and **Delete Class**.
Below, the **Candidates** list shows everyone in the class with their **Email**, **Assigned User**, **Applied For**, **Date Applied**, **Step**, **Activity Status**, **Status** and **Overall Score**. Use **Search candidates** to find someone. Hover over the icon next to a **Rejected** status to see when, by whom and why they were rejected.

## Act on the whole class
Tick candidates in the class's **Candidates** list, or the header box to select them all, and the actions bar offers **E-mail**, **Delete**, **Reject**, **Change Step**, **Hire**, **Assign User** and **Message**. They work just like they do on the **Candidates** page. See [Bulk actions](/candidates/bulk-actions).
> [!WARNING]
>
> **Delete** in the actions bar deletes the candidates' applications from the job req, not just from the class. To take someone out of the class, use the trash icon on their row, which asks **Remove candidate?** first.
* **Message the class:** use **E-mail** or **Message** to send everyone the same start-date details, with each candidate's own name filled in. See [Email candidates](/communication/email-candidates) and [Text messages](/communication/text-messages).
* **Move the class forward:** use **Change Step** to move everyone to the next step together. See [Move candidates through steps](/candidates/move-through-steps).
## Hire the class
When the class is ready to start, select the candidates and click **Hire**. You can hire up to 100 candidates in one run. Each hire's start date is filled in from the class's **Candidate Start Date**, so set it before you hire. See [Bulk hire](/onboarding/bulk-hire).
As candidates are hired, the class's **Hired** count and **Filled %** go up. When hires reach the number of openings, the class records its **Date Filled**. Set the class to **Complete** when you're done with it.
## Offers for a class
If the class has an **Offer Package**, and the job req's Offer activity allows it, offers for candidates in the class start from that package. That lets two classes on the same job req get different terms, like a different shift or pay rate. See [Offer packages](/offers/offer-packages).
## Track your classes
* **Fill progress:** **Candidates**, **Hired**, **Openings**, **Filled %** and **Days Left** on the **Hiring Classes** tab and each class's page.
* **Candidates by class:** on the **Candidates** page or a job req's **Candidates** tab, add the **Hiring Class** column with **Edit Columns**, or filter by **Hiring Class**.
* **In automation rules:** use the **Hiring Class** condition to act only on candidates in a certain class.
## FAQ
> [accordion] Why isn't my class in the list when I assign candidates?
>
> Only **Active** classes on the candidates' own job req are listed. Set a **Draft** class to **Active** first, or check that you selected candidates from the right job req.
> [accordion] Why don't I see Assign Class?
>
> On the **Candidates** page, your selection includes candidates from more than one job req. Select candidates from one job req only, or work from that job req's **Candidates** tab.
> [accordion] Can a candidate be in two classes?
>
> Not on the same Candidate Application. Assigning them to a new class takes them out of the old one.
> [accordion] Why can't I click the class name?
>
> The class's own page isn't turned on for your account. You can still assign candidates, change statuses and edit classes from the **Hiring Classes** tab. Ask your Customer Success Manager about the class page.
> [accordion] Does removing a candidate from a class change their application?
>
> No. They stay on the job req in the same step and status; they just aren't counted in the class any more.
## Related
> [card] [Create and manage classes](/hiring-classes/create)
>
> Set up a class's openings, dates and status.
> [card] [Bulk hire](/onboarding/bulk-hire)
>
> Hire a whole class at once.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Act on many candidates at once.
> [card] [Offer packages](/offers/offer-packages)
>
> Give a class its own offer terms.
# Welcome to the Journeyfront Help Center
Source: https://help.journeyfront.com/index
Everything you need to run high-volume hiring in Journeyfront, from your first login to reporting on your hires.
Journeyfront is an applicant tracking system (ATS) built for high-volume hiring. Assessments, interview scheduling, offers and analytics are built in, so your whole hiring process runs in one place. This Help Center covers what every feature does and how to set it up, with tips from our team along the way.
## Ask your AI assistant
Connect Claude, ChatGPT or any assistant that supports MCP to this Help Center, and it answers your Journeyfront questions from our latest articles, with links to the pages it used.
```text Help Center connection URL theme={null}
https://help.journeyfront.com/mcp
```
> [card] [Use the Help Center with your AI assistant](/getting-started/use-docs-with-ai)
>
> Setup steps for Claude, Claude Code and other assistants, plus prompts to try.
## Start here
> [card] [For TA leaders](/getting-started/ta-leaders)
>
> Own the hiring process: job reqs, workflows, automation and the dashboards that show what's working.
> [card] [For recruiters](/getting-started/recruiters)
>
> Your first day, and the pages and actions you'll use most.
> [card] [For hiring managers and interviewers](/getting-started/hiring-managers)
>
> Review candidates, run interviews and submit feedback.
> [card] [Admin setup checklist](/getting-started/admin-setup-checklist)
>
> Everything to set up before your team starts hiring.
## Working in Journeyfront
> [card] [Logging in and passwords](/getting-started/logging-in)
>
> Accept your invitation, sign in and reset your password.
> [card] [Saved views](/lists-and-exports/saved-views)
>
> Save the lists you use every day as tabs and share them with your team.
> [card] [Export data](/lists-and-exports/export-data)
>
> Download candidates, job reqs and hiring classes to CSV or Excel.
## Build your hiring process
> [card] [Job reqs](/job-reqs/overview)
>
> Create and manage the jobs you're hiring for.
> [card] [Workflows and automation](/workflows/overview)
>
> The steps and activities candidates move through, and the rules that move them.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Fill wave after wave of hires with the same start date.
## Attract candidates
> [card] [Source and attract candidates](/sourcing/job-boards)
>
> Job boards, invitations, magic links, lead ads and where candidates come from.
> [card] [Referrals](/referrals/overview)
>
> Reward programs, the referral portal and paying out rewards.
## Work with candidates
> [card] [Candidates and applications](/candidates/profiles-and-applications)
>
> Find, review, move and reject candidates, one at a time or in bulk.
> [card] [Email and texting](/communication/email-candidates)
>
> Email, text, WhatsApp and call candidates, and set up templates.
> [card] [Interviews and scheduling](/interviews/interview-activity)
>
> Self-scheduling, availability, interview guides and feedback.
## Evaluate candidates
> [card] [Assessments](/assessments/overview)
>
> Screening questions, typing, skills, language and system tests.
> [card] [Scoring](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and AI scoring.
> [card] [Predictive models](/scoring/predictive-models)
>
> Score candidates on what predicts success in your roles.
## Offer and hire
> [card] [Offers](/offers/overview)
>
> Offer templates, packages, e-signatures and sending offers.
> [card] [Hiring and onboarding](/onboarding/hire-candidates)
>
> Hire candidates, onboarding forms and background checks.
## Employees
> [card] [Employee records](/employees/employee-records)
>
> Find your employees, keep their job details current and record when someone leaves.
> [card] [Job profiles](/employees/job-profiles)
>
> Group employees by role and see which parts of your hiring predict success in it.
> [card] [Performance reviews](/employees/performance-reviews)
>
> Have managers score how employees are doing, so hiring data connects to real performance.
## Reporting and analytics
> [card] [Dashboards](/reporting/dashboards)
>
> Company and job req dashboards for applicants, funnels, sources and more.
> [card] [Turnover and performance](/reporting/turnover-and-performance)
>
> Connect hiring data to how long people stay and how they perform.
> [card] [EEOC reporting](/reporting/eeoc)
>
> Ask the voluntary self-identification questions and report on your applicant pool.
## Administer
> [card] [Account setup](/account-setup/company-details)
>
> Company details, users, security roles, custom fields and imports.
> [card] [Integrations](/integrations/overview)
>
> Connect your HR system, job boards, calendars, texting and more.
> [!TIP]
>
> Can't find what you need? Use search at the top of any page, [ask your AI assistant](/getting-started/use-docs-with-ai), or contact your Customer Success Manager.
# ATS integrations
Source: https://help.journeyfront.com/integrations/ats
Use Journeyfront alongside another applicant tracking system: send candidates to it in one click, or launch Journeyfront assessments from it.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect an ATS. Once it's connected, anyone who can open a Candidate Application can send that candidate to your ATS.
Some teams use Journeyfront for screening and assessments while another applicant tracking system (ATS) stays their system of record. Journeyfront connects to many ATSs, including Greenhouse, Lever, Ashby, Workday, iCIMS, SmartRecruiters and Teamtailor, through one standard integration, so the setup is the same whichever one you use.
There are two ways to connect, and you can use either or both:
| | **Send to ATS** | **ATS-launched assessments** |
| - | - | - |
| Where it starts | In Journeyfront | In your ATS |
| What happens | A recruiter pushes a candidate from Journeyfront into your ATS | A recruiter orders a Journeyfront assessment from your ATS, and the results flow back |
| Integrations section | **ATS** | **ATS Assessment** |
## Connect your ATS
Before you start, have your ATS sign-in details ready. Depending on the ATS, you may also need an API key, subdomain or client secret. The account you connect with needs permission to create candidates and applications and to read jobs.
**1. Find your ATS**
Go to **Settings**, then **Integrations**. Find your ATS under **ATS** to send candidates, or under **ATS Assessment** to launch assessments from your ATS. Use **Filter** or **Search** to find it quickly.

**2. Start the connection**
Click your ATS's tile, then click **Connect to** followed by its name.
**3. Review permissions**
A secure window lists the data Journeyfront needs. Required permissions must stay on for the integration to work. You can turn optional ones off.
**4. Sign in and confirm**
Follow the steps for your ATS, such as signing in or entering an API key or subdomain. When it's done, the tile shows **Active** and the details show who connected it and when.
## Send a candidate to your ATS
Once your ATS is connected, everyone in your account can send candidates to it from the Candidate Application.
**1. Open the Actions menu**
On the Candidate Application, click **Actions**, then **Send to** followed by your ATS's name.

**2. Check the pre-filled details**
The window shows what Journeyfront mapped from the Candidate Application, such as name, email and phone. Check that it's correct.
**3. Choose the job and stage**
Select the job and pipeline stage in your ATS where the candidate should land, and fill in any required fields. Required fields are marked with a red asterisk (\*).

**4. Attach documents and send**
Choose any documents to include, such as the resume, signed offer letter or screening uploads, if your ATS accepts them. Then click **Send**.
When the send succeeds:
* A new candidate and application are created in your ATS.
* A note is added to the ATS application with a link back to the candidate's Candidate Application in Journeyfront, so anyone in your ATS can see their results.
* **Comments & Activities** in Journeyfront records who sent the candidate and where.
* The menu item changes to **Sent to** your ATS with a check mark, so you can see at a glance that the candidate is already there.
> [!TIP]
>
> Double-check the job you pick in your ATS, especially when several open jobs have similar titles. The candidate lands wherever you send them, and the integration doesn't move them afterward.
## Launch Journeyfront assessments from your ATS
With an **ATS Assessment** connection, your recruiters stay in your ATS and order a Journeyfront assessment there, the same way they'd order any other assessment.
1. **Your job reqs become assessments in your ATS.** Each Journeyfront job req shows up as an assessment your ATS can order. New job reqs are added automatically.
2. **A recruiter orders the assessment in your ATS.** Journeyfront creates the candidate and their Candidate Application, and emails the candidate an invitation with a link to start. Some ATSs show the link directly instead.
3. **The candidate completes their Journeyfront workflow.** They go through the job req's steps, just like a candidate who applied in Journeyfront.
4. **Results go back to your ATS.** When the candidate finishes, Journeyfront sends their overall score, their attribute scores and a link to their Candidate Application to your ATS.
The invitation uses the **Invitation Applicant** email template. To change its wording, go to **Settings**, then **Templates**, then **E-mail Template**.
> [!TIP]
>
> Candidates ordered from your ATS complete the job req's workflow, so any change you make to that workflow applies to them too. Check the job req's steps before your recruiters start ordering it.
## What the integration doesn't do
* **It doesn't sync changes back from your ATS.** If someone updates a candidate's phone number in your ATS, Journeyfront doesn't see the change.
* **It doesn't update candidates you already sent.** Each send creates a new candidate and application in your ATS.
* **It doesn't sync job reqs or postings**, other than offering your job reqs as assessments with an ATS Assessment connection.
* **It doesn't follow candidates through your ATS pipeline.** Once sent, their progress there isn't reflected in Journeyfront.
* **It doesn't retry failed sends.** Fix the problem and send again.
## FAQ
> [accordion] Which ATSs are supported?
>
> Every supported ATS is listed on the **Integrations** page, including Greenhouse, Lever, Ashby, Workday, iCIMS, SmartRecruiters, Teamtailor and many more. If yours isn't listed, ask your Customer Success Manager.
> [accordion] Can I connect more than one ATS?
>
> No. Each Journeyfront account connects to one ATS at a time. To switch, disconnect the current one first.
> [accordion] What if my ATS requires a field Journeyfront doesn't have?
>
> The send window shows every field your ATS requires. Fill in anything Journeyfront doesn't have before you click **Send**. If a required field is always hard to fill in, your ATS administrator may be able to make it optional on the ATS side.
> [accordion] What happens if a send fails?
>
> You'll see an error explaining why, usually a missing required field or a connection problem. Fix it and try again. A failed attempt doesn't create a partial record in your ATS.
> [accordion] Can I disconnect the integration?
>
> Yes. Admins can disconnect it from the ATS's page in **Settings**, then **Integrations**. Candidates you already sent stay in your ATS. Disconnecting can't be undone; to use the integration again, you connect from the start.
> [accordion] How is this different from exporting a CSV?
>
> The integration creates live candidate records in your ATS through a secure connection. There's no file to download, format or upload.
## Related
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
> [card] [HRIS integrations](/integrations/hris)
>
> Send new hires to your HR system.
> [card] [Workflows overview](/workflows/overview)
>
> The steps candidates complete.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What the scores sent to your ATS mean.
# Background check integrations
Source: https://help.journeyfront.com/integrations/background-checks
Connect a background check provider so your team can order and track checks from Journeyfront.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect a background check provider.
>
> **Availability:** You need your own account with the provider, which bills you directly for each check. Journeyfront doesn't add a fee.
A background check integration lets your team order checks without leaving Journeyfront. The provider handles the candidate's invitation, consent and report, and the status flows back into the Candidate Application automatically. Full reports stay with the provider, which remains your system of record for results and adjudication.
To add background checks to a workflow and order them, see [Background checks](/onboarding/background-checks).
## Available integrations
> [card] [Checkr](/integrations/background-checks/checkr)
>
> Connect your Checkr account to order checks from the Candidate Application, with packages and billing managed in Checkr.
## What every background check integration has in common
* **Ordering happens in Journeyfront.** Your team adds the background check activity to a job req's workflow and orders a check from the Candidate Application.
* **Status comes back automatically.** Everyone who can open a Candidate Application sees the check's current status.
* **Reports stay with the provider.** Journeyfront stores the check's status and order details, not the full report.
* **Journeyfront doesn't decide.** It doesn't make eligibility or hiring decisions, and it doesn't replace your provider's compliance and adjudication tools.
## FAQ
> [accordion] Does Journeyfront charge for background checks?
>
> No. Your provider charges per check and bills you directly. Journeyfront doesn't add a fee for the integration.
> [accordion] Can I use a background check provider other than Checkr?
>
> Checkr is the background check provider Journeyfront connects to today. If you use a different provider, talk to your Customer Success Manager.
## Related
> [card] [Background checks](/onboarding/background-checks)
>
> Add the activity to a workflow and order checks.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
# Checkr
Source: https://help.journeyfront.com/integrations/background-checks/checkr
Connect your Checkr account so your team can order and track background checks from Journeyfront.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect and disconnect Checkr.
>
> **Availability:** You need your own Checkr account. Checkr bills you directly for each check; Journeyfront doesn't add a fee.
With Checkr connected, your team orders background checks without leaving Journeyfront. Checkr handles the candidate's invitation, consent and report, and the status flows back into the Candidate Application automatically. Full reports stay in Checkr, which remains your system of record for results and adjudication.
This page covers connecting Checkr. To add background checks to a workflow and order them, see [Background checks](/onboarding/background-checks).
## How it works
1. An admin connects your Checkr account to Journeyfront.
2. You set up your packages, billing and compliance settings in Checkr.
3. Your team adds the **Checkr Background Check** activity to a job req's workflow.
4. A recruiter orders a check from the Candidate Application, and Checkr invites the candidate.
5. Checkr processes the report, and Journeyfront shows the current status, with Checkr's report summary for people who have access in Checkr.
## Connect Checkr
**1. Open Checkr**
Go to **Settings**, then **Integrations**, and open **Checkr** under **Background Check**.
**2. Connect your account**
Click **Connect to Checkr**.

**3. Sign in to Checkr**
Sign in to your Checkr account, or create one if you don't have one yet, and approve the connection.

**4. Wait for Activated**
On the **Integrations** page, the Checkr tile shows **Pending** while Checkr finishes setting up your account, then **Activated**. You can order checks once it's activated.
## Set up Checkr
After you connect, sign in to Checkr directly to finish your setup there:
* **Packages:** the background check packages your team can choose from when ordering.
* **Billing:** how Checkr charges you.
* **Compliance and adjudication:** your rules for reviewing results and any adverse action process.
Journeyfront shows whatever packages you set up in Checkr, so there's nothing else to configure in Journeyfront.
> [!TIP]
>
> Set up your packages in Checkr before your team starts ordering. Recruiters pick a package each time they order, so clear package names save them from guessing.
## Who can see reports
Everyone who can open a Candidate Application can see a background check's status. To open the report details, a user also needs access in your Checkr account. People without Checkr access see the status only.
## What's shared with Checkr
* Journeyfront sends Checkr only what it needs to start a check: the candidate's email address and phone number, which fill in Checkr's order window.
* Full reports and sensitive details stay in Checkr. Journeyfront stores the check's status and order details, such as the package.
* Journeyfront doesn't make eligibility or hiring decisions, and it doesn't replace Checkr's compliance and adjudication tools.
## Disconnect Checkr
Go to **Settings**, then **Integrations**, open **Checkr** and click **Disconnect Checkr**. While Checkr finishes, the status may briefly show **Disconnecting**. Reports already in Checkr stay in your Checkr account.
## FAQ
> [accordion] Do I need my own Checkr account?
>
> Yes. If you don't have one, you can create it while you connect.
> [accordion] Does Journeyfront charge for Checkr background checks?
>
> No. Checkr charges per check and bills you directly. Journeyfront doesn't add a fee for the integration.
> [accordion] Where do I change packages or pricing?
>
> In your Checkr account. Journeyfront shows the packages you set up there.
## Related
> [card] [Background checks](/onboarding/background-checks)
>
> Add the activity to a workflow and order checks.
> [card] [Background check integrations](/integrations/background-checks)
>
> How background check integrations work.
# Calendars and video
Source: https://help.journeyfront.com/integrations/calendars
Which calendars and video services work with interview scheduling, and how each interviewer connects theirs.
> [!NOTE]
>
> **Who can do this:** Each interviewer connects their own calendar and video service under **Interviews**, then **My Profile**. There's no company-wide setup for an admin to do.
Interview scheduling works with the calendars and video tools your team already uses. Once an interviewer connects their calendar, Journeyfront offers candidates only the times they're really free, and every booked interview lands on their calendar with the video link already in it. No copying times between systems, and no double bookings.
## Supported calendars
You can connect a calendar from:
* Google
* iCloud
* Office 365
* Exchange
* Outlook.com
You can connect more than one calendar, for example a work and a personal calendar, so that busy time on either one keeps candidates out. You then choose one **Preferred Calendar** for interviews to be added to.
## Supported video services
| Service | How to set it up |
| - | - |
| **Zoom** | Click **Add Conferencing Service**, sign in to Zoom and allow access. |
| **Microsoft Teams** | Click **Add Conferencing Service**, sign in to Microsoft and allow access. |
| **GoToMeeting** | Click **Add Conferencing Service**, sign in to GoTo and allow access. |
| **Google Meet** | Offered automatically once you've connected a Google calendar. |
| **No Video Conferencing** | No video link is created for your interviews. |
Each interviewer picks their default under **Conferencing** in **My Profile**. An interview activity can use each interviewer's default (**Interviewer's Default**) or one **Custom Link** for everyone, and interviews can also be by **Phone** or **In-person**. See [Set up an interview activity](/interviews/interview-activity).
## What the connection does
* **Finds open times.** Journeyfront checks when you're busy on your connected calendars and offers candidates only the times you're free and inside your hours in **My Availability**.
* **Adds interviews to your calendar.** Booked interviews are created on your **Preferred Calendar**, with the video link from your conferencing service, and a link to the interview guide when the interview activity turns that on.
* **Lets you keep some events open.** Add the **Ignore Event Keyword** from **My Availability** to an event's description, and that time counts as free for interviews.
## Connect your calendar and video service
**1. Open My Profile**
Click **Interviews** at the top of the app, then **My Profile**.
**2. Connect a calendar**
Under **Synced Calendar**, choose your provider, sign in and allow access. Repeat for any other calendar you want counted.
**3. Pick your Preferred Calendar and Time Zone**
Choose where interviews should be added, and the time zone you work in.
**4. Choose your video service**
Under **Conferencing**, pick your default. Click **Add Conferencing Service** first if it isn't listed.
**5. Set your hours**
Go to **My Availability** and mark when you can interview. See [Your availability and calendar](/interviews/availability).

### Change or reconnect
* **Switch calendars:** in **Synced Calendar**, use **Edit Accounts** to remove the connected account, then connect the new one. Check your **Preferred Calendar** afterward.
* **Reconnect a video service:** if a service in the **Conferencing** list shows **Re-connect**, click it and sign in again.
> [!TIP]
>
> When someone leaves your team or changes roles, have them disconnect their calendar, and remove them from the interviewer pools of your interview activities so candidates aren't offered their times.
## For admins and recruiters: get interviewers connected
You can't connect a calendar for someone else, but you can see who still needs to and nudge them. When you add interviewers to an interview activity, anyone who hasn't synced their calendar is flagged, with an **Invite to Sync Calendar** button that emails them a request to connect. The button then shows **Invited**.
An interview activity needs at least one interviewer with a connected calendar before its settings can be saved, unless it's set to use the candidate's **Assigned User**.
## FAQ
> [accordion] Can Journeyfront see the details of my meetings?
>
> Journeyfront uses your calendar to know when you're busy and to add interviews to it. Candidates never see your events, only the open times they can book.
> [accordion] Why isn't Google Meet in my Conferencing list?
>
> Google Meet only appears after you've connected a Google calendar. Connect it under **Synced Calendar**, then pick Google Meet under **Conferencing**.
> [accordion] Do candidates need a calendar or video account?
>
> No. Candidates book from a link without signing in, and join with the link in their confirmation email and calendar invite.
> [accordion] An interviewer's open times look wrong. What should I check?
>
> Ask them to check that their calendar still shows under **Synced Calendar**, that their **Time Zone** is right, and that their **My Availability** hours are saved. See [Your availability and calendar](/interviews/availability#faq).
> [accordion] Can one interview use a shared meeting room link instead of each interviewer's video service?
>
> Yes. On the interview activity, set **Video Link** to **Custom Link** and enter the link. See [Set up an interview activity](/interviews/interview-activity).
## Related
> [card] [Your availability and calendar](/interviews/availability)
>
> My Profile and My Availability, step by step.
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interviewers, format and video link for an interview.
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> How candidates book from your open times.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
# Calling
Source: https://help.journeyfront.com/integrations/calling
Connect Webex Contact Center or QUO so your team can call candidates and have every call logged automatically.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect your company. Each recruiter then connects their own account in **Personal Settings**.
>
> **Availability:** Needs your company's own Webex Contact Center or QUO account. Calls are billed by your calling provider.
A calling integration lets recruiters call candidates from the Candidate Application and have each call written to the candidate's record automatically: who called, when, how long they spoke and, depending on your provider, the outcome, the recording and a transcript. Calls a candidate makes back to you are logged too.
Without a calling integration, candidate phone numbers are still clickable and open your computer's default calling app, but those calls aren't logged. For how recruiters place calls day to day, see [Calling candidates](/communication/calling).
## Available integrations
> [card] [Webex Contact Center](/integrations/calling/webex-contact-center)
>
> Pick this if your recruiters work as Webex Contact Center agents. Calls go through their own agent lines, with outcomes and recordings logged.
> [card] [QUO](/integrations/calling/quo)
>
> Pick this if your team calls from QUO (formerly OpenPhone). Calls are logged with QUO's summary, transcript and recording.
## Compare providers
| | Webex Contact Center | QUO (formerly OpenPhone) |
| - | - | - |
| **How recruiters dial** | Click the phone icon. Webex rings the recruiter's Agent Desktop first, then dials the candidate. | Click the phone icon or the number to open your default calling app, or dial in the QUO app as usual. |
| **What's logged** | Numbers, duration, ring time, the outcome the recruiter picks, the Webex wrap-up code and the recording | Numbers, duration, QUO's call summary, the transcript and the recording |
| **Transcripts** | No. Journeyfront doesn't get transcripts from Webex. | Yes |
| **Calls from candidates** | Logged when an agent answers on your inbound entry point | Logged when a candidate calls the QUO number of a recruiter who has connected QUO |
| **Company setup** | A Webex Control Hub administrator authorizes Journeyfront | Paste a QUO API key |
| **Recruiter setup** | Each recruiter signs in with their Webex agent account | One click: matched by email |
## How the phone icon picks a provider
You can connect both Webex Contact Center and QUO. For each recruiter, the phone icon next to a candidate's number works like this:
| The recruiter has connected | What the phone icon does |
| - | - |
| **Webex Contact Center** | Shows **Call via Webex** and places the call through Webex. If they've also connected QUO, Webex is used. |
| **QUO** only | Shows **Call via QUO** and opens your computer's default calling app. It opens QUO only if QUO is your default calling app. |
| Neither | Shows **Call** and opens your computer's default calling app. The call isn't logged. |
Both providers only log calls with phone numbers that match a candidate in your account. Recruiters' personal and internal calls are discarded and never logged in Journeyfront.
## FAQ
> [accordion] Do we need a calling integration to call candidates?
>
> No. Candidate phone numbers are clickable and open your default calling app. A calling integration adds automatic call logging, outcomes and recordings on the candidate's record.
> [accordion] Can we connect both Webex Contact Center and QUO?
>
> Yes. For a recruiter connected to both, the phone icon uses Webex Contact Center.
> [accordion] Who pays for calls?
>
> Your calling provider bills you. Calls go through your own Webex Contact Center or QUO account.
> [accordion] Are personal calls logged in Journeyfront?
>
> No. Only calls with a phone number that matches a candidate in your account are logged. Other calls are discarded.
## Related
> [card] [Calling candidates](/communication/calling)
>
> Call candidates and find every call log.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
> [card] [Texting providers](/integrations/texting-providers)
>
> Set up text messaging and WhatsApp.
> [card] [Text messages](/communication/text-messages)
>
> Message candidates by SMS or WhatsApp.
# QUO
Source: https://help.journeyfront.com/integrations/calling/quo
Connect QUO (formerly OpenPhone) so calls with candidates are logged automatically, with summaries, transcripts and recordings.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect your QUO workspace. Each recruiter then connects their own QUO user in **Personal Settings**.
>
> **Availability:** Needs your company's own QUO workspace. Calls are billed by QUO.
With QUO (formerly OpenPhone), recruiters keep dialing in the QUO app as usual. When a call with a candidate ends, Journeyfront logs it on the candidate with its numbers, duration, QUO's call summary, the transcript and the recording. Calls a candidate makes to one of your QUO numbers are logged too.
For how calling providers compare, see [Calling](/integrations/calling). For how recruiters place calls day to day, see [Calling candidates](/communication/calling).
You'll need:
* A QUO workspace and a **QUO API key**, created in QUO under your workspace settings
* Each recruiter set up as a user on one of your company's QUO phone numbers, with the same email address they use in Journeyfront
## Connect your QUO workspace
**1. Open QUO**
Go to **Settings**, then **Integrations**. Under **Calling**, select **QUO**.
**2. Paste your API key**
Paste your key into **QUO API key**.
**3. Save**
Click **Save**. Journeyfront checks the key with QUO, finds your phone numbers and sets up call logging automatically. The status changes to **Active**.

The key is stored securely and never shown again. Saving a new key replaces the connection. To stop logging QUO calls, click **Remove**; logging stops immediately.
## Each recruiter connects QUO
**1. Open your integrations**
Select your name in the top right, then **Personal Settings**, then **Integrations**. Click **QUO**.
**2. Connect**
Click **Connect QUO**. Journeyfront matches you to your QUO user by your email address.
**3. Check your numbers**
Your connection shows your **Email**, your **QUO numbers** and when you connected.
> [!TIP]
>
> If you see "No QUO user with your email was found on your company's QUO phone numbers," make sure your QUO user has the same email as your Journeyfront login and is assigned to at least one of your company's QUO numbers. Then try again.
Calls are logged only for recruiters who have connected QUO, and that includes calls from candidates: a candidate's call to a recruiter's QUO number is logged only if that recruiter has connected.
## How dialing works with QUO
The phone icon next to a candidate's number opens your computer's default calling app. It opens QUO only if QUO is set as your default calling app. You can also dial from the QUO app directly; the call is still logged.
After a call with a candidate is logged, Journeyfront adds the candidate to your QUO workspace as a contact, with just their name and the number dialed. That way, when the candidate calls back, your QUO app shows who's calling. Journeyfront never changes existing QUO contacts.
## QUO troubleshooting
| What you see | What to try |
| - | - |
| "QUO is not configured for your company yet." | An admin needs to add the QUO API key in **Settings**, then **Integrations**, then **QUO**. |
| A call isn't logged | Check that the recruiter has connected QUO in **Personal Settings**, and that the candidate's phone number in Journeyfront matches the number called. |
| The phone icon doesn't open QUO | Make sure QUO is your computer's default calling app. You can also dial from the QUO app directly; the call is still logged. |
## FAQ
> [accordion] Do recruiters have to dial from Journeyfront for calls to be logged?
>
> No. Calls dialed straight from the QUO app are logged too, as long as the recruiter has connected QUO and the number matches a candidate.
> [accordion] Does Journeyfront update our existing QUO contacts?
>
> No. After a logged call, it adds a contact with the candidate's name and the number dialed. It never changes contacts that are already in QUO.
## Related
> [card] [Calling](/integrations/calling)
>
> Compare calling providers.
> [card] [Calling candidates](/communication/calling)
>
> Call candidates and find every call log.
# Webex Contact Center
Source: https://help.journeyfront.com/integrations/calling/webex-contact-center
Call candidates through your own Webex Contact Center agent lines and log every call automatically.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect your Webex organization, with a Webex Control Hub administrator. Each recruiter then connects their own Webex account in **Personal Settings**.
>
> **Availability:** Needs your company's own Webex Contact Center subscription. Calls are part of your Webex service.
With Webex Contact Center, recruiters call through their own Webex agent line, so your existing telephony, caller IDs and Webex reporting keep working as they always have. Journeyfront adds the candidate's history on top: each call's numbers, duration, ring time, the outcome the recruiter picks, the Webex wrap-up code and the recording.
For how calling providers compare, see [Calling](/integrations/calling). For how recruiters place calls day to day, see [Calling candidates](/communication/calling).
You'll need:
* An active **Webex Contact Center** subscription, with your recruiters set up as Contact Center agents
* A **Webex Control Hub administrator** to authorize Journeyfront once for your organization
* Each recruiter who makes calls to connect their own Webex account
## Set up Webex first
Calling depends on how each recruiter is set up in Webex Control Hub. These settings live in Webex, not Journeyfront, and every one is required for a call to connect. If a call rings briefly and then ends, this list is almost always why.
For each recruiter who will make calls:
1. They're set up as a **Contact Center agent**, with an agent profile, a team and a multimedia profile. A Webex organization administrator isn't automatically an agent.
2. On their **Desktop Profile**, on the **Voice** tab: outdial is enabled, an Address Book is selected, an Outdial ANI is selected and a dial plan is attached.
3. Under **Channels**, a phone number is mapped to your inbound entry point.
4. Your **Outdial ANI** is configured, including a default.
5. On your **outdial queue**, the recruiter's team is added to a call distribution group. Without this, calls route to a queue with no agents and end after a few seconds.
6. The recruiter signs in to the **Webex Agent Desktop**, sets themselves to **Available** and chooses **Desktop** as their station.


To log calls from candidates, your inbound entry point also needs to route calls to an agent. Calls from candidates are logged when an agent answers on your inbound entry point.
## Connect your Webex organization
An administrator does this once for your company.
**1. Open Webex Contact Center**
Go to **Settings**, then **Integrations**. Under **Calling**, select **Webex Contact Center**.

**2. Set your region (if needed)**
If your Webex organization is outside the US1 region, expand **Is your Webex tenant outside the US1 region?** and enter your region's **API region base URL**. Leave it blank for US1.
**3. Connect as administrator**
Click **Connect as administrator**. Sign in with a **Webex Control Hub administrator** account and approve the access Journeyfront asks for. An ordinary agent account can't grant it.
**4. Check the connection**
The page shows who authorized the connection and what it turned on.

> [!WARNING]
>
> This step is required. Webex only lets an administrator read call results, so without it calls can be placed but their outcome, duration and recording can't be logged, and calls from candidates aren't logged at all.
The page's second step, **Set a fallback outdial entry point**, is optional. Each recruiter's entry point is read from their own Webex profile, so teams in different regions keep their own numbers with nothing to set up in Journeyfront. The fallback is only used for recruiters whose profile can't be read.
## Each recruiter connects their Webex account
Every recruiter who makes calls does this for themselves.
**1. Open your integrations**
Select your name in the top right, then **Personal Settings**, then **Integrations**. Click **Webex Contact Center**.
**2. Connect**
Click **Connect Webex** and sign in with the Webex account you use for the **Agent Desktop**. Approve the access.
**3. Check Outbound calling**
Your connection shows your Webex account and an **Outbound calling** line.

| Outbound calling | What it means |
| - | - |
| **Ready** | Webex will let this account place calls. |
| **Not available** | This Webex account isn't a Contact Center agent. Usually an administrator account was connected instead of the agent account used for the Agent Desktop. Disconnect and reconnect with the right one. |
| **Turned off in Webex** | The account is an agent, but its Webex desktop profile can't dial out: outdial is switched off, or the profile has no outdial entry point. The message names the profile for your Webex administrator to update. |
> [!TIP]
>
> Expect the first recruiter to connect the wrong Webex account. Many people have both an administrator login and an agent login, and only the agent login can place calls. The **Outbound calling** line tells you right away.
If your organization isn't connected yet, the **Outbound calling** line doesn't appear.
## What Webex controls
Some parts of calling live in Webex rather than Journeyfront:
| Managed by Webex | What it means for you |
| - | - |
| **Whether calls are recorded** | Recording is a Webex setting. It can be turned on for the organization even when a queue's own recording setting is off, so check both. |
| **The number candidates see** | Your caller ID comes from the Outdial ANI on the recruiter's Webex profile. Journeyfront shows which number was used but doesn't choose it. |
| **Call charges** | Calls are placed in your own Webex Contact Center, so they're part of your Webex service. |
| **Transcripts** | Journeyfront doesn't get transcripts from Webex, so Webex recordings are audio only. |
| **Whether a call can be placed** | Agent setup, queues and dial plans are all Webex settings. |
## Disconnect Webex
* **A recruiter's own account:** in **Personal Settings**, then **Integrations**, then **Webex Contact Center**, click **Disconnect**. Calls already logged stay on their candidates. Until they reconnect, that recruiter's phone icon opens their computer's default calling app instead, and those calls aren't logged.
* **Your organization:** in **Settings**, then **Integrations**, then **Webex Contact Center**, click **Disconnect** in step 1. Call results, recordings and logging of calls from candidates stop, and recordings of calls already logged can no longer be played. Calls already logged stay on their candidates.
## Webex troubleshooting
| What you see | What to try |
| - | - |
| A call rings for a few seconds and then ends | This is Webex setup. Check, in order: the recruiter's team is in a call distribution group on your outdial queue; their station is **Desktop**, not Extension; they're **Available** in the Agent Desktop; your Outdial ANI has a default. |
| "This Webex account is not an agent in your company's Contact Center." | The wrong Webex account was connected, usually an administrator account. Disconnect in **Personal Settings** and reconnect with the Agent Desktop account. |
| "Outbound dialing is turned off for your Webex desktop profile." | Your Webex administrator needs to turn on outdial for the profile named in the message. |
| Clicking call does nothing | Sign in to the Webex Agent Desktop and set yourself to **Available**. Webex rings you first, so the call can't start if the Agent Desktop is closed. |
| A call is logged but has no recording | Check that call recording is on in Webex, at both the organization and queue level. |
| Calls from candidates aren't logged | Check that your inbound entry point routes calls to an agent, and that the caller's number matches a candidate in your account. |
## FAQ
> [accordion] Why does an administrator need to connect Webex if each recruiter connects too?
>
> Webex only lets an administrator read the result of a call. Without the organization connection, calls can be placed but their outcome, duration and recording can't be logged, and calls from candidates aren't logged at all.
> [accordion] Do we need a separate setup for each country or region?
>
> Not in Journeyfront. With Webex, each recruiter dials through the entry point on their own Webex profile, so your existing regional setup applies.
> [accordion] Does this replace our Webex reporting?
>
> No. Calls are ordinary calls placed by your own agents, so they show up in your Webex reporting as they always have.
> [accordion] Is Webex Contact Center the same as Webex Connect?
>
> No. Webex Contact Center is for calling. Webex Connect is Cisco's messaging platform, used for texts and WhatsApp. See [Webex Connect](/integrations/texting-providers/webex-connect).
## Related
> [card] [Calling](/integrations/calling)
>
> Compare calling providers.
> [card] [Calling candidates](/communication/calling)
>
> Call candidates and find every call log.
# E-signature setup and credits
Source: https://help.journeyfront.com/integrations/e-signature
How e-signature is set up for your account, and how it uses credits.
> [!NOTE]
>
> **Who can do this:** Journeyfront sets up e-signature for your account. Admins with the *Company Settings Access* permission can see your e-signature credits.
>
> **Availability:** E-signature is an add-on that uses e-signature credits. To turn it on or buy more credits, ask your Customer Success Manager.
E-signature lets candidates sign their offer letter and supporting documents online, from any device, without leaving your hiring process. Unlike most integrations, there's nothing for you to connect: Journeyfront sets it up for your account, and you start sending offers for signature right away.
## How it's set up
* **No connection screen.** E-signature doesn't appear under **Settings**, then **Integrations**. There are no accounts to link and no keys to enter.
* **Turned on by Journeyfront.** When your account has the E-Signatures add-on, the e-signature options appear when you send an offer. Your Customer Success Manager turns it on and adds your credits.
* **Ready for your templates.** Once it's on, any offer letter or document template with signature fields can be signed. See [Offer letter and document templates](/offers/templates).
## Credits
Each signature request uses one e-signature credit. An offer letter and all of its supporting documents go to the candidate as one envelope, so one offer uses one credit, however many documents it has.
To see your balance, go to **Settings**, then **Add-Ons**, then **E-Signatures**. It shows what you've purchased, used and have left, with the full transaction history. See [Add-ons and credits](/account-setup/add-ons).

When you run out of credits, you can't send new signature requests until more are added. You can still create offers, generate the documents and record the candidate's answer yourself.
> [!TIP]
>
> Check your e-signature balance before a big hiring class goes to offer. When you send offers in bulk, Journeyfront warns you if you have fewer credits than candidates, but topping up goes through your Customer Success Manager.
## Sending offers for signature
Everything about sending, tracking and reminding signers is covered in the Offers section:
* [E-signatures](/offers/e-signatures): signing options, signer statuses, reminders and what candidates see.
* [Send an offer](/offers/send-offers): one candidate's offer, from terms to signature.
* [Send offers in bulk](/offers/bulk-send): a whole group at once.
## FAQ
> [accordion] How do I connect our e-signature account?
>
> You don't need to. Journeyfront provides e-signature as an add-on and sets it up for you. Ask your Customer Success Manager to turn it on.
> [accordion] Why don't I see e-signature options when I send an offer?
>
> Your account doesn't have the E-Signatures add-on, or it has no credits left. Check **Settings**, then **Add-Ons**, or ask your Customer Success Manager.
> [accordion] Can I use offers without e-signature?
>
> Yes. Generate or upload the documents, share them however you like, and record the candidate's answer with **Accept** or **Decline**. See [Send an offer](/offers/send-offers).
> [accordion] Do e-consent forms use e-signature credits?
>
> No. E-consent forms are signed inside Journeyfront and don't use e-signature credits. See [E-consent forms](/onboarding/e-consent-forms).
## Related
> [card] [E-signatures](/offers/e-signatures)
>
> Send, track and remind signers.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> Your e-signature balance and history.
> [card] [Offer letter and document templates](/offers/templates)
>
> Add signature fields to your templates.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
# HRIS integrations
Source: https://help.journeyfront.com/integrations/hris
Connect your HR system so new hires, employee records and HR reference lists flow between it and Journeyfront without retyping.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect and configure the integration. Users with the *Hire Candidates* permission create employees in your HR system when they hire.
>
> **Availability:** Your HR system needs to be on the supported list. If you don't see it on the **Integrations** page, ask your Customer Success Manager.
Journeyfront connects to your human resources information system (HRIS) so hiring data moves without spreadsheets or copy and paste. You can create a new hire's employee record in your HR system in one click, keep Journeyfront's employee records in step with your HR system, and pick real HR records, like departments and work locations, in your custom fields.
Journeyfront works with many HR systems, including Workday, BambooHR, ADP, Paylocity, Paychex and UKG, through one standard integration. Setup is the same whichever system you use.
## What the integration does
| Feature | Direction | What it does |
| - | - | - |
| **Create employees** | Journeyfront to your HR system | When you hire a candidate, create their employee record in your HR system, with documents attached. |
| **Employee sync** | Your HR system to Journeyfront | Bring your employees into the Journeyfront **Employees** page on a schedule, and optionally mark matching Candidate Applications as hired. |
| **HRIS objects** | Your HR system to Journeyfront | Pick records from your HR system in custom fields on job reqs, hiring classes and offers. |
## Connect your HR system
Before you start, make sure you have:
* **Sign-in details for your HR system.** Depending on the system, you may also need an API key or client secret. Your HRIS administrator can help.
* **The right access in your HR system.** The account you connect with needs permission to create employee records and to read the data Journeyfront uses, such as locations and departments.
**1. Find your HR system**
Go to **Settings**, then **Integrations**. HR systems are listed under **HRIS**. Use **Filter** or **Search** to find yours quickly.

**2. Start the connection**
Click your HR system's tile, then click **Connect to** followed by its name.

**3. Review permissions and sign in**
A secure window lists the data Journeyfront is asking to access. Review it and continue. Then follow the steps for your HR system: sign in, or enter the key it asks for. A short guide at the bottom of the window explains where to find each value.

**4. Confirm the connection**
When you see **Connection set up successfully!**, close the window. The tile now shows **Active**, and the **Details** tab shows who connected it and when.
Once connected, your HR system's page in **Integrations** has these tabs:
| Tab | What it's for |
| - | - |
| **Details** | Connection status, who connected it and when, and **Disconnect** |
| **Create Employee Settings** | Turn on employee creation at hire and map the fields it sends |
| **Employee Sync Settings** | Schedule the employee sync, choose how people are matched, and map synced fields |
| **Job Profile Mapping** | Match your HR system's job titles to Journeyfront job profiles |
| **Sync History** | Preview a sync, run one now, and review past runs |
| **HRIS Objects** | See the HR records and lists available to your custom fields |
## Create employees when you hire
### Turn on employee creation
**1. Open Create Employee Settings**
Go to **Settings**, then **Integrations**, open your HR system, and select the **Create Employee Settings** tab.
**2. Turn it on**
Turn on **Enable Employee Creation** and click **Save**. The **Create Employee in** option now appears in the hire window for your team.
**3. Map your fields**
Under **Field Mappings**, choose which Journeyfront field fills each field in your HR system. Add a **Default Value** for any field that should be filled in when the Journeyfront field is empty.
Two more settings appear once employee creation is on:
* **Pass JF Country Options** and **Pass JF State Options:** if your HR system doesn't supply its own country or state list, Journeyfront fills the dropdown from its own list. Turn these off if your HR system expects different codes; the field then becomes free text.
> [!TIP]
>
> Set default values for fields your HR system requires but recruiters rarely know at the moment of hire, such as a standard work schedule. Recruiters then only fill in what's different, and fewer sends stop on a missing field.
### Send a new hire to your HR system
**1. Hire the candidate**
On the Candidate Application, click **Actions**, then **Hire**. In the hire window, make sure **Create Employee in** your HR system is checked (it's checked for you when your HR system is connected), then complete the hire.

**2. Review the mapped information**
A window opens showing what Journeyfront filled in from the Candidate Application on the left, and your HR system's fields on the right. Check the pre-filled values, such as name and email.
**3. Fill in required fields**
Fill in anything your HR system requires that Journeyfront doesn't have, such as a start date, work location or manager. Required fields are marked with a red asterisk (\*).
**4. Attach documents and send**
Choose any documents to include, such as the resume or signed offer letter, if your HR system accepts them. Then click **Send**.
The employee record is created in your HR system right away. Journeyfront records who sent it and when at the top of the Candidate Application and in **Comments & Activities**.
> [!NOTE]
>
> Some HR systems, such as ADP and Paychex, create the record as an in-progress or onboarding hire rather than an active employee. That's decided by your HR system, not Journeyfront.

## Sync employees from your HR system
The employee sync brings your employees from your HR system into the Journeyfront **Employees** page on a schedule. It updates people who already exist in Journeyfront, adds new ones, and can mark their Candidate Applications as hired.
### Set up the sync
Go to **Settings**, then **Integrations**, open your HR system, and select **Employee Sync Settings**.
| Setting | What it does |
| - | - |
| **Enable Sync** | Runs the sync on your schedule. Turn it off to pause syncing without losing your settings. |
| **Sync Cadence** | **Daily**, **Weekly** (pick the day) or **Monthly** (pick a day from 1 to 28). |
| **Employee Identifier** fields | How each employee in your HR system is matched to a person in Journeyfront. Choose the value your HR system holds (**Personal Email**, **Work Email**, **Employee Number** or **Employee ID**). Journeyfront compares an email with the person's **Email**, and a number or ID with their **External Employee Identifier**. A match is updated; anyone without a match is added. |
| **Auto-Mark as Hired** | Finds the employee's Candidate Application in the job req tied to their job profile and marks it **Hired**. Applications already hired or rejected are left alone. |
| **When Multiple Applications Match** | **Mark most recent**, **Skip if multiple** (leave it for a person to review), or **Closest to hire date (window)**, which picks the application closest to the hire date within the number of days you set. |
| **Configure Employee Filters** | Limit which employees are pulled, for example by department, location or employment status. Changes apply on the next sync. |
Click **Save Configuration**. Once the sync is on, the **Field Mapping** section appears below. Map the fields pulled from your HR system to Journeyfront fields, and choose **Unknown Option Handling** for dropdown fields: **Auto-create** adds a value that isn't an option yet, and **Skip** leaves the field blank.
> [!TIP]
>
> Pick an identifier both systems really share. If candidates apply with their personal email, **Personal Email** finds the most matches. Use **Work Email** only when work emails are reliably filled in your HR system, and **Employee Number** or **Employee ID** when Journeyfront already stores that number for your people.
### Map job titles to job profiles
On the **Job Profile Mapping** tab, match each job title in your HR system to a Journeyfront job profile. Synced employees are assigned to that profile, and **Auto-Mark as Hired** uses it to find the right job req.
* **Match Strategy:** use **Job Title only** for one profile per title. Use **Job Title + Location** or **Job Title + Department** when the same title maps to different profiles depending on where someone works.
* **Add Manual Mapping** adds one mapping at a time. For many titles, click **Download Template**, fill it in, and use **Import CSV**.
Titles without a mapping are flagged when the sync runs.
### Preview and review syncs
The **Sync History** tab lists every run with its date, status, who started it, and how many people were created, updated, unchanged or had errors. Click **View** to see the results of a run, or **CSV** to download them.
**1. Preview first**
Click **Preview Sync** to see what a sync would do without changing anything. A preview is required before your first sync.
**2. Run the sync**
When the preview looks right, click **Run Sync Now** and confirm. After that, the sync also runs on your schedule.
> [!WARNING]
>
> A sync can create, update and end employee records in Journeyfront based on your HR system's data. Review a preview after any change to your matching, filters or mappings.
## Pick HR records in custom fields (HRIS objects)
An **HRIS Object** custom field lets your team pick a record straight from your HR system, such as a work location, company, department, job code or employee, instead of typing its code by hand. The field keeps both the record's **name**, so people can read it, and your HR system's **code** for it, so your exports, offer letters and other systems get exactly what they expect.
You can add HRIS Object fields to job reqs, hiring classes and offers. Candidates never see them; they aren't available on application forms.
[HRIS objects in custom fields](https://www.youtube.com/embed/6Xawbfedzss)
### Create an HRIS Object field
**1. Open the field settings**
Go to **Settings**, then **Custom Fields**, then **Job Req Fields** or **Hiring Class Fields**. For offers, go to **Settings**, then **Offers**, then **Offer Fields**. Add a field.
**2. Name it**
Enter a **Label**, the name everyone sees on the form and as a column header, such as "Department". The **Key** is suggested from the label. You can edit the key before you save, but not after.
**3. Choose the list**
Set **Type** to **HRIS Object**, then choose the **HRIS Object** list the field draws from. Lists are named the way your HR system names them, with a short description of each. If you picked a list of groups, set a **Group Type** to narrow it, for example so one field means Department and another means Division.
**4. Check the preview and save**
The **Preview** shows the real picker with your real records, so you can search it exactly as your team will. The **Values** row shows the two values the field produces and their merge fields. Click **Save**.

> [!TIP]
>
> Name the field the way your business talks about it, like "Cost Center", even if your HR system calls the list something else. And use the Preview before you save: it's the quickest way to confirm you picked the right list when several sound alike.
### Pick a value
Open the job req, hiring class or offer and click the field. A **Recently used** section shows the five records your team chose most recently for that field. To find anything else, start typing a name or a code; a full code matches exactly and comes first. The field shows the record's name with its code beside it as a chip, so leading zeros like `0001` stay visible.

Records retired in your HR system don't appear in the picker, so no one can choose one that no longer exists.
### Use an HRIS Object field in offer letters
An HRIS Object offer field gives your templates two merge fields. Use the field's key for the record's name, for example `{{WORK_LOCATION}}`, and add `_ID` for your HR system's code, for example `{{WORK_LOCATION_ID}}`. You can also set a default for the field on an offer package, so every offer from that package starts pre-filled.
### Keep your lists up to date
Lists refresh automatically. Using the picker never calls your HR system; it reads what Journeyfront has already synced, so it stays fast and puts no load on your HR system.
To pull a change right away, go to **Settings**, then **Integrations**, open your HR system, select the **HRIS Objects** tab and click **Refresh now**. The same tab shows every list, where it comes from, how many records it holds, whether a field uses it, and how the last sync went, including why a list couldn't be read.

When a record is renamed in your HR system, the new name shows everywhere on the next sync. When one is retired, it stops appearing for new selections, but every job req, hiring class and offer already using it keeps its name and code.
### Connect a web service for lists your integration doesn't cover
If a list you need isn't part of the standard integration, or your HR system isn't supported by it, you can connect to your HR system's own web services. You'll need details from whoever manages your HR system.
**1. Open the HRIS web service card**
Go to **Settings**, then **Integrations**, and open **HRIS web service** in the HRIS section.
**2. Enter the connection details**
Fill in **HRIS**, **Web services host**, **Service account username**, **Service account password**, **Company API key** and **User API key**. Your HR team creates the service account with read access to the lists you want.
**3. Test and save**
Click **Test and save**. Journeyfront signs in once to check the details, and the connection only turns on if that works.
**4. Add your lists**
For each list, give it a name your admins will see, the service to call, and which response fields hold the code and the display name. Your HR team provides these. Each list then appears as an **HRIS Object** option when you create a field.

Credentials are stored encrypted and never shown again. You'll see whether each one is set, not its value. A web service connection works with or without the standard integration.
### Edit, archive or delete an HRIS Object field
Open the field's menu on the settings page.
* **Edit:** change the label and description at any time. The **Key** can't change after the field is created, and the list can't change once any record has a value for it. To use a different list, create a new field.
* **Archive:** removes the field from forms but keeps every value already recorded. You can restore it later.
* **Delete:** removes the field and its values permanently. Journeyfront shows how many records would be affected before you confirm.
> [!TIP]
>
> Archive is almost always the better choice. It keeps your history and can be undone.
## Disconnect your HR system
Go to **Settings**, then **Integrations**, open your HR system and click **Disconnect** on the **Details** tab. Employee records you already sent stay in your HR system, and data already synced into Journeyfront stays in Journeyfront. Disconnecting can't be undone; to use the integration again, you connect from the start.
## FAQ
> [accordion] Which HR systems are supported?
>
> Every supported HR system is listed under **HRIS** on the **Integrations** page, including Workday, BambooHR, ADP, Paylocity, Paychex, UKG and many more. If yours isn't listed, ask your Customer Success Manager.
> [accordion] Can I connect more than one HR system?
>
> No. Each Journeyfront account connects to one HR system. To switch, disconnect the current one first.
> [accordion] What gets sent when I create an employee?
>
> First name, last name and email are mapped automatically. Your admins can map more fields and set defaults in **Create Employee Settings**. Depending on your HR system, the window may also ask for things like home address, start date, work location, department and manager. You can attach documents such as the resume and signed offer letter if your HR system accepts them.
> [accordion] Does sending a hire update an employee who already exists?
>
> No. Each send creates a new employee record in your HR system. Journeyfront shows a check mark once a candidate has been sent, so you don't send them twice by accident.
> [accordion] I un-hired a candidate and am hiring them again. Will it create a second employee?
>
> It can. If the candidate was sent before, the hire window shows when, with a warning that sending again may create a second employee in your HR system. Check your HR system before you send.
> [accordion] Can I create employees for a group of hires at once?
>
> Yes. When you hire several candidates at once, the bulk hire window includes a section for your HR system. Fill in shared values once, adjust any candidate individually, and Journeyfront creates each employee.
> [accordion] What happens if a send fails?
>
> You'll see an error explaining why, usually a missing required field or a connection problem. Fix it and send again. A failed attempt doesn't create a partial record, and Journeyfront doesn't retry on its own.
> [accordion] Why is my HRIS Object list showing no records?
>
> Usually the list hasn't synced yet. Open the **HRIS Objects** tab on your integration to see when it last ran and whether anything went wrong. If a list couldn't be read, the reason is shown there; often it's a permission your service account needs in your HR system.
> [accordion] How is an HRIS Object field different from a multiple choice field?
>
> A multiple choice field is a list you type and maintain by hand, and its value is just the option's label. An HRIS Object field gets its options from your HR system, stays current on its own, and carries your HR system's code alongside the name.
> [accordion] Is the connection secure?
>
> Yes. Journeyfront connects through secure, authenticated APIs, and you approve exactly what it can access when you connect.
## Related
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Add your own fields to job reqs, hiring classes and applications.
> [card] [Offer fields](/offers/offer-fields)
>
> Fields that fill in your offer letters.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who share a start date.
# Job board integrations
Source: https://help.journeyfront.com/integrations/job-boards
Send your jobs to Indeed, JobTarget and Appcast, and see which of them bring in your applicants.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect job board partners and turn them on for your job boards. Anyone who can edit a job req's postings can post it through JobTarget.
>
> **Availability:** Posting through these partners costs nothing extra from Journeyfront. Paid placements, such as sponsored Indeed jobs, paid JobTarget boards and Appcast campaigns, are billed by the partner.
In Journeyfront, a **job board** is your own careers page: the branded page that lists your open job postings, set up under **Settings**, then **Job Boards**. Job board integrations take those postings further, to Indeed, to thousands of other boards through JobTarget, and to programmatic job advertising through Appcast. Applicants come back into Journeyfront tagged with where they came from, so your reports show which channels actually work.
## Choose a partner
> [card] [Indeed](/integrations/job-boards/indeed)
>
> Pick this to put every active posting on Indeed automatically, as free listings, with optional Indeed Easy Apply.
> [card] [JobTarget](/integrations/job-boards/jobtarget)
>
> Pick this to choose and pay for specific boards, such as LinkedIn or niche and diversity boards, one posting at a time.
> [card] [Appcast](/integrations/job-boards/appcast)
>
> Pick this if you run programmatic job advertising campaigns with Appcast.
| Partner | What it does | Where you set it up |
| - | - | - |
| **Indeed** | Sends every active posting on a job board to Indeed automatically, with optional Indeed Easy Apply | **Integrations**, then each job board |
| **JobTarget** | Lets you pick and pay for boards from a marketplace of more than 25,000, one job posting at a time | **Integrations**, then each job posting |
| **Appcast** | Picks up your jobs from a job board's feed for programmatic advertising, and tracks conversions | **Integrations**, plus your job board's **Feed URL** |
You can use more than one partner at the same time.
## See where a posting has gone
Open the job req and go to **Setup**, then **Job Postings**, and open the posting. **External Job Board Posts** lists the partners the posting has been sent to, with each one's status. From here you can also click **Post to Job Board** to send it through JobTarget.
## How applicants are tagged
Every partner tags its applicants so your reports show what each channel brings in:
* **Indeed Easy Apply** candidates get the source set on the job board, or **Indeed** if none is set.
* **JobTarget** candidates get a source named after the board they came from, such as **JobTarget via LinkedIn**.
* **Appcast** has its own ready-made sources.
See [Magic links](/sourcing/magic-links) for how sources work across Journeyfront.
## FAQ
> [accordion] Who bills for sponsored jobs and paid boards?
>
> The partner. Indeed, JobTarget and Appcast manage their own pricing, invoices and accounts. Journeyfront never stores your payment details for them.
> [accordion] Do I need a separate job board for each partner?
>
> No. One job board can go to Indeed, feed Appcast and have its postings promoted through JobTarget, all at once.
## Related
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
> [card] [Lead ads](/sourcing/lead-ads)
>
> Turn Facebook and Instagram lead forms into candidates.
# Appcast
Source: https://help.journeyfront.com/integrations/job-boards/appcast
Advertise your jobs programmatically through Appcast and track which clicks turn into applications.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission turn on Appcast and share a job board's feed.
>
> **Availability:** Connecting Appcast costs nothing extra from Journeyfront. Your Appcast campaigns are billed by Appcast.
Appcast is a programmatic job advertising platform. It takes your jobs from a job board feed, runs your campaigns, and uses a tracking pixel to measure which clicks turn into applications.
For the other job board partners, see [Job board integrations](/integrations/job-boards).
## Set up Appcast
**1. Share your job feed**
Go to **Settings**, then **Job Boards**, and open the job board whose postings Appcast should advertise. On the **General** tab, copy the **Feed URL** and send it to your Appcast representative. The feed always lists the board's active postings, so Appcast stays current as you open and close jobs.
**2. Turn on conversion tracking**
Go to **Settings**, then **Integrations**, open **Appcast** under **Job Board**, and set **Activated** to **Yes**. Paste the Appcast conversion pixel or Google Tag Manager snippet into **Tracking Pixel / Tag** and save. Journeyfront adds it to the candidate apply page and the candidate progress page.
## Appcast sources
Journeyfront includes ready-made Appcast sources, including Appcast campaigns on Indeed and ZipRecruiter, so you can report on what Appcast brings in. They're named **Appcast**, **Appcast_Indeed**, **Appcast_ZipRecruiter**, **Appcast_Xtend**, **Appcast_Search_Ads** and **Appcast_Brand_Ads**.
## FAQ
> [accordion] Who do I contact about Appcast billing?
>
> Appcast. Appcast manages its own pricing, invoices and accounts. Journeyfront never stores your payment details for it.
> [accordion] Do I need to update Appcast when I open or close a job?
>
> No. The feed lists the job board's active postings, so Appcast picks up new and closed jobs on its own.
## Related
> [card] [Job board integrations](/integrations/job-boards)
>
> Compare Indeed, JobTarget and Appcast.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Find a job board's Feed URL.
# Indeed
Source: https://help.journeyfront.com/integrations/job-boards/indeed
Send every active posting on a job board to Indeed automatically, with optional Indeed Easy Apply.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect Indeed and turn it on for your job boards.
>
> **Availability:** Posting to Indeed costs nothing extra from Journeyfront. Jobs go up as free, organic listings; if you sponsor them, Indeed bills you directly.
Once Indeed is set up, every active posting on a connected job board is sent to Indeed and kept in sync. When you edit, deactivate or close a posting in Journeyfront, Indeed is updated too, so you don't leave stale jobs live. You decide in your Indeed account whether to sponsor them.
Journeyfront sends a posting to Indeed when it's saved. Indeed can take up to 48 hours to show it.
For the other job board partners, see [Job board integrations](/integrations/job-boards).
## Set up Indeed
Before you start, you need an Indeed employer account (create one at [employers.indeed.com](https://employers.indeed.com) if you don't have one), the company name on that account, and at least one job board with active postings.
**1. Activate Indeed**
Go to **Settings**, then **Integrations**, and open **Indeed** under **Job Board**. Set **Activated** to **Yes**. Enter your **Company Name** exactly as it appears in your Indeed employer account. Optionally, enter the **Email Address** associated with your Indeed account. Save.
**2. Turn on Indeed for a job board**
Go to **Settings**, then **Job Boards**, and open the job board. On the **General** tab, under **External Job Board Partners**, check **Post Jobs to Indeed**. Optionally check **Allow Indeed Easy Apply** and choose the **Source** that Easy Apply candidates are tagged with. Save, and repeat for each job board that should go to Indeed.

**3. Connect your Indeed employer account**
In Indeed, go to **Manage Jobs** and connect Journeyfront as your ATS (Indeed's wording varies). You only do this once. Without it, your jobs still appear in Indeed search, but not in your Indeed dashboard, so you can't sponsor them.
> [!TIP]
>
> The company name has to match your Indeed account character for character. If your jobs don't show in your Indeed dashboard, check this field first.
## Choose how Indeed candidates apply
| | **Apply on company site** (Easy Apply off) | **Indeed Easy Apply** (Easy Apply on) |
| - | - | - |
| Where the candidate applies | On your Journeyfront job posting | Inside Indeed |
| What they fill in | Your full Journeyfront application | Name, email, and the fields from your application form |
| After they submit | Their application is complete | They're added to Journeyfront and emailed a link to finish |
| Best for | Complete applications up front | More applicants |
> [!TIP]
>
> Easy Apply brings in more applicants because candidates never leave Indeed, but they tend to be more casual. If you want everyone to see your branded application and finish it in one go, leave Easy Apply off. You can change it at any time.
## Control what Easy Apply asks for
The job req's application form controls the Easy Apply form on Indeed. Indeed always asks for name and email. Beyond that, your own personal fields are required on Indeed when they're required on your application form, and optional when they're optional.
A few fields work differently:
* **Phone and resume** use Indeed's own fields on its form.
* **Education and work history** aren't asked on Indeed. Candidates fill them in when they finish their application in Journeyfront.
* **EEO questions** are asked on Indeed only when they're set to **Required** on your application form.
To change what Indeed asks, open the job req and go to **Setup**, then **Application Form**. Add, remove or reorder fields, set each one to required or optional, and save. There's no separate Easy Apply form to maintain.
> [!TIP]
>
> Keep required fields to a minimum: every required field costs you Easy Apply applicants. Make anything extra optional; Indeed still asks for it, and most candidates fill it in.
## Customize the Easy Apply Invite email
When someone applies with Easy Apply, Journeyfront emails them the **Easy Apply Invite** with a link to finish their application. To change it, go to **Settings**, then **Templates**, then **E-mail Template**, open the **System Emails** tab and edit **Easy Apply Invite**. Until you edit it, candidates get the standard system version. You can change the subject, body, sender and merge fields; your logo and branding come from your account.
> [!WARNING]
>
> Keep the **Click here to continue your application** link in the email. Without it, candidates can't get back into their application.
## See Easy Apply candidates in Indeed too (optional)
Easy Apply candidates always come into Journeyfront. If you also want them in Indeed's **Candidates** tab, link each job in Indeed: open the job under **Jobs** (or **Manage Jobs**), click **Manage Candidates** (wording varies) and confirm. The job then shows a link icon in your Indeed jobs list. Skip this if your team manages candidates only in Journeyfront.
## Check a posting's sync status
Open the job req and go to **Setup**, then **Job Postings**, and open the posting. Under **External Job Board Posts**, the **Indeed** row shows its status, **Synced**, **Not Synced**, **Expired** or **Failed to Sync**, and the date it was last sent to Indeed under **Date Added**.

If a posting isn't syncing, check that:
* The posting is active and has a **country** set.
* The posting has a title and description.
* **Post Jobs to Indeed** is checked on its job board.
* Indeed is **Activated** in **Integrations**, with a company name filled in.
## Take a posting down
Deactivate the posting in Journeyfront and it expires on Indeed automatically. Closing, archiving or deactivating the job req does the same, and so does unchecking **Post Jobs to Indeed** on the job board, which takes down every posting on that board. There's no separate pause: to stop a posting for a while, deactivate it or close the job req.
> [!NOTE]
>
> You can also pause or close a job inside Indeed, but that change doesn't come back to Journeyfront. The posting stays active in Journeyfront and may be sent to Indeed again the next time it's saved. Always take postings down in Journeyfront.
## Sponsor your Indeed postings
Sponsorship is set up entirely in your Indeed employer account. Go to **Manage Jobs**, find the posting, and attach it to a sponsored campaign with your budget and targeting. Journeyfront doesn't see or control your Indeed budget.
## What candidates see on Indeed
**With Easy Apply off,** the candidate clicks **Apply on company site** on Indeed, lands on your Journeyfront job posting and completes your full application there.
**With Easy Apply on,** the candidate clicks **Apply now** and fills in a short form inside Indeed. Shortly after, Journeyfront adds them, pre-fills their application form with their Indeed answers, and sends the **Easy Apply Invite** email. They click the link, set a password, and continue straight to the next steps, such as assessments. If something required couldn't be collected on Indeed, they're asked for it before they continue.
## How Indeed candidates are tagged
* **Easy Apply candidates** get the **Source** set for Easy Apply on the job board, or **Indeed** if none is set.
* **Candidates who apply on your site** are linked to the job posting they came through.
See [Magic links](/sourcing/magic-links) for how sources show up in reports.
## FAQ
> [accordion] Do I have to pay to post to Indeed?
>
> No. Jobs go to Indeed as free, organic listings, and Journeyfront doesn't charge for the integration. You only pay Indeed if you choose to sponsor a job from your Indeed account.
> [accordion] Why don't my jobs show in my Indeed employer dashboard?
>
> Usually your Indeed employer account isn't connected to the Journeyfront feed yet. In Indeed, go to **Manage Jobs** and connect Journeyfront as your ATS. Also check that the company name in Journeyfront's Indeed settings matches your Indeed account exactly.
> [accordion] Why are Easy Apply candidates in Journeyfront but not in Indeed?
>
> The job isn't linked in Indeed yet. Open the job in Indeed and click **Manage Candidates** (wording varies). No candidates are lost in the meantime; they're already in Journeyfront.
> [accordion] Indeed says a job is managed by another company account. What does that mean?
>
> The job is linked to a different Indeed employer account, usually a colleague's. Only one Indeed account can manage a job's candidates at a time, so ask that person to unlink it, then link it from your account. Journeyfront isn't affected; postings and candidates keep flowing either way.
> [accordion] Can I edit a posting directly on Indeed?
>
> Edit it in Journeyfront instead. Every save in Journeyfront is sent to Indeed, and an edit made only on Indeed may be overwritten the next time the posting is saved in Journeyfront.
> [accordion] Can I use Easy Apply on some job boards and not others?
>
> Yes. **Post Jobs to Indeed** and **Allow Indeed Easy Apply** are set per job board, so each board can work differently.
## Related
> [card] [Job board integrations](/integrations/job-boards)
>
> Compare Indeed, JobTarget and Appcast.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Set up the job boards whose postings go to Indeed.
# JobTarget
Source: https://help.journeyfront.com/integrations/job-boards/jobtarget
Pick and pay for job boards from JobTarget's marketplace, one job posting at a time.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect JobTarget. Anyone who can edit a job req's postings can post it through JobTarget.
>
> **Availability:** Connecting JobTarget costs nothing extra from Journeyfront. Paid boards are billed by JobTarget.
JobTarget gives you a marketplace of more than 25,000 job boards, including general, niche, industry and diversity boards, free and paid. You choose the boards for each job posting, and JobTarget handles posting and billing.
For the other job board partners, see [Job board integrations](/integrations/job-boards).
## Connect JobTarget
Go to **Settings**, then **Integrations**, open **JobTarget** under **Job Board**, and set **Activated** to **Yes**. If you don't have a JobTarget account yet, one is created and linked for you.

## Post a job through JobTarget
Before you start, make sure the posting has a **State/Region** and a **Zip** filled in. JobTarget needs both.
**1. Open the posting**
Open the job req and go to **Setup**, then **Job Postings**, and open the posting you want to promote.
**2. Open the marketplace**
Under **External Job Board Posts**, click **Post to Job Board**, then **Job Post Using Job Target**. JobTarget opens in a panel beside your posting.

**3. Choose your boards**
Search or filter the marketplace by name, industry, job type or location, and add free or paid boards to your cart.

**4. Check out**
Complete your order in JobTarget. Pricing, payment and invoices are all handled by JobTarget.
## Manage your JobTarget posts
Back in Journeyfront, **External Job Board Posts** lists the boards you posted to. Click **Manage Job Post** to reopen JobTarget and change or extend your postings.

> [!NOTE]
>
> Changes you make to the posting or job req in Journeyfront don't update or end your JobTarget posts. Editing, deactivating or closing them in Journeyfront leaves them running on the boards you bought. Use **Manage Job Post** to manage them in JobTarget.
## How JobTarget candidates apply
The apply link on every board takes candidates to your Journeyfront application. Their source shows JobTarget together with the specific board, for example **JobTarget via LinkedIn**. These sources are created automatically.
## FAQ
> [accordion] Who do I contact about JobTarget billing?
>
> JobTarget. JobTarget manages its own pricing, invoices and accounts. Journeyfront never stores your payment details for it.
> [accordion] If I close the job req, do my JobTarget posts end?
>
> No. Closing or deactivating in Journeyfront doesn't reach JobTarget. Your posts run until they expire or you change them in JobTarget through **Manage Job Post**.
## Related
> [card] [Job board integrations](/integrations/job-boards)
>
> Compare Indeed, JobTarget and Appcast.
> [card] [Job postings](/sourcing/job-postings)
>
> Create and manage a job req's postings.
# Meta Lead Ads
Source: https://help.journeyfront.com/integrations/meta-lead-ads
Connect your Meta Business account so lead forms on your Facebook and Instagram Pages send candidates to Journeyfront.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* connect Meta. The person who connects must also be a Page admin and a Business admin in Meta. Recruiters don't need any Meta access.
>
> **Availability:** Meta Lead Ads needs to be turned on for your account. Ask your Customer Success Manager.
This page covers connecting Meta to Journeyfront. Once your Meta Business account is connected, the lead forms on the Pages you choose come into Journeyfront, ready to link to job reqs. Linking forms, mapping their questions and following each lead are the same for every platform; see [Lead ads](/sourcing/lead-ads).
## Before you start
* **Your lead forms live in Meta.** Create them in Meta Ads Manager. Journeyfront brings in the forms from the Pages you connect, but can't create forms for you.
* **The right Meta access.** The person connecting needs to be both a Page admin and a Business admin on your Meta Business account.
* **Company Settings access** in Journeyfront.
* **Leads Access, if your business uses it.** If your Meta Business restricts who can access leads, a Business admin also needs to allow Journeyfront as a CRM. See [Allow Journeyfront in Leads Access](#allow-journeyfront-in-leads-access).
## Step 1: Connect your Meta Business account
**1. Open the Meta Business tile**
Go to **Settings**, then **Integrations**, and click the **Meta Business** tile.
**2. Connect**
Click **Connect Meta Business**. A Facebook window opens.
**3. Choose your Business and Pages**
Log in, choose the Meta Business whose lead forms you want, and choose one or more Pages.
**4. Approve the permissions**
Approve all six permissions Journeyfront asks for. Leave every one turned on; if one is missing, Journeyfront asks you to reconnect.
| Permission | What it lets Journeyfront do |
| - | - |
| `leads_retrieval` | Read the answers people submit on your lead forms. |
| `pages_show_list` | List the Pages you manage so you can choose which to connect. |
| `business_management` | See your Meta Business and the Pages it owns. |
| `pages_manage_ads` | Read your lead forms and their questions, and create test leads. |
| `pages_manage_metadata` | Ask Meta to send each new lead to Journeyfront as soon as it's submitted. Without it, no leads arrive. |
| `pages_read_engagement` | Read Page content that Meta requires for reading lead forms. |
Journeyfront can't post to your Page, change your ads, or read your Page's messages.
When the window closes, the Meta Business page shows an **Active** badge, the **Connection Details** (the Meta Business, who connected it and when, and the permissions granted) and the Pages you connected under **Connected Sources**.
### Allow Journeyfront in Leads Access
Meta's **Leads Access** setting controls which people and CRMs can receive leads for a Page. If your business uses it, Meta only sends leads to the CRMs on the list. Until Journeyfront is added, the connection looks healthy, but new leads never reach Journeyfront.
You need this step if any of these are true:
* Your Meta Business has set up Leads Access for the Page, or you're not sure whether it has.
* The form's health check shows leads at Meta marked **Never received**, even though **Page sends lead notifications** is **OK**.
* The Page shows **Receiving leads**, but the form's **Leads** count stays at 0.
A Business admin for the Meta Business that owns the Page can do this in about a minute:
**1. Open Business Settings**
Go to [business.facebook.com/settings](https://business.facebook.com/settings).
**2. Open Leads Access**
In the left menu, open **Integrations**, then **Leads Access**.

**3. Select your Page**
Select the Page your lead forms are on.
**4. Assign Journeyfront**
Open the **CRMs** tab and click **Assign CRM**. In **Add CRMs and set permissions**, paste the Journeyfront app ID into **Search**: `1661431234740842`. Searching by name doesn't find it. Select **Journeyfront** and click **Confirm**.

> [!NOTE]
>
> Journeyfront only shows up here after the Page is connected in Journeyfront. If the app ID finds nothing, connect the Page first.
When it's done, Journeyfront is listed under **CRMs with leads access**.

New leads start arriving within a few minutes. To bring in the leads that arrived before the change, open the form, run the health check on the **Health** tab, and click **Import missing leads**. See [Check a form's health](/sourcing/lead-ads#check-a-forms-health).
> [!NOTE]
>
> If Journeyfront is already on the list, or you don't see a **CRMs** tab, Leads Access isn't the cause. Contact your Customer Success Manager.
## Fix connection problems
Each Page under **Connected Sources** on the Meta Business page shows whether Meta is sending its leads to Journeyfront: **Receiving leads**, **Not subscribed** or **Not checked yet**. Hover over the status for details.
| What you see | What to do |
| - | - |
| **Missing permissions** on the Meta Business page | Click **Reconnect** and approve every permission in the Facebook window. |
| **Not subscribed** next to a Page | Leads from that Page aren't reaching Journeyfront. Click **Repair** next to the Page, or choose **Repair Page subscription** from a form's menu on the **Meta Lead Ads** page. |
| A Page you need isn't listed | Click **Reconnect** and pick the Page again. |
| The health check shows leads marked **Never received**, but **Page sends lead notifications** is **OK** | Your Meta Business may be blocking Journeyfront in Leads Access. [Allow Journeyfront in Leads Access](#allow-journeyfront-in-leads-access), then click **Import missing leads**. |
For problems with a single form, such as **Needs mapping** or leads from a form that isn't linked, see [Fix common problems](/sourcing/lead-ads#fix-common-problems).
## Add Pages or disconnect
* **To add more Pages later**, click **Reconnect** on the Meta Business page and pick the Pages again.
* **To disconnect**, click **Disconnect**. Candidates already in Journeyfront stay; new leads stop coming in.
## FAQ
> [accordion] Is candidate data secure?
>
> Yes. Journeyfront connects through Meta's official sign-up flow, stores the connection securely, and only asks for the permissions needed to receive leads. You can disconnect at any time from the Meta Business page.
> [accordion] Do recruiters need access to our Meta Business?
>
> No. Only the person who connects needs to be a Page admin and a Business admin in Meta. Everyone else works with lead ad candidates in Journeyfront.
> [accordion] Does connecting Meta cover Instagram?
>
> Yes. Instagram lead forms run on the same Meta lead ads system, so forms on your connected Pages come in the same way, whether the lead was submitted on Facebook, Instagram, Messenger or the Audience Network.
## Step 2: Link your lead forms
With Meta connected, your lead forms appear under **Settings**, then **Meta Lead Ads**. Link each one to a job req and map its questions so every submission becomes a candidate.
> [card] [Lead ads](/sourcing/lead-ads)
>
> Link lead forms to job reqs, map their questions and follow every lead.
# Integrations overview
Source: https://help.journeyfront.com/integrations/overview
Connect Journeyfront to the HR, recruiting and communication tools your team already uses.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission connect company-wide integrations in **Settings**, then **Integrations**. Each interviewer connects their own calendar under **Interviews**, then **My Profile**.
>
> **Availability:** Some integrations need to be turned on for your account or use a partner account of your own. Ask your Customer Success Manager.
Journeyfront connects to the rest of your hiring and HR stack so candidate and hire data flows without retyping. On the **Integrations** page, every integration is grouped by category with an **Active** or **Inactive** status, and you can use **Filter** and **Search** to find one quickly.
A few connections are set up elsewhere: texting and WhatsApp under **Settings**, then **Add-Ons**, then **Text Messages**; e-signature, which Journeyfront turns on for you as an add-on; and calendars, which each interviewer connects themselves.

> [card] [HRIS](/integrations/hris)
>
> Create employees in your HR system when you hire, sync employee records into Journeyfront, and pick HR records in custom fields.
> [card] [ATS](/integrations/ats)
>
> Send candidates to another applicant tracking system, or launch Journeyfront assessments from it.
> [card] [Job boards](/integrations/job-boards)
>
> Post to Indeed with optional Easy Apply, buy boards through JobTarget, and advertise through Appcast.
> [card] [Background checks](/integrations/background-checks)
>
> Order Checkr background checks as a workflow activity and follow their status.
> [card] [E-signature](/integrations/e-signature)
>
> Send offer letters and documents for signature without leaving Journeyfront.
> [card] [Calendars and video](/integrations/calendars)
>
> Sync interviewers' calendars so candidates book real open times, with Zoom, Microsoft Teams, GoToMeeting or Google Meet for the meeting.
> [card] [Calling](/integrations/calling)
>
> Call candidates through Webex Contact Center, and log calls automatically from QUO.
> [card] [Texting providers](/integrations/texting-providers)
>
> Text candidates by SMS or WhatsApp, using Journeyfront's texting or your own provider account.
> [card] [Meta Lead Ads](/integrations/meta-lead-ads)
>
> Connect your Meta Business account so Facebook and Instagram lead form submissions become candidates automatically.
> [card] [Single sign-on (SSO)](/integrations/single-sign-on)
>
> Let your team sign in with their company account. The Journeyfront team sets it up with you.
> [!TIP]
>
> Don't see a system you use? Ask your Customer Success Manager whether it's supported.
# Single sign-on (SSO)
Source: https://help.journeyfront.com/integrations/single-sign-on
Sign in to Journeyfront with your company's account, and how SSO gets set up for your company.
> [!NOTE]
>
> **Who this is for:** Your team, when your company signs in with single sign-on. Setting SSO up is done with the Journeyfront team.
With single sign-on (SSO), you sign in to Journeyfront with the same company account you use for your other work tools. You don't have a separate Journeyfront password: your company's sign-in page checks who you are, then sends you back to Journeyfront.
## Sign in with SSO
**1. Go to the sign-in page**
Open [app.journeyfront.com](https://app.journeyfront.com).
**2. Enter your work email**
Under "Enter your email to continue.", type your work email and click **Next**. Journeyfront recognizes your company's email domain and sends you to your company's sign-in page. You aren't asked for a Journeyfront password.
**3. Sign in with your company account**
Sign in the way you normally do at work. If you're already signed in to your company account in this browser, this step may happen on its own.
**4. Land back in Journeyfront**
You're sent back to Journeyfront and land on the **Job Reqs** page.
Accepting an invitation works the same way: the link in your invitation email sends you to your company's sign-in page instead of asking you to create a password.
## What SSO changes
* **Passwords:** your password belongs to your company account. To change or reset it, go to your company's IT team, not to **Forgot your password?** or **Change Password** in Journeyfront.
* **Your first sign-in:** you don't need an invitation. If your email's domain is set up for SSO, the first time you sign in Journeyfront creates your user for you. If your company's groups are matched to Journeyfront roles, your role follows your group, so it's changed there. Otherwise you start as **Hiring Team Member** and an admin can change your role. See [Users](/account-setup/users) and [Security roles](/account-setup/security-roles).
* **Leaving the company:** when your company turns off your work account, you can no longer sign in through SSO. An admin should still deactivate you in Journeyfront.
* **Candidates and employees:** they sign in with the email they applied or were invited with, as described in [Logging in](/getting-started/logging-in).
## Set up SSO for your company
SSO isn't self-serve. The Journeyfront team sets it up with you: your Customer Success Manager works with your IT team to connect your company's sign-in system, choose the email domains that use it, and, if you want, match your company's groups to Journeyfront roles.
To start, or to add another email domain later, contact your Customer Success Manager.
## Troubleshooting
| What you see | What to do |
| - | - |
| You're asked for a Journeyfront password instead of being sent to your company's page | Your email's domain isn't set up for SSO. Check you typed your work email, then ask your Customer Success Manager whether that domain should use SSO. |
| Your company's sign-in page says you don't have access to Journeyfront | Your IT team needs to give your company account access to Journeyfront. |
| You can sign in but can't see what you need | You may have the default **Hiring Team Member** role. Ask an admin to change your role, or your IT team if roles come from your company's groups. See [Security roles](/account-setup/security-roles). |
| You're locked out of your company account | Contact your company's IT team. Journeyfront can't reset it. |
## Related
> [card] [Logging in](/getting-started/logging-in)
>
> Sign in with a password, reset it, and help a candidate who can't log in.
> [card] [Users](/account-setup/users)
>
> Invite teammates and set their roles.
# Texting providers
Source: https://help.journeyfront.com/integrations/texting-providers
Set up text messaging and WhatsApp through Journeyfront's Twilio account, your own Twilio account or Webex Connect.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission. Some steps also need someone who can make changes in your Twilio console, your Webex Connect portal or your company's Meta (Facebook) Business account.
>
> **Availability:** The Text Messages add-on needs to be turned on for your account. Ask your Customer Success Manager.
Before your team can text or WhatsApp candidates, your account needs a **messaging provider** and at least one **sending number**. You can text through a Twilio account Journeyfront provides, your company's own Twilio account, or your company's Webex Connect account, and you can use more than one. Everything is set up and checked on one page, so you can see at a glance whether texting and candidate replies are working.
For how recruiters send messages day to day, see [Text messages](/communication/text-messages) and [WhatsApp](/communication/whatsapp).
## Available integrations
> [card] [Twilio](/integrations/texting-providers/twilio)
>
> Pick this for the simplest start with Journeyfront's Twilio account, or if your company already runs its own Twilio account.
> [card] [Webex Connect](/integrations/texting-providers/webex-connect)
>
> Pick this if your company standardizes on Webex Connect for messaging.
> [card] [WhatsApp](/integrations/texting-providers/whatsapp)
>
> Add a WhatsApp Business number through either provider, once texting is set up.
## Choose a provider
| | Journeyfront's Twilio account | Your own Twilio account | Your Webex Connect account |
| - | - | - | - |
| **Who sets it up** | Journeyfront | You, in Journeyfront | You, in Journeyfront and Webex Connect |
| **Texting** | Yes | Yes | Yes |
| **WhatsApp** | Connected in Journeyfront through Facebook | Connected in Journeyfront through Facebook | Set up in Webex Connect, then linked in Journeyfront |
| **WhatsApp templates** | Written and submitted in Journeyfront | Written and submitted in Journeyfront | Written and approved in Webex Connect, then linked in Journeyfront |
| **Candidate replies** | Set up by Journeyfront | One click in Journeyfront | A webhook you add in Webex Connect |
| **Billing** | Your prepaid messaging balance in Journeyfront | Twilio bills you directly | Webex Connect bills you directly |
> [!TIP]
>
> Journeyfront's Twilio account is the simplest way to start. If you already run Twilio, with your own numbers, carrier registrations and billing, connect your own account. If your company standardizes on Webex Connect for messaging, connect that.
Each phone number belongs to one provider, and every message goes out through the provider of the number it's sent from. Recruiters never pick a provider when they send. Replies, delivery updates and opt-outs from every provider land on the same Candidate Application.
## The Text Messages page
Go to **Settings**, then **Add-Ons**, then **Text Messages**. The page has four parts:
* **Status:** the pill at the top. **Ready** means at least one provider is fully set up: connected, with a sending number and, when you use your own account, candidate replies turned on. While setup is incomplete, it shows how many steps are left. **Not set up** means no provider is connected yet. **Off** means the Text Messages add-on isn't turned on for your account.
* **Text messaging:** one section for each provider you text through, each with its setup steps: the provider account, your sending number and, when you use your own account, candidate replies. If Journeyfront provides your Twilio account, the account step reads **Managed by Journeyfront** and there's no candidate replies step to set up. Providers you haven't connected appear as **Add** buttons. If you use more than one provider, a provider that's ready folds up to show just its numbers. Click it to open it.
* **WhatsApp:** connect WhatsApp through one of your providers. See [WhatsApp](/integrations/texting-providers/whatsapp).
* **Billing:** your messaging balance if Journeyfront provides your Twilio account, or a note that your provider bills you directly. **Show transactions** lists your usage history. See [Add-ons and credits](/account-setup/add-ons).

If the status reads **Off**, ask your Customer Success Manager to turn on the Text Messages add-on.
## Set up texting
**1. Connect a provider**
If Journeyfront provides your Twilio account, this is done for you. Otherwise, connect [your own Twilio account](/integrations/texting-providers/twilio#connect-your-own-twilio-account) or [Webex Connect](/integrations/texting-providers/webex-connect).
**2. Add a sending number**
Add the number you'll text candidates from in **Settings**, then **Phone Numbers**.
**3. Turn on candidate replies**
Without this step, texts go out but candidate replies never reach Journeyfront.
**4. Connect WhatsApp (optional)**
See [WhatsApp](/integrations/texting-providers/whatsapp).
When the status at the top of the page reads **Ready**, your team can start texting candidates.
## Phone numbers
Go to **Settings**, then **Phone Numbers** to manage the numbers your team sends from.
* **Add a number** with the add button. If you use more than one provider, choose the provider the number belongs to in **Sends Through**.
* **Channels** shows what each number can do: an SMS pill, and a WhatsApp pill once the number is connected to WhatsApp. Numbers on Webex Connect show "via Webex Connect".
* **Remove a number** with the remove icon on its row. It's hidden from messaging everywhere, and its message history is kept.

> [!TIP]
>
> A number connected to WhatsApp can't be removed until you disconnect WhatsApp.
## FAQ
> [accordion] Can we use more than one messaging provider?
>
> Yes. Each phone number belongs to one provider, and each message goes out through the provider of the number it's sent from. Replies, delivery updates and opt-outs from every provider show up on the same Candidate Application.
> [accordion] Why don't I see a messaging balance?
>
> A balance only appears when Journeyfront provides your Twilio account. If you use your own Twilio account or Webex Connect, your provider bills you directly.
> [accordion] Texts are going out, but we never see replies. Why?
>
> Check the **Candidate replies** step for your provider on the Text Messages page. It shows whether replies can reach Journeyfront and what to do if they can't.
> [accordion] Can I buy phone numbers in Journeyfront?
>
> No. Buy or move numbers in your Twilio console or Webex Connect, then add them in **Settings**, then **Phone Numbers**.
## Related
> [card] [Text messages and WhatsApp](/communication/text-messages)
>
> How your team messages candidates day to day.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> Your messaging balance and usage history.
> [card] [Calling](/integrations/calling)
>
> Connect Webex Contact Center or QUO.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
# Twilio
Source: https://help.journeyfront.com/integrations/texting-providers/twilio
Text candidates through Journeyfront's Twilio account or connect your company's own Twilio account.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission. Connecting your own account also needs someone who can make changes in your Twilio console.
>
> **Availability:** The Text Messages add-on needs to be turned on for your account. Ask your Customer Success Manager.
Twilio is the most common way to text candidates from Journeyfront. You can use a Twilio account that Journeyfront provides and manages for you, or connect your company's own Twilio account, with your own numbers, carrier registrations and billing.
For how texting providers compare, the Text Messages page and phone numbers, see [Texting providers](/integrations/texting-providers). To connect WhatsApp through Twilio, see [WhatsApp](/integrations/texting-providers/whatsapp#whatsapp-through-twilio).
## Journeyfront's Twilio account
When Journeyfront provides your Twilio account, there's nothing for you to set up. Your Customer Success Manager connects it and adds your number, and the Twilio section reads "Managed by Journeyfront." There's no candidate replies step to set up. Usage comes out of the prepaid messaging balance on the **Billing** card. See [Add-ons and credits](/account-setup/add-ons).
Because Journeyfront manages these accounts, you can't change their credentials from your settings. Contact your Customer Success Manager if something needs to change.
## Connect your own Twilio account
You'll need:
* Your Twilio **Account SID** and primary **Auth Token**
* A phone number in your Twilio account that can send texts
* A **Messaging Service** in Twilio that includes that number (needed for candidate replies)
**1. Add Twilio**
Go to **Settings**, then **Add-Ons**, then **Text Messages**. Under **Text messaging**, click **Add Twilio**, or open the Twilio section if it's already there.
**2. Enter your Account SID**
It starts with "AC" and is on the Account Info panel of your Twilio console.
**3. Enter your Auth Token**
Use your primary auth token, not an API key secret.
**4. Connect Twilio**
Click **Connect Twilio**. Journeyfront checks your credentials with Twilio before saving them. After that, it only ever shows the last four characters of your Account SID.
> [!TIP]
>
> Don't use a Twilio API key (it starts with "SK"). Journeyfront refuses it, because texts would still go out but candidate replies couldn't be matched to your account.
To change credentials later, for example after you rotate your token in Twilio, click **Update credentials** on the **Twilio account** step, enter the new ones and click **Save credentials**. Journeyfront checks the new ones before replacing the old ones.
## Add your Twilio sending number
**1. Open Phone Numbers**
On the **Sending number** step, click **Add number** (or **Manage numbers**). This opens **Settings**, then **Phone Numbers**. Click **+ Phone Numbers**.
**2. Choose Twilio**
If you also text through Webex Connect, set **Sends Through** to **Twilio**.
**3. Pick your number**
Choose your number from the list of numbers in your Twilio account that aren't added yet, and save. Numbers that can't send texts show "(no SMS)" and can't be picked. If your number isn't listed, click **Don't see your number? Enter it manually** and type it in.
To get a new number, buy it in your Twilio console. Once it's there, it appears in this list.
## Turn on Twilio candidate replies
Twilio sends candidate replies to Journeyfront through the Messaging Service that holds your sending number. The **Candidate replies** step checks it for you:
| What the step shows | What to do |
| - | - |
| **On** | Nothing. Replies already reach Journeyfront. |
| **Off**, with **Enable replies** | Click **Enable replies** and Journeyfront sets up your Messaging Service. If Twilio doesn't say which service holds your number, you'll see a list of services: choose the right one. |
| Your number isn't in any service | In Twilio, go to **Messaging**, then **Services**, and add your number to a service's sender pool. Then click **Check again**. |
| Your Twilio account has no messaging services | Create a Messaging Service in Twilio and add your number to it. Then click **Check again**. |
Changed something in Twilio? Click **Changed something in Twilio? Check again** to refresh the step.
## Twilio troubleshooting
| What you see | What to try |
| - | - |
| Your Account SID is refused as an API key | Copy the Account SID that starts with "AC" from your Twilio Account Info panel, and use your primary auth token. |
| Texts send, but candidate replies never show up | Look at the **Candidate replies** step. It tells you whether your Messaging Service sends replies to Journeyfront, and what to do if not. |
| **Candidate replies** went back to **Off** | Click **Enable replies** again. |
| The step says your account has no messaging services | Create a Messaging Service in Twilio, add your number to its sender pool, then click **Check again**. |
| Your number isn't in the list | It's already added, it can't send texts (listed as "(no SMS)"), or it's in a different Twilio account from the one you connected. You can also click **Don't see your number? Enter it manually**. |
| A message shows **Not delivered** | Hover over it to see the reason. |
## FAQ
> [accordion] Should we use Journeyfront's Twilio account or our own?
>
> Journeyfront's Twilio account is the simplest way to start. If you already run Twilio, with your own numbers, carrier registrations and billing, connect your own account.
> [accordion] Do we need to register with U.S. carriers?
>
> U.S. carriers require A2P 10DLC registration for reliable texting to U.S. numbers. With your own Twilio account, you complete it in Twilio. If Journeyfront provides your account, ask your Customer Success Manager.
> [accordion] Who bills us for texts?
>
> With Journeyfront's Twilio account, usage comes out of your prepaid messaging balance in Journeyfront. With your own Twilio account, Twilio bills you directly.
## Related
> [card] [Texting providers](/integrations/texting-providers)
>
> Compare providers, and manage phone numbers and billing.
> [card] [WhatsApp](/integrations/texting-providers/whatsapp)
>
> Connect a WhatsApp Business number through Twilio.
# Webex Connect
Source: https://help.journeyfront.com/integrations/texting-providers/webex-connect
Text and WhatsApp candidates through your company's own Webex Connect account, numbers and contract.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission, together with someone who can make changes in your Webex Connect portal.
>
> **Availability:** The Text Messages add-on needs to be turned on for your account. Ask your Customer Success Manager. Webex Connect bills you directly for messages.
If your company uses Webex Connect for messaging, you can text and WhatsApp candidates through your own Webex Connect account, numbers and contract. It works alongside Twilio if you use both.
For how texting providers compare, the Text Messages page and phone numbers, see [Texting providers](/integrations/texting-providers). To connect WhatsApp through Webex Connect, see [WhatsApp](/integrations/texting-providers/whatsapp#whatsapp-through-webex-connect).
> [!NOTE]
>
> Webex Connect is for texting and WhatsApp. To call candidates through Webex, see [Webex Contact Center](/integrations/calling/webex-contact-center), a separate product.
You'll need access to your Webex Connect portal, with:
* The Webex Connect **service** you'll text candidates from, and its **service key** (on the service's API tab)
* A **phone number** in Webex Connect that can send texts
* For WhatsApp: a **WhatsApp app** for your number, verified with Meta in Webex Connect, and approved WhatsApp templates
## Connect your service
**1. Add Webex Connect**
Go to **Settings**, then **Add-Ons**, then **Text Messages**. Under **Text messaging**, click **Add Webex Connect**. If you already text through Twilio, you'll find it next to **Also text through**.
**2. Choose your region**
Choose the **Region** where your Webex Connect account is hosted, for example United States (Oregon) or Europe (Ireland). Your Webex Connect administrator can tell you which one.
**3. Paste your service key**
Paste your **Service Key** from the API tab of your service in Webex Connect.
**4. Connect**
Click **Connect Webex Connect**. Journeyfront checks the key with Webex Connect before saving it. If the key is refused, the reason appears under the field.
After you connect, Journeyfront only ever shows the last four characters of your key.
## Add your Webex Connect sending number
**1. Open Phone Numbers**
On the **Sending number** step, click **Add number**. This opens **Settings**, then **Phone Numbers**. Click **+ Phone Numbers**.
**2. Choose Webex Connect**
In **Sends Through**, choose **Webex Connect**.
**3. Type the number**
Type the number in international format, exactly as it appears in Webex Connect (for example, +15017122661), and save. It shows "via Webex Connect" on your Phone Numbers page.
> [!WARNING]
>
> Journeyfront can't look up your Webex Connect numbers, so double-check the number. If it doesn't match Webex Connect exactly, texts won't send and replies won't reach Journeyfront.
## Turn on Webex Connect candidate replies
Texts go out as soon as your number is added, but candidate replies only reach Journeyfront once you add a webhook in Webex Connect.
**1. Copy the webhook URL**
On the **Candidate replies** step, copy the **Webhook URL**.

**2. Add an Outbound Webhook in Webex Connect**
In Webex Connect, go to **Assets**, then **Integrations**, and choose **Add Integration**, then **Outbound Webhook**.
**3. Set it up**
For **Entity**, choose the phone number you text candidates from. Tick **Incoming Message**. Paste the webhook URL as the endpoint and save.
**4. Check it in Journeyfront**
Webex Connect checks the URL when you save, and the **Candidate replies** step turns green. If you had the Journeyfront page open already, click **Check again**.
> [!TIP]
>
> Keep the webhook URL private: it's unique to your account. Once replies are on, you can find it again under **Show webhook URL**.
## Update your key or disconnect
* **Update your key:** on the Webex Connect service step, click **Update key** and paste the new key. If your Webex Connect service lets you keep two active keys, create the new key, save it in Journeyfront, then delete the old one to avoid downtime.
* **Disconnect Webex Connect:** click **Disconnect** and confirm. Your Webex Connect numbers are removed from Journeyfront, including a WhatsApp number connected through Webex Connect, and message history is kept. If you reconnect later, add the numbers again, and update your webhooks in Webex Connect, because you'll get a **new webhook URL**.
## Webex Connect troubleshooting
| What you see | What to try |
| - | - |
| Your key is refused | Copy the key from the API tab of the service your number belongs to, and check that you chose the right region. |
| **Candidate replies** stays off | In Webex Connect, check that the Outbound Webhook exists, its Entity is your texting number, **Incoming Message** is ticked and the full URL was pasted. Then click **Check again**. |
| Text replies arrive, but WhatsApp replies don't | Add the second Outbound Webhook with your WhatsApp app as the Entity. See [WhatsApp through Webex Connect](/integrations/texting-providers/whatsapp#whatsapp-through-webex-connect). |
| Texts fail from a number that works in Webex Connect | Make sure the number on your Phone Numbers page matches Webex Connect exactly and was added with Webex Connect as its provider. If not, remove it and add it again. |
| A message shows **Not delivered** | Hover over it to see the reason from Webex Connect. |
| Replies stopped after reconnecting | Reconnecting gives you a new webhook URL. Update your webhooks in Webex Connect. |
| Numbers are missing after reconnecting | Disconnecting removes your Webex Connect numbers. Add them again in **Settings**, then **Phone Numbers**. |
| Nothing arrives while testing with a sandbox | A Webex Connect sandbox may only send to phone numbers you've verified in it. Check your sandbox settings in Webex Connect. |
## FAQ
> [accordion] Can Journeyfront set up the Webex Connect webhooks for us?
>
> No. Webex Connect only allows webhooks to be set up in its own portal. Journeyfront gives you the exact URL and steps.
> [accordion] Can we write WhatsApp templates in Journeyfront if we use Webex Connect?
>
> No. With Webex Connect, you write WhatsApp templates and get them approved in Webex Connect, then link them in Journeyfront. See [Link a WhatsApp template from Webex Connect](/integrations/texting-providers/whatsapp#link-a-whatsapp-template-from-webex-connect). Text message templates are written in Journeyfront for every provider.
> [accordion] Is Webex Connect the same as Webex Contact Center?
>
> No. Webex Connect is Cisco's messaging platform, used for texts and WhatsApp. Webex Contact Center is for calling candidates. See [Webex Contact Center](/integrations/calling/webex-contact-center).
> [accordion] Who bills us for Webex Connect messages?
>
> Webex Connect bills you directly, so there's no messaging balance in Journeyfront.
## Related
> [card] [Texting providers](/integrations/texting-providers)
>
> Compare providers, and manage phone numbers and billing.
> [card] [WhatsApp](/integrations/texting-providers/whatsapp)
>
> Connect WhatsApp through Webex Connect.
# WhatsApp
Source: https://help.journeyfront.com/integrations/texting-providers/whatsapp
Connect your company's WhatsApp Business number through Twilio or Webex Connect.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission. Through Twilio, you also need someone with admin access to your company's Meta (Facebook) Business account. Through Webex Connect, you need someone who can make changes in your Webex Connect portal.
>
> **Availability:** WhatsApp is part of the Text Messages add-on, so there's no separate WhatsApp add-on. Ask your Customer Success Manager to turn on Text Messages.
WhatsApp goes through the same provider you text through, so set up texting first with [Twilio](/integrations/texting-providers/twilio) or [Webex Connect](/integrations/texting-providers/webex-connect). Each account connects one WhatsApp number.
Go to **Settings**, then **Add-Ons**, then **Text Messages**. On the **WhatsApp** card, you'll see **Connect WhatsApp**, or **Connect through Twilio** and **Connect through Webex Connect** if you use both providers.
For how recruiters send WhatsApp messages and write templates, see [WhatsApp](/communication/whatsapp).
## WhatsApp through Twilio
You'll need:
* The number you'll use for WhatsApp, already added in **Settings**, then **Phone Numbers**
* Someone with admin access to your company's Meta (Facebook) Business account, because you'll sign in to Facebook during setup
**1. Start the connection**
Go to **Settings**, then **Add-Ons**, then **Text Messages**. On the **WhatsApp** card, click **Connect WhatsApp** (or **Connect through Twilio**).
**2. Choose the number and display name**
Choose the **phone number** candidates will message you on, and confirm your **display name**. This is what candidates see, and it's pre-filled with your company name.

**3. Open Facebook**
Click **Connect your WhatsApp Business Account**. A Facebook window opens.
**4. Finish in Facebook**
Sign in and select **your own** business account. When asked about the phone number, choose **"Use a display name only."** Journeyfront attaches your real number right after.





**5. Wait for Online**
When the window closes, the **WhatsApp** card shows your number as connected. The status usually moves to **Online** within a few minutes, which means you're ready to message. The number also shows up in your Meta WhatsApp Manager, usually shortly after.

> [!TIP]
>
> The two most common setup mistakes happen in the Facebook window: selecting a business account that isn't yours, and not choosing **"Use a display name only."** If Meta shows a placeholder 555 number next to yours, that's expected and harmless.
### WhatsApp connection status
The WhatsApp card shows a connection status. It doesn't refresh on its own, so reload the page to see the latest status.
| Status | What it means |
| - | - |
| Registering | Your number is being registered with WhatsApp. This usually takes a few minutes. |
| Verifying | WhatsApp is waiting for proof that you own the number. |
| Online | Registered and ready to send and receive. |
| Offline | Registered but can't send right now. Check WhatsApp Manager for details. Most often seen after reconnecting too quickly, and usually clears up on its own within about 10 minutes. |
| Failed | Registration failed. Disconnect and connect again. |
## WhatsApp through Webex Connect
First, in your Webex Connect portal:
**1. Create a WhatsApp app**
Go to **Assets**, then **Apps**, and create a **WhatsApp app** for your number. Meta verifies your business as part of this. A number generally can't be registered with WhatsApp in two places at once, so it shouldn't be in use with WhatsApp anywhere else.
**2. Copy the App ID**
Once the app is live, copy its **App ID**. It starts with "a\_".
**3. Add a second Outbound Webhook**
Add another Outbound Webhook the same way as for [text replies](/integrations/texting-providers/webex-connect#turn-on-webex-connect-candidate-replies), but choose your **WhatsApp app** as the Entity. Use the same webhook URL and tick **Incoming Message**.
Then, in Journeyfront:
**1. Start the connection**
Go to **Settings**, then **Add-Ons**, then **Text Messages**. On the **WhatsApp** card, click **Connect WhatsApp** (or **Connect through Webex Connect**).
**2. Enter your details**
Enter your **WhatsApp Number** in international format and the **App ID**.
**3. Link it**
Click **Link WhatsApp**. The card shows your number as connected through Webex Connect, with a **Webhook for WhatsApp replies** link if you need the URL again.
> [!TIP]
>
> Without the second webhook, WhatsApp messages still send, but candidate replies won't reach Journeyfront.
### Link a WhatsApp template from Webex Connect
With Webex Connect, WhatsApp templates are written and approved in Webex Connect (under **Tools**, then **Templates**). Then you link each one in Journeyfront.
**1. Copy the template from Webex Connect**
Open the approved template in Webex Connect and copy its **template ID** and its message.
**2. Open the template in Journeyfront**
Go to **Settings**, then **Templates**, then **Message Template**. Click **Add Message Template**, or edit an existing one, and click the **WhatsApp** tab.
**3. Paste the ID and message**
Paste the **Template ID**. Paste the message into **Approved Message** exactly as it was approved. Variables like `$(name)` or `{{name}}` are picked up automatically.
**4. Fill the variables**
Under **Fill Each Variable With**, choose the candidate detail for each variable: First Name, Last Name, Company Name, Job Name, Job Invite Link or Current Step. A variable fills itself in only when its name exactly matches a candidate detail's key: `first_name`, `last_name`, `company_name`, `job_name`, `job_invite_link` or `current_step_name`.
**5. Save**
The template shows as **Active** and is ready to send. To unlink it later, clear its Template ID and save.
Writing WhatsApp templates in Journeyfront for Twilio numbers is covered in [WhatsApp](/communication/whatsapp#whatsapp-templates).
## Disconnect or reconnect WhatsApp
Go to **Settings**, then **Add-Ons**, then **Text Messages**, find the **WhatsApp** card, click **Disconnect** and confirm. Your templates and message history are kept. To reconnect, use **Connect WhatsApp** again.
* **Twilio:** if you're reconnecting the same number, wait about 10 minutes after disconnecting.
* **Webex Connect:** disconnecting only stops Journeyfront from sending WhatsApp from that number. Your WhatsApp app stays set up in Webex Connect, and if the number also texts, it keeps texting. Disconnecting Webex Connect itself also removes the WhatsApp number from Journeyfront.
> [!TIP]
>
> A number connected to WhatsApp can't be removed from **Phone Numbers** until you disconnect WhatsApp.
## WhatsApp limits and quality
WhatsApp (Meta) sets its own rules for your business account. None of this is configured in Journeyfront, but it helps to know what to expect:
* **Daily limit on new conversations.** Meta limits how many unique candidates a new WhatsApp number can start conversations with in 24 hours, often starting around 250. WhatsApp raises the limit automatically as you build a good sending history. Replying in a conversation the candidate started doesn't count.
* **Limits are shared across your business.** They apply to your whole Meta Business account, not to each number separately.
* **Verifying your business raises your limits.** If you plan to message candidates at volume, complete business verification with Meta.
* **Quality rating.** WhatsApp rates your number based on how candidates react. If many candidates block or report you, your limits can drop or your templates can be paused. Messages that are relevant, expected and tied to the candidate's application keep your rating healthy.
You can see your number's current limit and quality rating in your Meta WhatsApp Manager.
## FAQ
> [accordion] Do we need a separate add-on for WhatsApp?
>
> No. WhatsApp is part of the Text Messages add-on and goes through the same provider you text through.
> [accordion] Can we connect more than one WhatsApp number?
>
> No. Each account connects one WhatsApp number.
> [accordion] Can we write WhatsApp templates in Journeyfront if we use Webex Connect?
>
> No. With Webex Connect, you write WhatsApp templates and get them approved in Webex Connect, then link them in Journeyfront. With Twilio, you write them in Journeyfront.
## Related
> [card] [Texting providers](/integrations/texting-providers)
>
> Compare providers, and manage phone numbers and billing.
> [card] [WhatsApp](/communication/whatsapp)
>
> Message candidates on WhatsApp day to day.
# Your availability and calendar
Source: https://help.journeyfront.com/interviews/availability
Connect your calendar, set your time zone and video service, and choose the hours candidates can book with you.
> [!NOTE]
>
> **Who can do this:** Everyone who interviews candidates. Each person sets up their own calendar and availability under **Interviews**.
Before candidates can book time with you, Journeyfront needs to know when you're free. You connect your calendar once in **My Profile**, then set your regular interviewing hours in **My Availability**. From then on, candidates only see times that are open on your real calendar and inside the hours you chose, and booked interviews land on your calendar automatically.
## Set up My Profile
**1. Open My Profile**
Click **Interviews** (1) at the top of the app, then **My Profile** (2).

**2. Connect your calendar**
Under **Synced Calendar**, choose your calendar provider, sign in to it and allow access. Your connected account then appears under **Synced Calendar**. See [Calendars and video](/integrations/calendars) for the providers you can connect.
**3. Choose your Preferred Calendar**
If you connected more than one calendar, pick the one interviews should be added to under **Preferred Calendar**. With one calendar, it's selected for you.
**4. Set your Time Zone**
Choose the time zone you work in.
**5. Choose your video service**
Under **Conferencing**, pick the video service to use for your video interviews. If it isn't in the list, click **Add Conferencing Service**, sign in to it and allow access, then pick it.
Each change saves as soon as you make it.
> [!TIP]
>
> Connect the calendar you actually live in, the one with your meetings, lunch and time off. Journeyfront can only keep candidates out of times it can see are busy.
## Set your weekly availability
**1. Open My Availability**
Go to **Interviews**, then **My Availability**. If you haven't connected a calendar yet, the page asks you to do that on **My Profile** first.
**2. Mark your interviewing hours**
The weekly grid shows 8am to 6pm in 30-minute blocks, in your time zone from **My Profile**. Blue blocks are times candidates can book; white blocks are not. Click a block to switch it.
**3. Save**
Click **Save Availability**. You'll see "Availability saved".

> [!TIP]
>
> Mark your normal working hours as available, then leave meetings, breaks and focus time to your calendar. Journeyfront removes anything that's busy on your calendar, so you rarely need to change the grid.
### Fine-tune when you can be booked
Below the grid, these settings save as soon as you change them:
| Setting | What it does | Options |
| - | - | - |
| **Scheduling Period** | How far in advance candidates can book with you | 1, 3, 7, 14, 30 or 60 days |
| **Buffers** | Free time you need **Before** and **After** each interview | None, or 5, 10, 15, 30 or 60 minutes |
| **Minimum Notice** | How soon before an interview starts it can still be booked | None, or 1, 2, 4, 12, 24, 36 or 48 hours |
> [!TIP]
>
> A short buffer after interviews, like 10 or 15 minutes, gives you time to finish your feedback before the next candidate. And a few hours of **Minimum Notice** stops someone booking a slot that starts in five minutes.
### Ignore Event Keyword
Some calendar events don't really block you, like a recurring "admin time" placeholder. Click **Copy** next to **Ignore Event Keyword** and paste the text, `{Journeyfront - Ignore Event}`, into that event's description on your calendar. Journeyfront then treats that time as available for interviews.

Only use it on events you'd genuinely move for a candidate. A real meeting with the keyword in its description can be booked over.
## Best practices
Small habits keep your calendar bookable and stop double bookings, especially when you run many interviews a week.
* **Keep your connected calendar current.** Journeyfront only knows you're busy from your calendar. Put meetings, lunch, training and time off on it, even short ones.
* **Set realistic hours in My Availability.** Mark only the hours you really interview, not your whole workday. Leave time for feedback and other work, and adjust the grid when your schedule changes, such as a new shift or a regular team meeting.
* **Use a buffer after interviews.** 10 to 15 minutes under **Buffers**, **After** gives you time to finish feedback before the next candidate.
* **Set Minimum Notice.** A few hours stops candidates booking a slot that starts in minutes. For same-day hiring events, lower it for the day, then set it back.
* **Use the ignore keyword for placeholder blocks.** Recurring "focus time" or "admin time" holds can quietly use up your week. Add `{Journeyfront - Ignore Event}` to the ones you'd give up for an interview.
* **Block holidays on your calendar.** Add holidays and days off to your connected calendar as busy events. To close dates for everyone on one interview, like a site holiday, whoever sets up the interview can add **Date exceptions** to its activity hours.
* **Check the Availability Preview.** After you change your hours, ask whoever sets up the interview to open its **Availability Preview**, or open it yourself if you can, to see the times candidates will actually be offered.
* **Keep your time zone right.** If you travel or move, update **Time Zone** in **My Profile** so your hours line up.
> [card] [Candidate self-scheduling](/interviews/self-scheduling#add-or-block-specific-dates)
>
> Date exceptions, activity hours and the Availability Preview for an interview.
## How your availability is used
A time is offered to a candidate only when all of these are true:
* It's inside your blue hours in **My Availability**.
* Your connected calendar shows you as free, including your buffers.
* It's within your **Scheduling Period** and after your **Minimum Notice**.
* It fits the interview's own settings, such as its length, how many interviewers must be free together, and any activity hours set for that interview.
If you haven't saved any hours in **My Availability**, you offer no times at all, and the interview's **Scheduling Options** flags you to whoever sets it up. There's no default schedule.
When a candidate books, the interview is added to your **Preferred Calendar** with your video link, if it's a video interview using **Interviewer's Default**. If you later drag the event to a new time in your calendar, Journeyfront takes the new time and emails the candidate. If you delete the event, the interview is canceled and the candidate is emailed. The interview's own settings are covered in [Set up an interview activity](/interviews/interview-activity) and [Candidate self-scheduling](/interviews/self-scheduling).
## When someone asks you to connect your calendar
If you're added as an interviewer before you've connected a calendar, whoever sets up the interview sees a note that you haven't synced your calendar, and can click **Invite to Sync Calendar**. You'll get an email asking you to connect your calendar for interviews. Follow the steps under [Set up My Profile](#set-up-my-profile), then set your hours in **My Availability**.
## FAQ
> [accordion] Candidates can't book with me. What should I check?
>
> Work through this list:
>
> * **Calendar connected?** **Interviews**, then **My Profile**, should show your account under **Synced Calendar**.
> * **Hours saved?** Check the blue blocks in **My Availability**, and that you clicked **Save Availability**.
> * **Too narrow?** A short **Scheduling Period**, long **Buffers** or long **Minimum Notice** can leave very little open.
> * **Calendar full?** Any busy event blocks the time unless it has the ignore keyword.
> * **Interview settings?** Ask whoever set up the interview to check its length, the number of required interviewers and any activity hours. See [Candidate self-scheduling](/interviews/self-scheduling).
> [accordion] Can candidates see my calendar?
>
> No. Candidates only see the open times they can book, never your events.
> [accordion] How do I take a day off from interviews?
>
> Add the time off to your connected calendar as a busy event. Journeyfront stops offering those times. For a regular change, like no longer interviewing on Fridays, update the grid in **My Availability**.
> [accordion] I work in a different time zone from my candidates. Is that a problem?
>
> No. Set your own **Time Zone** in **My Profile**. Candidates always see open times in their own time zone.
> [accordion] Where do booked interviews go?
>
> Onto your **Preferred Calendar**, and into **Interviews**, then **My Interviews**. See [Conduct an interview](/interviews/conduct-an-interview#my-interviews).
> [accordion] Why don't I see Google Meet in the Conferencing list?
>
> Google Meet is offered when you've connected a Google calendar. For Zoom, Microsoft Teams or GoToMeeting, click **Add Conferencing Service** first.
## Related
> [card] [Calendars and video](/integrations/calendars)
>
> Which calendars and video services you can connect.
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> How candidates book from your open times.
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interviewers, length and how they're picked.
> [card] [Conduct an interview](/interviews/conduct-an-interview)
>
> Open the guide and submit feedback.
# Conduct an interview and submit feedback
Source: https://help.journeyfront.com/interviews/conduct-an-interview
Open an interview guide, score the candidate as you go, and submit your feedback.
> [!NOTE]
>
> **Who can do this:** Anyone with a Journeyfront user account at your company can open an interview guide and submit their own feedback. The **Comments** panel needs *View & Submit Comments*. Unlocking submitted feedback needs *Can Unlock Interviews*.
The interview guide keeps every interview structured: the same questions, the same scoring criteria and one place for your notes. Score as you talk, submit your feedback when you're done, and your scores land on the candidate's Candidate Application right away, ready for the rest of the hiring team.
## Open the interview guide
Pick whichever way fits your day:
* **From your calendar event.** When the interview activity has **Include interview guide on calendar event** turned on, the event on your calendar has a link to the guide.
* **From My Interviews.** Go to **Interviews**, then **My Interviews**, and click the **Start Interview** icon on the interview's row. See [My Interviews](#my-interviews) below.
* **From Start.** Click **Start** at the top of the app, then **Interview**. Find the candidate under "Who are you interviewing?", click their row, and click **Start** next to the interview. Click **Preview** first if you want to read the questions before you begin.
* **From the candidate.** On their Candidate Application, open **Actions**, then **Interview**, and click **Interview Guide** on the interview. In a candidate list, the **Interview** column's **Interview Link** opens the same window.
If you're asked to sign in, sign in and the guide opens.

> [!TIP]
>
> Interviewing a walk-in, for example at a hiring event, who isn't in Journeyfront yet? Under **Start**, then **Interview**, click **New Candidate**, enter their details and choose the job req they're interviewing for. Then start the interview as usual.
### Share the guide with another interviewer
To send the guide to someone else, copy its link: **Copy Interview Link** in **My Interviews**, or **Copy Link**, then **Copy Interview Guide Link** in the candidate's **Actions**, then **Interview** window. (**Copy Candidate Scheduling Link** in the same menu copies the candidate's booking page, not the guide.) Each interviewer who opens the link fills in and submits their own feedback.
## Fill in the guide
The top of the guide shows the candidate, the job req they applied for, you as the interviewer, and the **Instructions** from your team. Then, for each question:
**1. Ask the question**
Ask it as written. Hover over an attribute's name to read its description.
**2. Take notes**
Type what the candidate said in the **Notes** box. Each note can be up to 4,000 characters.
**3. Score each attribute**
Compare the answer with the scoring criteria under each attribute and enter a score from 1 to 5 in its **Score (1-5)** box. If the answer didn't give you enough to judge an attribute, click **Unable to score**.
Your answers save automatically each time you move to another box. Click **Print** at the top if you need a paper copy.
> [!TIP]
>
> Score each question right after the candidate answers, while it's fresh, rather than at the end. And write down what the candidate actually said or did ("described calming an angry caller by repeating the issue back"), not just your impression ("great with customers"). Evidence-based notes make your scores easy for the rest of the team to trust.
### Comments
If your security role has *View & Submit Comments*, a **Comments** panel sits on the right of the guide. Click the comment icon to open or close it. It shows your team's comments on the candidate, and anything you add there appears on the Candidate Application's **Comments & Activities** tab, labeled with the interview's name. See [Comments and activity](/candidates/comments-and-notes#comments-during-an-interview).
## Save and finish later
Click **Save - I'll finish later** to keep your answers and leave. To pick up where you left off, open the guide again from any of the places above. Under **Start**, then **Interview**, the button reads **Continue**.
If you click **Close** at the top before submitting, Journeyfront asks what to do: **Yes - Save Answers**, **Yes - Discard Answers**, or **No - Cancel** to stay.
To throw away everything you've entered, click **Cancel - discard answers**, then confirm. This can't be undone.
## Submit your feedback
When you've scored every attribute, click **Submit - I'm all done**.
If anything is missing, Journeyfront points to it: every attribute needs a score from 1 to 5, or **Unable to score**. Fix the questions marked in red and submit again.
Once submitted:
* You'll see **Interview Submitted**, with links to the candidate's Candidate Application and the job req's candidates, if you have access to them.
* Your feedback is locked, and the guide shows **Submitted**.
* Your scores appear in your own column on the candidate's **Score** and **Steps** tabs, and your notes on their **Notes** tab. See [Reading a candidate's scores](/scoring/reading-scores#interviewer-scores-and-notes).
## My Interviews
**Interviews**, then **My Interviews**, lists the interviews you're booked for and the interview guides you've worked on. Use the **Search** box to find a candidate, interview or job req.
| Tab | What each row shows |
| - | - |
| **Upcoming** | The time and how soon it is (for example, today or tomorrow), the candidate's name and email, the interview and job req, and the interviewers |
| **Past** | The date and time, the candidate, the interview and job req, the status (**Not Started**, **Started** or **Completed**) and your score |
The icons on each row:
1. **Start Interview** (**Open Interview Guide** on past interviews) opens the interview guide.
2. **Open Scorecard** opens the candidate's Candidate Application.
3. **Copy Interview Link** copies the guide's link, to share with another interviewer.
4. The **â‹®** menu has the same actions, plus **Unsubmit Interview** on past interviews.

## Unlock submitted feedback
Submitted feedback is locked so scores can't quietly change after a decision. If an interviewer needs to correct theirs, someone whose security role has *Can Unlock Interviews* unlocks it:
* **From the candidate:** on the Candidate Application's **Steps** tab, expand the step with the interview, hover over the interviewer's score on the interview's row and click **Unlock Interview**, then **Yes**.

* **From My Interviews:** to unlock your own feedback, open the **Past** tab (1), click **â‹®** on the interview (2) and choose **Unsubmit Interview** (3).

While feedback is unlocked, that interviewer's score is removed from the candidate's scores. The interviewer opens the guide again, makes their changes and clicks **Submit - I'm all done**, and the score comes back.
To give someone the permission, an admin goes to **Settings**, then **Security**, edits their security role and turns on *Can Unlock Interviews*. See [Security roles](/account-setup/security-roles).
## FAQ
> [accordion] Why isn't my interview in My Interviews?
>
> **My Interviews** shows interviews that are booked with you as an interviewer, plus any interview guides you've opened. If the candidate hasn't booked yet, or someone else was picked as the interviewer, it won't be there. Open the guide from **Start**, then **Interview**, or from the candidate instead.
> [accordion] Can more than one person submit feedback for the same interview?
>
> Yes. Each interviewer fills in and submits their own guide. Every interviewer's scores show in their own column on the candidate's **Score** and **Steps** tabs.
> [accordion] Why can't I submit?
>
> Every attribute on every question needs a score from 1 to 5, or **Unable to score**. Look for the messages in red, fix those questions, and click **Submit - I'm all done** again.
> [accordion] What happens if I close my browser in the middle of an interview?
>
> Your answers save as you go, so open the guide again and continue where you left off.
> [accordion] Can I score on paper and enter it later?
>
> You can print the guide with **Print**, but the scores only count once they're entered in Journeyfront and submitted. Entering them right away keeps your team's view of the candidate up to date.
> [accordion] I submitted by mistake. Can I change my feedback?
>
> Yes, once it's unlocked. Ask someone with *Can Unlock Interviews*, or unsubmit it yourself from **My Interviews** if your role has that permission.
> [accordion] Can candidates see my notes or scores?
>
> No. Interview notes and scores are only visible to your team.
## Related
> [card] [Interview guides](/interviews/interview-guides)
>
> Build the questions and scoring criteria.
> [card] [Your availability and calendar](/interviews/availability)
>
> Set the hours candidates can book with you.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Where your feedback shows up.
> [card] [Interview notes](/interviews/interview-notes)
>
> Read every interviewer's notes and scores on the Notes tab.
# Set up an interview activity
Source: https://help.journeyfront.com/interviews/interview-activity
Add an interview to a job req's workflow and choose its interview guide, interviewers and scheduling settings.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission. Interviewers need to connect their calendar before candidates can book time with them.
An interview activity puts an interview into a job req's workflow. You choose the interview guide your interviewers follow, who can interview, and how the interview gets scheduled. Set it up once and every candidate who reaches the step can be invited, book a time and land on the right interviewer's calendar, without anyone coordinating by hand.
## Add an interview to a workflow
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the interview**
In the building blocks on the left, find **Interviews**. Drag **New Interview** into the step where the interview belongs to start from scratch, or start from one of your saved interview templates: click **Templates** under **New Interview** to show them (the number is how many you have), then drag one in to start from its questions. Click the eye icon next to a template to preview it first.

**3. Review the questions and instructions**
Click the interview in the flow. Its settings open on the right:
* **Instructions for Interviewer** starts collapsed and shows **Added** or **Not added**. Click it to expand it, then type the notes interviewers should read before they start, like how to open the interview. Candidates never see it.
* **Questions** lists what the interviewer asks, in order. Each question measures an attribute and has scoring criteria that describe a weak and a strong answer. Drag a question to reorder it, or use the pencil and trash can to edit or remove it.

**4. Add questions**
Under **Questions**, click **Add Question**. Search your question library, or tick attributes under **Quick filter by your attributes**, and click **Add** on each question you want. If the question doesn't exist yet, click **Create New Question**.

**5. Save the draft**
Click **Save Draft**. You stay in the editor. See [Build a workflow](/workflows/build).
**6. Set up scheduling**
Click the interview again and set up its scheduling (below) to choose who interviews and how candidates book.
**7. Publish**
When the workflow is ready, publish it so candidates get the interview. See [Publish workflow changes](/workflows/publish).
> [!TIP]
>
> Save the interview guides you use often as templates in **Settings**, then **Templates**, then **Interview Questions**. They're listed under **Interviews**, then **Templates**, in the workflow editor, so every team can start from the same guide.
## The interview guide
The questions, scoring criteria and instructions you set here make up the interview guide that interviewers follow and score from. Building questions and templates, and how interviewers open the guide, are covered in Interview guides.
> [card] [Interview guides](/interviews/interview-guides)
>
> Build questions and templates, then interview, score and review results.
## Open the scheduling settings
Scheduling is set up in the workflow editor. Open the job req's **Setup**, then **Workflow**, click **Create New Version** (or **Edit Draft**), and click the interview activity. In its settings on the right, find **Interview Scheduler** and click **View and Edit Details**.

> [!NOTE]
>
> **Just added the interview?** **View and Edit Details** only appears once the interview has been saved. Until then, the **Interview Scheduler** section says "Save your draft to set up interview scheduling for this activity." Click **Save Draft** at the top right, click the interview again, and **View and Edit Details** is there.
The **Scheduling Options** window opens with the settings on the left and a live preview of your interviewers' availability on the right.

### Meeting details
| Setting | What it does |
| - | - |
| **Duration** | How long the interview lasts. The default is 30 minutes. |
| **Time Slot Interval** | How often start times are offered. With a 15-minute interval, candidates see 9:00, 9:15, 9:30 and so on. |
| **Format** | **Video**, **Phone** or **In-person**. The format decides what goes on the calendar invite. |
| **Video Link** | For video interviews. **Interviewer's Default** uses each interviewer's own conferencing service, such as Zoom or Google Meet. **Custom Link** uses one link you enter. |
| **Location** | For in-person interviews, the address that goes on the calendar invite. |
Each interviewer picks their own default conferencing service, along with their calendar and time zone, in **My Profile**.
> [card] [Your availability and calendar](/interviews/availability#set-up-my-profile)
>
> Connect a calendar and choose a video service in My Profile.
### Interviewers
Under **Interviewer(s)**, click **Add Interviewer** to build the pool of people who can host this interview. Search by name or email and click a person to add them. Each row then shows how many upcoming interviews that person already has.
The first option in the list, **Assigned User**, sends the interview to whoever is assigned to the candidate. **Assigned User** takes the place of the pool: you can't add other interviewers alongside it.

| Setting | What it does |
| - | - |
| **Number of Required Interviewers** | How many people from the pool must be free at the same time for a time to be offered. **All** means everyone in the pool. |
| **Maximum Number of Interviewers** | The most people invited to any one interview. **No Maximum** invites everyone who's available. |
| **How to pick interviewers** | **List Order Priority** works down the list from the top; drag rows to change the order. **Random** picks at random. **Least Number Of Upcoming Interviews** picks whoever has the fewest interviews booked. |
For example, a one-on-one phone screen needs one interviewer, so set **Number of Required Interviewers** to 1. For a panel where any two of four senior interviewers should attend, add all four, then set both the required and maximum numbers to 2.
> [!TIP]
>
> **All** is the strictest setting and the most common reason candidates see few or no open times. For panels of three or more people, set the smallest number of required interviewers that still works.
### Calendar invite and emails
| Setting | What it does |
| - | - |
| **Event Description** | Text on the calendar invite, seen by the interviewers and the candidate. Use it for the agenda or what to prepare. |
| **Message to Candidate** | A personal note included in the email the candidate receives. |
| **Include interview guide on calendar event** | Adds a link to the interview guide on the interviewers' calendar events. Candidates don't see it. |
Candidates also get emails to schedule, to confirm the booking and to remind them before the interview. Their wording comes from your company's system email templates.
> [card] [Email templates](/communication/email-templates#system-emails)
>
> Edit the interview invite, confirmation and reminder emails.
Reminders are on by default, and each job req sets whether they go out and when.
> [card] [Job settings](/job-reqs/job-settings#interviews)
>
> Turn interview reminders on or off and choose their timing on the job req.
### Scheduling settings
These switches control what candidates can do with their scheduling link. The numbers match the picture.

| # | Setting | What it does | Default for a new interview |
| - | - | - | - |
| 1 | **Accept new interviews** | Pauses new bookings without deleting the activity. Candidates who already booked keep their times. | On |
| 2 | **Send email invite to candidates when entering step** | Emails every candidate a scheduling link as soon as they reach this step. Turn it off to invite candidates yourself. | Off |
| 3 | **Interview link expiry** | Makes scheduling links stop working after the number of days you set in **Days until link expires**. | On, 30 days |
| 4 | **Allow candidates to reschedule** | Lets candidates pick a new time from the same link after they book. When off, they can only cancel, with a reason. | Off |
| 5 | **Allow candidates to request more time** | Lets candidates ask for more availability when no time works for them. | On |
> [!TIP]
>
> **Send email invite to candidates when entering step** starts out off. Turn it on if you want candidates invited automatically when they reach the step.
Changes to these settings reach invites you've already sent: the scheduling, reschedule and request-more-time settings apply to every open interview, and a new link expiry or interviewer pool applies to invites that haven't been booked yet. Booked interviews keep their time and interviewers. To see how each setting changes the candidate's experience, read [Candidate self-scheduling](/interviews/self-scheduling).
### Check the availability preview
The right side of the window shows a weekly calendar of when your interviewers are free for an interview of this length. Blue blocks are times candidates could book. Use the arrows below the calendar to move between weeks. Check it before you save: if there's very little blue, candidates will see very few open times.

> [!TIP]
>
> If the preview looks thin, add interviewers to the pool, lower **Number of Required Interviewers**, or ask interviewers to open up their availability. If the preview asks you to select a user with a synchronized calendar, none of the interviewers in the pool have connected their calendar yet. An interviewer who hasn't connected shows **Invite to Sync Calendar** in the pool; click it to invite them. An interviewer who hasn't saved working hours in **My Availability** is flagged too: they offer no times until they do. The preview uses exactly the same rules as the candidate's booking page.
When everything looks right, click **Save Settings**. It stays grayed out until at least one interviewer in the pool has connected their calendar (or you use **Assigned User**). In-person interviews also need a **Location**.
## Book an interview for one candidate
You don't have to wait for a candidate to book. You can send one candidate a scheduling link or pick a time for them from their Candidate Application.
> [card] [Schedule an interview for a candidate](/interviews/schedule-for-a-candidate)
>
> Share availability or book a time for one candidate.
## FAQ
> [accordion] Can different job reqs use different interviewers for the same kind of interview?
>
> Yes. Each job req has its own workflow, so each interview activity has its own interviewers and settings, even when the activity has the same name on another job req.
> [accordion] How does List Order Priority decide who interviews?
>
> Journeyfront works down the **Interviewer(s)** list from the top and picks the first people who are free at that time. To favor someone, drag them to the top. To spread interviews more evenly, choose a different option in **How to pick interviewers**.
> [accordion] Why don't the open times match my interviewer's calendar?
>
> Check that the interviewer has connected their calendar in **Interviews**, then **My Profile**. Then check their settings in **My Availability**, such as how far ahead they can be booked, buffers between meetings, and minimum notice. Finally, make sure the interview's **Duration** and **Time Slot Interval** fit the free time on their calendar, and that any activity hours aren't narrowing things more than you meant.
> [accordion] What happens to booked candidates if I turn off Accept new interviews?
>
> Nothing. Their interviews stay booked and they can still see their interview details. The setting only stops new bookings.
> [accordion] Can I still book a candidate when Accept new interviews is off?
>
> Yes. Use **Schedule Time** from the candidate's Candidate Application. Only the candidate's own scheduling link is paused. See [Schedule an interview for a candidate](/interviews/schedule-for-a-candidate).
> [accordion] An interviewer needs to change feedback they already submitted. What should they do?
>
> Submitted feedback is locked. Ask someone with the *Can Unlock Interviews* permission to unlock it so the interviewer can make changes.
> [accordion] How is this different from using a separate scheduling tool?
>
> Scheduling is built into the candidate's workflow. Bookings, statuses, reminders and interview feedback all live on the Candidate Application, feed your reports and automation, and never need to be synced with another system.
## Related
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> Scheduling links, activity hours and what candidates see.
> [card] [Schedule an interview for a candidate](/interviews/schedule-for-a-candidate)
>
> Send one candidate a link or book a time for them.
> [card] [Interview guides](/interviews/interview-guides)
>
> Questions, scoring criteria and templates.
> [card] [Workflows overview](/workflows/overview)
>
> How steps and activities make up a job req's workflow.
> [card] [Attributes](/scoring/attributes)
>
> The traits and skills each interview question measures.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> How interview scores fit into a candidate's overall score.
# Interview guides
Source: https://help.journeyfront.com/interviews/interview-guides
Build the questions, scoring criteria and instructions interviewers follow, reuse them with templates, and add them to a job req.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* manage the interview question library and templates. Users with the *Manage Job Req Settings* permission add interview guides to a job req. Editing a question candidates have already been interviewed with needs *Edit Locked Questions*.
An interview guide is what interviewers follow during one interview: your instructions, the questions to ask, and the scoring criteria that describe a weak, average and strong answer for each attribute. Interviewers take notes, score each answer from 1 to 5 and **submit feedback** from the guide, and their scores count toward the candidate's attribute scores alongside everything else in the workflow.
Because every candidate gets the same questions and every interviewer uses the same criteria, you can compare candidates fairly, even when different people interview them.
## What's in an interview guide
| Part |
What it does |
| **Instructions for Interviewer** |
Shown at the top of the guide. Use it for how to open the interview, what to cover, and anything interviewers shouldn't ask. |
| **Questions** |
What the interviewer asks, in order. Each question measures one or more [attributes](/scoring/attributes). |
| **Scoring criteria** |
For each attribute, what an answer worth 1, 2, 3, 4 or 5 sounds like. Interviewers see them next to the score box. |
Interviewers also get a notes box under every question and, if their security role allows comments, a **Comments** panel. See [Conduct an interview](/interviews/conduct-an-interview).

## Set up interview guides
Setting up interview guides happens in two places:
* **Settings** holds what your whole company shares: the interview question library (**Measurements**, then **Interview Questions**), plus reusable scoring criteria and question templates (**Templates**).
* **The job req's workflow** is where a guide is used. Each interview activity in the workflow has its own instructions and list of questions, picked from the library or started from a template.
Build the library and templates once, then add an interview to each job req that needs one.
### Build your interview question library
Interview questions live in a library your whole company shares, so a good question can be reused on every job req.
**1. Open the library**
Click the gear icon (1) to open **Settings**, then go to **Measurements** (2), then **Interview Questions** (3). Search or sort the list by **Question Name** or **Question**.

**2. Add a question**
Click **Question**. Write the question as the interviewer should ask it, and give it a short **Question Name** so it's easy to find later.
**3. Choose what it measures**
Under **Attribute**, pick an attribute from **Select Attribute**, or click **Add Attribute** to create one. For **Response Type**, choose **Multiple choice**, the only type interview questions use: the interviewer scores the answer on your scale.
**4. Write the scoring criteria**
Click **Option** to add a row for each score, from 1 to 5, and describe in the **Label** what an answer at that level looks like. Or click **Templates** and **Use Template** to start from a saved scale (see below).
**5. Measure more than one attribute (optional)**
One question can measure several attributes, each scored separately. Click **Attribute** next to "What Attribute(s) does this question measure?" and repeat the last two steps.
**6. Check the preview and save**
The **Live Preview** on the right shows the question the way interviewers will see it. Click **Save**.

> [!TIP]
>
> Write criteria that describe what you'd actually hear. "Gives a specific example of resolving a conflict with a teammate, and two or more steps they took" is much easier to score consistently than "Good teamwork". When your criteria are concrete, two interviewers hearing the same answer give the same score.
### Edit, clone or delete a question
Use the icons on the question's row:
1. **Clone** makes a copy you can change, after you confirm. It's the easiest way to create a variation of an existing question.
2. **Edit** opens the question. Changing its wording changes it everywhere the question is used.
3. **Delete** removes the question after you confirm. It's only offered for questions that haven't been used yet.

Once candidates have been interviewed with a question, it's **locked** so their scores keep meaning the same thing. To change a locked question, clone it and use the copy. Users with *Edit Locked Questions* see **Edit Anyway**; Journeyfront then warns that the change applies for everyone who has already answered and can't be undone, and asks you to confirm with **Yes - Proceed**.
> [!TIP]
>
> Only edit a locked question for small fixes like spelling. For anything that changes its meaning, clone it, so past candidates' scores stay comparable.
### Save scoring criteria as a template
If you use the same scale on many questions, for example a standard 1 to 5 scale for communication, save it once.
**1. Open Scoring Criteria templates**
Go to **Settings**, then **Templates**, then **Scoring Criteria**, and click **Scoring Criteria**.
**2. Build the scale**
Enter a **Template Name**, then a score and label for each option. Scores must be between 1 and 5.
**3. Save**
Click **Save**. The template is now available from **Templates** on every question you create or edit.
Journeyfront's built-in templates can be used but not edited or deleted.
### Create an interview question template
An interview question template is a ready-made set of questions, like "Phone screen" or "Supervisor interview", that you can drop into any job req's workflow.
**1. Open Interview Questions templates**
Go to **Settings**, then **Templates** (1), then **Interview Questions** (2), and click **Question Template** (3).

**2. Name it**
Type a name and click **Save**.
**3. Add questions**
Click the arrow next to the template to expand it (1). Its instructions and questions open below. Click **Add Question to Template** (2).

Search your library (1) and click **Add** (2) on each question you want, or click **Create New Question** (3) to write one. Questions already in the template show **Added**.

To rename a template, click its name. To remove a question from it, or delete the whole template, use the trash icon.
> [!TIP]
>
> Build one template per interview type and use it on every job req that runs that interview. Every team then interviews the same way, and your reports compare like with like.
### Add an interview guide to a job req
You add the interview, and its guide, in the job req's workflow editor.
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft) to open the editor.
**2. Drag in an interview**
In the building blocks on the left, find **Interviews**. Drag **New Interview** into the step where the interview belongs to start from scratch, or click **Templates** under **New Interview** and drag one of your interview templates to start with its questions. Click the eye icon on a template to preview it first.
**3. Open the interview**
Click the interview in the flow. Its details open on the right. Give it a clear name at the top, like "Hiring Manager Interview".
**4. Write the instructions**
Click **Instructions for Interviewer** to expand it, and type the interviewer's notes. The section shows **Added** once it has something in it.

**5. Add and arrange questions**
Under **Questions**, click **Add Question**, search your library (or tick attributes under **Quick filter by your attributes**) and click **Add**. Drag questions to put them in order, click the pencil to edit one, or the trash icon to remove it.
**6. Save the draft**
Click **Save Draft**. You stay in the editor.
**7. Publish**
When you're ready for candidates to get the change, click **Publish**. See [Publish workflow changes](/workflows/publish).

A newly added interview, and any questions you add, show a note that they'll be created when you save your draft.
Next, choose who interviews and how candidates book. Click the interview, and under **Interview Scheduler** click **View and Edit Details**. (On an interview you've just added, it says to save your draft first.) See [Set up an interview activity](/interviews/interview-activity).
> [!TIP]
>
> Aim for a handful of focused questions that each measure something the job really needs, rather than a long list. Interviewers stay on script, candidates get the same experience, and every score means something.
## Use interview guides
Once a job req's interviews are set up, the guide is where the interview happens: interviewers open it, score the candidate and submit feedback, and the hiring team reviews the results on the candidate.
### See who's scheduled
* **Interviewers:** **Interviews**, then **My Interviews**, lists the interviews you're booked for on the **Upcoming** tab, with the time, the candidate and the job req, and a button to start each one. The **Past** tab shows each interview's status (**Not Started**, **Started** or **Completed**) and your score.
* **Recruiters and hiring managers:** a candidate's **Actions**, then **Interview**, window shows each interview's status and booked time. To find every candidate in the interview step who hasn't picked a time yet, build a saved view.
> [card] [My Interviews](/interviews/conduct-an-interview#my-interviews)
>
> Your upcoming and past interviews, with buttons to start each one.
> [card] [See who hasn't booked](/interviews/who-hasnt-booked)
>
> Find candidates who haven't picked a time and help them book.
### Interview and submit feedback
Interviewers open the guide from the link on their calendar event, from **My Interviews**, from **Start**, then **Interview**, or from the candidate's **Actions**, then **Interview**, window. For each question, they take notes, score each attribute from 1 to 5 against the scoring criteria (or click **Unable to score**), and click **Submit - I'm all done** when they've finished. Submitted feedback is locked.
> [card] [Conduct an interview and submit feedback](/interviews/conduct-an-interview)
>
> Open the guide, score as you go and submit your feedback.
### Review interview scores
As soon as an interviewer submits, their scores show in their own column on the candidate's **Score** and **Steps** tabs, and their notes on the **Notes** tab. Each attribute they scored counts toward the candidate's attribute scores, weighted the way the job req's **Attributes** page sets. If an interviewer needs to change submitted feedback, someone with *Can Unlock Interviews* unlocks it from the **Steps** tab.
> [card] [Reading a candidate's scores](/scoring/reading-scores#interviewer-scores-and-notes)
>
> Where each interviewer's scores show up on the candidate.
> [card] [Interview notes](/interviews/interview-notes)
>
> Read every interviewer's notes and scores on the Notes tab.
## FAQ
> [accordion] Can I use the same question on several job reqs?
>
> Yes. Questions live in your library and can be added to any interview. Remember that changing a question's wording changes it everywhere it's used.
> [accordion] If I change a template, do job reqs that used it change too?
>
> No. Adding a template copies its list of questions into the interview. Adding or removing questions in the template later doesn't change interviews already built from it.
> [accordion] Why can't I edit a question?
>
> It's locked because candidates have already been interviewed with it. Clone it and use the copy, or ask someone with *Edit Locked Questions* to make a small fix.
> [accordion] Why can't I find a question when I add questions to an interview?
>
> Check your search and any attribute filters under **Quick filter by your attributes**. If the question doesn't exist yet, click **Create New Question** right there.
> [accordion] Do candidates see the interview guide?
>
> No. The guide, its scoring criteria and interviewers' notes are only visible to your team. Candidates only see the interview invite.
> [accordion] How do interviewers open the guide?
>
> From the link on their calendar event, from **Interviews**, then **My Interviews**, or from **Start**, then **Interview**. See [Conduct an interview](/interviews/conduct-an-interview).
> [accordion] How do interview scores count toward the candidate's score?
>
> Each attribute an interviewer scores counts toward that attribute, the same way other activities do. Your admins decide on the job req's **Attributes** page how much each attribute matters. See [Attributes](/scoring/attributes).
## Related
> [card] [Conduct an interview](/interviews/conduct-an-interview)
>
> Run the interview and submit feedback.
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interviewers, scheduling and calendar invites.
> [card] [Attributes](/scoring/attributes)
>
> The traits and skills each question measures.
> [card] [Build a workflow](/workflows/build)
>
> Steps and activities in the workflow editor.
# Interview notes
Source: https://help.journeyfront.com/interviews/interview-notes
Read what each interviewer recorded on their interview guide, with their scores, on the Candidate Application's Notes tab.
When interviewers fill in an interview guide, their notes and scores are saved on the candidate's Candidate Application. The **Notes** tab collects them for every interview the candidate has had, so the hiring team can compare what each interviewer saw before deciding. Candidates never see interview notes.
## Read interview notes
**1. Open the Notes tab**
On the Candidate Application, open the **Notes** tab. Each interview is listed with its **Interview Name**, **Interviewers** and **Interview Date(s)**.
**2. Expand an interview**
Click the interview to see each interviewer's notes on every question, the attribute scores they gave and their **Interview Score**.
**3. Print it if you need to**
Click the print icon on an interview's row to print just that interview.
## Notes and comments are different
Interview notes are what an interviewer records against each question in the interview guide. Comments are quick messages for the team about a candidate. Comments an interviewer adds in the interview guide's **Comments** panel go to the **Comments & Activities** tab, not the **Notes** tab. See [Comments and activity](/candidates/comments-and-notes).
## FAQ
> [accordion] Can candidates see interview notes?
>
> No. Interview notes are only visible to your team.
## Related
> [card] [Conduct an interview](/interviews/conduct-an-interview)
>
> Score questions and take notes in an interview guide.
> [card] [Interview guides](/interviews/interview-guides)
>
> Set up the questions interviewers answer.
> [card] [Comments and activity](/candidates/comments-and-notes)
>
> Team comments and the candidate's full history.
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
# Interview reminders
Source: https://help.journeyfront.com/interviews/reminders
Email candidates automatically before their interview to cut down on no-shows.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission set reminders for a job req. Changing the reminder email needs *Company Settings Access*.
No-shows waste interviewer time and slow down your hiring. Interview reminders email candidates automatically before their interview, with the time, who they're meeting and how to join, so they show up ready. Reminders are set per job req and are on by default.
## How reminders work
* Every candidate with a booked interview on the job req gets a reminder email at each time you choose before the interview.
* New job reqs send reminders **24 hours before** and **1 hour before**.
* The setting covers every interview on the job req.
* Reminders go to candidates. Interviewers have the interview on their own calendar, so their usual calendar reminders apply.
## Choose when reminders go out
**1. Open the job req's Configurations**
Open the job req and go to **Setup**, then **Configurations**. Find **Interview Reminders** in the **Interviews** card.
**2. Turn reminders on or off**
Use the switch next to **Interview Reminders**. When it's off, the card says candidates won't receive interview reminders for this job.
**3. Pick the times**
Under **Reminder Timing**, choose one or more of: **1 hour before**, **2 hours before**, **4 hours before**, **12 hours before**, **24 hours before** and **48 hours before**. Each time you pick sends its own email.
**4. Save**
Click **Save** at the top of the page.

> [!TIP]
>
> Two reminders work well for most roles: one the day before, so candidates can plan or reschedule, and one shortly before, so they don't forget. For interviews booked days ahead, add **48 hours before** too.
## What candidates receive
The reminder uses the **Interview Reminder Notification** email. By default its subject is "Your upcoming interview with" your company name, and it includes:
* Who they're interviewing with, and the date and time
* The interview type, such as video, phone or in-person
* The video link for video interviews, or the address for in-person interviews
* A link to reschedule or cancel their interview. When the interview activity has **Allow candidates to reschedule** off, the link says "cancel" instead, and the page it opens offers **Cancel Interview** with a note to contact the recruiter for a new time.
### Change the reminder email
The **Email Template** shown in the **Interviews** card is for reference. To change the wording, go to **Settings**, then **Templates**, then **E-mail Template**, open the **System Emails** tab, and edit **Interview Reminder Notification**. The change applies to reminders on every job req.
See [Email templates](/communication/email-templates) and [Template variables](/communication/template-variables).
## Good to know
* **Only booked interviews get reminders.** Candidates who haven't picked a time yet don't get interview reminders. To follow up with them, see [See who hasn't booked](/interviews/who-hasnt-booked).
* **Canceled or declined interviews don't.** If an interview is canceled, or the candidate or an interviewer declines it, no more reminders go out.
* **Late bookings skip early reminders.** A reminder only goes out at its time. If a candidate books 3 hours before the interview, the 24-hour reminder is skipped and the 1-hour reminder still goes out.
* **Each reminder is recorded** in the candidate's activity history, like other emails. See [Comments and activity](/candidates/comments-and-notes#the-activity-history).
## FAQ
> [accordion] Will a candidate get several emails if I pick several times?
>
> Yes, one email for each time you selected.
> [accordion] If I turn reminders off on one job req, does it affect others?
>
> No. Reminders are set per job req.
> [accordion] Can I send text message reminders instead?
>
> Interview reminders are emails. To text candidates about their interview, set up an automation rule with a **Send SMS to Candidate** action. See [Automation rules](/workflows/automation-rules) and [Text messages](/communication/text-messages).
> [accordion] Do interviewers get reminders?
>
> Not from Journeyfront. Each interview is on the interviewer's own calendar, so their calendar's reminders apply.
> [accordion] Why didn't a candidate get a reminder?
>
> Check that **Interview Reminders** is on for the job req, that the interview was booked before the reminder time, and that it hasn't been canceled or declined. Then check the candidate's email address, and ask them to look in their spam or junk folder.
> [accordion] Can I choose a different email template for one job req?
>
> No. Every job req uses the **Interview Reminder Notification** template. Edit that template to change what all candidates receive.
## Related
> [card] [Job settings](/job-reqs/job-settings)
>
> All of a job req's Configurations.
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> Invites, confirmations and rescheduling.
> [card] [See who hasn't booked](/interviews/who-hasnt-booked)
>
> Follow up with candidates who haven't picked a time.
> [card] [Email templates](/communication/email-templates)
>
> Edit the emails candidates receive.
# Schedule an interview for a candidate
Source: https://help.journeyfront.com/interviews/schedule-for-a-candidate
Send one candidate a scheduling link, or pick a time and book the interview for them.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team, or with *All Job Req Access*. The interview activity must already be set up with interviewers. See [Set up an interview activity](/interviews/interview-activity).
Most candidates book their own interview from the scheduling link Journeyfront emails them. When you need to step in, for example after a phone call where you agreed on a time, or when a candidate's first link went missing, you can schedule the interview for one candidate from their Candidate Application.
You have two choices:
* **Share Availability** emails the candidate a link so they pick a time themselves.
* **Schedule Time** lets you pick the time and book it for them.
## Open the candidate's interviews
**1. Open the Candidate Application**
Click the candidate's name in a candidate list to open their Candidate Application.
**2. Open Interviews**
Click **Actions** at the top right, then **Interview**. The **Interviews** window lists each interview in the candidate's workflow with its step and status.
**3. Click Schedule**
Find the interview and click **Schedule**. The **Scheduling Options** window opens.

In a candidate list, the **Interview** column's **Interview Link** opens the same window.
The window shows the interview's settings on the left, such as **Duration**, **Format** and **Interviewer(s)**, and the interviewers' availability on the right. Choose **Share Availability** or **Schedule Time** at the top of the availability.

## Send a scheduling link
**1. Choose Share Availability**
Check the availability preview to make sure there are enough open times, then click **Next**.
**2. Review the email**
Check the **Subject** and **Body**. You can insert variable fields or attach a file.
**3. Send it**
Click **Invite candidate to self schedule**. The candidate gets the email with their link.
## Book a time for the candidate
**1. Choose Schedule Time**
Click **Schedule Time**. Under **Select a time**, click an open (blue) time in the calendar.
**2. Review the booking**
Check the **Date**, **Time** and **Selected Interviewers**. To pick a different time, click **Select Other Time to Reschedule**.
**3. Book it**
Click **Schedule Interview**. The interview goes on the interviewers' calendars and the candidate is sent the details.
Once an interview is booked, the **Interviews** window shows **Edit Interview** in place of **Schedule** so you can change it.
> [!TIP]
>
> **Schedule Time** still works when **Accept new interviews** is off for the interview activity. Only the candidate's own scheduling link is paused.
## FAQ
> [accordion] Should I share availability or book a time?
>
> Share availability when the candidate can choose for themselves: it saves you a phone call. Book a time when you've already agreed on one with the candidate, or when they're having trouble finding a time that works.
> [accordion] Why don't I see any open times?
>
> None of the interviewers in the pool are free for an interview of this length, or they haven't connected their calendar. Add interviewers to the interview activity, or ask interviewers to open up their availability. See [Your availability and calendar](/interviews/availability).
> [accordion] Can I give one candidate different hours?
>
> Yes. In the **Scheduling Options** window, open **Activity Hours** to change the hours for this candidate only. See [Customize hours for one candidate](/interviews/self-scheduling#customize-hours-for-one-candidate).
> [accordion] How do I find every candidate who still needs an interview booked?
>
> Build a saved view of candidates whose interview isn't booked yet. See [See who hasn't booked](/interviews/who-hasnt-booked).
## Related
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interviewers, scheduling settings and calendar invites.
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> Scheduling links, activity hours and what candidates see.
> [card] [See who hasn't booked](/interviews/who-hasnt-booked)
>
> Find candidates who haven't picked a time and help them book.
> [card] [Interview guides](/interviews/interview-guides)
>
> What interviewers follow and score during the interview.
# Candidate self-scheduling
Source: https://help.journeyfront.com/interviews/self-scheduling
Let candidates book their own interview time from your team's real availability.
> [!NOTE]
>
> **Who can do this:** Setting up scheduling and activity hours needs the *Manage Job Req Settings* permission. Anyone on the job req's hiring team, or with *All Job Req Access*, can send a candidate a scheduling link or cancel their interview.
>
> **Availability:** Interviewers need a connected calendar and saved working hours in **My Availability**.
Self-scheduling lets candidates pick an interview time that suits them from your interviewers' live calendars. There's no back-and-forth: the candidate books, the interview lands on your interviewers' calendars, and the candidate's status updates in Journeyfront. When you're hiring at volume, it's the fastest way to move candidates from screening to interview.
## How it works
**1. The candidate gets a link**
When a candidate reaches the interview step, Journeyfront emails them a scheduling link. You can also send one yourself. Candidates get step-by-step help in [Book your interview time](https://candidatehelp.journeyfront.com/interviews/book-your-interview) on the candidate help site.
**2. They pick a time**
The link shows the times when the required interviewers are free, in the candidate's own time zone. No sign-in needed.
**3. The interview is booked**
Journeyfront checks the interviewers' calendars once more, adds the interview to them, emails the candidate a confirmation and marks the interview **Scheduled**. If someone took that time a moment earlier, the candidate is asked to pick another.
**4. Reminders go out**
Candidates get reminder emails before the interview: 24 hours and 1 hour before, unless you change the timing for the job req.
The interview activity's settings decide who interviews, how long it takes and what the link allows. See [Set up an interview activity](/interviews/interview-activity).
## Before you start: connect interviewer calendars
Open times come from each interviewer's connected calendar, so every interviewer should do this once:
**1. Connect a calendar**
Go to **Interviews**, then **My Profile**. Connect a calendar under **Synced Calendar**, then set **Time Zone** and a default **Conferencing** service.
**2. Set regular availability**
Go to **My Availability**, mark the hours you're generally free to interview on the weekly grid, and save them. Then set **Scheduling Period** (how far ahead candidates can book), **Buffers** (free time before and after interviews) and **Minimum Notice** (how soon an interview can start).

> [!WARNING]
>
> An interviewer who hasn't connected a calendar can't be booked, and one who hasn't saved working hours offers no times. **Scheduling Options** flags both next to the interviewer's name, so you can fix it before candidates see an empty page. **Invite to Sync Calendar** emails them a link to connect.

> [!TIP]
>
> Happy to interview over a recurring placeholder, like "admin time"? Copy the keyword shown under **Ignore Event Keyword** into that event's description and Journeyfront treats the time as free.
## Send a scheduling link
**Automatically:** turn on **Send email invite to candidates when entering step** on the interview activity. Every candidate who reaches the step gets a link.
**For one candidate:**
**1. Open the candidate's interviews**
On the Candidate Application, open **Actions**, then click **Interview**.

**2. Click Schedule**
The **Interviews** window lists each interview with its status. Click **Schedule** on the interview.

**3. Share availability**
Choose **Share Availability** (1), check the interviewers' availability on the calendar and click **Next** (2).

**4. Review the email and send it**
The **Email to Candidate** shows the **From**, **Reply To**, **Subject** and **Body** of the invite. Change them if you need to, insert a variable field or attach a file, then click **Invite candidate to self schedule**.

> [card] [Schedule an interview for a candidate](/interviews/schedule-for-a-candidate)
>
> Book a time for the candidate yourself instead of sending a link.
### Copy a candidate's scheduling link
To text a candidate their link, or paste it into a message, open **Actions**, then **Interview**. On the interview, open **Copy Link** and choose **Copy Candidate Scheduling Link**. **Copy Interview Guide Link** copies the interviewer's guide instead.
**Copy Candidate Scheduling Link** is available once the candidate has a link: after an invite is sent, and while the interview is booked. Before that, or when the link is canceled or expired, it's grayed out and its tooltip says why.

## Cancel an interview or invite
Cancel from the candidate's **Interviews** window: on the Candidate Application, open **Actions**, then **Interview**.
**1. Click Cancel Interview or Cancel Invite**
A booked interview shows **Cancel Interview**. An invite the candidate hasn't booked yet shows **Cancel Invite**.

**2. Add a reason**
The confirmation shows the interview time and interviewers. Enter a **Reason** (required). For a booked interview you can also add a **Message to candidate**, which goes in their cancellation email.

**3. Confirm**
Click **Cancel Interview** (or **Cancel Invite**).
What happens next:
| | Cancel Interview (booked) | Cancel Invite (not booked) |
| - | - | - |
| **Calendars** | The event is removed from the interviewers' calendars. | Nothing to remove. |
| **Emails** | The candidate and the interviewers on the interview are emailed, with your message to the candidate. | No email is sent. |
| **Scheduling link** | Closes. The candidate sees that the interview was canceled. | Closes. The candidate sees that the interview was canceled. |
| **History** | Who canceled and the reason are recorded. | Who canceled and the reason are recorded. |
The interview then shows **Canceled**, and **Schedule** is there to send a new invite, which opens the link again.

> [!NOTE]
>
> Rejecting, hiring or moving a candidate never cancels their interview. Cancel it here if they shouldn't attend. An interview that's complete, or whose time has passed, can't be canceled.
If the interviewer's calendar can't be reached when you cancel, the interview is still canceled in Journeyfront and you see a message asking you to have the interviewer delete the event.
## When an interviewer changes the calendar event
Journeyfront keeps the interview in step with the interviewer's own calendar:
* **Moved:** if the interviewer drags the event to a new time in Google or Outlook, Journeyfront takes the new time. The candidate gets an email with it, and reminders follow the new time.
* **Deleted:** if the interviewer deletes the event, the interview is canceled and the candidate is emailed.
## Control what the link allows
These settings live on the interview activity, under **Scheduling Options**.
| Setting | What candidates experience |
| - | - |
| **Accept new interviews** | When off, the link tells candidates scheduling is closed. Candidates who already booked keep their times, and you can still book for them with **Schedule Time**. |
| **Interview link expiry** | The link stops taking bookings after the number of days in **Days until link expires**, counted from when the invite was sent. A candidate who already booked can still cancel. |
| **Allow candidates to reschedule** | When on, candidates who already booked can use the same link to pick a new time. When off, they can cancel (with a reason) but can't pick a new time; the page tells them to contact their recruiter, and you send a new invite when you're ready. |
| **Allow candidates to request more time** | Candidates who don't see a time that works can ask for more availability. The interviewer is notified and the interview's status changes to **More Time Requested**. |
These rules apply to every link, including links sent before you changed a setting, and Journeyfront enforces them when the candidate books or cancels, not only on the page.
**Changing settings after invites are out:**
* **Accept new interviews**, **Allow candidates to reschedule** and **Allow candidates to request more time** apply to every open interview right away, booked or not.
* A new **Days until link expires** moves the expiry of invites that haven't been booked yet, still counted from when each invite was sent.
* Removing an interviewer from the activity takes them off invites that haven't been booked yet. Adding one adds them to those invites.
* Booked interviews always keep their time and their interviewers.
* If you changed one of these settings on a single candidate's interview, saving the activity only replaces it when you change that same setting on the activity.
## Set interview hours for an activity
Activity hours set the windows when candidates can book one specific interview, separate from each interviewer's own calendar. Candidates only see times that fit both the interviewer's availability and the activity hours.
This helps when the same interviewers cover several kinds of interview. For example, your recruiters might hold customer care interviews from 12 to 1 and technical support interviews from 2 to 4, without changing their personal calendars every week. Activities without activity hours keep working exactly as before.

### Set weekly hours
**1. Open Activity Hours**
Open the interview activity's **Scheduling Options** and click **Activity Hours** on the right.
**2. Paint the bookable times**
The grid runs Monday to Sunday, 6am to 10pm, in 30-minute rows. Click a cell to make it bookable (it turns blue), or click and drag to paint a range. Click or drag across blue cells to clear them.
**3. Pick a time zone**
Choose the **Time Zone** your hours are written in. Candidates still see times in their own time zone.
**4. Save**
Click **Save Settings**.
> [!TIP]
>
> Activity hours can only narrow availability, never add to it. If an interviewer is busy at a time you painted, that time still isn't offered.
### Add or block specific dates
Under **Date exceptions**:
* **Add available window** opens times on dates outside your weekly hours, such as a Saturday hiring event. Pick the dates, set **From** and **To**, and click **Add**. It shows in the list as **Available**.
* **Block out dates** removes dates, such as a holiday or a training day. **All day** is checked by default; uncheck it to block only part of a day. It shows in the list as **Blocked**.
A blocked date always wins over your weekly hours. To remove an exception, click the **X** next to it.

### Preview what candidates will see
Click **Availability Preview** to see the times candidates will actually be offered: your interviewers' availability combined with the activity hours. It updates as you edit, before you save.

### Customize hours for one candidate
Need a special window for one candidate, such as an accommodation or a one-off slot?
**1. Open the candidate's interview**
On the Candidate Application, open **Actions**, then **Interview**, and click **Schedule** on the interview.
**2. Edit their hours**
Click **Activity Hours**. It starts with the activity's hours. Change the grid or add a date exception.
**3. Send the invite**
Send the invite or book a time as usual.
Only this candidate's invite changes. To undo it, open **Activity Hours** for the candidate again and click **Reset to activity defaults**.

> [!NOTE]
>
> If you later change the activity's hours, candidates still using the activity's hours pick up the change. Candidates with their own customized hours keep theirs.
### Activity hours vs. My Availability
| | My Availability | Activity hours |
| - | - | - |
| **Belongs to** | The interviewer | The interview activity |
| **Applies to** | Every interview that person does | Only this interview |
| **Good for** | "I'm generally free Monday to Friday, 9 to 5" | "Technical support interviews happen Tuesday to Thursday, 2 to 4" |
| **Set by** | The interviewer | Whoever manages the job req's workflow |
| **Can it add availability?** | Yes, it sets the baseline | No, it only narrows it |
## Track scheduling status
Each interview on a Candidate Application shows where scheduling stands:
| Status | What it means |
| - | - |
|  | No scheduling link has been sent yet. |
|  | The candidate has a link but hasn't booked. |
|  | The interview is booked. |
|  | The candidate asked for more availability. |
|  | An interviewer submitted the interview guide. |
|  | An interviewer declined the calendar invite. |
|  | The candidate canceled the interview from their link. Their reason is in the candidate's history. |
|  | A recruiter canceled the interview or invite, or an interviewer deleted the calendar event. |
> [!TIP]
>
> Keep an eye out for **More Time Requested**. Those candidates want to interview; they just need a time. Open up availability or book them directly with **Schedule Time**.
## What candidates see
* **An email invite.** The default subject is "Interview Invite - Schedule your interview" with your company name. You can change its wording in the **Interview Schedule Invite** system email.
* **A booking page.** The link opens "Schedule your interview with" your company name, and asks them to choose a day and time that works for them. Times show in their own time zone, and they don't need to sign in.
* **Help when nothing fits.** If no times are open, the page says "No times are open right now." If requesting more time is allowed, they can say when they're available and click **Request More Times**.
* **Their booked interview.** After booking they get a confirmation email with a link to cancel, or to reschedule or cancel if you allow rescheduling. Opening the link shows the date, time, length and format of their interview, with the join link or address, plus **Cancel Interview** and, if you allow it, **Reschedule**. Canceling asks for a reason.
* **Reschedule off.** Instead of **Reschedule**, the page says "To pick a new time, contact your recruiter."
* **A closed link.** The page explains what happened: the link expired, the interview isn't taking new bookings, the candidate canceled, or you canceled it. They're told to contact the recruiting team or watch for a new invite.
Candidates never see your activity hours or other rules. To them, it simply looks like the times you have open.


> [card] [Book your interview time](https://candidatehelp.journeyfront.com/interviews/book-your-interview)
>
> The candidate help article on picking a time, with what to do when nothing fits.
> [card] [Team emails and system emails](/communication/email-templates#system-emails)
>
> Edit the Interview Schedule Invite and Interview Schedule Confirmation emails.
## FAQ
> [accordion] Why does a candidate see no open times?
>
> Usually the interviewers' combined availability is too narrow. Work through this list, using **Availability Preview** on the interview activity to check each change:
>
> * **Calendars:** every interviewer in the pool has connected a calendar in **Interviews**, then **My Profile**. Interviewers without one can't be booked.
> * **Working hours:** every interviewer has saved working hours in **My Availability**. Interviewers without them offer no times. **Scheduling Options** flags both problems.
> * **Required interviewers:** **Number of Required Interviewers** set to **All** means every interviewer must be free at once. Lower it if you can.
> * **Personal settings:** interviewers' **My Availability** hours, **Scheduling Period**, **Minimum Notice** and **Buffers** can all shrink what's open.
> * **Activity hours:** the painted hours may be too narrow, or dates may be blocked.
> * **Length:** a long **Duration** needs a long free block on every required calendar.
>
> If **Allow candidates to request more time** is on, the candidate can ask for more availability and you'll see **More Time Requested**. You can also book them directly with **Schedule Time**.
> [accordion] A candidate says they can't find their interview link. What should I do?
>
> Check these first:
>
> * **Did we send it?** If the interview shows **Not Scheduled**, no link has gone out. **Send email invite to candidates when entering step** may be off for this activity.
> * **Right address?** Check the email address on the candidate's Candidate Profile.
> * **Spam?** Ask the candidate to check spam, junk and promotions folders for an email about scheduling an interview.
> * **Still active?** If the candidate opened the link and saw that it's no longer active, it has expired or **Accept new interviews** is off.
>
> To send a fresh link, open **Actions**, then **Interview**, click **Schedule**, choose **Share Availability**, click **Next**, then **Invite candidate to self schedule**. Or skip the link and book a time for them with **Schedule Time**.
> [accordion] Can a candidate change their interview time?
>
> Yes, if **Allow candidates to reschedule** is on: they open the same link and click **Reschedule**. If it's off, they can only cancel, with a reason. Change the time yourself with **Edit Interview**, or send them a new invite once they've canceled.
> [accordion] Does rejecting or moving a candidate cancel their interview?
>
> No. Status and step changes never cancel interviews. If the candidate shouldn't attend, open **Actions**, then **Interview**, and click **Cancel Interview**.
> [accordion] Why can't I cancel an interview?
>
> **Cancel Interview** isn't offered once the interview is complete or its time has passed. A canceled invite shows **Schedule** instead, so you can send a new one.
> [accordion] What time zone do candidates see?
>
> Their own. Journeyfront shows every open time in the candidate's local time, whatever time zone your interviewers or activity hours use.
> [accordion] When does a scheduling link expire?
>
> Only when **Interview link expiry** is on. The clock starts when the invite is sent and runs for the number of days in **Days until link expires**. Candidates who miss the window need a new invite. A candidate who already booked can still use the link to cancel.
> [accordion] Can activity hours repeat on a pattern like every other Tuesday?
>
> Not yet. Activity hours support a weekly schedule plus date exceptions. Use **Add available window** and **Block out dates** for anything outside the weekly pattern.
> [accordion] Can activity hours cover overnight shifts?
>
> The weekly grid covers 6am to 10pm. If you interview outside those hours, let your Customer Success Manager know.
> [accordion] Can I change hours for one candidate without affecting anyone else?
>
> Yes. Edit **Activity Hours** from that candidate's interview. Only their invite changes, and **Reset to activity defaults** puts them back on the activity's hours.
## Related
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interview guides, interviewers and scheduling settings.
> [card] [Workflows overview](/workflows/overview)
>
> Where interviews fit in a job req's workflow.
# See who hasn't booked
Source: https://help.journeyfront.com/interviews/who-hasnt-booked
Find candidates waiting in the interview step who haven't picked a time, and help them book.
> [!NOTE]
>
> **Who can do this:** Anyone on the job req's hiring team, or with *All Job Req Access*, can find these candidates and send them a new scheduling link. Setting up an automatic nudge needs *Manage Job Req Settings*.
When you're hiring at volume, some candidates reach the interview step and never pick a time: the invite went to spam, the link expired, or nothing fit their schedule. Every day they wait, you risk losing them to another employer. A saved view shows you exactly who's stuck, so you can follow up in a few clicks or let an automation do it for you.
## Interview statuses to watch
Each interview on a Candidate Application has a scheduling status. These are the ones that mean "not booked yet":
| Status | What it means | What to do |
| - | - | - |
| **Not Scheduled** | No scheduling link has gone out yet. | Send one, or check that the interview sends invites automatically. |
| **Schedule Invite Sent** | The candidate has a link but hasn't booked. | Nudge them, or send a fresh link. |
| **More Time Requested** | The candidate asked for more availability because nothing fit. | Open up more times, or book a time for them. |
| **Canceled** or **Candidate Declined** | The booking was canceled or the candidate declined. | Decide whether to invite them again. |
See [Candidate self-scheduling](/interviews/self-scheduling#track-scheduling-status) for every status.
## Build a "hasn't booked" view
**1. Open the job req's candidates**
Open the job req. It opens on the **Candidates** tab. (To look across job reqs, use the **Candidates** page and add the **Job Req** filter.)
**2. Filter to the interview step**
Click **Filters**. In **Current Step**, choose the step that holds the interview. On a job req, you can also click that step's tab in the **Steps** group.
**3. Filter by interview status**
Open **Activity Status**. Statuses are grouped by activity: under your interview's name, tick **Not Scheduled**, **Schedule Invite Sent** and **More Time Requested**.
**4. See who's waited longest**
Click **Edit Columns** and add **Time in Step** and **Interview**, then sort. You can also add the **Time in Current Step** filter, from **More**, to show only candidates who've waited a certain time.
**5. Save the view**
Click **Save as New View** and name it, for example "Hasn't booked". It appears as a tab, ready every morning. If several recruiters follow up on the same job req, set **Who can see this** to share it, so everyone works the same list. See [Saved views](/lists-and-exports/saved-views#share-a-view).

See [The Candidates page](/candidates/candidates-page) for more on filters, columns and saved views.
> [!TIP]
>
> Check the view at the same time every day and work from the top. A candidate who has waited two days is far more likely to book after a quick personal nudge than one who has waited two weeks.
## Check one candidate's interview
Open the candidate's **Interviews** window in either of two ways.
**From the list:** click **Interview Link** in the **Interview** column. If you don't see the column, add it with **Edit Columns**.

**From the Candidate Application:** open **Actions**, then click **Interview**.

The **Interviews** window shows each interview with its status and, once booked, the date and time. From there you can click **Schedule** (or **Edit Interview** once it's booked) to send a link or book a time.

## Help them book
Pick what fits the situation:
* **Send a fresh link.** In the **Interviews** window, click **Schedule** on the interview, choose **Share Availability**, click **Next**, and then **Invite candidate to self schedule**. Use this when the first email went missing or the link expired.
* **Book it for them.** Click **Schedule**, choose **Schedule Time**, pick an open time and click **Schedule Interview**. Handy after a phone call where you agree a time together.
* **Open up more times.** For **More Time Requested**, ask interviewers to widen their hours in **My Availability**, or add interviewers to the interview activity. See [Your availability and calendar](/interviews/availability).
* **Text them their link.** In the **Interviews** window, open **Copy Link** on the interview and choose **Copy Candidate Scheduling Link**, then paste it into a text or message. It's available while the candidate has an open invite or a booking.
* **Reach out.** Email or text candidates from the list: tick them and use **E-mail** or **Message**. Ask them to look for the scheduling email from Journeyfront, including in spam and junk folders. See [Bulk actions](/candidates/bulk-actions).

See [Candidate self-scheduling](/interviews/self-scheduling#send-a-scheduling-link) for each option step by step.
> [!TIP]
>
> A text gets read much faster than an email. A short message like "Your interview link is in your email from us, it only takes a minute to pick a time" often gets the booking the same day.
## Nudge candidates automatically
An automation rule can follow up for you. For example:
* **Trigger:** **Candidate Time in Step Reaches**, the interview step, 2 **Days**.
* **Condition:** **Activity Status is**, your interview activity, **Schedule Invite Sent**.
* **Action:** **Send SMS to Candidate** or **Send Email to Candidate** with a friendly reminder.
To add it:
**1. Open the Workflow page**
Open the job req and go to **Setup**, then **Workflow**.
**2. Add an automation to the interview step**
Click the purple lightning bolt next to the interview step's name. The automation editor opens with the trigger set to **Candidate Moved to Step**.
**3. Set it up**
Name the automation. Change the **Trigger** to **Candidate Time in Step Reaches** and set **Days**. Click **+ Add Condition** for the interview's status, and **+ Add Action** for the email or text.
**4. Turn it on and save**
New automations start **Off**. Switch **Enabled** to **On** and click **Save**.
> [!WARNING]
>
> Automations you add on the Workflow page save straight to the version you're viewing. On the live version (**Latest**), the rule starts working as soon as you save it turned on.
See [Automation rules](/workflows/automation-rules) for every trigger, condition and action.
## If candidates show Not Scheduled
Candidates should get a scheduling link as soon as they reach the interview step. If many show **Not Scheduled**, check the interview's settings: on the job req's **Workflow** page, click **Create New Version** (or **Edit Draft**), click the interview, and under **Interview Scheduler** click **View and Edit Details**. Make sure **Send email invite to candidates when entering step** is on, and that **Accept new interviews** is on if your account has it. See [Set up an interview activity](/interviews/interview-activity).
## FAQ
> [accordion] Do interview reminders go to candidates who haven't booked?
>
> No. Reminders only go out for booked interviews. Use a saved view and the steps above, or an automation rule, to follow up with candidates who haven't booked. See [Interview reminders](/interviews/reminders).
> [accordion] A candidate says their link doesn't work. What now?
>
> It has probably expired, or scheduling is paused for that interview. Send a fresh link with **Share Availability**, or book a time for them with **Schedule Time**.
> [accordion] Can I see who hasn't booked across all my job reqs?
>
> Yes. Build the same view on the **Candidates** page. The **Activity Status** filter lists each interview by name, so tick the not-booked statuses under every interview you want to include.
> [accordion] Why is a candidate missing from my view?
>
> Check that they're in the step you filtered on, and that their interview status is one you ticked. Candidates who booked show **Scheduled** and drop out of the view, which is the point.
## Related
> [card] [Candidate self-scheduling](/interviews/self-scheduling)
>
> Scheduling links, statuses and what candidates see.
> [card] [The Candidates page](/candidates/candidates-page)
>
> Filters, columns and saved views.
> [card] [Automation rules](/workflows/automation-rules)
>
> Follow up with candidates automatically.
> [card] [Interview reminders](/interviews/reminders)
>
> Reminders for candidates who've booked.
# Application form
Source: https://help.journeyfront.com/job-reqs/application-form
Choose which fields candidates fill in when they apply, and in what order.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission.
The application form is the first thing candidates fill in when they apply: their name and contact details, plus anything else you need to know up front, such as a resume, an address or your own custom fields. Each job req has its own form, so you can ask for exactly what that role needs and nothing more.
The application form collects information; it doesn't score candidates. To screen candidates on their answers, use [screening questions](/assessments/screening-questions) in the workflow.
## Open the application form
Open the job req and go to **Setup**, then **Application Form**. The **Form Fields** table lists every field on the form, with a **Hidden**, **Optional** and **Required** choice for each.

* **Required:** candidates must fill it in before they can submit.
* **Optional:** candidates see it and can skip it.
* **Hidden:** candidates don't see it.
## The built-in fields
| Field | New job reqs start with |
| - | - |
| **First Name**, **Last Name**, **Email** | Required, and can't be changed |
| **Secondary Email**, **Phone Number**, **Date of Birth**, **Country**, **State/Region**, **City** | Optional |
| **Zip/Postal Code**, **Address Line 1**, **Address Line 2** | Hidden |
| **Linkedin URL**, **Resume** | Optional |
| **Work History**, **Education History** | Hidden. When shown, they're filled in from the candidate's resume when one is available. |
| **EEOC Compliance Questions** | Hidden. Collects gender, race, veteran and disability status. It can be Required or Hidden, not Optional. |
Older job reqs may have different starting choices. Change any of them to suit the role.
## Add your own fields
Add the custom fields your account has set up. Create them first under **Settings**, then **Custom Fields**. See [Custom fields](/account-setup/custom-fields).
**1. Click Add**
Click **Add**, then **Add Field**.
**2. Pick a field**
Search or scroll the list. It's grouped into **Personal Fields** and **Application Fields**, and shows each field's type. Fields already on the form are marked **Added**.

**3. Set it up and save**
The field is added as **Optional**. Change it to **Required** if you need it, then click **Save** at the top of the page.
Each custom row is tagged so you can tell them apart:
* **Personal:** about the person. The answer is saved on their Candidate Profile and shared across all their applications.
* **Application:** about this application. The answer is saved on this Candidate Application only.
To take a custom field off the form, click its trash icon and save. Custom fields don't have a **Hidden** option; removing them does the same thing.
User fields (fields that pick one of your team members) aren't offered on the application form.
## Add an e-consent form
To have candidates sign a consent form as part of applying, click **Add**, then **Add E-Consent Form**, and pick the form. It's added as **Required** and tagged **E-Consent**. See [E-consent forms](/onboarding/e-consent-forms).
## Change the order
Contact and address fields always come first, in a fixed order. Drag any other row by its handle to move it, for example to put a custom question above the resume upload. Click **Save** when you're done.
**Save** and **Cancel** appear at the top of the page as soon as you change something. **Cancel** puts the form back to how it was last saved.
> [!TIP]
>
> Shorter forms get more finished applications. Ask only for what you need to decide whether to move someone forward, and collect the rest later, for example with [onboarding forms](/onboarding/onboarding-forms) once they're hired.
## What candidates see
Candidates fill in the form as their **Personal Profile**, the first part of their application. Required fields must be filled in, and required consent forms signed, before they can continue.
Your team sees the answers on the **Details** tab of the Candidate Application. Answers to personal fields also appear on the Candidate Profile.
## FAQ
> [accordion] Do application form answers affect a candidate's score?
>
> No. The application form only collects information. Use [screening questions](/assessments/screening-questions) for anything you want to score or screen on.
> [accordion] How do I require a resume?
>
> Set the **Resume** row to **Required** and click **Save**. Do the same with **Linkedin URL** to require a LinkedIn profile.
> [accordion] Can I make First Name, Last Name or Email optional?
>
> No. Every candidate needs a name and an email address, so these three are always required.
> [accordion] Why can't I find my custom field in the list?
>
> Check it was created as a personal or application field under **Settings**, then **Custom Fields**. Other kinds of custom fields, and user fields, aren't offered on the application form.
> [accordion] Do I have to set up the form again for every job req?
>
> Each job req has its own form. When you [duplicate a job req](/job-reqs/create#start-from-an-existing-job-req), the copy keeps the original's application form.
## Related
> [card] [Custom fields](/account-setup/custom-fields)
>
> Create personal and application fields for your account.
> [card] [E-consent forms](/onboarding/e-consent-forms)
>
> Consent forms candidates sign as they apply.
> [card] [Screening questions](/assessments/screening-questions)
>
> Questions that screen and score candidates.
> [card] [Create a job req](/job-reqs/create)
>
> Set up a new job req from start to finish.
# Create a job req
Source: https://help.journeyfront.com/job-reqs/create
Create a new job req, or copy one you already have, and get it ready for candidates.
> [!NOTE]
>
> **Who can do this:** Creating a job req needs the *All Job Req Access* permission. Editing its details and setup needs *Manage Job Req Settings*. Duplicating needs *Duplicate Job Reqs*.
A new job req starts with the basics: what the role is called, what candidates see, and where it is. Journeyfront gives it a starter workflow, and it stays **Inactive** while you finish setting it up, so no one can apply until you're ready.
## Create a job req
**1. Click New Job Req**
Go to **Job Reqs** in the top navigation and click **New Job Req**. The **Job Req Details** window opens.

**2. Fill in the details**
* **Linked to Job Profile** (required): the [job profile](/employees/job-profiles) this role belongs to.
* **Job Req Name** (required): the name your team sees, for example "Customer Care - Tampa - Day Shift".
* **External Job Title** (required): the title candidates see, for example "Customer Service Agent".
* **Description** (optional).
* **Employment Type**, **Job Country** and **Job Location** (city and state), all optional.
**3. Click Save**
Journeyfront creates the job req and opens it on the **Setup** tab.

> [!TIP]
>
> Keep the Job Req Name specific (location, shift, client) and the External Job Title simple. Your team filters and reports on the name; candidates only ever see the title.
## Finish setting it up
Work through the **Setup** tab. You can do these in any order:
* **Details:** check the basics and fill in your account's custom fields in the **Custom Fields** card. Custom fields aren't in the New Job Req window, so add them here and click **Save**.
* **Application Form:** choose what candidates fill in when they apply. See [Application form](/job-reqs/application-form).
* **Attributes:** check what the job req measures. See [Attributes](/scoring/attributes).
* **Workflow:** every new job req starts with a draft workflow, **Workflow 1.0**, with **Pre-screen**, **Recruiter Interview**, **Hiring Manager Interview**, **Offer** and **Onboarding** steps. Click **Edit Draft** to change it to match your process. See [Build a workflow](/workflows/build).
* **Team:** add the recruiters, hiring managers and interviewers who work on it. See [Hiring team](/job-reqs/hiring-team).
* **Configurations:** candidate assignment, interview reminders and candidate experience options. See [Job settings](/job-reqs/job-settings).
* **Job Postings:** advertise the job on your career site and job boards. See [Job postings](/sourcing/job-postings).
Then add your first class on the **Hiring Classes** tab. See [Create a hiring class](/hiring-classes/create).
> [!WARNING]
>
> The starter workflow includes two automation rules on the **Pre-screen** step: one moves candidates with strong scores to **Recruiter Interview**, and one rejects candidates with low scores. Review them, and change or remove them, before candidates start applying. See [Automation rules](/workflows/automation-rules).
## Open it to candidates
A new job req is **Inactive**, so its application link tells candidates the position isn't accepting applications yet. When everything is ready:
* Click **Actions**, then **Activate**. This needs the *Deactivate Job Reqs* permission.
- Or publish the workflow. Publishing makes an inactive job req **Active**. See [Publish workflow changes](/workflows/publish).
See [Job req statuses](/job-reqs/statuses) for what each status does.
## Edit a job req's details
Open the job req and go to **Setup**, then **Details**. Change any field in the **Basic Info** card or the **Custom Fields** card. **Save** and **Cancel** appear at the top as soon as you change something. If you leave the page without saving, Journeyfront asks whether to save or discard your changes.

To change the workflow, the application form or the job req's settings, use the other pages on the **Setup** tab.
## Start from an existing job req
When a new role works like one you already run, for example the same process for a new site or client, copy it instead of starting from scratch.
**1. Open the job req to copy**
Open the job req and click **Actions**, then **Duplicate Job Req**.

**2. Confirm**
Click **Duplicate**. Journeyfront creates the copy, named after the original with "- copy" at the end, and opens it.
**3. Update the copy**
Rename it on **Setup**, then **Details**, and update anything that's different for the new role.
The copy includes:
* The job req's details, settings and custom field values
* Its published workflow: steps, activities, questions, assessments, attributes and automation rules
* The application form
* The hiring team and candidate assignment (with each team member's "Candidate completes application" emails turned off)
It doesn't include candidates, hiring classes or job postings. The copy also starts with the same status as the original, so check its status before you share any links.
> [!TIP]
>
> Duplicating a job req that's already working well is the fastest way to stand up a new role, and it keeps your screening consistent across sites. Review the copy's workflow and postings before you open it.
## FAQ
> [accordion] Why can't I create a job req?
>
> Creating a job req needs the *All Job Req Access* permission. Ask your Journeyfront admin to check your security role.
> [accordion] Where did options like Require Resume and Allow Retakes go?
>
> The job req's options now live on the **Setup** tab. Whether candidates must give a resume or LinkedIn profile is set on the [application form](/job-reqs/application-form). Re-takes, hiding interviewer names, the predictive model and the other candidate experience options are under **Setup**, then **Configurations**. See [Job settings](/job-reqs/job-settings).
> [accordion] Why can't candidates apply to my new job req?
>
> New job reqs start **Inactive**. Click **Actions**, then **Activate** when you're ready, or publish the workflow.
> [accordion] Does duplicating a job req copy its candidates?
>
> No. Only the setup is copied. Candidates stay on the original job req.
> [accordion] Can I change the job profile later?
>
> Yes. Choose a different one in **Linked to Job Profile** on **Setup**, then **Details**, and click **Save**.
## Related
> [card] [Workflows overview](/workflows/overview)
>
> The steps and activities every candidate follows.
> [card] [Job settings](/job-reqs/job-settings)
>
> Assignment, reminders, gate steps and scoring options.
> [card] [Job req statuses](/job-reqs/statuses)
>
> Activate, deactivate, close, archive or delete a job req.
> [card] [Job postings](/sourcing/job-postings)
>
> Advertise the job on your career site and job boards.
# Hiring team
Source: https://help.journeyfront.com/job-reqs/hiring-team
Choose who works on a job req, and who gets emailed as candidates finish their applications.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission manage a job req's team on its **Setup** tab. Admins with *Company Settings Access* and the *Manage Users* permission can also manage it from each user's settings.
A job req's hiring team is the recruiters, hiring managers and interviewers who work on it. Being on the team is what gives someone access to the job req and its candidates.
## Who can see a job req
* People with the *All Job Req Access* permission in their security role see every job req, whether or not they're on its team.
* Everyone else sees only the job reqs they're on the hiring team for. Those are the job reqs on their **Job Reqs** page.
So when a hiring manager or interviewer can't find a job req or its candidates, add them to its hiring team.
## Add someone to the team
**1. Open the Team page**
Open the job req and go to **Setup**, then **Team**. The **Team Members** list shows everyone on the team.
**2. Click Team Member**
Click **Team Member** (with the plus) at the top right. The **Add Team Member** window opens.

**3. Enter their email**
Enter the **Team Member Email** and click **Save**.
If no one in Journeyfront has that email yet, you're asked for their first and last name. Click **Add Name** to create their user and add them to the team.
> [!TIP]
>
> Add hiring managers and interviewers while you set up the job req, so they can see its candidates from the first day it's open.
## Remove someone from the team
On **Setup**, then **Team**, click the trash icon on their row and click **Confirm**. They won't see the job req anymore, unless their security role has *All Job Req Access*.
## Add people from user settings
Admins can manage everything one person works on from their user record instead of job req by job req.
1. Go to **Settings**, then **Users**, and edit the user.
2. On the **Available Job Reqs** tab, tick the job reqs the person should work on and untick the ones they shouldn't.
3. Click **Save**.

Ticking a job req adds the person to its hiring team. People whose role has *All Job Req Access* see **All Job Reqs** here instead, because they already see every job req.
## Get an email when a candidate finishes applying
Each team member can choose to get an email when a candidate completes their whole application for the job req. The email names the candidate and links to their Candidate Application.
**1. Edit the team member**
On **Setup**, then **Team**, click the edit icon on the person's row. The **Edit Team Member** window opens.
**2. Turn on the notification**
Under **Notifications**, set **Candidate completes application** to **Yes**.

**3. Save**
Click **Save**.
Each email also links to this setting on the job req's **Team** page. Changing it there needs the *Manage Job Req Settings* permission; without it, ask someone who has it to turn the emails off for you.
An admin can set this for someone else from **Settings**, then **Users**: edit the user, and on the **Available Job Reqs** tab click the edit icon next to a ticked job req.
## Get an email when a candidate finishes an activity
To hear about one activity instead, for example a skills test you review by hand, use the bell on that activity in the job req's workflow.
> [card] [Get notified when an activity is completed](/workflows/build#get-notified-when-an-activity-is-completed)
>
> Add yourself or teammates to an activity's Get Notified list.
## FAQ
> [accordion] A hiring manager can't see the job req. What do I do?
>
> Add them to the job req's hiring team on **Setup**, then **Team**. Unless their security role has *All Job Req Access*, people only see job reqs they're on the team for.
> [accordion] Do I need to add admins to every hiring team?
>
> No. People whose security role has *All Job Req Access* already see every job req. Add them to a team only if they should be in that team's lists, for example to be picked as a [default assigned user](/job-reqs/job-settings#candidate-assignment).
> [accordion] Does duplicating a job req copy its hiring team?
>
> Yes. The copy has the same team members, with their "Candidate completes application" emails turned off. Turn them back on for the people who want them.
> [accordion] How do I stop getting these emails?
>
> On the job req's **Team** page, edit yourself and set **Candidate completes application** to **No**, or ask someone with the *Manage Job Req Settings* permission to do it. For activity emails, open the activity's bell and remove yourself from the list.
## Related
> [card] [Security roles](/account-setup/security-roles)
>
> Permissions like All Job Req Access and Manage Job Req Settings.
> [card] [Users](/account-setup/users)
>
> Add users to your account.
> [card] [Job settings](/job-reqs/job-settings)
>
> Candidate assignment, reminders and gate steps.
> [card] [Job reqs overview](/job-reqs/overview)
>
> What's inside a job req.
# The Job Reqs page
Source: https://help.journeyfront.com/job-reqs/job-reqs-page
Find, filter and organize your job reqs with saved views.
> [!NOTE]
>
> **Who can do this:** Everyone can use the Job Reqs page. It lists every job req for users with the *All Job Req Access* permission, and only the job reqs you're on the hiring team for otherwise. Creating a job req also needs *All Job Req Access*.
The **Job Reqs** page is your list of every job req you work on. Search it, filter it, choose the columns that matter to you, and save the combinations you use often as views, so your open roles in one region or your busiest job reqs are always one click away.
To get there, click **Job Reqs** in the top navigation. Click any row to open that job req.

## Search and sort
* **Search** matches the Job Req Name and the External Job Title.
* Click a column header to sort by that column. Click it again to reverse the order.
* The list shows 25 job reqs per page. Change it to 50 or 100 at the bottom of the table, and use the page numbers to move through the list.
## Columns
The list starts with these columns: **Job Req Name**, **Job Req External Name**, **Job Profile**, **Created Date**, **Country**, **State/Region**, **City**, **Candidates**, **Hires** and **Status**. **Candidates** counts everyone who has applied to the job req, and **Hires** counts those hired.
To change them, click **Edit Columns**. Add or remove columns, drag them into the order you want, and click **Save**. **Job Req Name** is always shown.
If your account has [custom job req fields](/account-setup/custom-fields), they're listed under their own **Custom Job Req Fields** heading in **Edit Columns**. Once a custom field column is showing, you can change a value without opening the job req: hover over the cell, click the pencil, and save.
## Filter
Click **Filters** to open the filter bar. It starts with **Status**, **Job Profile**, **Country**, **State/Region**, **City** and **Created Date**. Click **More** to add the **Candidates** and **Hires** filters, or a filter for any custom job req field. Click the **X** on a filter to take it off the bar.

* **Candidates** and **Hires** compare numbers, so you can find, for example, open job reqs with more than 50 candidates, or with no hires yet.
* **Created Date** takes a date range.
* The **Filters** button shows how many filters are in use.
> [!NOTE]
>
> Archived job reqs don't appear in the list unless you filter **Status** to include them. See [Job req statuses](/job-reqs/statuses).
## Saved views
A saved view keeps your filters, columns and sort order together, as a tab across the top of the page. **All Job Reqs** is the starting view. Set up the list, click **Save as New View**, name it and click **Save**.
When you change a view you own, click **Save Changes** to keep the changes, or **Remove Changes** to go back to how it was saved. To rename a view, make it your default, share it or delete it, use the **Actions** menu.
You can share a view with your whole organization or with specific people, and add views your teammates shared from the **+** at the end of the tabs. See [Saved views](/lists-and-exports/saved-views).
> [!TIP]
>
> Build a view for each way you work: one per region or client, one for job reqs with no hires yet, one for your highest-volume roles. Switching tabs is faster than rebuilding filters every morning.
## Export
**1. Click Actions, then Export Data**
The export matches your current view: its filters, search and columns.

**2. Choose the file**
Change the **Export File Name** if you like, and choose **CSV** or **Excel** as the **File Format**.
**3. Click Start Export**
The file downloads when it's ready.
An export includes up to 10,000 job reqs. If you have more, filter the list first.
## FAQ
> [accordion] Can my teammates see my saved views?
>
> Only if you share them. Views start as **Only me**. To share one, open it and click **Actions**, then **Edit View**, and change **Who can see this**. See [Share a view](/lists-and-exports/saved-views#share-a-view).
> [accordion] Why is a job req missing from the list?
>
> Check three things: your filters (including the saved view you're on), whether the job req is archived (filter **Status** to include archived job reqs), and whether you're on its hiring team. Without the *All Job Req Access* permission, you only see job reqs you're on the hiring team for.
> [accordion] Can I sort by a custom job req field?
>
> No. Custom field columns can be shown, edited, filtered and exported, but not sorted.
> [accordion] Why doesn't New Job Req work for me?
>
> Creating a job req needs the *All Job Req Access* permission. Ask your Journeyfront admin to check your security role.
> [accordion] My Job Reqs page looks different from this.
>
> Some accounts can still switch between this page and the classic Job Reqs page. If you see **Switch Back to Classic** at the top, you're on the page described here.
## Related
> [card] [Create a job req](/job-reqs/create)
>
> Set up a new job req with New Job Req.
> [card] [Job reqs overview](/job-reqs/overview)
>
> What's inside a job req and how its tabs fit together.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Add your own fields to job reqs, like client or cost center.
> [card] [Export data](/lists-and-exports/export-data)
>
> Get candidate and hiring data out of Journeyfront.
# Job settings
Source: https://help.journeyfront.com/job-reqs/job-settings
Candidate assignment, interview reminders, referral portal visibility, candidate experience and scoring options for a job req.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission.
>
> **Availability:** The **Referrals** card applies to referral portals, which need to be turned on for your account. Ask your Customer Success Manager.
Each job req has its own settings for how candidates are assigned, when interview reminders go out, which referral portals show the job, how candidates move through their activities, and how the job req is scored and reported. They're all on one page, so you can review a job req's setup at a glance.
To find them, open the job req and go to **Setup**, then **Configurations**. The page has five cards: **Candidate Assignment**, **Interviews**, **Referrals**, **Candidate Experience**, and **Scoring & Reporting**.
When you change something, **Save** and **Cancel** appear at the top of the page. Nothing changes until you click **Save**. If you leave the page with unsaved changes, Journeyfront asks whether to save or discard them.

## Candidate Assignment
**Default Assigned User** decides who new candidates are assigned to when they apply.
* **Single User:** every candidate is assigned to one person.
* **Multiple Users(Round Robin):** candidates are assigned to a list of people in turn, in the order you set. You can add up to 20 people.
Click the **+** to pick someone, and the **x** on a person to remove them. Switching between the two methods clears the list, so pick your people again before you save.
> [!TIP]
>
> The list of people you can pick includes the job req's hiring team. If someone's missing, [add them to the hiring team](/job-reqs/hiring-team) first.
For other ways to assign candidates, such as automation rules and bulk actions, see [Candidate assignment](/workflows/candidate-assignment).
## Interviews
**Interview Reminders** remind candidates about upcoming interviews, to cut down on no-shows. It's on for new job reqs.
* **Reminder Timing:** choose when reminders go out: 1, 2, 4, 12, 24 or 48 hours before the interview. Pick several to send several reminders. New job reqs remind candidates 1 hour and 24 hours before.
* **Email Template:** the email candidates receive. It's shown here for reference; edit it in your company settings.
Turn **Interview Reminders** off and candidates on this job req won't get interview reminders. See [Interview reminders](/interviews/reminders).
## Referrals
**Show on Referral Portals** controls which of your [referral portals](/referrals/portal-setup) list this job req for referrers:
* **All Portals** (the default)
* **No Portals**
* **Specific Portals:** choose the portals in the box that appears.
If your account has no referral portals yet, there's nothing to choose under **Specific Portals**.
**Reward Program** sets what a referral to this job req earns. Each referral keeps the reward program's terms from the day it was made. The program has to cover every portal the job req is on. See [Rewards on job reqs](/referrals/job-req-rewards).
## Candidate Experience
* **Allow Candidates to Take Activities out of Order:** when on, candidates can complete their activities in any order. When off, they must take them in the order they're listed in the workflow. On by default.
* **Allow Re-Takes:** lets a candidate apply to this job req again. When it's on, set **Days before re-apply**: how many days someone must wait before applying again. It doesn't limit their first application. Off by default.
* This is about applying again, not retaking a single activity. For activity retakes, see [Retakes](/assessments/retakes).
* **Gate Steps** (on by default): candidates only see and complete the activities in the step your team or an automation has moved them into (see [Move candidates through steps](/candidates/move-through-steps)). Turn it off to let candidates continue through their activities without waiting.
## Scoring & Reporting
* **Use Predictive Model:** includes the Candidate Predictive Score in the candidate's overall score. When it's on, **Scoring Weights** appear, where you set how much the predictive score and the job req's own attributes each count toward the overall score. See [Predictive models](/scoring/predictive-models).
* **Hide Interviewer Names:** shows interviewers as "Interviewer 1", "Interviewer 2" and so on instead of their names in all reports. On by default for new job reqs.
## FAQ
> [accordion] Where are Require Resume and Require LinkedIn?
>
> On the job req's application form. Set **Resume** or **Linkedin URL** to **Required**, **Optional** or **Hidden** on **Setup**, then **Application Form**. See [Application form](/job-reqs/application-form).
> [accordion] If I change the Default Assigned User, are existing candidates reassigned?
>
> No. The default assigned user applies to candidates as they apply. Candidates who already applied keep their current assignee. To reassign them, see [Candidate assignment](/workflows/candidate-assignment).
> [accordion] Why can't I find the Configurations page?
>
> It's on the **Setup** tab, which needs the *Manage Job Req Settings* permission. Ask your Journeyfront admin to check your security role.
> [accordion] Can I use different settings for each job req?
>
> Yes. Every job req has its own configurations. When you [duplicate a job req](/job-reqs/create#start-from-an-existing-job-req), the copy starts with the same settings.
## Related
> [card] [Candidate assignment](/workflows/candidate-assignment)
>
> Every way to decide who owns each candidate.
> [card] [Interview reminders](/interviews/reminders)
>
> What candidates receive before an interview.
> [card] [Workflows overview](/workflows/overview)
>
> The steps and activities candidates move through.
> [card] [Predictive models](/scoring/predictive-models)
>
> How predictive scores fit into the overall score.
# Job reqs overview
Source: https://help.journeyfront.com/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](/hiring-classes/overview), 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](/job-reqs/job-reqs-page) 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](/job-reqs/statuses). 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

| Tab |
What it's for |
| **Hiring Classes** |
The groups of hires for this job req, each with its own openings and start date. See [Hiring classes](/hiring-classes/overview). |
| **Dashboard** |
Reporting for this job req. See [Job req dashboards](/reporting/job-dashboards). |
| **Candidates** |
Everyone who has applied, where they are in the workflow and their scores. See [The Candidates page](/candidates/candidates-page). |
| **Setup** |
How the job req is built. Only shown to users with the *Manage Job Req Settings* permission. |
| **Activity** |
A history of changes to the job req's setup. |
## 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](/job-reqs/create).
* **Application Form:** the fields candidates fill in when they apply. See [Application form](/job-reqs/application-form).
* **Attributes:** the traits and skills this job req measures. See [Attributes](/scoring/attributes).
* **Workflow:** the steps, activities and automation rules candidates move through, and its versions. See [Workflows overview](/workflows/overview).
* **Team:** who works on the job req. See [Hiring team](/job-reqs/hiring-team).
* **Predictive Models:** see [Predictive models](/scoring/predictive-models).
* **Job Postings:** where the job is advertised. See [Job postings](/sourcing/job-postings).
* **Configurations:** candidate assignment, interview reminders, referral portal visibility, the candidate experience, and scoring and reporting options. See [Job settings](/job-reqs/job-settings).
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](/sourcing/lead-ads#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.

> [!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](/job-reqs/create)
>
> Set up a new job req and get it ready for candidates.
> [card] [Job req statuses](/job-reqs/statuses)
>
> Deactivate, close, archive, duplicate or delete a job req.
> [card] [Workflows overview](/workflows/overview)
>
> The steps and activities every candidate follows.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Fill wave after wave of hires from one job req.
# Job req statuses
Source: https://help.journeyfront.com/job-reqs/statuses
Activate, deactivate, close, archive, duplicate or delete a job req, and what each one does.
> [!NOTE]
>
> **Who can do this:** Each action has its own permission: *Deactivate Job Reqs*, *Close Job Reqs*, *Duplicate Job Reqs*, *Archive Job Reqs* and *Delete Job Reqs*. Existing security roles have all five turned on. A role you create with **New Role** starts with every permission off, so turn on the ones it needs. Admins manage them under **Settings**, then **Security**. See [Security roles and permissions](/account-setup/security-roles).
A job req's status decides whether candidates can apply and whether its job postings are live. Change it from the **Actions** menu at the top right of the job req. The current status shows in the header, under the job req's name.
## The statuses
| Status | What it means | Candidates can apply | Job postings | On the Job Reqs page |
| - | - | - | - | - |
| **Active** | Open and taking applications | Yes | Live, as you've set them | Shown |
| **Inactive** | Paused, or not opened yet. New job reqs start here. | No | Turned off | Shown |
| **Closed** | Finished hiring | No | Turned off | Shown |
| **Archived** | Put away, but kept with all its history | No | Turned off | Hidden unless you filter **Status** to include it |
When a job req isn't Active, its application link tells candidates: "This position is not accepting new applications at this time."
When a job req becomes Inactive, Closed or Archived, Journeyfront turns off its job postings and takes them down from job boards. They don't come back on by themselves. After you reactivate a job req, turn its postings back on under **Setup**, then **Job Postings**: open each posting and turn on **Make job posting page active** and **Post job to job board**. See [Job postings](/sourcing/job-postings).
## The Actions menu
| Action | When you see it | What it does | Permission |
| - | - | - | - |
| **Deactivate Job Req** | Active | Makes the job req Inactive. You confirm first. | *Deactivate Job Reqs* |
| **Activate** | Inactive | Makes the job req Active right away. | *Deactivate Job Reqs* |
| **Close Job Req** | Active or Inactive | Makes the job req Closed. You confirm first. | *Close Job Reqs* |
| **Re-Open** | Closed | Makes the job req Inactive, ready for you to activate. | *Close Job Reqs* |
| **Archive Job Req** | Active, Inactive or Closed | Makes the job req Archived right away. | *Archive Job Reqs* |
| **Un-archive Job Req** | Archived | Makes the job req Inactive, ready for you to activate. | *Archive Job Reqs* |
| **Duplicate Job Req** | Any status | Makes a copy of the job req's setup. You confirm first. | *Duplicate Job Reqs* |
| **Delete Job Req** | Any status | Deletes the job req. You confirm first. | *Delete Job Reqs* |
The same menu also has **Invite Candidates**, **Add New Candidate** and **Import Candidates** (see [Invite candidates](/sourcing/invite-candidates), [Add candidates](/sourcing/add-candidates) and [Import candidates](/sourcing/import-candidates)), and **Export Data**, which downloads the job req's candidates as a CSV file (see [Export data](/lists-and-exports/export-data)). Closed and archived job reqs don't offer the invite, add and import actions, and an inactive job req won't let you add or import candidates.

## Deactivate or activate
Deactivate a job req to pause applications for a while, for example when you have enough candidates for the next class. Click **Actions**, then **Deactivate Job Req**, and click **Deactivate**.
To open it again, click **Actions**, then **Activate**. Then turn its job postings back on.
Publishing a new workflow version on an inactive job req also makes it Active. Keep that in mind if you publish changes while a job req is paused.
## Close or re-open
Close a job req when you've finished hiring for it. Click **Actions**, then **Close Job Req**, and click **Close**. Your team can still open it and see its candidates, but no one can apply and you can't invite, add or import candidates.
If you need it again, click **Actions**, then **Re-Open**. It comes back as Inactive; activate it when you're ready for applications.
## Archive or un-archive
Archive a job req to clear it out of your Job Reqs list while keeping everything in it. Click **Actions**, then **Archive Job Req**. There's no confirmation step.
To find an archived job req, filter **Status** on the Job Reqs page to include archived job reqs. Open it and click **Actions**, then **Un-archive Job Req**. It comes back as Inactive.
> [!TIP]
>
> Archive old job reqs rather than deleting them. Archiving keeps their candidates, scores and history, and you can always bring them back.
## Duplicate
Click **Actions**, then **Duplicate Job Req**, and click **Duplicate**. Journeyfront copies the job req's setup, including its workflow, application form, settings and hiring team, and opens the copy. Candidates, hiring classes and job postings aren't copied. See [Start from an existing job req](/job-reqs/create#start-from-an-existing-job-req).
## Delete
Click **Actions**, then **Delete Job Req**, and click **Delete**. You're taken back to the Job Reqs page.
> [!WARNING]
>
> Deleting a job req can't be undone. If you might need its candidates or history later, archive it instead, or export what you need first.
## Status history
Every status change is recorded on the job req's **Activity** tab, with who made it and when. See [Job reqs overview](/job-reqs/overview#activity-tab).
## FAQ
> [accordion] Why can't candidates apply to my job req?
>
> Only Active job reqs take applications. Check the status under the job req's name. New job reqs start Inactive; click **Actions**, then **Activate** when you're ready.
> [accordion] I reactivated a job req, but it's not on the job boards.
>
> Deactivating, closing or archiving a job req turns off its job postings, and reactivating doesn't turn them back on. Go to **Setup**, then **Job Postings**, and turn each posting back on.
> [accordion] What's the difference between Inactive and Closed?
>
> Both stop new applications and turn off job postings. Use Inactive for a pause: **Activate** opens the job req again in one click. Use Closed when you've finished hiring: your team can't invite, add or import candidates, and re-opening it brings it back as Inactive.
> [accordion] Why don't I see Close or Delete in the Actions menu?
>
> Each action needs its own permission, and some only appear in certain statuses. Ask your Journeyfront admin to check your security role under **Settings**, then **Security**.
> [accordion] Where did my archived job req go?
>
> Archived job reqs are hidden from the Job Reqs page by default. Filter **Status** to include archived job reqs to see them.
## Related
> [card] [Job reqs overview](/job-reqs/overview)
>
> What's inside a job req.
> [card] [Create a job req](/job-reqs/create)
>
> Create a job req or copy an existing one.
> [card] [Job postings](/sourcing/job-postings)
>
> Turn postings on and off on your career site and job boards.
> [card] [Security roles](/account-setup/security-roles)
>
> Who can deactivate, close, archive, duplicate and delete job reqs.
# Export data
Source: https://help.journeyfront.com/lists-and-exports/export-data
Download candidates, job reqs and hiring classes to a CSV or Excel file.
> [!NOTE]
>
> **Who can do this:** Anyone can export the lists they can see. Exports only include the job reqs and candidates you have access to, and values in private fields only for users with *Private Data Access*.
When you need your data in a spreadsheet, for a weekly report, a client update or your own analysis, export it from the list it lives in. Most exports match exactly what you see on screen: your current view, search, filters and columns.
## What you can export
| From | What you get | Formats | Limit |
| - | - | - | - |
| **Candidates** page, or a job req's **Candidates** tab | One row per Candidate Application, with the columns you've chosen | CSV or Excel | Excel up to 10,000 rows. Larger CSV exports are emailed to you. |
| **Job Reqs** page | One row per job req, with the columns you've chosen | CSV or Excel | 10,000 job reqs |
| **Classes** page, or a job req's **Hiring Classes** tab | One row per hiring class, with the columns you've chosen | CSV or Excel | 10,000 hiring classes |
| A job req's **Actions** menu, **Export Data** | A fixed set of columns for every candidate on the job req | CSV | None |
| **Referrals** page | Your current view of referrals | CSV or Excel | 10,000 rows. See [The Referrals page](/referrals/referrals-page). |
## Export candidates
**1. Set up the list**
On the **Candidates** page or a job req's **Candidates** tab, pick the tab or saved view, search, filters and columns you want in the file. See [The Candidates page](/candidates/candidates-page).
**2. Click Actions, then Export Data**
The **Export Data** window shows the view you're exporting and how many rows and columns the file will have.
**3. Name the file and pick a format**
Change the **Export File Name** if you like, and choose **CSV** or **Excel** under **File Format**.
**4. Click Start Export**
The file downloads when it's ready. Click **Done** to close the window.

### What's in the file
* **Application ID** is always the first column, then **Name**, then your columns in the order they appear on screen.
* The **Interview** and **AI Agent** columns are actions rather than data, so they aren't exported.
* Screening question, score, custom field, job req field and hiring class field columns export like any other column. Columns from the job req or hiring class are headed with where they come from, like "Hiring Class: Location".
* File upload fields export as a link to the file.
* Values in fields marked private are only included if your security role has *Private Data Access*.
> [!TIP]
>
> Save a view with the exact columns and filters you need for a recurring report, like "Hires this week". Then each export is two clicks. Share the view with whoever else runs the report, so everyone exports the same thing. See [Saved views](/lists-and-exports/saved-views).
### Large exports
Excel files are limited to 10,000 rows. To export more, choose **CSV**: Journeyfront prepares the file in the background and emails you a download link when it's ready. The file is compressed (a `.csv.gz` file; most computers open it with a double-click) and the link expires after two days.
## Export job reqs
On the **Job Reqs** page, set up your view, then click **Actions**, then **Export Data**. Change the **Export File Name** if you like, choose **CSV** or **Excel**, and click **Start Export**. The file has the columns you've chosen, including custom job req fields. An export includes up to 10,000 job reqs; if you have more, filter the list first. See [The Job Reqs page](/job-reqs/job-reqs-page).
## Export hiring classes
On the **Classes** page, or a job req's **Hiring Classes** tab, click **Actions**, then **Export Data**, then choose the file name and format and click **Start Export**. The file matches your view, up to 10,000 hiring classes. If your view has more, the window warns you that only the first 10,000 rows will be exported.
## Export a job req's candidates
To download every candidate on one job req with a standard set of columns, open the job req and click **Actions**, then **Export Data**. A CSV file downloads right away, named after the job req and the date.
It has one row per candidate, newest first, with these columns: first and last name, email, gender, date of birth, city, state, application date, status, job req title, overall score, rejection reason and rejection note, percent of the application completed, and assigned user.
> [!NOTE]
>
> The columns in this file are fixed. For other columns, like custom fields, screening answers or step, export from the job req's **Candidates** tab instead. The gender column is an older profile field, not the candidate's EEOC answer; EEOC answers aren't included in any export. See [EEOC reporting](/reporting/eeoc).
## Other exports
* **Employees:** on the **Employees** page, click **Actions**, then **Export Data**, to download your employees as a CSV file. See [Employee records](/employees/employee-records).
* **E-consent signatures:** see [E-consent forms](/onboarding/e-consent-forms).
* **Dashboards:** company and job req dashboards don't have a print or PDF option. See [Dashboards overview](/reporting/dashboards).
## FAQ
> [accordion] Which fields can I export?
>
> Any column you can add with **Edit Columns** on the Candidates page, except **Interview** and **AI Agent**. That includes your personal and application fields, screening question answers, scores, job req fields and hiring class fields. Add the column to your view, then export.
> [accordion] Why is my export missing some candidates?
>
> The export matches your current tab, search and filters, and only includes job reqs you have access to. Clear your filters, or check that you're on the right tab, and export again.
> [accordion] Why did my export come by email?
>
> Candidate exports over 10,000 rows are prepared in the background as a compressed CSV file, and you get an email with a download link. The link expires after two days.
> [accordion] Why can't I export to Excel?
>
> Excel exports are limited to 10,000 rows. Filter your view to fewer rows, or choose CSV.
> [accordion] Why are some columns blank in my file?
>
> Values in private fields are only exported for users with *Private Data Access*. Otherwise, a blank cell usually means the candidate has no value for that field.
> [accordion] Can I schedule a recurring export?
>
> Not from these pages. Save a view for the report you need and export it when you need it. To send data to another system automatically, see [Integrations overview](/integrations/overview).
## Related
> [card] [Saved views](/lists-and-exports/saved-views)
>
> Save and share the view you want to export.
> [card] [The Candidates page](/candidates/candidates-page)
>
> Build the view you want to export.
> [card] [The Job Reqs page](/job-reqs/job-reqs-page)
>
> Filter and export your job reqs.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Charts and trends without leaving Journeyfront.
# Saved views
Source: https://help.journeyfront.com/lists-and-exports/saved-views
Save the lists you use every day as tabs, share them with your team, and choose which tabs you see.
> [!NOTE]
>
> **Who can do this:** Everyone. A shared view only ever shows you the job reqs, candidates and classes you already have access to.
[Saved views](https://www.youtube.com/embed/ANnE21ZttE8)
A saved view remembers a list's filters, columns and sort order, and opens it as a tab above the list. Build "New applicants to screen" or "Ready for offer" once, and it's one click away every morning. Share it, and your whole team works from the same list instead of each person rebuilding the filters and getting slightly different results.
Saved views work the same way on every list:
| Page | Sharing |
| - | - |
| **Candidates** | Yes |
| A job req's **Candidates** tab | Yes |
| **Job Reqs** | Yes |
| **Classes**, and a job req's **Hiring Classes** tab | Yes |
| **Referrals** | Not yet. Everything else on this page works there. |

The first tab is the page's standard list, such as **All Job Reqs** or **All Candidates**. Your saved views follow it. A view with a people icon is shared: hover over it to see who shared it, or who you've shared it with.
## Create a view
There are two ways to start, depending on what's on your screen.
### From the list you have now
Use this when you've already filtered and arranged the list the way you want it.
**1. Set up the list**
On the page's starting tab, such as **All Job Reqs** or **All Candidates**, add your filters and columns and sort the list. As soon as the list differs from the starting tab, **Save as New View** appears in the toolbar. To start from a saved view instead, open it and click **Actions**, then **Clone View**.

**2. Click Save as New View**
The **Create New View** panel opens with your current filters, columns and sort order.
**3. Name it and choose who can see it**
Enter a **View Name**. Turn on **Make Default** if you want the page to open on this view. Under **Who can see this**, keep **Only me** or share it (see [Share a view](#share-a-view)).
**4. Click Save**
The view appears as a new tab and opens. The tab you started from is unchanged.
### From scratch
Click **+** at the end of the tabs, then **Create a new view**. The panel opens on the page's standard columns with no filters, whatever tab you were on. Name the view, click **Save**, then add the filters and columns you want and click **Save Changes**.

> [!TIP]
>
> When you're hiring at volume, build a view for each part of your day: "New today" for fresh applicants, "Ready to interview" for one step, "Waiting on me" for candidates assigned to you. Make the one you check first your default.
## Update your view
Open a view you own and change its filters, columns or sort order. The toolbar shows two buttons:
* **Save Changes** updates the view.
* **Remove Changes** puts the list back to how the view was saved.

To keep the changes as a separate view and leave this one as it was, click **Actions**, then **Clone View**.
To rename the view, make it your default or change who can see it, click **Actions**, then **Edit View**.
## The Actions menu
Everything you can do to the open view is in **Actions**, at the right of the toolbar.

| Action |
What it does |
| **Edit View** |
Rename the view, make it your default, or change who can see it. On a view someone else shared with you, you can't edit it, so this option is called **View Details** instead. See [Views shared with you](#views-shared-with-you). |
| **Export Data** |
Download the list as you see it, as a CSV or Excel file. See [Export data](/lists-and-exports/export-data). |
| **Clone View** |
Make a private copy of the view, named "\[view name] (clone)", from what's on screen right now, unsaved changes included. The copy opens straight away. |
| **Unpin View** |
Take the view off your tabs. See [Choose your tabs](#choose-your-tabs). |
| **Delete View** |
Delete a view you own, for everyone it's shared with. This can't be undone. |
**Edit View**, **Unpin View** and **Delete View** only appear when a saved view is open, and **Delete View** only on a view you own.
## Share a view
**1. Open the view's settings**
For a new view, use **Save as New View** or **+**, then **Create a new view**. For a view you already have, open it and click **Actions**, then **Edit View**.
**2. Choose who can see it**
Open **Who can see this** and pick an option.

| Option | Who sees it |
| - | - |
| **Only me** | Just you. This is where every view starts. |
| **Specific people** | Only the people you name. The view is added to their tabs. |
| **Everyone in my organization** | Anyone in your account can add it from the **+** menu. It isn't added to anyone's tabs automatically. |
**3. Name the people (Specific people only)**
Under **Share with**, search by name or email and pick each person. You need at least one.

**4. Click Save**
The view's tab gets the people icon. People you named see the view the next time they open the page.

Only you can change, rename or delete a view you've shared. To stop sharing, set **Who can see this** back to **Only me**. People you'd named lose the tab.
> [!NOTE]
>
> A shared view shares the filters and columns, never more access. If your view filters to job reqs a teammate isn't on, those rows don't appear for them, and the list explains why. People aren't notified when you share a view with them.
> [!TIP]
>
> Share the views your team should all work from, like "Ready for offer" or "Needs a callback", with everyone, and tell the team they're in the **+** menu. Use **Specific people** for a view that only makes sense for one group, like the recruiters on one client's hiring push.
## Views shared with you
A view someone shared with you is read-only. You can open it, filter it for a quick look and export it, but you can't save changes to it, rename it or delete it. **Save Changes** isn't in the toolbar, and **Actions** shows **View Details** instead of **Edit View**.

**View Details** opens the **Shared View** panel. It tells you who shared the view, and whether they shared it with you by name or with your whole organization. You can read the panel, but nothing in it can be changed. To make your own version, click **Clone View** in the panel, or in the **Actions** menu. Your copy is private, and you can change it however you like without touching the original.

To change a shared view's columns, filters or sort order, click **Clone View** and edit your copy.
## Choose your tabs
You decide which views sit on your tabs. Taking a view off your tabs doesn't delete it.
**Remove a tab:** hover over a saved view's tab and click the **x**, or open the view and click **Actions**, then **Unpin View**. Confirm with **Remove**.


**Add a tab:** click **+**. Under **Add an existing view**, you'll find views shared with you and your own views you removed earlier. Search by view name or by the name of the person who made it, then click a view to add it to your tabs and open it.
**Reorder tabs:** drag a tab by the handle on its left. Views shared with you stay at the end, because their order is set by the person who shared them.
When you have more tabs than fit, use the arrows at either end to scroll through them, or click **More** to see every view in a list.
## Views on a job req
A view you save on a job req's **Candidates** or **Hiring Classes** tab belongs to that job req: it only appears there, and the **+** menu there only offers views saved on that job req. Sharing works the same way, but only people who can access the job req can see or add its views.
| Where you save the view | Where it appears | Who can see it, if you share it |
| - | - | - |
| The **Candidates**, **Job Reqs** or **Classes** page | On that page only | The people you share it with |
| A job req's **Candidates** or **Hiring Classes** tab | On that tab, on that job req only | The people you share it with who can also access that job req |

> [card] [Hiring team](/job-reqs/hiring-team)
>
> See who can access a job req, and so who can see the views saved on it.
## FAQ
> [accordion] Can someone change a view I shared with them?
>
> No. They can open it, export it and clone it, but only you can change, rename or delete it.
> [accordion] What happens if I share a view filtered to job reqs a teammate isn't on?
>
> They only see rows for the job reqs they have access to. If they have access to none of them, the list is empty, with a message saying the view is filtered to job reqs they can't access.
> [accordion] If I remove a view from my tabs, is it deleted?
>
> No. It only leaves your tabs. Add it back any time from the **+** menu. To delete a view you own for everyone, use **Actions**, then **Delete View**.
> [accordion] What's the difference between Clone View and Save as New View?
>
> **Save as New View** appears on the starting tab once you've changed the list, and opens the panel so you can name the view and choose who can see it. **Clone View** is in **Actions** on a saved view, and makes a private copy of it straight away, named for you.
> [accordion] Why doesn't a view I shared with everyone show up on my teammates' tabs?
>
> Sharing with everyone makes the view available, without adding a tab for the whole organization. Teammates add it from the **+** menu. To put it on someone's tabs, share it with them by name.
> [accordion] Do people get notified when I share a view?
>
> No. People you name see the new tab the next time they open the page. Views shared with everyone wait in the **+** menu.
> [accordion] How do I change which view opens first?
>
> Open the view and click **Actions**, then **Edit View**. Turn on **Make Default** and click **Save**. You can only make your own views the default.
## Related
> [card] [The Candidates page](/candidates/candidates-page)
>
> Filters and columns for candidates.
> [card] [The Job Reqs page](/job-reqs/job-reqs-page)
>
> Filters and columns for job reqs.
> [card] [Export data](/lists-and-exports/export-data)
>
> Download any view as a spreadsheet.
> [card] [See who hasn't booked](/interviews/who-hasnt-booked)
>
> A saved view your whole team can work from.
# Send offers in bulk
Source: https://help.journeyfront.com/offers/bulk-send
Create, generate and send offers to a whole group of candidates at once, such as a hiring class.
> [!NOTE]
>
> **Who can do this:** Users with the *View and Send Offers* permission.
>
> **Availability:** Sending the offers for signature uses the E-Signatures add-on and one e-signature request per candidate. Without it, you can still create the offers and generate the documents in bulk. Ask your Customer Success Manager.
When a whole hiring class gets nearly the same offer, there's no need to open each Candidate Application and repeat the same steps. Send offers in bulk to enter the shared terms once, review every candidate's offer on one screen, adjust anyone who's different, and send them all together. Each offer is personalized automatically from the candidate's own details.
[Bulk Send Offers](https://www.youtube.com/embed/8AdtJOM0oqA)
## Before you start
* The job req needs an Offer activity in its workflow, pointing at an [offer package](/offers/offer-packages). The package pre-fills the bulk flow, so offer day becomes review and send.
* If your hiring classes have their own packages, each candidate's offer starts from their class's package.
* All the candidates in one run must be on the same job req.
## Send offers without moving candidates
Use **Send Offers** to create offers wherever the candidates are now. Nobody changes step.
**1. Select candidates**
On the **Candidates** page or a job req's candidates page, select candidates from the same job req and click **Send Offers** in the actions toolbar.

**2. Select Offer**
Choose the **Offer Activity** to create the offers on. Each option shows the step it belongs to. If the job req has only one, it's already selected. A summary shows the offer package the offers start from.
**3. Offer**
The middle of the progress bar shows your Offer activity's name, with small dots for its parts. First, enter the shared offer details once and review every candidate's offer in the grid. See [Review each candidate's offer](#review-each-candidates-offer). Then choose the documents and, with the E-Signatures add-on, the signing options. These work the same as for a single offer; see [Send an offer](/offers/send-offers#send-an-offer) and [E-signatures](/offers/e-signatures).
**4. Review & Send**
Check the summary and click **Create & Send Offers** (or **Create Offers** if you're not sending for signature).
## Send offers while moving candidates into your offer step
Use **Change Step** to move a group into the step that holds your Offer activity and create their offers in the same flow.
**1. Select candidates and click Change Step**
On the **Candidates** page or a job req's candidates page, select the candidates and click **Change Step**.
**2. Choose the destination step**
If the step contains an Offer activity, the Offer activity appears in the window's progress bar.

**3. Turn on Bulk Create Offers**
Click **Next** to reach the part of the window named after your Offer activity, and turn on **Bulk Create Offers**. A summary shows the offer package the offers start from. Leave it off to move the candidates without offers.

**4. Offer details, documents and e-signature**
Complete these the same way as with **Send Offers**.
**5. Review & Execute**
Check the summary and click **Move Candidates & Create Offers**. The candidates move first, then each offer is created.
> [!TIP]
>
> The move always finishes first. If one candidate's offer fails, they're still safely in the right step, and you can finish their offer from their Candidate Application.
The same window opens when you change one candidate's step from their Candidate Application to a step with an Offer activity. Turn on **Create Offer** to create their offer as part of the move.
## Review each candidate's offer
The offer details, the first part of the **Offer** step, are where the bulk flow saves you the most time.
* **Shared values:** enter a term once, such as salary or start date, and it applies to everyone. Package defaults are already filled in, and locked ones can't be changed. If the Offer activity isn't locked, you can choose a different **Offer package** for the run.
* **Review Candidate Offer Details:** a grid shows every candidate's exact values, including the candidate, job req and hiring class details that will go into the documents. You can fix a candidate's phone, address and custom fields in the grid, and those changes save to their Candidate Profile.
* **Include or exclude:** use the checkboxes to leave anyone out of this run.
### Change one candidate's value
If one person in the group negotiated a different salary or start date, edit just their value:
1. Hover over the value in the grid and click it.
2. Enter the new value in the editor that opens. It uses the same controls as the single offer form, like date pickers and currency selection.
3. Click **Save**. The edited value shows in blue, and only that candidate is affected.
To undo an edit, click the value again and choose **Use Default**. A shared value that's been edited for some candidates shows **Multiple Values**; **Edit for all** replaces those individual edits.

> [!TIP]
>
> Required values that are missing are flagged in the grid, and you can't continue until they're filled in or those candidates are deselected. Click the value to fill it in, or uncheck the candidate and send their offer later.
## Candidates with different offer packages
When the selected candidates' offers would start from different packages, for example because they're in hiring classes with their own packages, Journeyfront shows each group with its package and candidates. Bulk offers use one package for everyone, so choose which group to create offers for in this run. Run the flow again for the other group.
In a **Change Step** run, the candidates outside the chosen group still move; they just don't get an offer yet.
## Who's skipped automatically
* **Candidates who already have an offer** on the Offer activity are shown with their existing offer's values greyed out, and skipped. A bulk run never overwrites an offer that's already in progress.
* **Candidates outside the chosen package group** are skipped in that run.
## Track the run
When you confirm, a progress table shows each candidate's offer details, documents and e-signature request as they're created. Each candidate is processed on their own: if something fails for one person, the table shows which part failed, and the rest of the group finishes normally. Finish any failed offer from that candidate's Candidate Application.


## FAQ
> [accordion] Do the candidates have to be on the same job req?
>
> Yes. Offers use the job req's offer setup, so each run is for one job req. On the **Candidates** page, **Send Offers** appears once your selection is all from the same job req, and on the same version of its workflow. If some candidates are still on an older workflow version, run them separately.
> [accordion] How many candidates can I include at once?
>
> Up to 500 candidates per run.
> [accordion] Does Send Offers move the candidates?
>
> No. **Send Offers** creates and sends offers where the candidates are now. To move them and send offers together, use **Change Step**.
> [accordion] Do I have to send e-signatures in the same run?
>
> No. You can create the offer details only, or details plus documents, and send for signature later from each Candidate Application. Sending for signature needs the documents to be generated in the same run, since they're what gets signed.
> [accordion] What if I don't have enough e-signature credits for everyone?
>
> Journeyfront warns you in the e-signature part of the **Offer** step when you have fewer credits than candidates. Requests beyond your remaining credits won't send. See [E-signatures](/offers/e-signatures#e-signature-credits).
> [accordion] Are bulk offers different from offers sent one at a time?
>
> No. They use the same offer fields, packages, templates and e-signature setup, and they appear on each candidate's Offer tab exactly like an offer sent on its own.
## Related
> [card] [Send an offer](/offers/send-offers)
>
> The same flow for one candidate, and managing an offer afterward.
> [card] [Offer packages](/offers/offer-packages)
>
> Give each hiring class its own terms and documents.
> [card] [E-signatures](/offers/e-signatures)
>
> Signing options, tracking and credits.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who start and train together.
# E-signatures
Source: https://help.journeyfront.com/offers/e-signatures
Send offers for electronic signature, track every signer, and see what candidates experience when they sign.
> [!NOTE]
>
> **Who can do this:** Users with the *View and Send Offers* permission. Customizing the candidate's email needs *Company Settings Access*.
>
> **Availability:** E-signatures use the E-Signatures add-on and e-signature credits. Ask your Customer Success Manager.
E-signatures let candidates sign their offer online, from any device, without leaving your hiring process. The offer letter and every supporting document go to the candidate together as **one envelope**, with one email and one signing link. As people sign, the offer updates on its own, and the signed documents come back to the Candidate Application.
## How the envelope works
Every offer goes out as one envelope: the offer letter first, then each document in the order your [offer package](/offers/offer-packages) lists them. Every document is personalized with the same candidate and offer details.
* Documents with [signature fields](/offers/templates#signature-fields) are signed.
* Documents without signature fields, and PDFs, are included for the candidate to read.
* The candidate completes everything in one sitting.
## Send an offer for signature
You can send the signature request in two ways:
* **As part of Send Offer:** the e-signature part of the **Offer** step in the Send Offers window (the last dot next to your Offer activity's name), for [one candidate](/offers/send-offers) or [a group](/offers/bulk-send).
* **From the Offer tab:** once the documents are generated or uploaded, click **Send request** in the card's **E-Signature** section. In the **Offer E-signature** window, choose the options below and a **Title** for the request, click **Preview** to check the documents as they'll be signed, then click **Send Offer**.
Either way, you choose these options:
| Option | What it does |
| - | - |
| **Only have candidate sign** | Sends the documents to the candidate only, with no company signer. In Send Offers, it's turned on for you when no document in the envelope has a company signature field. |
| **Company Signer** | The person on your team who co-signs. |
| **Automatically Expire** | **Never**, or a **Date/Time** after which the request expires. In Send Offers, it's filled in from the Offer Expiration Date when the offer has one. |
| **Signing Order** | **Candidate First**, **Company First**, or **Send at same time**. |
| **Email Subject** and **Email Message** | The message is an optional note added to the candidate's email. The subject is filled in for you and is used on reminder emails; the first email's subject comes from the Offer E-Signature Candidate template (see [Customize the candidate's email](#customize-the-candidates-email)). |

> [!TIP]
>
> Expected a company signer but **Only have candidate sign** is already on? None of the documents has a company signature field. Add `{{COMPANY_E_SIGNATURE}}` to the template where your signer should sign, and upload it again.
## Track signatures
The **E-Signature** section of the offer's card on the Candidate Application shows each signer and their status:
| Status | What it means |
| - | - |
| Not Sent | Waiting for their turn in the signing order. |
| Not Opened | The email was sent, but the signing link hasn't been opened. |
| Opened | The signer opened the signing link. |
| Signed | The signer finished signing. |
With **Candidate First** or **Company First**, only the first signer is emailed at the start. The second is emailed automatically when the first finishes. With **Send at same time**, both are emailed at once.

The offer's own status follows along, from **Offer Sent** to **Offer Accepted**. See [offer statuses](/offers/send-offers#offer-statuses).
## Remind signers
* Click **Send reminder** next to a signer to email them again.
* Some accounts can also send reminders automatically: open the job req's Offer activity settings in its workflow and turn on **Auto reminders** under **Reminders**, then choose the **Days before first reminder** and how often to **Repeat reminder**. Automatic reminders depend on your e-signature setup and aren't available on every account; if you don't see **Reminders** there, use **Send reminder**.
## Change or cancel a request
* **Preview** shows the request as it was prepared for signing.
* **Update request** reopens the **Offer E-signature** window so you can change the signers or settings of a request that hasn't been completed, preview it and send it again.
* **Cancel request** voids the request. The signers are removed and the offer becomes **Offer Canceled**. You can send a new request at any time.
## When everyone signs
1. Each signed document is saved on the offer under **Documents**, plus one combined **Signed package (all documents)** PDF.
2. The offer becomes **Offer Accepted**.
3. The signing is recorded in the candidate's activity history.
If the candidate declines in the signing screen, the offer becomes **Offer Declined**. If the request expires, it becomes **Offer Canceled**.
## What candidates see
* An email from your company, with the job title, a link to sign, your message, and the expiry date if there is one.
* One signing link for the whole offer. They read each document and sign wherever there's a signature field, on a computer or phone.
* Documents that don't need a signature, like a benefits guide, are there to read in the same session.
* An option to decline instead of signing.
* A confirmation email once everyone has signed, with a copy of the signed documents attached.
## Customize the candidate's email
1. Go to **Settings**, then **Templates**, then **E-mail Template**, and open the **System Emails** tab.
2. Open the **Offer E-Signature Candidate** template.
3. Edit the subject and body, then click **Save**. See [Email templates](/communication/email-templates).
The email can include the candidate's name, your company name, the job title, the signing link, your custom message and the expiry date. The company signer's email and the reminder emails aren't templates you can edit; reminders use the request's **Email Subject** and **Email Message**.
## If your account uses DocuSign
Some accounts send e-signatures through DocuSign. The workflow is the same: send, track and receive the signed letter back automatically. These envelopes include the offer letter only; supporting documents in the package aren't sent. DocuSign sends the signing email itself, using the **Email Subject** and **Email Message** you enter, so the Offer E-Signature Candidate template doesn't apply.
## E-signature credits
Each signature request uses your account's e-signature credits. You can see your balance under **Settings**, then **Add-Ons**. When you run out, you'll see a message on the offer and can't send new requests until more credits are added. When you send offers in bulk, Journeyfront warns you if you have fewer credits than candidates. See [Add-ons](/account-setup/add-ons).
## FAQ
> [accordion] Can the candidate sign several documents at once?
>
> Yes. Every document in the offer package goes out in one envelope and is signed in one session.
> [accordion] Can a PDF be signed?
>
> No. PDFs are included for the candidate to read. Anything that needs a signature must be a Word template with signature fields. See [templates](/offers/templates).
> [accordion] Can I send an offer to just the candidate, with no company signer?
>
> Yes. Turn on **Only have candidate sign**. In Send Offers, it's already on when no document has a company signature field.
> [accordion] What if the candidate declines or the link expires?
>
> Declining sets the offer to **Offer Declined**. Expiry sets it to **Offer Canceled**. Both are recorded in the activity history, and you can send a new request.
> [accordion] Where are the signed documents?
>
> On the Offer tab of the Candidate Application, under **Documents**: each signed document on its own, plus the combined PDF. They stay there for your records.
> [accordion] The candidate signed a paper copy. How do I record it?
>
> In the offer's **Documents** section, click **Upload**, choose the file and tick **This is a signed copy**. Then record their answer with **Accept**. See [Send an offer](/offers/send-offers#documents).
> [accordion] How do I turn on e-signatures?
>
> E-signatures are an add-on. Ask your Customer Success Manager.
## Related
> [card] [Send an offer](/offers/send-offers)
>
> Create and send one candidate's offer.
> [card] [Offer letter and document templates](/offers/templates)
>
> Add signature fields to your templates.
> [card] [Offer packages](/offers/offer-packages)
>
> What goes in the envelope, and in what order.
> [card] [Add-ons](/account-setup/add-ons)
>
> E-signature credits and other add-ons.
# Offer fields and merge keys
Source: https://help.journeyfront.com/offers/offer-fields
Define the terms every offer captures, and use merge keys to put any value into your offer letters and documents.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access*.
**Offer fields** are the terms of an offer: salary, start date, employment type, pay frequency, bonus, hiring manager and anything else your offers need. **Merge keys** are the keys, like `{{SALARY}}` or `{{CANDIDATE_NAME}}`, that place values into your offer letters and documents. Every offer field has a merge key, and so do the candidate, job req, hiring class and company details Journeyfront already knows, so your documents fill themselves in.
## Offer fields
Offer fields appear on the offer form your team completes when sending an offer, and they're what an [offer package](/offers/offer-packages) can pre-fill and lock. They apply to every job req in your account.
Go to **Settings**, then **Offers**, then **Offer Fields**.

### Default fields
Every account starts with these offer fields:
| Field | Type | Merge key | Required by default |
| - | - | - | - |
| Job Title | Short Text | `{{JOB_TITLE}}` | Yes |
| Start Date | Date | `{{START_DATE}}` | Yes |
| Today's Date | Date | `{{TODAYS_DATE}}` | No |
| Offer Expiration Date | Date | `{{OFFER_EXPIRATION_DATE}}` | No |
| Employment type | Multiple Choice | `{{EMPLOYMENT_TYPE}}` | No |
| Salary | Currency | `{{SALARY}}` | No |
| Pay Frequency | Multiple Choice | `{{PAY_FREQUENCY}}` | No |
| Bonus | Currency | `{{BONUS}}` | No |
| Options | Number | `{{OPTIONS}}` | No |
| Hiring Manager | User | `{{HIRING_MANAGER}}` | No |
| Notes | Long Text | `{{NOTES}}` | No |
Job Title fills in from the job req (its external job title, if it has one) and Today's Date from the day the offer is created, unless a package or recruiter sets them. In **Send Offer**, the Offer Expiration Date also becomes the default expiry for the [e-signature request](/offers/e-signatures).
On a default field you can change the description and whether it's required. Its label, type and options are fixed, and it can't be deleted.
### Add an offer field
**1. Click + Field**
It's at the top right of the **Offer Fields** page.
**2. Describe the field**
Enter the **Label** your team sees (for example "Sign-On Bonus"), an optional **Description**, and the **Field Type**. For Multiple Choice, add the options.
**3. Set the merge key**
In **Merge Key**, type the key that goes between the braces, for example `SIGN_ON_BONUS`. In your templates it becomes `{{SIGN_ON_BONUS}}`.
**4. Choose whether it's required**
Turn on **Required** if recruiters must enter it on every offer, then click **Save**.
### Field types
| Type | What it holds | Good for |
| - | - | - |
| Short Text | Single-line text | Department, shift name |
| Long Text | Multi-line text | Notes, special conditions |
| Number | A whole number | PTO days, stock options |
| Date | A date picker | Start date, expiration date |
| Currency | An amount with a currency | Salary, bonus |
| Multiple Choice | A dropdown of your options | Employment type, pay frequency |
| User | A user on your account | Hiring manager, recruiter |
| Yes/No | A yes or no answer | Relocation offered, equipment provided |
| HRIS Object | A value from a list in your HRIS | Department, location or cost center |
### Edit, reorder or delete a field
* Click the **edit** icon on a row to change the label, description, required setting or options. The merge key can't be changed once saved, because your templates may already use it.
* Drag the **grip handle** on the left of a row to reorder fields. Recruiters see fields in this order when they send an offer.
* Click the **delete** icon to remove a field you added. Default fields can't be deleted.
> [!TIP]
>
> If a value is the same for everyone in a hiring class, such as the pay rate or schedule, don't make recruiters type it on every offer. Set it as a default on the class's [offer package](/offers/offer-packages) instead.
## Merge keys
A merge key is a key in double curly braces that you type into a Word template, like `{{CANDIDATE_FIRST_NAME}}`. When Journeyfront generates the document for a candidate, it replaces each key with the real value from that Candidate Application. The values that went into each document are saved with it, so you always have a record of exactly what the candidate received.
### Built-in keys
These work in any template with no setup:
| Group | Examples | Filled from |
| - | - | - |
| Candidate | `{{CANDIDATE_NAME}}`, `{{CANDIDATE_FIRST_NAME}}`, `{{CANDIDATE_LAST_NAME}}`, `{{CANDIDATE_EMAIL}}`, `{{CANDIDATE_PHONE}}`, `{{CANDIDATE_ADDRESS_LINE_1}}`, `{{CANDIDATE_CITY}}`, `{{CANDIDATE_STATE}}`, `{{CANDIDATE_ZIP}}` | The Candidate Profile and the candidate's primary address |
| Job | `{{JOB_REQ_NAME}}`, `{{EXTERNAL_JOB_TITLE}}`, `{{JOB_CITY}}`, `{{JOB_STATE}}` | The job req |
| Company | `{{COMPANY_NAME}}` | Your account |
| Hiring Class | `{{HIRING_CLASS_NAME}}`, `{{HIRING_CLASS_START_DATE}}`, `{{HIRING_CLASS_LOCATION}}` | The candidate's hiring class, when they're in one |
| Date | `{{CURRENT_DATE}}` | The day the document is generated |
| E-Signature | `{{CANDIDATE_E_SIGNATURE}}`, `{{COMPANY_E_SIGNATURE}}` and their date and initials versions | Where people sign. See [signature fields](/offers/templates#signature-fields). |
Your offer fields, and any personal or application fields you've given a key, use the key you chose.
### Give a personal or application field a merge key
Personal and application fields only need a key if you want them in a document. For example, you can put the candidate's preferred shift or their answer to a consent question straight into the offer letter.
**1. Open the field**
Go to **Settings**, then **Custom Fields**, then **Personal Fields** or **Application Fields**. Add a field with **+ Field**, or edit one that doesn't have a key yet.
**2. Enter the merge key**
In **Merge Key**, type the key between the braces. When you add a field, Journeyfront suggests one from the label, so "Preferred shift" becomes `PREFERRED_SHIFT`.
**3. Save**
The key now appears in the merge key reference and works in any template.
Merge keys follow the same rules everywhere:
* Upper-case letters, numbers and single underscores only.
* Unique across your account.
* Fixed once saved. You can change the field's label any time.

### Find the right key
Go to **Settings**, then **Offers**, then **Offer Letter Templates**, and open the **Merge Fields** reference. Keys are grouped by where their value comes from: Candidate, Job, Company, Hiring Class, Date, E-Signature, Offer Fields, and any custom fields you've given a key, such as Personal Fields and Application Fields. Search for a field and click its key to copy it, then paste it into your Word document.

### How values appear in documents
| Field type | What's merged |
| - | - |
| Date | The date written out, for example "October 21, 2026" |
| Currency | The amount formatted with its currency symbol, for example "\$40,000.00" |
| Multiple Choice | The option's label |
| User | The person's full name |
| File upload | The file name |
| Address | The candidate's primary address, or their most recently updated address if none is marked primary |
### When a value is missing
Before any document is generated, Journeyfront shows every key the documents use and the value each candidate will get. Missing values are flagged. In **Send Offer**, candidate details such as phone, address and custom fields can be fixed right there and are saved to the Candidate Profile. Anything still missing has to be filled in, or you choose to leave it blank in the documents. Nothing is generated with a gap you didn't see. See [Send an offer](/offers/send-offers).
## FAQ
> [accordion] What's the difference between a field's label and its merge key?
>
> The label is what your team sees on forms, for example "Sign-On Bonus". The merge key is the token you type into documents, for example `{{SIGN_ON_BONUS}}`. You can change a label any time; a key is fixed once saved. Personal and application fields also have an internal name, which is a free-text identifier and doesn't need to follow the key format.
> [accordion] Can I change a merge key after saving it?
>
> No. Your templates may already use it, and changing it would break them. If you need a different key, create a new field.
> [accordion] Where did the candidate name and address offer fields go?
>
> Candidate name, phone and address are built-in merge keys now, filled from the Candidate Profile. Recruiters don't type them on the offer form anymore. Use keys like `{{CANDIDATE_NAME}}` and `{{CANDIDATE_ADDRESS_LINE_1}}` in your templates.
> [accordion] Can I put a candidate's application answers in the offer letter?
>
> Yes. Give the application field a merge key, then add `{{YOUR_KEY}}` to the template. The candidate's answer for that Candidate Application is merged in.
> [accordion] I added a new offer field. Why isn't it in my letter?
>
> Existing templates only use the keys typed into them. Add the new key to your Word file and re-upload it. The template's **Used By** column shows which offer packages to check afterward.
> [accordion] Where do I set default values for offer fields?
>
> On an [offer package](/offers/offer-packages). A package can pre-fill any offer field and lock it so recruiters can't change it.
> [accordion] Is there a limit on how many offer fields I can add?
>
> No. Add as many as your offers need, and keep the required ones to what recruiters really have to enter.
## Related
> [card] [Offer letter and document templates](/offers/templates)
>
> Put merge keys and signature fields into your Word files.
> [card] [Offer packages](/offers/offer-packages)
>
> Set default values and lock them.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Personal and application fields, and where they appear.
> [card] [Offers overview](/offers/overview)
>
> How all the offer pieces fit together.
# Offer packages
Source: https://help.journeyfront.com/offers/offer-packages
Bundle an offer letter, supporting documents and default terms so every offer starts complete.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access*, or users with the *Offer Packages* permission, build and edit packages. Choosing a job req's package needs the *Manage Job Req Settings* permission.
[Offer packages](https://www.youtube.com/embed/4jFXrUc_UwQ)
An offer package is everything an offer starts from, saved once under a name: the offer letter, any supporting documents that go with it, and the default offer terms such as pay rate and schedule. Point a job req's Offer activity or a hiring class at a package, and every offer from it starts pre-filled with the right letter, documents and terms. Recruiters only complete what's specific to the candidate.
## What's in a package
* **Name and description:** what your team sees when choosing a package. Candidates never see it.
* **Offer letter:** one [offer letter template](/offers/templates).
* **Documents:** any number of [document templates](/offers/templates), in the order the candidate should see them.
* **Offer defaults:** starting values for any [offer field](/offers/offer-fields). Any default can be locked so recruiters can't change it.
A package needs at least an offer letter or one default value. Documents are optional.
## Create an offer package
**1. Start a new package**
Go to **Settings**, then **Offers**, then **Offer Packages**, and click **Create Package**.
**2. Name it**
Enter a **Name** your team will recognize, for example "Day shift, hourly", and an optional description of when to use it. Names must be unique in your account.
**3. Choose the offer letter**
Pick the letter template. A chip shows whether it includes an e-signature. You can preview it, or, with *Company Settings Access*, upload a new letter without leaving the page.
**4. Add documents**
Add any supporting documents in the order the candidate should see them. Each one shows whether it will be signed or is included for reference only. Use the arrows to reorder, preview any document, or, with *Company Settings Access*, upload a new one.
**5. Fill in the offer defaults**
Enter the terms every offer from this package should start with. Fields your letter or documents use are marked and listed first. Tick **Recruiters can't change this** on any value that must stay fixed.
**6. Read the setup check, then save**
The **Setup check** shows every merge key in the letter and documents and where its value will come from. When it looks right, click **Save**.

### Reading the setup check
| Group | What it means |
| - | - |
| **Filled automatically** | Values Journeyfront fills in from the candidate, job req, hiring class, company or date. |
| **Set by this package** | Offer fields this package gives a default value. Locked values are marked. |
| **Entered by the recruiter at offer time** | Offer fields with no default. Recruiters are asked for these on every offer. |
| **Not merge keys on this account** | Keys in your files that Journeyfront doesn't recognize, usually a typo. |
| **E-signature** | Which documents will be signed, and which are included for the candidate to read. |
> [!TIP]
>
> If a field shows under **Entered by the recruiter at offer time** but it's the same for everyone who gets this package, give it a default. It moves to **Set by this package**, and recruiters stop retyping it. Anything under **Not merge keys on this account** needs fixing in the Word file, or a custom field with that key.
## Duplicate a package
Most new packages are one small change away from an existing one, such as a new hiring class with a different pay rate.
1. On the **Offer Packages** page, open the row menu for the package you want to copy.
2. Click **Duplicate Package**. A copy named "Copy of" plus the original name opens in the editor, with the same letter, documents and defaults.
3. Rename it, change what's different, and click **Save**.
## Use a package on a job req
Each job req's Offer activity points at a package.
**1. Open the Offer activity**
Go to the job req's **Setup**, then **Workflow**, and click **Create New Version** (or **Edit Draft** if there's already a draft, or **Edit Scheduled Version** for a scheduled one). Click the Offer activity to open its settings on the right. If the workflow doesn't have one yet, drag **Offer** from the building blocks into the step where offers happen. See [Build a workflow](/workflows/build).
**2. Choose the package**
Under **Offer Details**, select the **Offer Package**. If you can view offers, a card below it shows what the package holds: its **Offer letter**, its **Documents** and its **Offer defaults**, so you can check it's the right one without leaving the editor.
**3. Decide how hiring classes work**
Turn on **Use the candidate's hiring class offer package** if a hiring class's own package should replace the job req's package for candidates in that class. It's on by default for new Offer activities.
**4. Decide how strict to be**
Turn on **Lock offers to the package** to keep every offer on this activity to exactly this package's letter and documents.
**5. Save and publish**
Click **Save Draft**, then **Publish** so offers use the package. See [Publish workflow changes](/workflows/publish).
| Setting | When it's on | When it's off |
| - | - | - |
| **Use the candidate's hiring class offer package** | A candidate whose hiring class has a package gets that package. Everyone else gets the job req's package. | Everyone gets the job req's package. |
| **Lock offers to the package** | Recruiters can't choose a different package, change the letter or documents, or upload their own letter. | Recruiters can choose a different package for an offer, and that choice is recorded on the offer. |
Offer defaults that aren't locked can still be edited per candidate either way.

> [!NOTE]
>
> Some accounts also see a **Reminders** section here, with **Auto reminders** that email signers until they sign or decline. It depends on your e-signature setup and isn't available on every account.
## Use a package on a hiring class
Give a hiring class its own package when its candidates need different terms or documents from the rest of the job req. See [Hiring classes](/hiring-classes/overview).
1. On the job req's **Hiring Classes** tab, edit a class or create a new one.
2. In **Offer Package**, search for and select the package. The first option, **Use the job's offer package**, means the class doesn't override the job req.
3. If you have the *Offer Packages* permission or *Company Settings Access*, the package's letter, documents and offer defaults appear under the picker, so you can check it's the right one.
4. Save the class.
The class's package is only used when the job req's Offer activity has **Use the candidate's hiring class offer package** turned on.
## Which package an offer starts from
When someone sends an offer, Journeyfront picks the package in this order:
1. The candidate's hiring class package, if they're in a class that has one and the Offer activity allows it.
2. Otherwise, the package on the job req's Offer activity.
3. If the activity isn't locked, the recruiter can choose a different package for that one offer.
The offer always shows which package it started from: "from the candidate's hiring class", "from this job's Offer activity" or "chosen for this offer".
## See where a package is used
The **Used By** column counts the job reqs and hiring classes pointing at each package. Click it to see the list, with a link to each one. You can't delete a package while anything uses it.
## FAQ
> [accordion] If I change a package, do existing offers change?
>
> No. Changes apply to new offers only. Offers that were already created keep the letter, documents and terms they started with.
> [accordion] Who can see what's inside a package?
>
> Anyone on your account can see package names, which is enough to choose one for a hiring class. Seeing the letter, documents and default terms (including pay) needs the *Offer Packages* permission or *Company Settings Access*.
> [accordion] Can recruiters change a locked default?
>
> No. A value marked **Recruiters can't change this** is fixed on every offer from the package. Only someone who can edit the package can change or unlock it.
> [accordion] A hiring class has a package and the job req has a different one. Which is used?
>
> The hiring class package, as long as the Offer activity has **Use the candidate's hiring class offer package** turned on. Otherwise the job req's package is used.
> [accordion] Where did Offer Details Templates go?
>
> Default offer terms now live on the offer package, next to the letter and documents. Existing setups were converted automatically: each Offer activity points at a package with the same letter and terms it had before, so nothing changed on your job reqs. You may want to rename those packages to something your team will recognize.
> [accordion] Can I delete a package?
>
> Only when no job req or hiring class uses it. **Used By** shows exactly which ones do, so you can point them at another package first.
> [accordion] Can the Offer Packages permission change templates?
>
> No. It lets people build and edit packages, and see the templates and fields a package needs. Uploading or changing templates and offer fields needs *Company Settings Access*.
## Related
> [card] [Offer letter and document templates](/offers/templates)
>
> The files a package is made of.
> [card] [Offer fields and merge keys](/offers/offer-fields)
>
> The terms a package's defaults are made of.
> [card] [Send offers in bulk](/offers/bulk-send)
>
> Send a whole hiring class its offers at once.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who start and train together.
# Offers overview
Source: https://help.journeyfront.com/offers/overview
How offer fields, templates, offer packages and e-signatures fit together, from setup to a signed offer.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* set up offer fields and templates. Admins, or users with the *Offer Packages* permission, build offer packages. Users with the *View and Send Offers* permission send offers to candidates.
>
> **Availability:** Sending offers for signature uses the E-Signatures add-on and e-signature credits. Ask your Customer Success Manager.
[Offer packages](https://www.youtube.com/embed/4jFXrUc_UwQ)
Journeyfront takes a candidate from "we want to hire you" to a signed offer without leaving your applicant tracking system (ATS). You set up your offer terms and documents once. After that, every offer starts pre-filled, personalized for the candidate and ready to sign, whether you're sending one offer or offers for a whole hiring class.

## How the pieces fit together
**1. Offer fields define the terms**
Offer fields are the terms of an offer, such as salary, start date and pay frequency. Each one has a merge key, like `{{SALARY}}`, that places its value in your documents. Candidate, job req, hiring class and company details have keys too. See [Offer fields and merge keys](/offers/offer-fields).
**2. Templates hold your documents**
Your offer letter, and anything that goes with it (an NDA, an agreement, a benefits guide), are Word files with merge keys where the details belong and signature fields where people sign. A document that's only there to read can also be a PDF. See [Offer letter and document templates](/offers/templates).
**3. Offer packages bundle them**
An offer package saves one offer letter, its supporting documents and the default terms under one name. You can lock any default so it can't be changed on an individual offer. See [Offer packages](/offers/offer-packages).
**4. Packages connect to your hiring**
Point a job req's Offer activity at a package. A hiring class can have its own package, so each class gets its own pay rate, schedule and documents from the same job req.
**5. You send, the candidate signs**
Send one offer from the Candidate Application, or send offers to a whole group at once. The candidate gets one email and signs every document in one session, and the signed copies come back to the Candidate Application. See [Send an offer](/offers/send-offers), [Send offers in bulk](/offers/bulk-send) and [E-signatures](/offers/e-signatures).
## Who does what
| Task | Where | Who |
| - | - | - |
| Set up offer fields and merge keys | **Settings**, then **Offers**, then **Offer Fields** | *Company Settings Access* |
| Upload the offer letter and documents | **Settings**, then **Offers**, then **Offer Letter Templates** or **Document Templates** | *Company Settings Access* |
| Build offer packages | **Settings**, then **Offers**, then **Offer Packages** | *Company Settings Access* or *Offer Packages* |
| Choose a job req's package | The Offer activity in the job req's workflow | *Manage Job Req Settings* |
| Choose a hiring class's package | The hiring class | Anyone who can edit the hiring class |
| Send offers | The **Offer** tab on the Candidate Application, or **Send Offers** on the Candidates page | *View and Send Offers* |
> [!TIP]
>
> Give your recruiting team the *Offer Packages* permission. They can then keep offer terms up to date for each hiring class themselves, without access to the rest of Settings.
## FAQ
> [accordion] Do I need e-signatures to use offers?
>
> No. You can create the offer, generate or upload the documents, and record the candidate's answer yourself with **Accept** or **Decline**. E-signatures let the candidate sign online and update the offer automatically. See [E-signatures](/offers/e-signatures).
> [accordion] Can different hiring classes on one job req get different offers?
>
> Yes. Give each hiring class its own offer package. One Offer activity on the job req serves every class, and each candidate's offer starts from their class's package. See [Offer packages](/offers/offer-packages).
> [accordion] Where do I see a candidate's offer?
>
> Open the Candidate Application and click the **Offer** tab. It shows the offer terms, the documents, the signature status and the candidate's response. See [Send an offer](/offers/send-offers).
> [accordion] Can I put other candidate details in an offer letter?
>
> Yes. Candidate, job req, hiring class and company details are built in, and any personal or application field can be given a merge key so its value appears in your documents. See [Offer fields and merge keys](/offers/offer-fields).
## Related
> [card] [Offer fields and merge keys](/offers/offer-fields)
>
> The terms of an offer, and the keys that fill your documents.
> [card] [Offer letter and document templates](/offers/templates)
>
> Upload the Word files your offers are built from.
> [card] [Offer packages](/offers/offer-packages)
>
> Bundle a letter, documents and default terms.
> [card] [Send an offer](/offers/send-offers)
>
> Send and manage one candidate's offer.
> [card] [Send offers in bulk](/offers/bulk-send)
>
> Send offers to a whole hiring class at once.
> [card] [E-signatures](/offers/e-signatures)
>
> How candidates sign, and how you track it.
# Send an offer
Source: https://help.journeyfront.com/offers/send-offers
Create, review and send one candidate's offer from the Offer tab, then manage it until it's signed.
> [!NOTE]
>
> **Who can do this:** Users with the *View and Send Offers* permission.
>
> **Availability:** Sending the offer for signature uses the E-Signatures add-on and e-signature credits. Without it, you can still create the offer, generate the documents and record the candidate's answer. Ask your Customer Success Manager.
Every candidate's offer lives on the **Offer** tab of their Candidate Application. **Send Offer** takes you through the terms, the documents and the signature request in one flow, starting from the [offer package](/offers/offer-packages) that applies to the candidate. Afterward, the same tab shows where the offer stands and lets you change it.
## Before you start
The candidate's job req needs an Offer activity in its workflow. Without one, the **Offer** tab says "There is no offer activity in your hiring process". For offers to start pre-filled, point that Offer activity at an offer package. See [Offer packages](/offers/offer-packages).
## The Offer tab
Open the Candidate Application and click the **Offer** tab. Each Offer activity on the job req has its own card. The card's header shows the activity's status and which offer package applies, for example "from the candidate's hiring class" or "from this job's Offer activity". Inside the card:
* **Candidate response:** record the candidate's answer, once there are documents.
* **Offer Details:** the terms of this offer.
* **Documents:** the offer letter, supporting documents and signed copies.
* **E-Signature:** each signer's status, reminders and the signature request.

## Send an offer
**1. Click Send Offer**
On the Offer activity's card, click **Send Offer**. The **Send Offers** window opens for this candidate.
**2. Select Offer**
Confirm the **Offer Activity**. If the job req has only one, it's already selected. A summary shows the package the offer starts from, with its letter, documents and defaults.
**3. Offer**
The middle of the progress bar shows your Offer activity's name, for example **Offer**. The small dots next to it are its parts, and you move through them with **Next**:
* **Offer details:** package defaults are already filled in, and locked values can't be changed. Fill in anything the package leaves open. If the Offer activity isn't locked, you can choose a different **Offer package** here. Below, a table shows every value that will go into the documents, grouped by where it comes from. Missing values are flagged; you can fix the candidate's phone, address and custom fields right there, and those changes save to the Candidate Profile.
* **Documents:** leave **Generate Offer Letters** on to create the documents. Check the offer letter and the documents from the package. Unless the activity is locked, you can add another document. Each document shows its merge keys and whether they're all filled. To send with a missing value left empty, tick **Leave these blank in the documents**. Turn **Generate Offer Letters** off to create the offer details only, with no documents or e-signature.
* **E-signature:** only there when your account has the E-Signatures add-on and credits left, and the documents are being generated. Leave **Send E-Signature Requests** on to send the documents for signature, and review the signer, signing order, expiry and email. See [E-signatures](/offers/e-signatures) for each option.
**4. Review & Send**
Check the summary and click **Create & Send Offer**. If you turned off e-signatures, the button reads **Create Offer**.

> [!TIP]
>
> If a value won't let you change it, it's locked on the offer package. Ask whoever maintains your packages. A hiring class with unusual terms should get its own package rather than having recruiters edit every offer.
Once the activity has an offer, **Send Offer** disappears from the card. Manage the existing offer from the card's sections instead.
## Manage an offer
### Offer Details
* Click **Create** to enter terms without running the full Send Offer flow.
* Click **Edit** to change any value that isn't locked, then save.
* Click **Remove** to delete the terms. You'll see what will be affected before you confirm.
> [!WARNING]
>
> If documents were already generated, editing or removing the terms deletes those documents and cancels any active e-signature request, because the documents would no longer match. Journeyfront warns you first. Send the offer again to regenerate them.
### Documents
The **Documents** section lists the offer letter and every document, each marked **Signed** or **Unsigned**. Everything unsigned goes into one e-signature envelope; signed copies are kept as received.
* **Generate** creates the letter and package documents from the offer details. Unless the activity is locked to its package, you can pick a different letter template or add documents.
* **Upload** adds a file you already have. Choose **Supporting document** (an NDA, agreement or other file) or **Offer letter** (a finished letter instead of a generated one), and tick **This is a signed copy** if it's already signed. Uploading your own offer letter isn't available when the activity is locked to its package.
* Each row lets you preview, download, rename, replace or delete the file. You can't replace or delete files while an e-signature request is out; cancel the request first. Once a signed copy is on the offer, the unsigned originals stay as the record of what was sent.
### Candidate response
When the candidate signs through e-signature, the offer is accepted automatically, and a candidate who declines in the signing screen declines the offer. If you're not using e-signatures, record their answer yourself:
* Click **Accept** or **Decline**.
* Click **Change** to switch the answer, or **Revert** to clear it.
## Offer statuses
| Status | What it means |
| - | - |
| Not Created | No offer has been created on this activity yet. |
| Offer Created | The offer terms exist. |
| Offer Drafted | An e-signature request was prepared but not sent: someone clicked **Preview** in the e-signature window and didn't send it, or a send from Send Offers didn't go through. |
| Offer Sent | The e-signature request has been sent. |
| Offer Opened by Candidate | The candidate opened the signing link. |
| Offer Signed by Candidate | The candidate signed. |
| Offer Signed by Company | Your company signer signed. |
| Offer Accepted | Everyone signed, or you recorded the candidate's acceptance. |
| Offer Declined | The candidate declined, in the signing screen or recorded by you. |
| Offer Canceled | The e-signature request was canceled or expired. |
## FAQ
> [accordion] Why is the Offer tab empty?
>
> If it says "There is no offer activity in your hiring process", the candidate's job req needs an Offer activity in its workflow. If you see the card but not the offer details, your security role needs the *View and Send Offers* permission.
> [accordion] Does sending an offer move the candidate to another step?
>
> No. **Send Offer** creates the offer on the Offer activity wherever the candidate is now. To move a candidate and create the offer in one go, change their step to the step with the Offer activity and turn on **Create Offer** in the window that opens. See [Send offers in bulk](/offers/bulk-send).
> [accordion] Where do the offer terms come from?
>
> From the offer package that applies to the candidate: their hiring class's package when the Offer activity allows it, otherwise the job req's package. You complete whatever the package leaves open. See [Offer packages](/offers/offer-packages).
> [accordion] Can I choose a different package or letter for one candidate?
>
> Only when the Offer activity isn't locked to its package. Locked activities show the package and don't offer a choice.
> [accordion] Can I use offers without e-signatures?
>
> Yes. Generate or upload the documents, share them however you like, and record the candidate's answer with **Accept** or **Decline**.
> [accordion] Can a job req have more than one Offer activity?
>
> Yes. Each one gets its own card on the Offer tab, with its own terms, documents and status.
> [accordion] How do I know when the candidate has signed?
>
> The signer statuses on the card update as the candidate opens and signs, and the signed documents appear under **Documents** when everyone is done. See [E-signatures](/offers/e-signatures).
## Related
> [card] [E-signatures](/offers/e-signatures)
>
> Signing options, tracking and what candidates see.
> [card] [Send offers in bulk](/offers/bulk-send)
>
> The same flow for a whole group of candidates.
> [card] [Offer packages](/offers/offer-packages)
>
> Where an offer's letter, documents and defaults come from.
> [card] [Offer fields and merge keys](/offers/offer-fields)
>
> How values get into your documents.
# Offer letter and document templates
Source: https://help.journeyfront.com/offers/templates
Upload the Word files your offer letters and supporting documents are built from.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* upload and manage templates. Users with the *Offer Packages* permission can see and preview templates while building a package, but can't upload or change them.
Templates are the reusable files your offers are built from. An **offer letter** template is the letter itself. A **document** template is anything that goes out with it, such as an NDA, an equipment agreement, an arbitration agreement or a benefits guide. You design them once in Microsoft Word, and Journeyfront personalizes them for every candidate with your logos, formatting and branding intact.
## Letters, documents and PDFs
| Kind | File type | Merge keys | Signed? | In an offer package |
| - | - | - | - | - |
| Offer letter | Word (.docx), under 5MB | Yes | Yes, when it has signature fields | One (a package that only sets default terms can have none) |
| Document (Word) | Word (.docx), under 5MB | Yes | Yes, when it has signature fields. Otherwise included for the candidate to read. | Any number, in the order you choose |
| Document (PDF) | PDF, under 5MB | No, attached as uploaded | No, included for the candidate to read | Any number |
A template with at least one signature field shows an **E-Signature** chip. One without shows **No signature** and goes out with the offer for the candidate to read.
## Create a template
**1. Design it in Word**
Build the letter or document in Microsoft Word, with your logo, headers, tables and styling.
**2. Add merge keys and signature fields**
Type merge keys in double curly braces where values should appear, such as `{{CANDIDATE_NAME}}`, `{{SALARY}}` or `{{HIRING_CLASS_START_DATE}}`. Add signature fields where people sign, such as `{{CANDIDATE_E_SIGNATURE}}`. Save the file as .docx.
**3. Open the right templates page**
Go to **Settings**, then **Offers**. Choose **Offer Letter Templates** for a letter, or **Document Templates** for a supporting document.
**4. Upload the file**
Click **Add Offer Letter Template** or **Upload Document** and choose the file. The **Template Name** fills in from the file name; edit it if you like.
**5. Check the detected fields**
Journeyfront lists the signature fields and merge keys it found in the file. Anything it doesn't recognize is called out, so you can fix a typo before the template is used.
**6. Save, then add it to a package**
Click **Save**. To use the template, add it to an [offer package](/offers/offer-packages).

> [!TIP]
>
> To find the right key, open the **Merge Fields** reference on the **Offer Letter Templates** page, search for the field and click its key to copy it. See [Offer fields and merge keys](/offers/offer-fields) for the full list and how to add keys to your own fields.
Merge keys work in the body text and in tables. Keys in headers, footers and text boxes aren't detected or filled in, so keep them in the body of the document.
## Signature fields
Signature fields mark where each person signs when the offer is sent for [e-signature](/offers/e-signatures). They aren't filled with a value; they become signing boxes.
| Field | What it places |
| - | - |
| `{{CANDIDATE_E_SIGNATURE}}` | The candidate's signature |
| `{{CANDIDATE_E_SIGNATURE_DATE}}` | The date the candidate signed |
| `{{CANDIDATE_E_SIGNATURE_INITIALS}}` | The candidate's initials |
| `{{COMPANY_E_SIGNATURE}}` | Your company signer's signature |
| `{{COMPANY_E_SIGNATURE_DATE}}` | The date your company signer signed |
| `{{COMPANY_E_SIGNATURE_INITIALS}}` | Your company signer's initials |
> [!TIP]
>
> If someone at your company should co-sign the offer, add `{{COMPANY_E_SIGNATURE}}` to the template. When no document in an offer has a company signature field, Journeyfront sends the offer for the candidate's signature only.
## Manage templates
Each row shows the template's name, its signature chip, **Used By** (the offer packages that include it; click to see them), and when and by whom it was last updated. Open the row menu to:
* **Preview** the rendered document in your browser. PDFs open in your browser's viewer. On the **Document Templates** page, the merge keys the file uses are listed under the preview, signature fields last. You see the same list when you preview a letter or document from the offer package editor or in Send Offers; the **Offer Letter Templates** page's own preview shows the letter without it.
* **Download** the file.
* **Edit** to rename the template or upload a new version. A new upload re-detects the fields.
* **Delete** the template. You can't delete a template that an offer package still includes.

## Generate a document outside an offer
You can create a personalized document for a candidate without sending an offer, for example to print and sign in person. In the **Documents** section on the Candidate Application's **Details** tab, click **Generate Document**, pick a document template, and Journeyfront fills it in for that candidate and saves it there. Nothing is sent for e-signature.
## FAQ
> [accordion] What file formats are supported?
>
> Offer letters must be Word (.docx) files. Documents can be Word files or PDFs. Every file must be under 5MB. PDFs are attached as uploaded and can't hold merge keys or signature fields.
> [accordion] What's the difference between an offer letter template and a document template?
>
> They're the same kind of file with the same fields. The difference is their role in an offer package: exactly one letter, and any number of documents. Upload each file on the page that matches its role.
> [accordion] Can a candidate sign a PDF?
>
> No. PDFs are included for the candidate to read. Anything that needs a signature must be a Word template with signature fields.
> [accordion] Why aren't my merge keys being detected?
>
> Check the format: two curly braces on each side, an upper-case key, and no spaces inside. Word sometimes splits a token internally when you edit part of it, so select the whole token, retype it and upload again. Keys in headers, footers or text boxes aren't detected; move them into the body text. The upload screen lists anything it didn't recognize.
> [accordion] Why can't I delete a template?
>
> An offer package still includes it. Click **Used By** to see which packages, point them at another template, then delete it.
> [accordion] What happens if a merge key has no value for a candidate?
>
> Your team sees the gap before anything is generated, and either fills in the value or chooses to leave it blank in the documents. See [Offer fields and merge keys](/offers/offer-fields#when-a-value-is-missing).
> [accordion] Can I include images and logos?
>
> Yes. Images, logos, headers, footers, tables and all Word formatting are kept in the generated document.
## Related
> [card] [Offer fields and merge keys](/offers/offer-fields)
>
> Every key you can use, and how to add your own.
> [card] [Offer packages](/offers/offer-packages)
>
> Put your templates to work.
> [card] [E-signatures](/offers/e-signatures)
>
> How the letter and documents are signed together.
> [card] [Offers overview](/offers/overview)
>
> How all the offer pieces fit together.
# Background checks
Source: https://help.journeyfront.com/onboarding/background-checks
Add a background check to a job req's workflow, order checks for candidates and follow their status.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add the background check activity to a workflow. Anyone who can open a Candidate Application can order a check and see its status. Opening the full report also needs access in your Checkr account.
>
> **Availability:** An admin needs to connect your Checkr account first. See [Checkr](/integrations/background-checks/checkr).
Background checks run through Checkr, right from the Candidate Application. You order the check in Journeyfront, Checkr invites the candidate and runs the report, and the status updates in Journeyfront on its own. Your team can see where every check stands without logging in to another system.
## Add a background check to a workflow
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).
**2. Add the activity**
In the building blocks on the left, find **Checkr Background Check** at the bottom of the list. Drag it into the step where background checks should happen, such as an onboarding step.

**3. Save and publish**
Click **Save Draft**, then **Publish** when you're ready. See [Publish workflow changes](/workflows/publish).
The activity doesn't order anything by itself. Each check is ordered from the candidate's Candidate Application, so your team decides when to spend on a check.
> [!TIP]
>
> Place the background check after the decisions that rule most candidates out, like interviews and the offer. Checks cost money and take a few days, so you only want to run them for people you plan to hire.
## Order a background check
**1. Open the Onboarding tab**
Open the Candidate Application and select the **Onboarding** tab. The **Background** section lists the job req's background check activities.

**2. Order the check**
Click **Order Background Check**. Checkr's ordering window opens with the candidate's email and phone number already filled in.
**3. Choose a package and submit**
Pick the background check package and submit the order.

The status changes to **Invitation Sent**, and Checkr emails the candidate. From here, Checkr runs the check and Journeyfront keeps the status up to date.

### Cancel or reorder a check
* **Cancel:** while the status is **Invitation Sent**, open the menu at the end of the row and choose **Cancel Background Check**, then confirm.
* **Reorder:** when an invitation expired or a check was canceled, click **Re Order Background Check** to send a new one.
## Follow the status
You'll see a check's status in two places:
* **The Onboarding tab** on the Candidate Application. Expand the row to see the report summary from Checkr, if you have access in Checkr.
* **The Candidates page**, as the activity's status, so you can see where every candidate stands at a glance.

| Status | What it means |
| - | - |
| **Not Started** | No check has been ordered yet. |
| **Invitation Sent** | Checkr invited the candidate, and they haven't responded yet. |
| **Invitation Expired** | The candidate didn't respond in time (seven days by default). Reorder to send a new invitation. |
| **Invitation Canceled** | The invitation was canceled, for example with **Cancel Background Check**, before the candidate started. |
| **Pending** | The report is in progress. Most finish in two to three days; some take longer when Checkr needs something from the candidate or a court search is slow. |
| **Suspended** | The report is paused because information is missing. Checkr contacts the candidate for it. |
| **Clear** | The report is complete and found nothing that needs your review under your guidelines. |
| **Eligible** | The report is complete and found nothing that makes the candidate ineligible under your Checkr guidelines, or your team chose to move forward with the candidate in Checkr. |
| **Complete** | The report came back clear, but some of its screenings were canceled before they finished. |
| **Review** | The report is complete but includes something you need to review in Checkr. Checkr's PDF report calls this "Consider". A check also shows Review while a pre-adverse action is in progress. |
| **Not Eligible** | Your team took a final adverse action on the report in Checkr. |
| **Disputed** | The candidate disputed something in the report with Checkr. Review is on hold until Checkr finishes its investigation, which can take up to 30 days. |
| **Canceled** | The report was canceled before any screenings finished. |
To see the full report or take compliance steps, such as an adverse action process, open the report in Checkr. People without access in Checkr see the status only.

## What candidates see
* **An email from Checkr,** not from Journeyfront, inviting them to start their background check.
* **Checkr's secure site,** where they enter their details and give consent.
* **Follow-up from Checkr** if anything more is needed, such as documents.
* **Their report and any dispute** are handled directly with Checkr.
> [!TIP]
>
> Tell candidates to expect an email from Checkr, for example in your offer or onboarding message. An invitation that sits unopened expires, and you'll need to order again.
## FAQ
> [accordion] How long does a background check take?
>
> Most reports finish in two to three days. Some take longer, for example when Checkr needs documents from the candidate or a county court search is slow.
> [accordion] The candidate says they never got the invitation. What can I do?
>
> Check the status on the **Onboarding** tab. If it shows **Invitation Expired**, **Invitation Canceled** or **Canceled**, click **Re Order Background Check**. Also confirm the candidate's email address and ask them to check their spam folder for a message from Checkr.
> [accordion] Why can't I see the report details?
>
> Report details are only visible to people with access in your Checkr account. Ask your Checkr admin to add you.
> [accordion] Can a Review status change to Clear?
>
> No. Review means there's something to look at in Checkr. Make your decision there, using your own process. If you move forward with the candidate in Checkr, the status changes to **Eligible**; if you complete an adverse action, it changes to **Not Eligible**.
> [accordion] Does Journeyfront decide whether a candidate passes?
>
> No. Journeyfront shows the status Checkr reports. Your team makes hiring decisions, and Checkr's tools handle compliance steps.
> [accordion] Is the full report stored in Journeyfront?
>
> No. Journeyfront keeps the status and the order details, such as the package. The report summary on the **Onboarding** tab is shown from Checkr, and the full report and sensitive details stay in Checkr.
## Related
> [card] [Checkr](/integrations/background-checks/checkr)
>
> Connect your Checkr account.
> [card] [Workflows overview](/workflows/overview)
>
> How steps and activities fit together.
# Bulk hire
Source: https://help.journeyfront.com/onboarding/bulk-hire
Hire a whole group of candidates at once, such as a full hiring class, and create them in your HR system in the same run.
> [!NOTE]
>
> **Who can do this:** Users whose security role has the *Hire Candidates* permission, on job reqs they can access.
>
> **Availability:** Creating employees in your HR system during the run needs an HRIS connection with employee creation turned on. See [HRIS integrations](/integrations/hris).
When a hiring class is ready to start, you don't want to hire 40 people one by one. **Hire** in the actions bar hires up to 100 candidates in one run. You set the shared details once, like the start date and job title, adjust anyone who's different, and Journeyfront hires everyone and creates their employee records. If your HR system is connected, it can create them there too.
## Hire a group
**1. Select the candidates**
On the **Candidates** page, a job req's **Candidates** tab, or a hiring class's candidate list, tick the boxes next to the candidates. You can select up to 100, from one job req or several.
**2. Click Hire**
**Hire** is in the actions bar above the list. The **Hire Candidates** window opens on **Hire Details**.
**3. Set the shared details**
Under **Journeyfront Group Hire Details**, check the fields that apply to everyone. See [Fill in the details](#fill-in-the-details).
**4. Check each candidate**
The **Candidates** table below shows every candidate's values. Click a cell to change it for one person, or untick **Include** to leave someone out of this run.

**5. Click Next**
**Confirm & Hire** shows how many candidates will be hired, and how many employees will be created in your HR system, along with every value.

**6. Hire them**
Click **Hire** followed by the number of candidates. Watch the progress, then click **Done**.
## Fill in the details
Each field starts with every candidate's own value, taken from their job req or hiring class. Type in a field to set one value for the whole group. Clear it to go back to each candidate's own value. When candidates have different values, the field reads **Multiple Values**.
| Field | Where each candidate's value comes from |
| - | - |
| **Job Profile** | Their job req's job profile |
| **Job Title** | Their job req's title |
| **Start Date** | Required. Their hiring class's candidate start date |
| **Company Email** | Nothing; fill it in per candidate in the table if you use it |
| **Supervisor Email** | Their application's supervisor email, if there is one |
Click **Show advanced options** for **Additional Job Details** (**Job City**, **Job State**, **Job Country** and **Employment Type**, taken from the job req) and **Custom Job Fields** (your account's employee job fields).
> [!TIP]
>
> Put candidates in the right hiring class before you bulk hire. The start date then fills in from the class, and you only touch the few people who start on a different day.
A **Company Email** becomes the candidate's main email address, which they use to sign in to Journeyfront, so every candidate needs their own. The window won't let you continue while two candidates share one or an address isn't valid.
## Create employees in your HR system
When your HR system is connected with employee creation on, a second section appears, named after your HR system, with the switch **Create employees in** your HR system.
* Turn it on to create everyone in your HR system as part of the run. Its fields appear, grouped the way your HR system groups them. Fill in shared values once, and edit any candidate in the table.
* Untick a candidate in your HR system's column to hire them in Journeyfront only.
* Leave the switch off to hire the whole group in Journeyfront only.
**Manage field mappings in Create Employee Settings** opens your field mappings in a new tab, so you don't lose what you've entered. See [HRIS integrations](/integrations/hris).
## Who's included
* **Already hired:** skipped, and shown as skipped on **Confirm & Hire**.
* **Rejected:** unticked for you, with a note naming them. You can tick them back on if you really mean to hire them; Journeyfront asks you to be sure.
* **Missing a required value:** the run can't continue until you fill it in or untick them. The footer tells you who and what.
* **No longer on the job req:** if a candidate's application can't be found, they're left out and named in a note at the top.
## Check the results
The run hires everyone in Journeyfront first, then creates employees in your HR system. The results show each candidate's progress, with counts of who was hired, who was already hired and who failed.
* **Edit and try again:** go back and fix the values for candidates who failed.
* **Retry failed:** send failed HR system pushes again. Candidates already hired in Journeyfront aren't hired twice.
* **Need checking in** your HR system: Journeyfront couldn't confirm whether the employee was created. Check your HR system before sending them again, so you don't create a duplicate.
Each hire then works exactly like a single hire: the candidate is marked **Hired**, gets an employee record, counts toward their hiring class, and starts any **Candidate is Hired** automation rules. See [What happens when you hire](/onboarding/hire-candidates#what-happens-when-you-hire).
## FAQ
> [accordion] Why is Hire greyed out?
>
> You've selected more than 100 candidates. Hover over **Hire** to see the limit, and hire the group in batches.
> [accordion] Why don't I see Hire at all?
>
> It needs the *Hire Candidates* permission. Ask your Journeyfront admin to check your security role.
> [accordion] Can I hire candidates from different job reqs in one run?
>
> Yes. Each candidate is hired into their own job req, with values from their own job req and hiring class.
> [accordion] Can I undo a bulk hire?
>
> Not in bulk. Un-hire candidates one at a time from their Candidate Application. See [Un-Hire a candidate](/onboarding/hire-candidates#un-hire-a-candidate).
> [accordion] Does bulk hire email the candidates?
>
> No. Use **E-mail** or **Message** in the actions bar, or an automation rule with the **Candidate is Hired** trigger, to welcome your new hires.
> [accordion] What if the HR system part fails for some candidates?
>
> They're still hired in Journeyfront. Fix what's missing and use **Retry failed** to send them again, or send them later from each Candidate Application. See [Hire candidates](/onboarding/hire-candidates).
## Related
> [card] [Hire candidates](/onboarding/hire-candidates)
>
> Hire one candidate, edit a hire, or un-hire.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who share a start date.
> [card] [HRIS integrations](/integrations/hris)
>
> Create employees in your HR system.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to a group of candidates.
# E-consent forms
Source: https://help.journeyfront.com/onboarding/e-consent-forms
Collect signed consents and acknowledgments inside your application and onboarding forms.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access*, or users with the *E-Consent Forms* permission, create and manage forms. Adding a form to a job req's application form needs the *Manage Job Req Settings* permission.
E-consent forms let you collect electronic signatures on consent and acknowledgment forms right inside your hiring process. Candidates read the form, check an agreement box and type their full name, and Journeyfront permanently records who signed, exactly what they agreed to, and when.
Signatures are included with Journeyfront, with no per-signature cost, so you can ask every applicant to sign without worrying about volume. Candidates can see and download everything they've signed at any time.
[E-consent forms](https://www.youtube.com/embed/aY4TO_fTHMA)

## Create a form
**1. Open E-Consent Forms**
Go to **Settings**, then **E-Consent Forms**, and click **Create New Form**.
**2. Write the form**
* **Name:** the title candidates see, for example "Consent to Interview Recording".
* **Internal Description:** an optional note for your team about when the form is used. Candidates don't see it.
* **Consent Content:** write the terms in the editor, upload a PDF, or both.
**3. Activate and save**
Leave **Active** on (it's on by default) so the form can be added to application and onboarding forms, then click **Save**.

> [!TIP]
>
> End your consent language with a line like "Please type your full legal name below to sign." That's exactly what candidates do next, so it removes any doubt.
Uploaded documents must be PDFs, up to 5MB.
## Add a form to a job req's application form
Ask candidates to sign when they apply.
**1. Open the application form**
Open the job req and go to **Setup**, then **Application Form**.
**2. Add the form**
Click **Add**, then **Add E-Consent Form**, and pick the form from the list.
**3. Choose Required or Optional**
The form is added as **Required**. Switch it to **Optional** if signing shouldn't block the application.
**4. Save**
Save the application form.
Candidates must sign every required consent before they can submit their application.
## Add a form to an onboarding form
Collect acknowledgments during onboarding, such as policy or confidentiality acknowledgments.
**1. Open the onboarding form**
Go to **Settings**, then **Onboarding Forms**, and create or edit an onboarding form.
**2. Add the form**
Click **Add**, then **Add E-Consent Form**, and pick the form from the list. It appears as a card with a **Required** checkbox.
**3. Save and use it**
Save the onboarding form and add it to your job req's workflow as you normally would.
Click **View Form** at any time to preview the onboarding form exactly as candidates will see it.
## Edit a form
You can update a form at any time without affecting anyone who has already signed.
1. On the **E-Consent Forms** page, open the form's actions menu and choose **Edit Form**.
2. Make your changes. Because the content changed, the save button now reads **Save as New Version**.
3. Click **Save as New Version**.
Candidates who already signed keep their signature on the version they saw and aren't asked to sign again. New signatures use the new version. To see an older version, open **Version History** on the edit page, or click the form in the list and switch versions.
> [!TIP]
>
> Since edits never change a signed record, you can fix a typo or update your terms the moment you need to.
## Review signatures
See who signed a form, when, and which version.
1. On the **E-Consent Forms** page, open the form's actions menu and choose **View Signatures**.
2. Search by candidate or typed name, or filter by **Job Req**, **Version** or **Signed Date**.
3. Click any row to see the exact content that candidate signed and download a signed copy as a PDF.
4. Click **Export** to download the filtered list as a CSV file.

## See a candidate's signed consents
* **On the Candidate Application:** signed consents appear as cards on the **Details** tab. Consents signed during onboarding also appear on the **Onboarding** tab.
* **On the Candidate Profile:** the **Details** tab shows every consent the person has signed across all their applications, labeled by job.
Click any card to view the signed content and download the signed copy as a PDF.

## What candidates see
Candidates see the full consent content inside the application or onboarding form. To sign, they check **I have read and agree to the terms above.**, type their full name and click **Sign**. The form then shows who signed and when.


Candidates can find everything they've signed on the **My Consents** page of their candidate portal, with options to view and download each one.
## Why e-consent signatures are legally valid
E-consent forms are designed around the U.S. **E-SIGN Act** and the state **UETA** laws adopted across nearly every state. Under these laws, an electronic signature is any electronic sound, symbol or process attached to a record and adopted by a person with the intent to sign. A checked agreement box with a typed full name qualifies; a signature doesn't need to look handwritten.
What decides whether an electronic signature holds up is the evidence behind it. Journeyfront captures that evidence on every signature:
| What the law looks for | How Journeyfront covers it |
| - | - |
| **Intent to sign** | The agreement box is never pre-checked. The candidate takes two deliberate steps: checking the box next to clear agreement language, then typing their full legal name. |
| **Who signed** | The candidate signs inside their own signed-in account. The record stores their typed name, the date and time, and technical details of the signing session, such as the network address it came from. |
| **What they agreed to** | Form content is versioned and can't be changed. Every signature is tied to the exact version the candidate saw, so a later edit never changes a signed record. |
| **Retention and access** | Signed records can't be deleted or altered. The candidate can download a signed copy from their portal at any time, and your team can produce the same record from the signatures list. |
The signed-copy PDF puts all of this in one shareable document: the signer's name, the date and time, the company and job, the content version, and the complete content that was on screen, including any uploaded document.
> [!NOTE]
>
> This section describes how e-consent forms work and the legal framework they're designed around. It's general information, not legal advice. Requirements vary by location and by the type of consent you collect, so review your consent language and process with your own legal counsel.
## FAQ
> [accordion] Is a typed name a valid signature?
>
> Yes. Under the U.S. E-SIGN Act, an electronic signature is any electronic process adopted with the intent to sign. A typed full name with an agreement checkbox qualifies, and Journeyfront strengthens the record by storing the date, time and exact version of the content the candidate saw.
> [accordion] What happens if I edit a form people have already signed?
>
> Your edit creates a new version. Everyone who already signed keeps their record on the version they saw, and no one is asked to sign again. New signatures use the new version.
> [accordion] Can I delete a form?
>
> Only while no one has signed it. After the first signature, you can **Deactivate** the form to remove it from the form builders. The form and its signatures are kept so your records stay complete. A form that's still on an application form or onboarding form can't be deleted or deactivated; remove it from those forms first.
> [accordion] Does a candidate sign once, or once per application?
>
> Once per application. If a candidate applies to two job reqs that both require the same consent, they sign on each application and each signature is recorded separately.
> [accordion] Can I make a consent optional?
>
> Yes. On an application form, set the consent to **Optional**. On an onboarding form, clear the **Required** checkbox on the form's card.
> [accordion] Do candidates get an emailed copy?
>
> No. Candidates can view and download everything they've signed from the **My Consents** page in their portal, so their copy is always available.
> [accordion] Is there a cost per signature?
>
> No. E-consent signatures are included with Journeyfront and don't use e-signature credits.
> [accordion] How is this different from offer e-signatures?
>
> Offer e-signatures send offer letters through a signing service, with signature placement on the document and support for more than one signer, and each send uses an e-signature credit. E-consent forms are for consents and acknowledgments: candidates sign with a checkbox and typed name right inside the application or onboarding form, with no credits used.
## Related
> [card] [Offer e-signatures](/offers/e-signatures)
>
> Send offer letters for signature.
> [card] [Workflows overview](/workflows/overview)
>
> Where application and onboarding forms fit in a job req.
# Hire candidates
Source: https://help.journeyfront.com/onboarding/hire-candidates
Mark a candidate as hired, record their job details, and undo a hire if you need to.
> [!NOTE]
>
> **Who can do this:** Users whose security role has the *Hire Candidates* permission, for both **Hire** and **Un-Hire**.
>
> **Availability:** Creating the employee in your HR system at the same time needs an HRIS connection with employee creation turned on. See [HRIS integrations](/integrations/hris).
Hiring a candidate closes the loop on their Candidate Application. Journeyfront marks the application **Hired**, creates their employee record with their job title and start date, and counts them toward their hiring class. If your HR system is connected, you can create them there in the same step, so nobody retypes their details.
To hire a group at once, such as a whole hiring class, see [Bulk hire](/onboarding/bulk-hire).
## Hire a candidate
**1. Open the Hire window**
On the Candidate Application, click **Actions**, then **Hire**. The **Hire** window opens with the candidate's name at the top.
If the person is flagged **Do Not Hire**, or matches someone who is, a warning appears first. Click **Proceed** to continue. See [Do Not Hire](/candidates/do-not-hire).
**2. Check the job details**
Most details are filled in from the job req. Check them and fill in the rest (see the table below).
**3. Add more details (optional)**
Click **Show advanced options** for the job's location, country, employment type and your account's employee job fields.
**4. Click Hire**
If **Create Employee in** your HR system is ticked, the HR system's window opens next. See [Create the employee in your HR system](#create-the-employee-in-your-hr-system).

| Field | What to enter |
| - | - |
| **Email** | The candidate's current email, shown for reference. |
| **Job Profile** | The employee job profile they're hired into. It starts as the job req's job profile. |
| **Company Email** | Optional. The work email you've given them. It becomes their main email address, and the email they had is kept as their secondary email. |
| **Job Title** | Required. Starts as the job req's title. |
| **Start Date** | Required. Their first day. It starts as today's date, so change it to the real start date. |
| **Supervisor Email** | Optional. Their supervisor's email. |
| **HRIS Integration** | Shown when your HR system is connected with employee creation on. **Create Employee in** your HR system is ticked for you. |
| **Job Location**, **Job Country**, **Employment Type** | Under **Show advanced options**. They start from the job req. |
| **Additional Job Fields** | Under **Show advanced options**. Your account's employee job fields. Fields marked with an asterisk are required. See [Custom fields](/account-setup/custom-fields). |
> [!TIP]
>
> Enter the **Company Email** only once the account really exists. It becomes the address the person signs in to Journeyfront with and the one your emails go to, so a typo here sends messages to nowhere.
**Hire** only appears in **Actions** for users with *Hire Candidates*, and only while the candidate isn't already hired or rejected. To hire someone you rejected, [un-reject](/candidates/reject#un-reject-a-candidate) them first.
## Create the employee in your HR system
When **Create Employee in** your HR system is ticked, clicking **Hire** opens your HR system's form instead of finishing the hire straight away.
**1. Choose where they work (if asked)**
Some HR systems ask which part of your organization the hire belongs to first. The window names it the way your HR system does. If the job req already has one saved, this is skipped.
**2. Complete the form**
The **Send** window shows what Journeyfront filled in and the fields your HR system needs. Fill in anything required, and choose documents to attach if your HR system accepts them.
**3. Click Send**
Journeyfront creates the employee in your HR system, then completes the hire.
The candidate isn't marked hired until the employee is sent. If you close the HR system's window, the hire doesn't happen; click **Hire** again when you're ready. See [HRIS integrations](/integrations/hris#send-a-new-hire-to-your-hr-system) for how fields are mapped.
## What happens when you hire
* The Candidate Application's status changes to **Hired**, and the header shows the start date. When the employee was sent to your HR system, a **Sent to** badge appears next to it.
* The person gets an employee record in the job profile you chose. It shows on the **Jobs** tab of their Candidate Profile and on the **Employees** page. See [Employee records](/employees/employee-records).
* If the candidate is in a hiring class, they count toward its openings. Once a class has as many hires as openings, it's marked filled. See [Hiring classes](/hiring-classes/overview).
* Automation rules with the **Candidate is Hired** trigger run. See [Automation rules](/workflows/automation-rules).
* The candidate's step doesn't change, and Journeyfront doesn't email the candidate.
## Edit hire details
On a hired Candidate Application, click the edit icon next to **Hired** in the header. The Hire window opens with the saved details, plus the **Hired Date**. Change what you need and click **Hire** to save.
## Un-Hire a candidate
Use **Un-Hire** when a hire shouldn't stand, for example a no-show or a hire made by mistake.
**1. Open the Un-Hire window**
On the hired Candidate Application, click **Actions**, then **Un-Hire**.
**2. Review what will change**
The window lists the employee record (or records) that will be removed. If the person was already sent to your HR system, it says so: Journeyfront can't remove them there, so remove them in your HR system if needed.
**3. Choose a reason**
Pick a **Reason**: **Hired by mistake**, **No-show**, **Start date changed** or **Other**. Add a **Note** if you like.
**4. Click Un-Hire**
The candidate goes back to **Active** in their current step and keeps their hiring class. You can hire them again later.

When you un-hire someone:
* Their employee record for this hire is removed.
* Automation rules from the hire that haven't run yet, such as a delayed email, are canceled.
* They no longer count toward their hiring class's openings, so a class that drops below its openings is no longer marked filled.
* The reason and note are recorded on the **Comments & Activities** tab.
If the employee record already has performance data, the hire can't be reversed. To record that the person left, add a separation to their employee record instead.
> [!TIP]
>
> Pick the reason that really applies. The reasons are a fixed list on purpose, so hires that never started are always recorded as **No-show** and can be told apart from mistakes.
## FAQ
> [accordion] Why can't I see Hire in the Actions menu?
>
> You need the *Hire Candidates* permission, and the candidate can't already be hired or rejected. Ask your Journeyfront admin to check your security role. See [Security roles](/account-setup/security-roles).
> [accordion] Where do I set the candidate's hiring class?
>
> Not in the Hire window. Set it before you hire, with **Assign Class** on the Candidates list or the **Hiring Class** value on the Candidate Application's **Details** tab. See [Hiring classes](/hiring-classes/overview).
> [accordion] Does hiring move the candidate to another step?
>
> No. The candidate stays in their current step. If you want everyone to end in a final step, move them with **Change Step** or an automation rule.
> [accordion] I hired someone without sending them to our HR system. Can I send them now?
>
> Yes. Click the edit icon next to **Hired** in the header, tick **Create Employee in** your HR system, and click **Hire**. The HR system's window opens so you can send them.
> [accordion] I un-hired someone and am hiring them again. Will it create a second employee in our HR system?
>
> It can. The Hire window shows when they were sent before, with a warning that sending again may create a second employee. Check your HR system before you send.
> [accordion] Can I hire someone flagged Do Not Hire?
>
> Journeyfront warns you before the Hire window opens, with the reason. The warning doesn't block the hire; click **Proceed** if the hire has been approved.
> [accordion] Why can't I un-hire someone?
>
> Their employee record already has performance data, so the hire is part of their employment history. Add a separation to their employee record instead.
## Related
> [card] [Bulk hire](/onboarding/bulk-hire)
>
> Hire a whole group at once.
> [card] [HRIS integrations](/integrations/hris)
>
> Create employees in your HR system.
> [card] [Onboarding forms](/onboarding/onboarding-forms)
>
> Collect new-hire information before day one.
> [card] [Employee records](/employees/employee-records)
>
> Where your hires go next.
# Onboarding forms
Source: https://help.journeyfront.com/onboarding/onboarding-forms
Collect new-hire information and documents before day one, right in Journeyfront.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* build onboarding forms. Users with the *Manage Job Req Settings* permission add them to a job req's workflow. Anyone who can open a candidate can send them a form and review what they submitted.
Onboarding forms replace the paper packet and the back-and-forth of emailed attachments. You build a form once, with the fields, documents and acknowledgments you need, and attach it to the step in a job req's workflow where onboarding starts. When a candidate reaches that step, they get the form, fill it in on any device, and everything they submit is saved on their Candidate Application.
## How it works
**1. Build the form**
In **Settings**, create a form with the fields, instructions and consent forms you need.

**2. Add it to the workflow**
Add an **Onboarding Form** activity to the right step of the job req's workflow, and choose the form it uses.
**3. Send it**
When candidates reach that step, the form is assigned to them, and emailed if you've turned that on. You can also send a form to one candidate yourself.

**4. Review and complete**
Check what they submitted on the **Onboarding** tab of their Candidate Application, then mark it complete.
## Build a form
**1. Open Onboarding Forms**
Go to **Settings**, then **Onboarding Forms**, and click **Create New Form**.

**2. Name and activate it**
Under **Form Settings**, enter the **Onboarding Form Name**. Turn **Activate Onboarding Form** to **Yes** so the form can be used.
**3. Add content**
Click **Add** and choose what to add. Drag items by their handle to put them in order.
**4. Preview and save**
Click **View Form** to see the form the way candidates will. Then click **Save** (or **Update** when you're editing a form).
| Add | What it is | Options |
| - | - | - |
| **Add Section** | A heading that groups the items below it | **Section Name**, **Section Description**, **Hide from Candidate View** |
| **Add Rich Text** | Formatted instructions or policy text | The text itself |
| **Add Field** | A question, picked from your account's personal and application fields or the standard address fields | **Display Name** (what the candidate sees), **Candidate Help Text**, **Required**, **Hide from Candidate View** |
| **Add E-Consent Form** | One of your consent forms, which candidates sign with a checkbox and their typed name | **Required** |

Because form fields are your custom fields, a candidate's answers are saved to those fields, the same ones you see on their Candidate Application's **Details** tab. A field can only be on a form once, and each field needs its own display name.
> [!TIP]
>
> Need a field that isn't in the list, like a photo ID upload or a uniform size? Create it first in **Settings**, then **Custom Fields**, as a personal or application field. Use the **File Upload** type for documents, and mark sensitive fields **Private**. See [Custom fields](/account-setup/custom-fields).
Use **Hide from Candidate View** for things your team fills in, like an internal badge number. Candidates don't see them, but your team can complete them on the **Onboarding** tab.
To manage your forms, use the menu on each row of the **Onboarding Forms** list: **View Form**, **Edit Form** or **Delete Form**. The list shows each form's **Status** (**Active** or **Inactive**). Only active forms can be chosen for a job req or a candidate.
## Add a form to a job req's workflow
**1. Open the workflow editor**
Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft) to open the editor.
**2. Add the activity**
In the building blocks on the left, find **Onboarding Form** and drag it into the step where onboarding should start. Many teams add a step just for it, for example after the offer step.
**3. Choose the form**
Click the activity to open its settings on the right. Under **Select a default onboarding form**, pick the form. Below it, **What the candidate sees on this form** previews it.
**4. Decide whether to send it automatically**
Turn **Auto-invite candidate to onboarding form** to **Yes** to email candidates the form as soon as they reach this step.
**5. Save and publish**
Click **Save Draft**, then **Publish** when you're ready. See [Publish workflow changes](/workflows/publish).

On the job req's **Workflow** page, click the activity to see which **Form** it uses, whether **Auto-invite candidate** is on, and a preview of the form.
## Send a form to candidates
There are three ways a candidate gets their form:
* **They reach the step.** The activity's default form is assigned to them. With **Auto-invite candidate to onboarding form** on, they're emailed straight away.
* **You move them with Change Step.** When the step you're moving them to has an Onboarding Form activity, the **Change Candidate Step** window asks which **Onboarding form** to assign and whether to **Send Invite Email**. Choosing a form is required to move them. See [Move candidates through steps](/candidates/move-through-steps#moving-actions).
* **You send it from their Candidate Application.** On the **Onboarding** tab, click **Select Form** next to the activity. In the **Select Onboarding Form** window, choose the form, leave **Send Invite to Candidate** on to email them, and click **Confirm**. **Select Form** appears when no form has been assigned yet.
The invite uses the **Onboarding Form** system email, with the subject "Please Complete Your Onboarding Form" and your company name. You can edit it in **Settings**, then **Templates**, then **E-mail Template**, on the **System Emails** tab. See [Email templates](/communication/email-templates).
> [!TIP]
>
> Send the form as soon as the offer is accepted, not on the first day. Candidates have time to gather documents, and your team has time to chase anything missing before training starts.
## What candidates see
The email links to their form. They see your sections, instructions and questions, with any help text under each one. Required questions must be answered, and consent forms are signed with a checkbox and their typed name. When they click **Next** at the end, the form is submitted and they see "Thank you for completing your onboarding form".
See [E-consent forms](/onboarding/e-consent-forms) for how consent forms work.
## Review and complete a form
Open the Candidate Application and click the **Onboarding** tab. Each Onboarding Form activity in the workflow has its own row, with its status:
| Status |
What it means |
| **Not Sent** |
The form hasn't been sent to the candidate. |
| **Sent To Candidate** |
The form has been sent. |
| **In Progress** |
The candidate has started. |
| **Submitted** |
The candidate submitted the form. |
| **Complete** |
Your team marked it complete. |
Click a row to expand it and see the answers. You can fill in or correct values right there, including fields hidden from the candidate. Uploaded files open in a new tab, and signed consent forms can be opened to view the signed record. Fields marked private only show to users whose security role has *Private Data Access*.
When everything's in, open the row's menu and click **Set To Complete**.

The **Onboarding** tab also shows the candidate's background checks. See [Background checks](/onboarding/background-checks).
> [!TIP]
>
> To act on submitted forms without checking each candidate, add an automation rule with the **Activity Status Changes To** trigger, your onboarding activity and the status **Submitted**, for example to assign a coordinator or move the candidate to the next step. See [Automation rules](/workflows/automation-rules).
## FAQ
> [accordion] Can candidates upload documents?
>
> Yes. Add a **File Upload** personal or application field to the form. Create the field in **Settings**, then **Custom Fields** first if you don't have one.
> [accordion] Can I use different forms for different roles?
>
> Yes. Each job req's Onboarding Form activity has its own default form, and you can choose a different form for one candidate when you move them or send it from the **Onboarding** tab.
> [accordion] Why isn't my form in the list when I set up the activity?
>
> Only active forms are listed. Edit the form in **Settings**, then **Onboarding Forms**, and turn **Activate Onboarding Form** to **Yes**.
> [accordion] Why can't I move a candidate into the onboarding step?
>
> The **Change Candidate Step** window needs an onboarding form chosen before it lets you continue. Pick a form under **Onboarding form**.
> [accordion] Where do the answers go?
>
> Into the candidate's personal and application fields, so they show on the **Details** tab and can be added as columns and filters on the Candidates page. Personal fields belong to the person, so their answers show on all of their Candidate Applications.
> [accordion] Are onboarding forms legally binding signatures?
>
> Consent forms on an onboarding form are signed with a checkbox and a typed name. For offer letters and other documents that need a full e-signature, use offers with e-signatures. See [E-signatures](/offers/e-signatures).
> [accordion] Can I change the email candidates get?
>
> Yes. Edit the **Onboarding Form** template on the **System Emails** tab in **Settings**, then **Templates**, then **E-mail Template**.
## Related
> [card] [E-consent forms](/onboarding/e-consent-forms)
>
> Consent forms candidates sign during the application or onboarding.
> [card] [Custom fields](/account-setup/custom-fields)
>
> The fields your onboarding forms collect.
> [card] [Hire candidates](/onboarding/hire-candidates)
>
> Mark candidates as hired.
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities to a job req.
# Badges
Source: https://help.journeyfront.com/referrals/badges
The badges employees earn for referring, and how each one is earned.
> [!NOTE]
>
> **Who sees badges:** Employees signed in to a referral portal with full access. Former employees who can see only their payouts don't see badges.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Badges give employees a reason to keep referring. They're earned for the referrals themselves: people referred, people who apply, hires, hires who reach a milestone, and hires who stay. Badges are never about money, so they work the same for everyone, whatever their currency or reward program.
There are 34 badges in six tracks. Each track climbs from bronze to silver, gold, platinum and, for the biggest goals, diamond.
## Where employees see badges
* **Home** has a **Your Badges** card with how many are earned, the **Next Badge** and its progress, and up to six of the **Latest Earned**. **See All 34 Badges** opens the Badges page.
* **Badges** in the portal's menu lists every badge, track by track.
* Each badge has **its own page**, opened by clicking it.

The **Next Badge** is the one the employee is closest to earning. Each track's next badge is a goal; Home picks the one that's furthest along. When an employee has earned them all, the card says so.
## The Badges page
The page opens with how many badges the employee has earned. Each track has its own card with a count like "2 of 9" and its badges, easiest first:
* **Earned** badges are in full color, with the date they were earned.
* The track's **next** badge is in full color on a light background, with a progress bar like "6/10".
* The rest are grey with a lock, and say how many to go, like "19 to go".

Each track has its own medal shape, so badges are easy to tell apart. Badges that take more than one count to earn show the number on a banner across the medal. Hiring and One Year medals hang from a ribbon.
| Track | Medal shape | Counts |
| - | - | - |
| **Referring** | Hexagon | People you've referred. |
| **Applying** | Shield | People you referred who applied. |
| **Hiring** | Rosette with a ribbon | People you referred who were hired. |
| **Milestones** | Eight-point star | Hires who reached a reward milestone. |
| **Staying Power** | Diamond | Hires who stayed 90 days. |
| **One Year** | Round medal with a ribbon | Hires who stayed a year. |
## A badge's own page
Click any badge to open its page. It shows the medal, its metal and track (for example "Bronze · Hiring") and what it takes. If it's earned, the page shows **Earned** with the date. If not, it says how many more are needed, like "1 more hire to go.", with a progress bar. As on Home and the Badges page, the track's next badge is in full color and the badges after it are grey with a lock, here and in the track's list below.
Below that, **How to Earn It** gives a tip for the track, and the track's other badges are listed so the employee can jump between them. Click **All Badges** to go back.

## Every badge
### Referring
People you've referred. Tip: refer someone from the Refer page, or share your personal link or a job. Everyone who applies through your link counts.
| Badge | Metal | How to earn it |
| - | - | - |
| **First Referral** | Bronze | Refer someone for the first time. |
| **Connector** | Bronze | Refer 5 people. |
| **Talent Scout** | Silver | Refer 10 people. |
| **Super Referrer** | Silver | Refer 25 people. |
| **Rising Star** | Gold | Refer 50 people. |
| **Century Club** | Gold | Refer 100 people. |
| **Talent Magnet** | Platinum | Refer 250 people. |
| **Referral Legend** | Platinum | Refer 500 people. |
| **Hall of Fame** | Diamond | Refer 1,000 people. |
### Applying
People you referred who applied. Tip: a quick message after you refer someone helps them follow through and apply.
| Badge | Metal | How to earn it |
| - | - | - |
| **Foot in the Door** | Bronze | Someone you referred applies. |
| **Door Opener** | Bronze | 5 people you referred apply. |
| **Pipeline Builder** | Silver | 25 people you referred apply. |
| **Full Pipeline** | Gold | 100 people you referred apply. |
| **Open the Floodgates** | Platinum | 250 people you referred apply. |
| **Application Icon** | Diamond | 500 people you referred apply. |
### Hiring
People you referred who were hired. Tip: refer people you'd want to work with, for jobs that fit them.
| Badge | Metal | How to earn it |
| - | - | - |
| **First Hire** | Bronze | Someone you referred is hired. |
| **Team Builder** | Bronze | 3 people you referred are hired. |
| **Hiring Hero** | Silver | 10 people you referred are hired. |
| **Dream Team** | Gold | 25 people you referred are hired. |
| **Department Maker** | Gold | 50 people you referred are hired. |
| **Hiring Legend** | Platinum | 100 people you referred are hired. |
| **Workforce Builder** | Diamond | 250 people you referred are hired. |
### Milestones
Hires who reached a reward milestone, like Training Completed. Tip: checking in with your hires in their first weeks helps.
| Badge | Metal | How to earn it |
| - | - | - |
| **Milestone Maker** | Bronze | Someone you referred reaches a reward milestone, like Training Completed. |
| **Milestone Master** | Silver | 10 people you referred reach a reward milestone. |
| **Milestone Machine** | Gold | 50 people you referred reach a reward milestone. |
| **Milestone Legend** | Platinum | 100 people you referred reach a reward milestone. |
### Staying Power
Hires who are still employed 90 days after their start date.
| Badge | Metal | How to earn it |
| - | - | - |
| **90 Days Strong** | Bronze | Someone you referred stays 90 days. |
| **Staying Power** | Silver | 10 people you referred stay 90 days. |
| **Built to Last** | Gold | 50 people you referred stay 90 days. |
| **Rock Solid** | Platinum | 100 people you referred stay 90 days. |
### One Year
Hires who are still employed a year after their start date.
| Badge | Metal | How to earn it |
| - | - | - |
| **One Year Club** | Bronze | Someone you referred stays a year. |
| **Loyalty Leader** | Silver | 10 people you referred stay a year. |
| **The Long Haul** | Gold | 25 people you referred stay a year. |
| **Culture Keeper** | Platinum | 50 people you referred stay a year. |
## What counts
* **Every referral at your company counts**, whichever of your company's portals it came through, including people who applied through the employee's links.
* **Denied referrals don't count.** If the recruiting team doesn't approve a referral, it doesn't count toward any badge.
* **Hires** count from the hire's start date.
* **Milestones** count a hire once, when they reach a milestone in a reward program.
* **Staying badges** count a hire on the day they reach 90 days or a year after their start date, only if they're still employed on that day.
* **The earned date** is the day the count was reached. For example, Connector is earned on the day of the fifth referral.
> [!TIP]
>
> Mention badges when you launch or promote your referral program. Early badges like First Referral and Foot in the Door come quickly and get people started, and the long tracks keep your busiest referrers going.
## FAQ
> [accordion] Can admins turn badges off or change them?
>
> No. Every employee with full access to a portal sees the same 34 badges.
> [accordion] Do badges depend on how much someone was paid?
>
> No. Badges count referrals, applications, hires, milestones and how long hires stay. Reward amounts never count.
> [accordion] Are badges per portal?
>
> No. Badges count all of an employee's referrals at your company, so they're the same on every portal the employee can use.
> [accordion] Can someone lose a badge?
>
> Badges always reflect the employee's current referrals. If a referral is later denied, it stops counting, which can take a badge away.
> [accordion] Do former employees see their badges?
>
> No. Employees who left and can still see their payouts see only **Payouts** and **Settings**.
> [accordion] Can other employees see my badges?
>
> No. Each employee sees only their own badges.
## Related
> [card] [Using the referral portal](/referrals/employee-portal)
>
> The employee's guide to the portal.
> [card] [Employee sign-in and access](/referrals/portal-access)
>
> Who gets full access to a portal.
> [card] [Reward programs](/referrals/reward-programs)
>
> Set up rewards with milestones like Training Completed.
> [card] [How referrals work](/referrals/overview)
>
> The referral process from referral to payout.
# Referrals dashboard
Source: https://help.journeyfront.com/referrals/dashboard
See whether your referral program is producing hires, who is driving it, and what you owe.
> [!NOTE]
>
> **Who can do this:** Users with *View Referrals* see the dashboard. Payout amounts (the **Payouts** panel and the Paid, Owed and Per Hire columns) only show for users who also have *Manage Referral Payouts*. Users without *All Referral Portals Access* only see the referral portals they're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
The Referrals dashboard shows how your referral program is doing at a glance: how many referrals came in, how many turned into hires who stayed, which employees and job reqs drive the most hires, and what you've paid and still owe. Every number follows the filters at the top, so you can look at one portal, one referrer or one reward program in a couple of clicks.
Go to **Referrals**, then the **Dashboard** tab.
## Choose what to look at

The bar at the top stays in view as you scroll.
| Control | What it does |
| - | - |
| **Referred Date** | The range of referrals to look at. It starts at **Past 90 Days** and can cover up to three years. |
| **Referral Portal** | Only referrals from the portals you pick. |
| **Referrer** | Only referrals from the employees you pick. |
| **More** | Adds **Job Req**, **Reward Program** and **Referral Status** filters. |
| **Compare with** | What the change on each card is measured against: **Previous period**, **Same period last year** or **No comparison**. Each option shows its dates. |
| **Day**, **Week**, **Month**, **Quarter** | How the charts group dates. The dashboard picks one to fit the range; click another to change it. **Day** is available for ranges up to about three months, and **Quarter** for ranges longer than a month. |
| **Reset** | Appears once you've changed anything, and puts everything back to the defaults. |
The page address keeps your filters and choices, so you can bookmark a view or send the link to a teammate and they'll see the same thing (for the portals they can access).
> [!TIP]
>
> Recent referrals are often still in the hiring process, so a short or very recent range can make the hire rate look low. For a fair read on conversion, look at a range that ended a month or two ago.
## Headline cards
| Card | What it shows |
| - | - |
| **Referrals** | Referrals made in the range, and how many employees made them. |
| **Hires** | People referred in the range who were hired, whenever the hire happened. Someone referred twice counts once. |
| **Hire Rate** | Hires out of the people referred in the range. |
| **Active Hires** | People hired from referrals made in the range who are still employed today, and what share of hires that is. |
Each card shows its change against the comparison period in a small green or red pill (grey when there's no change). Hover the pill to see the earlier number and its dates. Hover the info icon on any card or panel to see exactly how it counts.
## Referrals and Hires
A line chart of referrals by the day they were made and hires by the day of the hire, grouped by day, week, month or quarter. The totals for the range sit next to the legend. Hover the chart to see each period's numbers.
The hires line counts hires that happened in the range, for referrals made at any time, so it can differ from the **Hires** card.
## Referral Funnel

The funnel follows every referral made in the range from left to right:
1. **Referrals**, split into the **Candidates** they were for and **Duplicate referrals** (a person referred more than once counts once).
2. Whether each candidate **Applied** or has **Not applied yet**.
3. How far each person got, using their furthest application: **Hired**, **In progress**, **Rejected** or **Withdrew**.
4. Whether each hire is **Still employed** or has **Exited**.
Hover a block or a band to see its count and its share. Under the chart you'll see the share of candidates hired and how many referrals were for someone already referred.
The **Referral status** bar below shows how many of the range's referrals are **Needs Review**, **Active** or **Denied**. See [Review, credit and Reward Status](/referrals/review-and-credit) for what each one means.
## Payouts
This panel only shows for users with **Manage Referral Payouts**.

| Tile | What it shows |
| - | - |
| **Paid** | Payouts payroll paid in the range, with the change against the comparison period. |
| **Owed** | Earned and overdue payouts not paid yet. |
| **Overdue** | Owed payouts earned longer ago than the overdue window in **Payout Settings**. The tile turns red when there's anything overdue. |
| **Upcoming** | Payouts that become owed once their installment is earned. |
Under the tiles, a strip shows what a [payout batch](/referrals/payout-batches) would pick up today: how many payouts are ready to pay and their total, how many are already in a batch waiting for results, and how many are held until their referral is reviewed. Click **Go to Payout Batches** to act on it.
The chart stacks what was paid (by the date payroll paid it) and what's still owed (by the date it was earned) for each period. If you pay rewards in more than one currency, use the currency buttons at the top of the panel. Amounts in different currencies are never added together.
## Reward Programs
A table of the range's referrals grouped by the reward program they were made under (the program on the job req at the time), with each program's **Referrals**, **Hires** and **Hire Rate**. Archived programs are marked **Archived**.
With **Manage Referral Payouts**, the table also shows **Paid**, **Owed** and **Per Hire**: everything paid, owed and still to come for those referrals, divided by their hires.
> [!TIP]
>
> Use **Per Hire** to compare what each program costs you for every hire it brings in. Then filter by **Reward Program** to see which job reqs and referrers each one is reaching.
## Top Referrers and Top Job Reqs

**Top Referrers** ranks the employees whose referrals in the range led to the most hires, then the most referrals. The top three get a highlighted rank. With **Manage Referral Payouts**, **Paid** shows everything paid to them for those referrals, one line per currency.
* Click a referrer's name to narrow the whole dashboard to just them.
* Hover the row and click the open icon to open the referrer's details.
The table is hidden while you're filtered to a single referrer, since it would only list them.
**Top Job Reqs** ranks the job reqs with the most hires from the range's referrals, with their referrals, hires and hire rate. Click a job req to open it.
Each list shows up to 10 rows.
## Download a chart or table
Click the menu at the top right of a panel:
* **Download PNG** saves the chart as an image (Referral Funnel, Referrals and Hires, Payouts).
* **Download CSV** saves the numbers behind any panel.
## FAQ
> [accordion] Why doesn't the Hires card match the Hires line on the chart?
>
> The card counts people referred in the range who were hired, whenever they were hired. The chart counts hires that happened in the range, for referrals made at any time.
> [accordion] Why don't I see the Payouts panel or any amounts?
>
> Amounts are only shown to users with **Manage Referral Payouts**. Ask an admin to add it to your security role. See [Permissions and portal admins](/referrals/permissions).
> [accordion] Why is someone referred twice only counted once?
>
> The dashboard measures people, not referral forms. Extra referrals for the same person show as **Duplicate referrals** in the funnel.
> [accordion] Can I share what I'm looking at?
>
> Yes. Copy the page address. It carries your filters, comparison and grouping. Whoever opens it sees the same view for the portals they can access.
> [accordion] How far back can I look?
>
> Up to three years in one range.
> [accordion] Why can't I pick Day?
>
> Daily grouping is only available for ranges of about three months or less. Pick **Week** or **Month** for longer ranges.
## Related
> [card] [The Referrals page](/referrals/referrals-page)
>
> Work through individual referrals.
> [card] [Payouts](/referrals/payouts)
>
> See every installment and its status.
> [card] [Payout batches](/referrals/payout-batches)
>
> Send what's owed to payroll.
> [card] [Reward programs](/referrals/reward-programs)
>
> Set what referrals earn.
# Using the referral portal
Source: https://help.journeyfront.com/referrals/employee-portal
A guide for employees: refer friends, share jobs, and track your referrals and rewards.
> [!NOTE]
>
> **Who this is for:** Employees of a company that uses Journeyfront referrals. Your company shares the portal's link with you. Admins can send this page to their employees as-is.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Your company's referral portal is where you refer people you know, share open jobs, and follow every referral from the day you send it to the day your reward is paid. It works on your phone and your computer, and it carries your company's logo and colors.
## Sign in
Some portals let anyone browse jobs and refer without signing in. Signing in adds everything that's yours: Home, My Referrals, Payouts, the Leaderboard and Badges. If your company's portal requires sign-in, you'll see the sign-in page first.
**1. Enter your work email**
Open the portal link and click **Sign In**. Enter your **Work Email** and click **Send Code**.
**2. Enter the code or click the link**
If your email can sign in to this portal, you get an email with a 6-digit code and a sign-in link. Enter the code under **6-Digit Code** and click **Sign In**, or just click the link in the email. Both expire after 15 minutes. Wrong email? Click **Use a Different Email**.
You land on **Home**. The portal keeps you signed in on that browser for up to 30 days. To sign out, open your name in the menu and click **Sign Out**.
> [!TIP]
>
> No email arrived? Check that you used your work email, and look in your spam folder. The portal never says whether an address can sign in, so if the code doesn't come, ask your recruiting team whether your email is set up for the portal.
Who can sign in is up to your company. Usually that's everyone with an active employee record, plus new hires whose work email is on your company's list. If you leave the company, your company may let you keep seeing your **Payouts** for a while, so you can follow rewards you already earned. Referring isn't available then. See [Employee sign-in and access](/referrals/portal-access) for how admins set this up.
## Find your way around
On a computer, the portal has a sidebar on the left: **Home**, **Jobs**, **Refer**, **My Referrals**, **Payouts**, **Rewards**, **Leaderboard** and **Badges**. Click the panel icon at the top (or press Cmd+B or Ctrl+B) to shrink the sidebar to icons. At the bottom are a link to your company's site and your name, which opens your account menu.
On a phone, tap the menu icon in the top left to open the same list. Your photo or initials in the top right opens your account menu.
Your account menu has your name and email, **Switch Portal** (when you can use more than one), **Settings** and **Sign Out**.

What you see depends on your access. The **Leaderboard** appears only when your company turns it on, and **Rewards** only when your company shows rewards on the portal. Before you sign in, you see **Jobs**, **Refer** and, when it's shown, **Rewards**.
## Home
Home shows how your referrals are doing at a glance:
* **Paid**, **In Review** and **Upcoming**: your reward money so far. If you earn rewards in more than one currency, each currency gets its own row.
* **Next Payout**: the next installment that's due, when it's due, for whom and which installment, for example "Priya Shah · Day 180". **Track Your Payouts** opens Payouts.
* **Your Personal Link**: your own link to all open jobs, with where it opens and how many jobs are open. Anyone who applies through it is credited to you. Copy it, share it to an app, or click **Show QR** for a QR code you can download or copy.
* **Your Referrals**: how many people you **Referred**, how many **Applied**, how many were **Hired** and how many were **Paid**.
* **Your Badges**: your next badge and the ones you earned most recently. See [Badges](/referrals/badges).
* **Jobs to Share**: a few open jobs, the ones with rewards first, each with a **Share** button.
* **Leaderboard**: your rank and the top five, when your company shows the leaderboard.
Featured jobs, reward programs and announcements from your company appear at the top of Home and Jobs under **Featured**.

> [!TIP]
>
> Print your QR code or put it on a slide. Anyone who scans it and applies is credited to you, the same as your link.
## Find and share jobs
**Jobs** lists every open job on the portal. Search by job title or location. Each card shows the location and, when the job pays a reward, **Earn** and the amount. Click a card to open the job's page, with **About the Job** and **What It Pays** (each installment and when it pays).
To share a job, click **Share** on its card (or **Share This Job** on its page). The share sheet shows what you earn and your own link to that job's application:
* Click **Copy** to copy the link.
* Under **Share It**, send it with your phone's own **Share** menu, WhatsApp, Facebook, LinkedIn, Messenger, Telegram, **Email** or **Text**.
* Click **Show QR** for a QR code.
Your link stays the same every time, so you can share it as often as you like.

If you haven't signed in, the portal asks for your first name, last name and work email before it makes your link, so the referral is credited to you.
## Refer someone
Use **Refer** when you'd rather send the person's details yourself.
**1. Open Refer**
Click **Refer** in the menu, or **Refer Someone** on Home, Jobs or a job's page. **Refer Someone** is selected at the top. (**Share a Job** next to it gives you your link to all jobs and a link for each job.)
**2. Choose the job**
Under **Who You're Referring**, pick a **Job Opening**. If your company takes general referrals, you can choose **General Referral (No Specific Job)**. When the job pays a reward, **What You Could Earn** shows the amount and each installment.
**3. Add the people**
Enter each person's **First Name**, **Last Name**, **Email** and **Phone**. Click **Add Person** to refer more than one person for the same job, up to 10 at a time. Your company may also ask for their location.
**4. Add a note and send**
Add a **Note for the Recruiting Team (Optional)**. If your company asks for it, check the box confirming the people you're referring agreed to be contacted. Click **Send Referral** (or **Send 3 Referrals** and so on).
When it's sent, you see **Referral Sent** and a link you can pass on so they can apply. Click **Refer Someone Else** to start another. When you're signed in, the form shows **Referring as** with your name. If you're not signed in, you fill in your own name and work email under **You**.
> [!TIP]
>
> Let the person know you referred them, and send them the link. People who expect the recruiting team's message are much more likely to apply.
## My Referrals
**My Referrals** lists everyone you've referred at your company, newest first, with the job, the date you referred them, their stage and their reward. Filter by stage with the chips at the top.
| Stage | What it means |
| - | - |
| **Referred** | You referred them, and they haven't applied yet. |
| **Applied** | They applied for the job. |
| **Interviewing** | Their application is under review. |
| **Hired** | They were hired. |
| **Not Moving Forward** | The referral wasn't approved, or the application closed. |
For some jobs, your company shows only whether the person applied and whether they were hired. Those referrals never show **Interviewing**. The reward column reads "Worth \$500" until something is paid, then "\$200 paid of \$500".
## Payouts
**Payouts** tracks every reward installment, from your hire's start date to payday. At the top are your **Paid**, **In Review** and **Upcoming** totals, then **Rewards Over Time**, a chart of your rewards by month.
Under **By Hire**, each person you referred who was hired has a card with their job, start date and how many days they've been there. A track runs from **Start** to each installment, such as **Day 90** or **Training Completed**, with a row below for each installment saying where it stands. Each installment is named by when it pays, such as **Day 90**, plus its own name when your company gave it one, for example "Day 150 · Sign-On Bonus".

| Status | On the track | What it means |
| - | - | - |
| **Upcoming** | An outlined dot | Not due yet. The row says when it's up for review, for example "Up for review on 12/12/2026 · in 45 days", or which milestone it's waiting on. |
| **In Review** | A filled dot | It reached its date and payroll is confirming it. |
| **Paid** | A green dot with a check | Payroll marked it as paid. The money can reach your bank account a little later. |
| **Not Paid Out** | A grey dot with an x | It won't be paid, with the reason, for example "They left before day 150" or "Not approved by the recruiting team". |
Filter the installments with **All**, **Upcoming**, **In Review**, **Paid** and **Not Paid Out**. Questions about a payout? Ask your recruiting team.
> [!TIP]
>
> Days count from your hire's start date. If a reward pays at a milestone like Training Completed, it has no date until your hire reaches it.
## Rewards
When your company shows rewards on the portal, **Rewards** explains how referring works in three steps, then lists the **Reward Programs** behind the portal's jobs. Each program shows its **Total Reward**, every payment and when it's due, and its effective dates when it has them. Your company's own rules for who is eligible are in the program's description.
## Leaderboard
When your company turns it on, the **Leaderboard** ranks the portal's top referrers by hires, then by referrals. Pick **This Month**, **This Quarter**, **This Year** or **All Time** at the top. This Year is selected when the page opens.
Your card shows **Your Rank**, your **Hires** and **Referrals**, and how many more hires would move you up, like "2 more hires to pass #2". The top three stand on a podium, and everyone else is listed below with a bar for their hires.

Only referrals made through this portal in the period you picked count. The leaderboard never shows anyone's reward money.
## Badges
You earn **Badges** for referring: your first referral, people who apply, hires, hires who reach a milestone, and hires who stay. Badges are never about money. See [Badges](/referrals/badges) for every badge and how to earn it.
## Settings
Open your account menu and click **Settings**.
* **Profile Photo**: click **Upload Photo** and choose a JPG, PNG or WebP photo. It's cropped to a square and shown to coworkers on the leaderboard, only on your company's referral portals. Use **Replace Photo** or **Remove** to change it. This card appears only when your company allows photos.
* **Email Notifications**: a switch for each email the portal sends you, grouped under **Your Referrals**, **Your Payouts** and **From Your Company**. Every email is on until you turn it off, and changes save right away.
| Email | When it's sent |
| - | - |
| **Referral Received** | When a referral you submit is received. |
| **Referral Applied** | When someone you referred applies, including through your link. |
| **Referral Hired** | When someone you referred is hired. |
| **Not Moving Forward** | When a referral isn't moving forward. |
| **Payout In Review** | When an installment reaches its date and goes to payroll for review. |
| **Payout Marked as Paid** | When payroll marks an installment as paid. |
| **Payout Not Paid Out** | When an installment won't be paid out, and why. |
| **Featured Jobs and News** | When your company features a job, reward or announcement and emails it. |
You only see the emails your company sends from this portal.
## Switch portals
Some companies have more than one referral portal, for example one per region. If you can use more than one, open your account menu and pick a portal under **Switch Portal**. You stay signed in. Your referrals, payouts and badges are the same on every portal of your company. The leaderboard counts only the portal you're on.
## FAQ
> [accordion] I didn't get a sign-in code. What now?
>
> Make sure you entered your work email, check your spam folder and wait a minute. If it still doesn't arrive, ask your recruiting team to check that your email can sign in to the portal. Codes and links expire after 15 minutes, so request a new one if yours is old.
> [accordion] Do I have to sign in to refer someone?
>
> It depends on your company's portal. Many let you refer or share a job without signing in, using your name and work email. Signing in lets you follow your referrals and payouts.
> [accordion] Does someone who applies through my link count as my referral?
>
> Yes. Anyone who applies through your personal link, a job link or your QR code is credited to you, and shows up in My Referrals.
> [accordion] Why does my payout say In Review?
>
> It reached its date, and payroll is confirming that you and your hire both still qualify before paying it. When payroll marks it as paid, it moves to **Paid** and you get an email if that email is turned on.
> [accordion] Why does a referral show only Applied, not Interviewing?
>
> For some jobs your company shares only whether the person applied and whether they were hired, to protect candidates' privacy.
> [accordion] Can my coworkers see how much I earned?
>
> No. The leaderboard shows hires and referrals only. Your payouts are visible to you and your company's referral team.
> [accordion] What happens if I leave the company?
>
> Your company decides. Often you can still sign in and see **Payouts** for a while, so you can follow rewards you already earned. Referring isn't available then.
> [accordion] How do I stop the emails?
>
> Open your account menu, click **Settings**, and turn off any email under **Email Notifications**.
## Related
> [card] [Badges](/referrals/badges)
>
> Every badge you can earn, and how.
> [card] [How referrals work](/referrals/overview)
>
> The referral process from referral to payout.
> [card] [Employee sign-in and access](/referrals/portal-access)
>
> How admins decide who can sign in.
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> For admins: build and brand a portal.
# Featured items and email notifications
Source: https://help.journeyfront.com/referrals/featured-and-notifications
Promote jobs, rewards and news at the top of the portal, and choose which emails employees get.
> [!NOTE]
>
> **Who can do this:** People whose security role has *Manage Referral Settings*. Without *All Referral Portals Access*, you can only change the portals you're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Featured items put the jobs, bonuses and news you care about most right in front of your employees, at the top of the portal. Email notifications keep employees in the loop on their referrals and payouts without them having to check the portal.
Both live in **Settings**, then **Referral Portals**. Open a portal and click **Featured** or **Notifications**.
## Feature a job, reward or announcement
You can feature three kinds of items:
| Kind | Use it for |
| - | - |
| **Job Req** | An open job you want more referrals for. |
| **Reward Program** | A bonus you want staff to know about. |
| **Announcement** | A short note, like a referral contest. |
Featured items show at the top of the portal's **Home** and **Jobs** pages, in the order you set.
**1. Open Featured**
Open the portal and click **Featured** in the section list, then **Add Featured**.
**2. Choose what to feature**
Pick **Job Req**, **Reward Program** or **Announcement**. For a job req or reward program, choose it from the list. Each option shows what it pays.

**3. Write the details**
| Field | What it does |
| - | - |
| **Headline** | Shown in place of the job title or program name, like "We need 20 agents by December." Required for an announcement, optional otherwise. |
| **Message** | An optional short note, up to 500 characters. |
| **Ends On** | The item shows through this day, then comes off the portal on its own. Leave it empty to keep it up until you remove it. |
| **Email** | Check **Email it to employees** to send it once, right away, to employees on this portal who get featured emails. |
**4. Feature it**
Click **Feature It**. The item is added to the end of the list and saves right away. There's no need to click **Save**.
> [!TIP]
>
> Write a headline that says why the job matters right now, like a hiring goal or a deadline. Pair it with an **Ends On** date so the item comes down on its own once the push is over.
A portal can feature up to 6 items at once. Items that have ended don't count toward the limit. When the list is full, **Add Featured** is turned off until you remove one or one ends.
If a reward program isn't paid by any open job req on the portal, the window warns you that employees won't see it until one is.
## Manage featured items

Each item shows its headline, its kind, what it points at and its end date, plus a status:
| Status | What it means |
| - | - |
| **Showing** | Employees see it on the portal now. |
| **Not Showing** | It's still on your list but employees can't see it. Hover over the status for the reason: the job req isn't open on this portal, the portal doesn't show rewards, or the program isn't in effect on any open job req on this portal. |
| **Ended** | Its **Ends On** date has passed. |
From the list you can:
* **Reorder** items by dragging the handle on the left. The portal shows them in this order.
* **Edit** an item with the pencil icon to change its **Headline**, **Message** or **Ends On** date. What it points at can't change, so add a new item instead.
* **Remove** an item with the trash icon.
Every change here saves right away.
> [!TIP]
>
> A **Not Showing** item comes back on its own when the reason is fixed, for example when you reopen the job req. You don't need to add it again.
## Choose which emails employees get
The portal emails employees when something happens with their referrals or payouts. Every email is on unless you turn it off. Turning one off on the **Notifications** section stops it for everyone on this portal. Click **Save** when you're done.

| Email | Sent when |
| - | - |
| **Referral Received** | A referral the employee submits is received. |
| **Referral Applied** | Someone they referred applies, including through their referral link. |
| **Referral Hired** | Someone they referred is hired. |
| **Not Moving Forward** | A referral isn't moving forward. |
| **Payout In Review** | An installment reaches its date and goes to payroll for review. |
| **Payout Marked as Paid** | Payroll marks an installment as paid. |
| **Payout Not Paid Out** | An installment won't be paid out, with the reason. |
| **Featured Jobs and News** | You feature a job, reward or announcement and choose to email it. |
Each email carries the portal's name, logo and brand color, with a button back to the right page on the portal. Its footer links to the employee's portal **Settings**.
### What employees can change
Employees can turn off any of these emails for themselves in their portal **Settings**. They only see the emails this portal sends, so an email you turned off here doesn't appear for them.
### Who gets emails
* Emails only go to people who can sign in to the portal. A **Public** portal doesn't send them. See [Employee sign-in and access](/referrals/portal-access).
* A former employee with payouts-only access gets payout emails only.
* **Not Moving Forward** follows the portal's **Referral Status Shown** setting. On a portal set to **Accepted and Joined Only**, it's only sent when a referral itself is not approved, not when an application is rejected later.
* Each email is sent once. If the same thing happens again, the employee isn't emailed twice.
> [!TIP]
>
> Keep the payout emails on. They answer most "when do I get paid?" questions before they reach your team.
## FAQ
> [accordion] Can I email an item I already featured?
>
> No. The email option is only available when you add an item, and it sends once. To send news again, add a new featured item and check **Email it to employees**.
> [accordion] Why did my featured email not go out?
>
> The email only goes out if the item is showing when you add it. A job req that isn't open on the portal, for example, isn't emailed. Employees who turned off **Featured Jobs and News** in their portal **Settings** don't get it either.
> [accordion] Why can't I add another featured item?
>
> A portal can show up to 6 items at once. Remove one, or wait for one to reach its **Ends On** date.
> [accordion] Do employees get emails about referrals made on another portal?
>
> Each email comes from the portal the referral was made on. If that portal is inactive, it comes from your account's first active portal.
> [accordion] If I turn an email back on, will employees who turned it off get it?
>
> No. An employee's own choice in their portal **Settings** still applies.
## Related
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Create a portal and set its branding and form.
> [card] [Employee sign-in and access](/referrals/portal-access)
>
> Who can sign in and receive portal emails.
> [card] [Payouts](/referrals/payouts)
>
> The installments behind the payout emails.
> [card] [Using the referral portal](/referrals/employee-portal)
>
> Where featured items appear for employees.
# Rewards on job reqs
Source: https://help.journeyfront.com/referrals/job-req-rewards
Choose which referral portals show a job req and which reward program its referrals earn.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission. To see and pick a reward program, you also need *View Referrals*.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Each job req decides two things for referrals: which referral portals list it, and which reward program its referrals earn. Set them once and every referral to the job req is worth the right amount, with no spreadsheet to keep in sync.
## Set a job req's reward
**1. Open the job req's Configurations**
Open the job req, go to the **Setup** tab, then click **Configurations**.
**2. Choose where it shows**
In the **Referrals** card, set **Show on Referral Portals**. See the options below.
**3. Pick the reward program**
Choose a program in **Reward Program**. Each option shows the program's name and total, such as "Agent Referral Bonus (\$500)". Choose **No Reward Program** if referrals to this job req don't earn a bonus.

**4. Save**
Click **Save** at the top of the page.
If you have *Manage Referral Settings*, a **Manage Reward Programs** link under the picker opens the Reward Programs tab in a new browser tab, so you can create or check a program without losing your place.
### Show on Referral Portals
| Option | What it does |
| - | - |
| **All Portals** | The job req is listed on every referral portal. This is the default. |
| **No Portals** | The job req isn't listed on any portal. |
| **Specific Portals** | The job req is listed only on the portals you pick in the box that appears. |
Archived job reqs are never listed on a portal.
### Which programs you can pick
* Only **Active** programs are in the list. Drafts don't appear until they're published. See [Reward programs](/referrals/reward-programs).
* A program must cover every portal the job req is posted on. A program for **All Referral Portals** always fits. A program for specific portals only fits when the job req is posted on some or all of those portals and no others.
* If your role only covers some portals, you only see programs for your portals or for all portals. A job req whose program you can't manage shows the program's name, but you can't change it.
> [!TIP]
>
> Use one program for all portals for your standard bonus, and portal-specific programs only where the bonus really differs, for example a different currency for another region. Fewer programs means fewer mismatches when job reqs move between portals.
## When the program doesn't fit the portals
If you change the portals so the job req's program no longer covers them, a message appears under **Reward Program** and you can't save until you fix it.

To fix it, either post the job req only on the portals the message names, or pick a reward program for all referral portals.
## When you change or archive a program
* **You pick a different program:** new referrals to the job req earn the new program. Referrals made before the change keep the terms they were made under.
* **The program is archived:** the job req keeps showing it, marked **(Archived)**, but new referrals don't earn it, and employees no longer see the reward on the portal. Pick an active program to start rewarding referrals again.
* **The program's effective dates end:** referrals made after the end date don't earn it, and the reward stops showing on the portal.
## What employees see
When a portal shows rewards, each job req with a reward program displays **Earn** and the program's total on the portal's job list. The job's page adds a **What It Pays** card with each installment and when it's paid.

Employees only see a reward that a referral made today would earn: the program has to be active, inside its effective dates and on that portal. Portal admins can hide rewards on a portal with the **Show Rewards** setting on its **Referral Form** tab. See [Set up a referral portal](/referrals/portal-setup).
## FAQ
> [accordion] Why can't I see the Reward Program setting?
>
> It only appears when Referrals is turned on for your account and your role has *View Referrals*.
> [accordion] Why isn't my program in the list?
>
> It's a draft, it's archived, or it doesn't cover every portal this job req is posted on. Publish or restore it, or check its **Referral Portals** on the Reward Programs tab.
> [accordion] Why is the Save button grayed out?
>
> The reward program doesn't cover the portals the job req is posted on. Read the message under **Reward Program**, then change the portals or the program.
> [accordion] If I change the program, do existing referrals change too?
>
> No. Each referral keeps the terms from the day it was made. Only new referrals earn the new program.
> [accordion] Can a job req have more than one reward program?
>
> No. Each job req has one reward program, or none. To pay differently by region, post the job req on the right portals and use a program for each, or duplicate the job req for each region.
> [accordion] Does a duplicated job req keep its reward program?
>
> Yes. When you [duplicate a job req](/job-reqs/create#start-from-an-existing-job-req), the copy keeps the same reward program and **Show on Referral Portals** setting, including the specific portals the original was posted on. Check them on the copy's **Configurations** page if the new job req is for a different region.
## Related
> [card] [Reward programs](/referrals/reward-programs)
>
> Create the programs you pick here.
> [card] [Job req settings](/job-reqs/job-settings)
>
> Every setting on the Configurations page.
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Branding, sign-in and what a portal shows.
> [card] [How referrals work](/referrals/overview)
>
> The big picture and a setup checklist.
# How referrals work
Source: https://help.journeyfront.com/referrals/overview
How employee referrals, reward programs, payouts and the referral portal fit together, plus a setup checklist.
> [!NOTE]
>
> **Who can do this:** People whose security role has *View Referrals* can open the **Referrals** section. Setting up portals and reward programs takes *Manage Referral Settings*, and payouts take *Manage Referral Payouts*. See [Permissions and portal admins](/referrals/permissions).
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
[Referrals](https://www.youtube.com/embed/buf1jKG9RQw)
Referrals turn your employees into a recruiting channel and keep every referral bonus on track, from the day someone is referred to the day payroll pays the reward. Employees refer people on a branded referral portal, your team reviews and credits each referral, and Journeyfront works out what each referrer has earned and when.
This page gives you the big picture. Each step links to a page with the details.
## The life of a referral

**1. An employee refers someone**
Employees refer people they know on your [referral portal](/referrals/portal-setup), or share a referral link to a job. Anyone who applies through the link is recorded as their referral. Your team can also add referrals in Journeyfront, one at a time or in bulk. See [The Referrals page](/referrals/referrals-page).
**2. Your team reviews it**
Most referrals start as **Active**. When a referral might not deserve the credit, for example someone else already referred the same person or the referrer referred themselves, it's set to **Needs Review** so a person can decide. You can make it **Active** or **Denied**. See [Review, credit and Reward Status](/referrals/review-and-credit).
**3. The candidate is hired**
When you [hire the candidate](/onboarding/hire-candidates), Journeyfront creates one payout for each installment of the referral's reward program. The reward program comes from the job req the person was referred to. See [Rewards on job reqs](/referrals/job-req-rewards).
**4. Each payout is earned**
A payout is earned on its **Earned On** date: a number of days after the hire's start date, or the day a milestone like Training Completed is reached. The hire and the referrer both need to still be employed on that date. See [Payouts](/referrals/payouts).
**5. Payroll pays it**
Earned payouts go into a payout batch that you hand to payroll. When payroll sends the results back, you record which payouts were paid. Journeyfront tracks what's owed and paid. Your payroll system pays the money. See [Payout batches](/referrals/payout-batches).
## Key concepts
| Term | What it means |
| - | - |
| **Referral portal** | A branded page where employees refer people, see open jobs and, if they sign in, track their referrals and payouts. You can have more than one, for example one per region. |
| **Referral** | One person referred by one referrer, usually to a specific job req. |
| **Referrer** | The employee who made the referral. Journeyfront links referrers to their employee record so it knows whether they're still employed. |
| **Reward program** | What a referral pays: an amount, a currency and a schedule of installments. You attach a reward program to job reqs. |
| **Installment** | One part of a reward program, due a number of days after the hire's start date or when a named milestone is reached. |
| **Payout** | One installment for one hired referral. It moves through **Upcoming**, **Earned** or **Overdue**, and ends as **Paid** or **Ineligible**. |
| **Payout batch** | A group of earned payouts that you send to payroll at once, with a record of what payroll paid. |
| **Reward Status** | A summary of what a referral has paid so far, such as **Not Hired Yet**, **Owed**, **Partly Paid** or **Rewarded**. Journeyfront works it out from the referral's payouts. |
> [!TIP]
>
> Each referral keeps the reward program terms it was made under. If you raise a bonus next quarter, referrals made before the change still pay the old amount, so you can always explain any payout.
## Where things live
Everything your team works with day to day is in the **Referrals** section of the top menu. Its tabs are **Dashboard**, **Referrals**, **Referrers**, **Payouts**, **Payout Batches** and **Reward Programs**.

**Payouts** and **Payout Batches** only appear for people with the *Manage Referral Payouts* permission, since they show pay data. The same goes for paid, owed and upcoming amounts on the other tabs.
Two other places hold referral settings:
* **Settings**, then **Referral Portals**: create and set up your portals, including branding, who can sign in, the referral form, email notifications and featured items.
* A job req's **Setup** tab, then **Configurations**: choose which portals show the job req and which reward program its referrals earn.
## Setup checklist
**1. Turn on Referrals**
Ask your Customer Success Manager to turn on Referrals for your account.
**2. Give your team access**
Add the Referrals permissions to the right security roles, and decide who should only manage certain portals. See [Permissions and portal admins](/referrals/permissions).
**3. Create a referral portal**
Go to **Settings**, then **Referral Portals**, and click **New Referral Portal**. Add your branding and choose who can sign in. See [Set up a referral portal](/referrals/portal-setup) and [Employee sign-in and access](/referrals/portal-access).
**4. Create your reward programs**
Go to **Referrals**, then **Reward Programs**, and click **New Reward Program**. See [Reward programs](/referrals/reward-programs).
**5. Put rewards on your job reqs**
On each job req, go to **Setup**, then **Configurations**. Choose the portals it shows on and its reward program. See [Rewards on job reqs](/referrals/job-req-rewards).
**6. Share the portal with employees**
Copy the portal's link and share it with your employees. See [Using the referral portal](/referrals/employee-portal) for what they'll see.
**7. Pay rewards on a schedule**
Each payroll cycle, check the **Payouts** tab and run a payout batch. See [Payouts](/referrals/payouts) and [Payout batches](/referrals/payout-batches).
> [!TIP]
>
> Connect your [HR system](/integrations/hris) before you start paying rewards. Journeyfront uses employee records to know whether a hire or a referrer has left, which decides whether a payout can still be earned.
## FAQ
> [accordion] Does Journeyfront pay the rewards?
>
> No. Journeyfront tracks what each referrer has earned and when, and gives you payout batches to hand to payroll. Your payroll system pays the money, and you record the results back in Journeyfront.
> [accordion] Do employees need a Journeyfront account?
>
> No. Employees use the referral portal, not Journeyfront itself. Depending on the portal's settings, anyone can refer without signing in, or employees sign in to the portal to see their own referrals and payouts. See [Employee sign-in and access](/referrals/portal-access).
> [accordion] What if two employees refer the same person?
>
> Only one referral gets the credit for a hire. The first referral keeps it, and the later one is set to **Needs Review**. You can move the credit to a different referral if that's the right call. See [Review, credit and Reward Status](/referrals/review-and-credit).
> [accordion] What happens if I change a reward program?
>
> The change applies to new referrals only. Referrals made before the change keep the terms they were made under.
> [accordion] What if the hire or the referrer leaves?
>
> A payout is only earned if both people are still employed on its **Earned On** date. If either one leaves before then, the payout becomes **Ineligible** and won't be paid. Payouts that were already earned aren't affected.
> [accordion] Can a referral be for no job in particular?
>
> Yes. An employee can refer someone without picking a job. If that person later applies to a job req, the referral picks up that job req's reward program.
## Related
> [card] [Reward programs](/referrals/reward-programs)
>
> Define what a referral pays and when.
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Create the page employees use to refer people.
> [card] [The Referrals page](/referrals/referrals-page)
>
> Find, add and update referrals.
> [card] [Payouts](/referrals/payouts)
>
> Track what's upcoming, earned and owed.
# Payout batches
Source: https://help.journeyfront.com/referrals/payout-batches
Send what is owed to payroll in a logged batch, then record what payroll paid.
> [!NOTE]
>
> **Who can do this:** Users with *Manage Referral Payouts*. Users without *All Referral Portals Access* only see payouts from the referral portals they're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
A payout batch is a record of one payroll run: which owed payouts you sent, who sent them, and the file payroll received. Payroll still does the paying. When payroll reports back, you record the results on the batch, and each payout is updated for you.
Batches keep every payout from being paid twice or forgotten. A payout that's waiting in one batch can't go into another, and anything payroll didn't pay goes back into the pool for the next batch.
## Run a payout batch
**1. Choose what to include**
Go to **Referrals**, then the **Payouts** tab. Either filter the list (for example by **Currency** or **Job Req**), or tick the boxes of the payouts you want.
**2. Click Run Payout Batch**
With no rows ticked, click **Run Payout Batch** in the toolbar to use the list's filters. With rows ticked, click **Run Payout Batch** in the bar above the list.
**3. Name the batch and set Earned By**
Give the batch a **Name** if you like, for example "October 2026 payroll". If you leave it blank, it's called "Payout Batch" plus its number.
Set **Earned By** to your payroll cutoff. The batch includes payouts earned on or before this date. It starts as today.
**4. Review the payouts**
The **Payouts** list shows every payout the batch will include, with its referrer's status, the hire, the installment, the amount, the Earned On date and the payout status. **Includes** shows how many are included and the total per currency.
Untick any payout to leave it out of this batch.

**5. Run it**
Click **Run Batch with** and the number of payouts. The batch is saved and its file downloads as a CSV for you to send to payroll.
> [!TIP]
>
> Read the yellow warning before you run. It counts payouts whose referrers can't be confirmed as still employed (**Exited** or **Unknown**). Hover a payout's status chip to see why it's still owed, for example a referrer who left after the payout was earned.
### What a batch includes
Only owed payouts (**Earned** or **Overdue**) go in a batch. A payout is left out when:
| Left out because | What to do |
| - | - |
| Already in a batch waiting for results | Record that batch's results first. |
| Its referral needs review | Review the referral on the [Referrals page](/referrals/referrals-page). See [Review, credit and Reward Status](/referrals/review-and-credit). |
| Not earned by the Earned By date | Wait, or move the **Earned By** date. |
| Milestone not reached yet | [Record the milestone](/referrals/payouts#record-a-milestone) first. |
| Already paid, or Ineligible | Nothing. These are never sent. |
When you run a batch from the list's filters, the window counts the owed payouts it left out because they're already in a waiting batch or their referral needs review. When you run it from ticked rows, a **Left Out** list names each ticked payout that couldn't be included and the reason. A batch can hold up to 20,000 payouts.
## The batch file
The file payroll receives has one row per payout, with these columns:
| Column | What it holds |
| - | - |
| **Batch** | The batch number. |
| **Payout ID** | The ID that matches the row back to its payout. Keep it in the file. |
| **Referrer**, **Referrer Email** | Who to pay. |
| **Referrer User ID**, **Referrer External Employee ID** | The referrer's Journeyfront User ID and the employee ID from their employee record, so payroll can match its own records. |
| **Hire**, **Job Req** | The hire the reward is for. |
| **Installment**, **Amount**, **Currency**, **Earned On** | What's owed. |
| **Status**, **Paid Date**, **Payroll Reference**, **Note** | Left blank for payroll to fill in and send back. |
The file is saved exactly as it was run, so you can download it again later.
## The Payout Batches tab
Go to **Referrals**, then the **Payout Batches** tab, to see every batch your team has run.

| Column | What it shows |
| - | - |
| **Batch** | The batch's name. Click it to open the batch. |
| **Batch ID** | A short ID for the batch. Click it to copy it. |
| **Ran Date** | When it was run. |
| **Ran By** | Who ran it. |
| **Earned By** | The cutoff date it was run with. |
| **Payouts** | How many payouts it holds. |
| **Total** | Its total, per currency. |
| **Results** | How many payouts have a result, for example "6 of 8 recorded", or **All Recorded** in green once nothing is waiting. |
Search by name, number, batch ID or who ran it, and filter by **Results** (**Waiting** or **All Recorded**), **Ran By**, **Ran Date** and **Earned By**.
## Record what payroll paid
Open a batch to see its details and its payouts. Each payout has a **Result**:
| Result | Chip | What it means |
| - | - | - |
| **Waiting** | Grey | Waiting for what payroll reports back. |
| **Paid** | Green | Payroll paid it. The payout is marked Paid. |
| **Not Paid** | Amber | Payroll didn't pay it this time. It stays owed and can go in the next payout batch. |
| **Ineligible** | Red | It won't be paid. The payout is marked Ineligible. |
A payout's result follows the payout itself, so if someone changes its status on the **Payouts** tab, the batch shows it too.
### Record results by hand
**1. Pick the payouts**
Open the batch. To record the same result for everything still waiting, leave the boxes unticked. To record some, tick the waiting payouts you want.

**2. Choose the result**
Click **Record All as Paid**, **Record All as Not Paid** or **Record All as Ineligible**. With payouts ticked, the buttons read **Record Selected as** instead.
**3. Add the details**
For Paid, enter the **Paid Date** (today by default) and an optional **Payroll Reference**. For any result you can add a **Note**, for example why payroll didn't pay it. The note is saved on each payout, for admins only.
**4. Save**
Click the button at the bottom of the window to record the results.
### Upload the returned file
If payroll fills in the batch file and sends it back, upload it instead of recording each result.
**1. Open the batch**
Open the batch the file belongs to and click **Upload Payroll File**.
**2. Upload the file**
Upload the file. It needs a **Payout ID** and a **Status** column (Paid, Not Paid or Ineligible), and can include **Paid Date**, **Payroll Reference** and **Note**.
**3. Check the summary**
Journeyfront tells you how many payouts were recorded as Paid, Not Paid and Ineligible.
How each row is read:
| Status in the file | Result |
| - | - |
| Paid | Recorded as paid, with payroll's date and payroll reference. |
| Not Paid (or Not Processed, Unpaid) | Recorded as not paid. It stays owed for the next payout batch. |
| Ineligible (or Not Eligible) | Marked ineligible. |
| Blank | Keeps waiting. |
Every row must be a payout in this batch. If any row can't be applied, nothing changes and the problem rows are listed, so you can fix the file and upload it again.
> [!TIP]
>
> Ask payroll to send back the file you gave them, with only the **Status**, **Paid Date**, **Payroll Reference** and **Note** columns filled in. The **Payout ID** column is what matches each row, so it must stay as it was.
When payouts are recorded as Paid or Ineligible, referrers get an email about it, unless they or their portal turned that email off. See [Featured items and email notifications](/referrals/featured-and-notifications).
## Rename or download a batch
In an open batch:
* Click the pencil next to the name to **Rename** it.
* Click **CSV** or **Excel** to download the batch file again.
* Click the **Batch ID** to copy it.
A batch is done when nothing in it is waiting. Its **Results** then read **All Recorded**.
## FAQ
> [accordion] Does running a batch pay anyone?
>
> No. Journeyfront records the batch and gives you its file. Your payroll team pays, and you record what they report back.
> [accordion] Why isn't a payout in my batch?
>
> It may not be owed by the **Earned By** date, its milestone may not be recorded, it may already be waiting in another batch, or its referral may need review. The Run Payout Batch window tells you how many were left out and why.
> [accordion] What happens to payouts payroll didn't pay?
>
> Record them as **Not Paid**. They stay owed and show up for the next batch.
> [accordion] Can I put the same payout in two batches?
>
> Not while it's waiting in one. Once it's recorded as Not Paid, it can go in a later batch.
> [accordion] Can I run a batch for one currency?
>
> Yes. Filter the **Payouts** tab by **Currency** before you click **Run Payout Batch**. Totals are always shown per currency.
> [accordion] Can I change a payout's result after recording it?
>
> Change the payout's status on the **Payouts** tab. The batch picks up the change.
## Related
> [card] [Payouts](/referrals/payouts)
>
> See what's upcoming, owed and paid.
> [card] [Referrers](/referrals/referrers)
>
> Link referrers to their employee records.
> [card] [Review, credit and Reward Status](/referrals/review-and-credit)
>
> Clear referrals that need review.
> [card] [Permissions and portal admins](/referrals/permissions)
>
> Who can see and manage payouts.
# Payouts
Source: https://help.journeyfront.com/referrals/payouts
Track every installment a hire earns, from Upcoming to Paid, record milestones and set when a payout is overdue.
> [!NOTE]
>
> **Who can do this:** Users with *Manage Referral Payouts* see the **Payouts** tab and can change payout statuses and record milestones. Changing **Payout Settings** also needs *Manage Referral Settings* and *All Referral Portals Access*. Users without *All Referral Portals Access* only see payouts from the referral portals they're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
A payout is one installment of a referral reward. When a referred candidate is hired, Journeyfront creates a payout for each installment of the reward, works out when each one is earned, and keeps its status up to date as people's employment changes. The **Payouts** tab is where you see what's coming, what's owed and what's been paid.
## How payouts are created
When a candidate is referred to a job req with a [reward program](/referrals/reward-programs), the referral keeps a copy of that program's terms. Nothing is owed yet. When the candidate is hired, Journeyfront creates **one payout per installment**.
For example, a hire made through the **Agent Referral Bonus** (USD 500: \$200 after 90 days and \$300 after 180 days) gets two payouts: \$200 and \$300.
Each payout's **Earned On** date is worked out from its installment:
| Installment type | Earned On |
| - | - |
| A number of days after start | The hire's start date plus that many days. If the employee record has no start date, the hire date is used. If the start date changes later, the date moves with it. |
| A milestone (for example Training Completed) | The day an admin records that the milestone was reached. Until then the payout shows **Waiting on** the milestone. |
One hire pays one referral. If several people referred the same candidate to the same job req, only the referral with the credit gets payouts that can be paid. See [Review, credit and Reward Status](/referrals/review-and-credit).
## Payout statuses
| Status | Chip | What it means |
| - | - | - |
| **Upcoming** | Grey | Not earned yet: the Earned On date is in the future, or the milestone hasn't been reached. It still depends on the hire and the referrer staying employed. |
| **Earned** | Blue | Earned and waiting for payroll. |
| **Overdue** | Amber | Earned, and still unpaid after the number of days set in **Payout Settings** (30 by default). |
| **Paid** | Green | Payroll has paid it. |
| **Ineligible** | Red | It won't be paid. |
Earned and Overdue together are what you owe right now.
### Why a payout becomes Ineligible
Journeyfront checks that the hire and the referrer are both still employed on the Earned On date. A payout becomes **Ineligible** on its own when:
| Reason | When |
| - | - |
| Hire left before it was earned | The hire's employee record ended before the Earned On date. |
| Referrer left before it was earned | The referrer's employee record shows they left before the Earned On date. |
| Referral was denied | An admin denied the referral. |
| Hire was reversed | The hire was undone. |
| Credited to another referral | Another referral of the same Candidate Application has the credit. |
| Marked ineligible by an admin | Someone set it by hand. |
A referrer who left after a payout's Earned On date is still owed that payout. A referrer whose employment can't be confirmed (no linked employee record, shown as **Unknown**) is treated as still employed, so no payout is withheld because of missing data. Employment comes from your employee records, so an end date from your [HRIS integration](/integrations/hris) is picked up automatically.
Paid payouts never change on their own.
## The Payouts tab
Go to **Referrals**, then the **Payouts** tab.

The cards across the top show the count and total for each status, for whatever filters and search you have applied. Click a card to filter the list to that status, and click it again to remove the filter. Amounts in different currencies are never added together, so a total can read like "\$4,300 + CA\$1,000".
> [!TIP]
>
> Before payroll day, click the **Earned** and **Overdue** cards. The list then shows exactly what you owe, and the totals tell you the size of the run before you start a [payout batch](/referrals/payout-batches).
### Columns
| Column | What it shows |
| - | - |
| **Referrer** | The employee who made the referral. Click the name to open the referrer's details. |
| **Referrer User ID** | The User ID of the referrer's employee record, if they're linked to one. |
| **Referrer Status** | **Active**, **Exited** or **Unknown** (no linked employee record). |
| **Hire** | The referred candidate. Click the name to open their Candidate Application. |
| **Job Req** | The job req they were hired into. |
| **Installment** | The installment's label, for example "90 Days" or "Training Completed". |
| **Amount** | The payout amount in its currency. |
| **Earned On** | The day it's earned, or **Waiting on** the milestone. |
| **Status** | The payout status. Hover the chip to see what it means for this payout, who marked it paid and when, its payout batch and payroll reference, and any note. |
| **Paid Date** | The day payroll paid it, as entered when it was marked Paid. |
| **Payout Batch** | The number of the batch it was sent in. Click it to open the batch. |
Click **Edit Columns** to add **Payout ID**, **Referrer Email**, **Hire Email**, **Hire User ID**, **Start Date**, **Ineligible Reason**, **Payroll Reference** and **Note**.
### Search, filters and views
Search by referrer, hire, User ID or payroll reference. Click **Filters** to filter by **Status**, **Earned On**, **Currency**, **Referrer Status** and **Payout Batch**, plus **Paid Date**, **Amount**, **Job Req**, **Installment** and **Ineligible Reason** (any of the reasons in [Why a payout becomes Ineligible](#why-a-payout-becomes-ineligible), including **Credited to another referral**).
Save a filtered list as its own tab with **Save as New View**, and click **Export** to download the list.
## Change a payout's status
**1. Pick the payouts**
For one payout, click the menu at the start of its row and choose **Mark Paid** or **Mark Ineligible**. For several, tick their boxes and click **Change Status** in the bar above the list.
**2. Choose the new status**
The **Change Payout Status** window shows how many payouts you're updating and their total. Choose a status:
| Option | What it does |
| - | - |
| **Paid** | Payroll has paid it. |
| **Ineligible** | It will not be paid. |
| **Eligible** | Owed once earned, regardless of employment changes. |
| **Reset to Automatic** | Undo a manual status and let employment decide again. |
**3. Add the details**
For **Paid**, enter the **Paid Date** (today by default) and, if you like, a **Payroll Reference**, such as a pay run or transaction number. Add a **Note** for other admins if it helps.

**4. Save**
Click **Change Status**. A message tells you how many payouts were updated.
A status you set by hand sticks: later employment changes won't change it. The status chip's hover says "Set by an admin" so other admins know. To hand a payout back to the automatic checks, choose **Reset to Automatic** from its row menu or in the **Change Payout Status** window. Resetting a paid payout makes it unpaid again.
Notes are for your team only. Employees never see them; the referral portal shows them a plain reason instead.
> [!TIP]
>
> When you send payouts to payroll in a [payout batch](/referrals/payout-batches), record payroll's results on the batch instead. Each payout is updated the same way, and the batch keeps track of what's still waiting.
When a payout is marked Paid, or becomes Ineligible (other than because the referral was denied), the referrer gets an email about it, unless they or their portal turned that email off. See [Featured items and email notifications](/referrals/featured-and-notifications).
## Record a milestone
A milestone installment, like a \$50 **Training Bonus** at Training Completed, stays **Upcoming** until you record the day the hire reached it. That day becomes its Earned On date.
**1. Open Record Milestone**
For one payout, choose **Record Milestone** from its row menu. For several, tick their boxes and click **Record Milestone** in the bar above the list.
**2. Enter the date**
Enter the **Reached On** date. It can't be in the future. Add a **Note** if you'd like, for example where the date came from.

**3. Save**
Click **Record Milestone**. The payout is then earned on that date, as long as the hire and the referrer were both still employed on it.
If you selected payouts that aren't milestone installments or are already paid, the window tells you they won't change.
To fix a date, choose **Change Milestone Date** from the row menu. To remove it, open the same window and click **Clear Reached Date**. A reached date can't be cleared while the payout is in a payout batch that's waiting for payroll.
### Import milestone dates
To record many milestones at once, click **Actions**, then **Import Milestone Dates**, and upload a file with two columns: **Payout ID** and **Milestone Reached On**. Export your payouts (with the **Payout ID** column added) to get the IDs.
If any row can't be applied, nothing changes and the problem rows are listed so you can fix them and try again.
## Set when a payout is overdue
**1. Open Payout Settings**
On the **Payouts** tab, click **Actions**, then **Payout Settings**.
**2. Set Overdue After**
Enter a number of days from 0 to 365 in **Overdue After**. A payout that's still unpaid this many days after it was earned shows as **Overdue**.
**3. Save**
Click **Save**. The setting applies to your whole account.
> [!TIP]
>
> Set **Overdue After** to about one payroll cycle. Anything Overdue has then most likely been missed by payroll and is worth a look.
## FAQ
> [accordion] Why doesn't a referral have any payouts?
>
> Payouts are only created once the referred candidate is hired, and only when the referral has a reward, which comes from the reward program on its job req. Check the referral's **Reward Status** on the [Referrals page](/referrals/referrals-page).
> [accordion] A hire's start date changed. Do I need to update the payouts?
>
> No. Payouts that count days from the start date follow it automatically, unless they're already paid.
> [accordion] The referrer left the company. Do they still get paid?
>
> They're paid for any installment earned before they left. Installments earned after their exit date become Ineligible. If you decide to pay anyway, set those payouts to **Eligible** or **Paid**.
> [accordion] Why is the referrer's status Unknown?
>
> The referrer isn't linked to an employee record yet, so Journeyfront can't confirm their employment. Their payouts are still treated as owed. Link them on the [Referrers](/referrals/referrers) page to be sure.
> [accordion] Why are some totals shown with a plus sign?
>
> Amounts in different currencies are never added together. Each currency gets its own total, joined with a plus sign.
> [accordion] Can employees see payout notes?
>
> No. Notes are only for admins. Employees see their payout's status and a plain reason in the referral portal.
## Related
> [card] [Payout batches](/referrals/payout-batches)
>
> Send what's owed to payroll and record what was paid.
> [card] [Reward programs](/referrals/reward-programs)
>
> Set the amounts and installments a referral earns.
> [card] [Review, credit and Reward Status](/referrals/review-and-credit)
>
> Decide which referral gets the credit for a hire.
> [card] [Referrers](/referrals/referrers)
>
> Link referrers to their employee records.
# Permissions and portal admins
Source: https://help.journeyfront.com/referrals/permissions
Control who can view referrals, manage them, handle payouts and change settings, and limit admins to their own portals.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission edit security roles. Anyone with *Manage Referral Settings* can choose a portal's admins.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Referral data includes pay, so Journeyfront splits Referrals access into five permissions. You decide who can see referrals, who can change them, who handles payouts and who sets up programs and portals. You can also limit people to the referral portals they're responsible for, so a regional team only works with its own referrals and payouts.
## The Referrals permissions
Referrals permissions live in each security role, in the **Referrals** section. Go to **Settings**, then **Security**, and open a role. The section only appears when Referrals is turned on for your account. See [Security roles and permissions](/account-setup/security-roles).

| Permission | What it allows |
| - | - |
| **View Referrals** | See the **Referrals** section: the dashboard, referrals, referrers and reward programs. Also needed to pick a reward program on a job req. |
| **Manage Referrals** | Add and edit referrals and referrers, and change referral statuses. |
| **Manage Referral Payouts** | View payouts and payout amounts, run payout batches for payroll, record what payroll paid and change payout statuses. It's needed everywhere pay data shows: the **Payouts** and **Payout Batches** tabs, the paid, owed and upcoming amounts on the **Referrals** and **Referrers** tabs and in their exports, a referral's payouts and the dashboard's payout amounts. |
| **Manage Referral Settings** | Create and edit reward programs, and create and set up referral portals under **Settings**, then **Referral Portals**. |
| **All Referral Portals Access** | Work with every referral portal. When it's off, the person only works with the portals they're an admin of. See [Limit someone to certain portals](#limit-someone-to-certain-portals). |
> [!TIP]
>
> Keep **Manage Referral Payouts** to the few people who should see what employees are paid. With **View Referrals** alone, people see each referral's **Reward**, **Reward Program** and **Reward Status** (what the program promises and how it turned out), but not the amounts paid, owed or upcoming. Recruiters can review and credit referrals with **Manage Referrals** without seeing pay data or sending it to payroll.
### Defaults
* **Existing roles** have **View Referrals**, **Manage Referrals** and **All Referral Portals Access** turned on. Roles with *Company Settings Access* also have **Manage Referral Payouts** and **Manage Referral Settings**.
* **New roles** start with the Referrals permissions turned off, except **All Referral Portals Access**, which is on. Turn on what the role needs before you save.
### What people without a permission see
Journeyfront hides what a role doesn't allow:
* Without **View Referrals**, the **Referrals** menu item and the job req **Reward Program** setting don't appear.
* Without **Manage Referral Payouts**, the **Payouts** and **Payout Batches** tabs don't appear and the dashboard leaves out payout amounts. The **Referrals** tab has no **Paid**, **Owed**, **Upcoming** or **Next Earned On** columns. The **Referrers** tab has no **Paid**, **Owed**, **Overdue** or **Upcoming** columns and no **Overdue Payouts** filter, and a referrer's **Rewards** card shows only **Referrals** and **Hires**. Exports leave those columns out, and you can't sort by them.
* Without **Manage Referral Settings**, there's no **New Reward Program** button, no menu on reward program cards, and no **Referral Portals** page in Settings.
## Limit someone to certain portals
If your company runs several referral portals, for example one per region, you can give each portal its own admins. A portal admin only sees and changes that portal's data.
**1. Turn off All Referral Portals Access**
In the person's security role, turn off **All Referral Portals Access** and click **Save**. Leave on the other Referrals permissions they need.
**2. Open the portal**
Go to **Settings**, then **Referral Portals**, and open the portal.
**3. Add them as an admin**
On the **General** tab, add the person under **Admins**, then click **Save**. Only people whose role has **View Referrals** appear in the list.

People whose role has **All Referral Portals Access** already manage every portal. Adding them as a portal admin changes nothing for them.
> [!TIP]
>
> Their role still decides what portal admins can do. The portal list only decides where they can do it. A portal admin with **View Referrals** alone can see their portal's referrals but not change them.
### What a portal admin sees
| Area | What they work with |
| - | - |
| **Referrals** | Referrals that belong to their portals. |
| **Payouts** and **Payout Batches** | Payouts from those referrals. |
| **Referrers** | Referrers who referred through their portals, plus referrers with no referrals yet. |
| **Reward Programs** | Programs on their portals or on all portals. They can only change programs that are only on their portals. A program shared with other portals shows a lock icon. New programs they create must be for their own portals. |
| **Dashboard** | Numbers for their portals only. |
| **Referral Portals** settings | Only their portals. A portal they create lists them as an admin automatically. |
| **Job reqs** | When adding a referral, only job reqs posted on their portals or on all portals. |
Anything outside their portals behaves as if it doesn't exist for them. Account-wide settings, such as when an earned payout counts as overdue, can only be changed by someone with **Manage Referral Settings** and **All Referral Portals Access**.
## How a referral gets its portal
Every referral belongs to exactly one portal, and its payouts belong to the same portal. That's what decides which portal admins see it.
| How the referral starts | Its portal |
| - | - |
| Submitted on a referral portal | That portal |
| Through a referral link | The portal the link was made from |
| For a job req posted on exactly one portal | That portal |
| Added by your team, for a job req on several portals, or with no job req | You choose the portal in **Referral Portal** when you add it |
| Any other way | Your account's first active portal |
In bulk uploads, if some job reqs are on several portals, you choose one **Referral Portal** for those rows. See [The Referrals page](/referrals/referrals-page).
### Move a referral to another portal
Open the referral, click **Edit**, and choose a new **Referral Portal**. The picker only appears if you can manage referrals and there's more than one portal to choose from. A portal admin can only move referrals between portals they manage. The referral's payouts move with it, and the change is recorded in its history. See [Referral details and milestones](/referrals/referral-details).
## FAQ
> [accordion] Someone can't see the Payouts tab. Why?
>
> Their role doesn't have **Manage Referral Payouts**. Turn it on in their security role if they should see pay data.
> [accordion] Why can't I find the Referrals permissions on the Security page?
>
> The **Referrals** section only appears when Referrals is turned on for your account. Ask your Customer Success Manager.
> [accordion] A portal admin sees no referrals at all. What's wrong?
>
> Their role has **All Referral Portals Access** turned off, but they aren't listed as an admin on any portal yet. Add them under **Admins** on a portal's **General** tab.
> [accordion] Why can't someone be added as a portal admin?
>
> Only people whose role has **View Referrals** appear in the **Admins** list. Turn it on in their role first.
> [accordion] Why is there a lock on a reward program?
>
> The program is shared with portals you don't manage. Only someone who manages all of its portals can change it.
> [accordion] Can someone set up portals without full Company Settings access?
>
> Yes. **Manage Referral Settings** is enough to reach **Settings**, then **Referral Portals**, and to create and change reward programs.
## Related
> [card] [Security roles and permissions](/account-setup/security-roles)
>
> Create roles and turn permissions on or off.
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Create a portal and choose its admins.
> [card] [Reward programs](/referrals/reward-programs)
>
> What a referral pays, and on which portals.
> [card] [How referrals work](/referrals/overview)
>
> The big picture and a setup checklist.
# Employee sign-in and access
Source: https://help.journeyfront.com/referrals/portal-access
Decide who can sign in to a portal, what they see, and what happens when someone leaves.
> [!NOTE]
>
> **Who can do this:** People whose security role has *Manage Referral Settings*. Without *All Referral Portals Access*, you can only change the portals you're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Signing in lets employees track every person they referred, follow their payouts and share their own referral link. You decide whether a portal uses sign-in at all, who can get in, and what happens when someone leaves the company. Access follows your employee records, so new hires, transfers and departures take effect on their own.
You'll find these settings in **Settings**, then **Referral Portals**. Open a portal and click **Employee Access**. Click **Save** when you're done, except for the **Specific People** list, which saves right away.
## Choose who can use the portal

Under **Who Can Use It**, pick one of three options:
| Option | What it means |
| - | - |
| **Public** | Anyone with the link can refer. No one signs in. |
| **Public, Sign-In Optional** | Anyone can refer. Employees can sign in to track their referrals and payouts. |
| **Sign-In Required** | Only employees who can sign in can see the portal and refer. Everyone else lands on the sign-in page. |
The other settings on this page only appear when the portal uses sign-in.
> [!TIP]
>
> Choose **Public, Sign-In Optional** when you also want referrals from people outside your company, such as friends of employees or partners. Choose **Sign-In Required** when only your own staff should refer and every referral should be tied to a known employee.
## Who can sign in
When someone tries to sign in, Journeyfront checks these rules in order:
1. **Specific People** comes first. A person you **Block** can't sign in, and a person you **Allow** can, whatever the other rules say.
2. **Active employees** can sign in. That's anyone with an employee record in your account that has no turnover date.
3. **Former employees** follow your **When an Employee Leaves** setting.
4. **People with no employee record** can sign in when their email is on one of your **Allowed Email Domains**.
Journeyfront matches the email they sign in with against the primary and secondary email on their record. The rules are checked again every time they use the portal, not just when they sign in, so a transfer, a departure or a change you make applies on their next visit.
### Allowed Email Domains
Every active employee can already sign in. Add your company's email domains to also let in people who don't have an employee record yet, such as new hires before your HR system sync runs. Type a domain and press **Enter** or a comma to add it. Subdomains are included, so `example.com` also covers `west.example.com`.
> [!TIP]
>
> Only list domains your company controls. Anyone with an address on an allowed domain can sign in, even without an employee record.
### Other settings
| Setting | What it does |
| - | - |
| **Referral Status Shown** | **Full Application Status** shows employees where each referral is in your hiring process. **Accepted and Joined Only** shows only whether the referral was accepted and whether the person was hired, for regions that keep candidate progress private. |
| **Leaderboard** | Signed-in employees see this portal's top referrers, ranked by hires for this month, quarter, year or all time, and their own rank. |
| **Profile Photos** | Employees can add a photo in their portal **Settings**, and coworkers see it on the leaderboard. Turn it off to hide every photo on this portal. |
## When an employee leaves

Under **Access After Turnover**, choose what happens once a person's employee records all have a turnover date:
| Option | What happens |
| - | - |
| **Keep Their Payouts Visible for a While** | For the number of days you enter in **For How Many Days** (1 to 365) after their turnover date, they can sign in to see their payouts only. They can't refer anyone new. |
| **End Access on Their Turnover Date** | They lose access to the portal once their employee record has a turnover date. |
While a former employee has payouts-only access, the portal shows them just their **Payouts** and **Settings**, and they only get payout emails.
> [!TIP]
>
> Keeping payouts visible for a while cuts down on "was I paid?" questions to your team. Match the number of days to how long your last installments can take to pay out after someone leaves.
## Allow or block specific people
Use **Specific People** for anyone the rules above miss, like an outside referrer or a contractor, or to block someone they would let in.
**1. Enter their email**
Under **Add Person**, type the person's email address.
**2. Choose Allow or Block**
Pick **Allow** or **Block** and click **Add**. The person appears in the list with an **Allowed** or **Blocked** chip.
Changes in this list save right away. Click the trash icon to remove someone, and they go back to following the portal's rules. Adding someone who is already on the list changes them between **Allow** and **Block**.
## How employees sign in
Employees sign in with their work email. There's no password to remember.
**1. Enter a work email**
On the portal, the employee clicks **Sign In**, enters their **Work Email** and clicks **Send Code**. On a **Sign-In Required** portal, the sign-in page is the first thing they see.
**2. Get the code**
If that email can sign in to the portal, Journeyfront emails a 6-digit code and a sign-in link. Both expire in 15 minutes. The page says the same thing whether or not the email can sign in, so no one can use it to find out who works for you.
**3. Enter the code or click the link**
The employee types the code and clicks **Sign In**, or clicks the link in the email. **Use a Different Email** starts over.

After signing in, employees stay signed in on that device for up to 30 days. One sign-in covers every sign-in portal in your account that they can use, and they can move between them with **Switch Portal** in their menu.
Signing in to the portal doesn't give anyone access to Journeyfront itself. Someone who signs in through an allowed domain or an **Allow** entry gets a portal-only account with no password and no security role.
## FAQ
> [accordion] An employee says they never got a code. What should I check?
>
> Make sure they have an employee record with no turnover date, or that their email is on one of your **Allowed Email Domains**, and that they aren't on the **Specific People** list as **Blocked**. Also check that the portal is **Active** and not set to **Public**. If they still can't get in, add their email under **Specific People** with **Allow**.
> [accordion] What happens if someone types the wrong code?
>
> After 5 wrong tries, that code stops working and they need to request a new one. A new code can be requested any time from the sign-in page.
> [accordion] Do I need to remove employees who leave?
>
> No. When their employee record gets a turnover date, the portal follows your **Access After Turnover** setting on their next visit.
> [accordion] Can someone outside the company sign in?
>
> Yes, if you add their email under **Specific People** with **Allow**. On a **Public, Sign-In Optional** portal, anyone can also refer without signing in.
> [accordion] Do employees on a public portal get emails?
>
> No. Portal emails go to people who can sign in to the portal. See [Featured items and email notifications](/referrals/featured-and-notifications).
> [accordion] What does Accepted and Joined Only hide?
>
> Employees don't see interview stages or other steps in your hiring process. They only see whether the referral was accepted and whether the person was hired.
## Related
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Create a portal, brand it and share its link.
> [card] [Using the referral portal](/referrals/employee-portal)
>
> What employees see once they sign in.
> [card] [Permissions and portal admins](/referrals/permissions)
>
> Who can change portal settings.
> [card] [Employee records](/employees/employee-records)
>
> The records and turnover dates portal access follows.
# Set up a referral portal
Source: https://help.journeyfront.com/referrals/portal-setup
Create a branded portal where employees refer people and share jobs, and get its link and QR code.
> [!NOTE]
>
> **Who can do this:** People whose security role has *Manage Referral Settings*. Without *All Referral Portals Access*, you only see and edit the portals you're an admin of.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
A referral portal is the page your employees use to refer people to your open jobs. Each portal has its own name, branding, sign-in rules, referral form and admins, so you can run one portal for the whole company or a separate one for each site or region.
This page covers creating a portal and its **General**, **Branding** and **Referral Form** settings. Sign-in is covered in [Employee sign-in and access](/referrals/portal-access), and the **Notifications** and **Featured** sections in [Featured items and email notifications](/referrals/featured-and-notifications).
## Create a portal
**1. Open Referral Portals**
Go to **Settings**, then **Referral Portals**. The list shows each portal's **Name**, **Status** (Active or Inactive), **Access**, **Admins** and **Last Updated**.

**2. Name the portal**
Click **New Referral Portal**, enter a **Name** and click **Create Referral Portal**. The portal opens in its editor.
**3. Work through the sections**
The editor lists its sections on the left: **General**, **Branding**, **Employee Access**, **Referral Form**, **Notifications** and **Featured**. Make your changes and click **Save** at the top. **Save** and **Cancel** appear as soon as something changes, and **Cancel** puts back the last saved version.
> [!TIP]
>
> You can switch between sections before saving. One **Save** keeps the changes from every section. If you try to leave the editor with unsaved changes, Journeyfront asks whether to **Save and Leave** or **Discard Changes**.
To edit a portal later, click its row. The menu at the end of each row also has **Edit Referral Portal**, **View Live Page** and **Delete Referral Portal**.
## General

| Setting | What it does |
| - | - |
| **Active** | Turns the portal on or off. Visitors can't use an inactive portal, and no one can sign in to it. |
| **Name** | The portal's name, shown to employees on the portal and in its emails. Required. |
| **Company Website** | Shown as a link at the bottom of the portal's menu. Leave it blank to hide the link. |
| **Admins** | The people who manage this portal's referrals, payouts, reward programs and settings. You can pick anyone whose role can view Referrals. |
| **Referral Source** | The source given to candidates created through this portal. **Default (Referral)** unless you pick another enabled source. |
| **Link Job Boards** | Which job boards (and their postings) employees can make referral links to from this portal: **All Job Boards** or **Specific Job Boards**. |
People whose role has **All Referral Portals Access** already manage every portal, so you only need to list admins who are limited to certain portals. See [Permissions and portal admins](/referrals/permissions).
> [!TIP]
>
> Give each portal its own **Referral Source** when you run several portals. You can then compare where referred candidates came from in your source reporting.
The jobs a portal shows are your active job reqs that are set to show on all portals or on this one. You choose that on each job req. See [Rewards on job reqs](/referrals/job-req-rewards).
## Share the portal
The **Sharing** card at the bottom of **General** gives you three ways to send people to the portal.

| Option | How to use it |
| - | - |
| **Referral Portal Link** | Copy the link to send in an email or chat. **View Live Page** opens the portal in a new tab. |
| **Intranet Button** | A **Refer a Friend** button in your brand color. Copy its code and paste it into your intranet or another web page. It opens the portal in a new tab. |
| **QR Code** | For posters and flyers. Scanning it opens the portal. Use **Download PNG** to save it or **Copy QR** to paste it into a document. |
The live page always shows the last saved version. While you have unsaved changes, **View Live Page** reminds you of that.
## Branding
Branding is a few simple choices. The portal's layout, fonts and spacing are already designed for you.
| Setting | What it does |
| - | - |
| **Logo** | Shown at the top of the portal's menu (the top bar on phones) and on its sign-in page. A wide image on a transparent background works best. |
| **Icon** | A square version of your logo for the collapsed menu and the browser tab. At least 128×128px. |
| **Brand Color** | Buttons and links use this color. Very light colors are darkened so text stays readable. |
Click **Upload Logo** or **Upload Icon** to add an image, **Replace Logo** or **Replace Icon** to change it, or the trash icon to remove it. The brand color is also used on the **Refer a Friend** intranet button and in the portal's emails.
> [!TIP]
>
> Upload an icon even if you have a logo. Without one, the collapsed menu shows your company's initials instead.
## Referral Form
These settings shape the form employees fill in when they refer someone.

| Setting | What it does |
| - | - |
| **Require Candidate Phone** | Makes the candidate's phone number required instead of optional. |
| **Allow General Referrals** | Lets employees refer someone without choosing a specific job req. The candidate isn't contacted. The referral is recorded for your recruiters. |
| **Show Rewards** | Shows what each job req's reward program pays next to the job req. When it's off, the portal's **Rewards** page is hidden too. |
| **Country**, **Region/State**, **City** | Set each to **Hidden**, **Optional** or **Required**. Region/State options load from the chosen country, so it can't be more required than **Country**. |
| **Require Consent** | Employees must tick a box confirming they have the candidate's permission before they submit. |
| **Consent Text** | The statement they agree to. It appears when **Require Consent** is on. |
> [!TIP]
>
> Turn on **Require Consent** with text in your own words, especially where privacy rules apply. It gives you a record that every referred person agreed to be contacted.
## Run several portals
Create one portal per site, region or workforce when each needs its own look, sign-in rules or admins. For example, "Acme Careers" can require sign-in for your US staff while "Acme West" stays public.
Each portal shows the job reqs set to show on it, and each reward program can belong to all portals or to specific ones (see [Reward programs](/referrals/reward-programs)). Portal admins only see the referrals, payouts and settings of their own portals.
## Delete a portal
Open the menu on the portal's row and click **Delete Referral Portal**, then **Delete**. This can't be undone. The portal's link stops working.
> [!TIP]
>
> To take a portal down for a while, turn off **Active** instead of deleting it. Its settings stay ready for when you turn it back on.
## FAQ
> [accordion] Can I embed the portal in our intranet?
>
> Use the **Intranet Button** on the **Sharing** card. Paste its code into your intranet page and it opens the portal in a new tab.
> [accordion] Why doesn't a job show on the portal?
>
> A portal only shows active job reqs that are set to show on all portals or on that portal. Check the job req's referral settings. See [Rewards on job reqs](/referrals/job-req-rewards).
> [accordion] Why is Save grayed out?
>
> Something needs fixing first. Hover over **Save** to see what, for example a missing name on the **General** section.
> [accordion] Who can I make a portal admin?
>
> Anyone in your account whose security role can view Referrals. Admins without **All Referral Portals Access** work only with the portals they're listed on.
> [accordion] I created a portal but I'm not on the Admins list. Will I lose access?
>
> No. If your role is limited to certain portals, Journeyfront adds you as an admin of any portal you create.
> [accordion] Do my Featured changes need Save?
>
> No. Featured items save as soon as you make each change. Everything else in the editor saves with **Save**.
## Related
> [card] [Employee sign-in and access](/referrals/portal-access)
>
> Who can sign in, what they see and what happens when someone leaves.
> [card] [Featured items and email notifications](/referrals/featured-and-notifications)
>
> Promote jobs and news, and choose which emails employees get.
> [card] [Permissions and portal admins](/referrals/permissions)
>
> The referral permissions and how portal admins work.
> [card] [Using the referral portal](/referrals/employee-portal)
>
> What your employees see and do on the portal.
# Referral details and milestones
Source: https://help.journeyfront.com/referrals/referral-details
Open a referral to see its people, status, portal and reward, and record when a hire reaches a milestone.
> [!NOTE]
>
> **Who can do this:** *View Referrals* to open a referral. *Manage Referrals* to edit it or change its status. *Manage Referral Payouts* to see its payouts and record milestones.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Every referral has a details panel that brings together the candidate, the referrer, where the referral came from and what it pays. Once the candidate is hired, it also shows each payout and lets you record milestones like training completed, so the right reward is earned on the right day.
## Open a referral
On the **Referrals** tab, click the candidate's name, or open the row's menu and click **View Details**. The referral opens in a panel on the right. Click the **X** or press Esc to close it.

## The header
* **The candidate's name and status chip.** With **Manage Referrals**, click the chip to change the status. It saves right away. See [Review, credit and Reward Status](/referrals/review-and-credit).
* **Referred by** the referrer, **for** the job req, or **General Referral**.
* **Edit**, **Candidate Profile** and **Application**. Candidate Profile and Application open in a new tab.
If the referral is **Needs Review**, a box under the header lists why and lets you decide. For a duplicate, it links to the referral that has the credit, so you can open it and compare. See [Review a flagged referral](/referrals/review-and-credit#review-a-flagged-referral).
## What each card shows
| Card | What it shows |
| - | - |
| **Referral Details** | **Job Req**, **Origin**, **Referral Portal**, **Application Status**, **Referred Date**, **Applied Date**, **Referral Code** (click to copy) and **Added By** (who added the referral; edits and status changes don't change it). Once the candidate is hired and has an employee record, it adds **Employment** (**Active** or **Exited**), **Employee Job Title**, **Job Profile**, **Start Date**, **Turnover Date**, **Tenure** and **Separation Reason**. |
| **Candidate** | The candidate's **Email**, **Phone** and **Location**. |
| **Referrer** | The referrer's **Name**, **Email** and **User ID**. The name links to their Candidate Profile when they're linked to an employee record. |
| **Reward** | The reward program, its total and its schedule or payouts. See below. |
| **Application & Note** | The **Associated Application** the referral is linked to, and the **Note**. |
Employment details come from the hire's employee record. See [Employee records](/employees/employee-records).
## The Reward card
The **Reward** card follows the referral from promise to payment.
**Before the hire**, it shows the **Reward Program**, the **Total** and the schedule copied onto the referral when it was made, for example **\$200 after 90 days**.

**After the hire**, people with **Manage Referral Payouts** see the payouts instead, one row per installment:
| Column | What it shows |
| - | - |
| **Installment** | The installment's name, and under it when it's due, for example **After 90 days** or **At Training Completed**. |
| **Amount** | What the installment pays. |
| **Earned On** | The date the installment is earned: the hire's start date plus its days, or the day its milestone was reached. A milestone not reached yet shows **Mark Reached**, or **Not reached** when the payout is already paid or ineligible. |
| **Status** | **Upcoming**, **Earned**, **Overdue**, **Paid** or **Ineligible**. Hover an **Ineligible** chip to see why. |
Click **View in Payouts** to see the same payouts on the **Payouts** tab. See [Payouts](/referrals/payouts).
People without **Manage Referral Payouts** keep seeing the reward schedule, not the payouts.
> [!TIP]
>
> The reward is copied onto the referral when it's made, so changing a reward program later doesn't change what existing referrals promise. Only edit a referral's **Reward Program** when you mean to apply the program's current terms.
## Record a milestone
Some installments are earned at a milestone, like **Training Completed**, instead of after a number of days. Journeyfront doesn't know when the hire reached it, so someone with **Manage Referral Payouts** records the day.
**1. Find the installment**
Open the referral. In the **Reward** card, find the installment that shows **Mark Reached** under **Earned On**.

**2. Click Mark Reached**
The **Record Milestone** window shows the **Milestone**, the installment's **Label** when it has its own name, the **Amount** and the **Hire**.
**3. Enter the date**
Enter **Reached On**, the day the hire reached the milestone. It can't be in the future. Add a **Note** for other admins if you'd like, such as where the date came from. Employees never see notes.

**4. Save**
Click **Record Milestone**. The installment is earned on that date, as long as the hire and the referrer were both still employed.
**Mark Reached** only shows on installments that can still pay. To change or clear a date you already recorded, use the **Payouts** tab: open the payout's menu, click **Change Milestone Date**, then change the date or click **Clear Reached Date**. You can also record many milestones at once there. See [Payouts](/referrals/payouts).
## Edit a referral
With **Manage Referrals**, click **Edit**. You can change:
* The referrer's **First Name**, **Last Name** and **Email**.
* The **Reward Program**. Changing it applies the reward program's current terms. Draft programs aren't offered, and archived programs show **(Archived)**.
* The **Referral Portal**, if you work with more than one. The referral's payouts move with it.
* The **Associated Application** and the **Note**.
Click **Save**. If you close the panel or click **Cancel** with changes, Journeyfront asks before discarding them.
Once the candidate is hired and payouts are scheduled, the reward program can't change. Once any payout is paid, the associated application can't change either.
To delete a referral, use the row's menu on the **Referrals** tab. See [Row actions](/referrals/referrals-page#row-actions).
## FAQ
> [accordion] Why don't I see payouts on a hired referral?
>
> Payouts are pay data, so they only show with **Manage Referral Payouts**. Without it, you see the reward schedule.
> [accordion] Why is the Reward Program box grayed out?
>
> Payouts are already scheduled from that program, so it can no longer change. Hover the box to see the reason.
> [accordion] What if the hire left before the milestone?
>
> The installment is only earned if both the hire and the referrer were still employed on the **Reached On** date. Otherwise it becomes **Ineligible**.
> [accordion] I recorded the wrong milestone date. How do I fix it?
>
> Go to the **Payouts** tab, open that payout's menu and click **Change Milestone Date**. Change the date, or click **Clear Reached Date**.
> [accordion] Where does the Employment information come from?
>
> From the hire's employee record in Journeyfront, which your HR system can keep up to date. If the hire has no employee record yet, those rows don't show.
> [accordion] Can I move a referral to a different portal?
>
> Yes, if you work with more than one referral portal. Click **Edit**, choose the **Referral Portal** and save. Its payouts move with it.
## Related
> [card] [Review, credit and Reward Status](/referrals/review-and-credit)
>
> Decide which referrals count.
> [card] [Payouts](/referrals/payouts)
>
> Every installment across all referrals.
> [card] [Reward programs](/referrals/reward-programs)
>
> Set up rewards, installments and milestones.
> [card] [The Referrals page](/referrals/referrals-page)
>
> Find and manage every referral.
# The Referrals page
Source: https://help.journeyfront.com/referrals/referrals-page
Find, filter and manage every referral, add referrals one at a time or in bulk, and export.
> [!NOTE]
>
> **Who can do this:** *View Referrals* to see the page. *Manage Referrals* to add, edit, delete and change the status of referrals.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
The **Referrals** page is your list of every referral: who referred whom, for which job req, whether it counts, and what it has paid. From here you can add referrals yourself, add a whole batch at once, change statuses in bulk and export the list.
To get there, click **Referrals** in the top navigation, then the **Referrals** tab.

## What each column shows
These are the default columns:
| Column | What it shows |
| - | - |
| **Candidate Name** | The person who was referred. Click the name to open the referral's details. |
| **Referrer Name** | The employee who made the referral. |
| **Referrer User ID** | The User ID of the employee record the referrer is linked to. Blank when they aren't linked to one. Click to copy. |
| **Job Req** | The job req the referral is for. Referrals that aren't for a specific job show **General Referral**. |
| **Status** | Whether the referral counts: **Needs Review**, **Active** or **Denied**. With **Manage Referrals**, click the chip to change it. Hover a **Needs Review** chip to see why it was flagged. |
| **Reward** | The total reward for the referral, from its reward program. |
| **Reward Status** | What the referral has paid so far, worked out from its payouts. See [Reward Status](/referrals/review-and-credit#reward-status). |
| **Application Status** | Where the candidate's application stands. |
| **Referred Date** | When the referral was made. |
Click **Edit Columns** to add more. The extra columns are grouped the same way as the filters:
* **Default Fields:** **Referrer Email**, **Candidate Email**, **Note**, **Origin**, **Referral Portal**, **Applied Date**, **Added By** and **Referral Code**.
* **Candidate Location:** **Candidate Country**, **Candidate Region/State** and **Candidate City**.
* **Reward & Payout:** **Reward Program**, **Paid**, **Owed**, **Upcoming**, **Next Earned On** and **Rewarded Date**. **Paid**, **Owed**, **Upcoming** and **Next Earned On** are pay data, so they're only listed for people who also have **Manage Referral Payouts**.
* **Employment:** the hire's **Start Date**, **Turnover Date**, **Employee Job Title**, **Job Profile**, **Tenure** and **Separation Reason**, from their employee record.
* **Job Location:** **Job Req Country**, **Job Req Region/State** and **Job Req City**.
**Added By** always shows who added the referral. Editing a referral or changing its status doesn't change it. Who made each change is in the candidate's history, on the Candidate Application's **Comments & Activities** tab.
> [!TIP]
>
> Everyone with **View Referrals** sees **Reward**, **Reward Program** and **Reward Status**, since those are the program's terms and the outcome, not amounts paid. Give **Manage Referral Payouts** only to the people who should see what employees are paid and owed.
The **Origin** column tells you how a referral came in:
| Origin | Meaning |
| - | - |
| **Referral Portal** | An employee submitted it on a referral portal. |
| **Referral Link** | A candidate applied through an employee's referral link. |
| **Manually Added** | Someone on your team added it on this page or on a candidate's record. |
| **API** | It came in through the Journeyfront API. |
## Search, filter and save views
* **Search** by referrer, candidate, email or User ID.
* Click **Filters** to filter by **Status**, **Job Req**, **Application Status**, **Origin** and **Referral Portal**. Add more filters for the referred date, **Reward Status**, **Added By**, candidate and job req location, reward amount, currency and program, **Payout Status**, **Rewarded Date**, the hire's **Employment Status** and their **Start Date**.
* Click **Save as New View** to keep your columns and filters as a tab of your own. On a view you made, **Save Changes** updates it and **Remove Changes** puts it back the way it was saved.
> [!TIP]
>
> Save a view filtered to **Status** is **Needs Review**. It gives you a short daily queue of referrals waiting on a decision.
Click **Export** to download the list with the columns and filters you have on screen. Without **Manage Referral Payouts**, the export leaves out the **Paid**, **Owed**, **Upcoming** and **Next Earned On** columns, and you can't sort by them.
## Add a referral
Use this when an employee tells you about someone in person, by email or anywhere outside the referral portal.
**1. Open New Referral**
On the **Referrals** tab, click **New Referral**.
**2. Enter the referrer**
Under **Referrer**, enter their **First Name**, **Last Name** and **Email**. Journeyfront matches the referrer to their employee record so their payouts follow their employment.
**3. Enter the candidate**
Under **Candidate**, enter their **First Name**, **Last Name** and **Email**. **Phone**, **Country**, **Region/State** and **City** are optional and are saved to the candidate's profile. If the email matches someone already in Journeyfront, the referral is added to that person.
**4. Choose the job req**
Under **Referral**, pick the **Job Req**, or check **General Referral** to refer the candidate without choosing a specific job req. For a job req, Journeyfront also creates the candidate's application for that job.
If the job req is on more than one of your referral portals, or it's a general referral and you have more than one portal, choose the **Referral Portal**. The referral, and its payouts, belong to the portal you pick.
**5. Add a note and invitation**
Add a **Note** if you'd like. For a job req referral, check **Email the candidate a link to apply** to send the candidate an invitation email with a link to begin their application.

**6. Create the referral**
Click **Create Referral**.
If the candidate already has an application for that job req, or has already been referred, Journeyfront warns you first. Click **Create Referral Anyway** to add it, or **Go Back** to change it.
> [!TIP]
>
> Leave the invitation box unchecked when the candidate has already applied or you plan to reach out yourself. The person adding the referral usually isn't the person who knows the candidate, so a personal note from the referrer often lands better.
A new referral that looks like a duplicate, a past applicant or a self-referral is flagged **Needs Review** automatically. See [Review, credit and Reward Status](/referrals/review-and-credit).
## Add referrals in bulk
Use this to catch up on a stack of referrals, for example from a hiring event or a spreadsheet you kept before.
**1. Open Add Referrals**
On the **Referrals** tab, click **Actions**, then **Add Referrals in Bulk**.
**2. Choose how to add them**
Under **Add referrals by**, choose one:
* **Enter Them:** type one referrer, then each person they referred under **People They Referred**. Click **Add Person** for each new row. Leave a row's **Job Req** on **General Referral** for a general referral.
* **Upload a File:** upload a CSV or Excel file (up to 10 MB) with one referral per row. Identify the job req by its exact title in **Job Req**, or by **Job ID**.
**3. Check the referrals**
Click **Check Referrals**. Nothing is added yet. Journeyfront shows each row with its result:
* **Ready:** the row will be added.
* **Warnings** in amber, such as **Already has an application for this job req** or **Already referred by** another employee. The row is still added, so decide whether you want it before you continue.
* **Errors** in red, such as a missing email or a job req that matches several reqs. These rows are skipped.
If some job reqs are on more than one of your referral portals, choose the **Referral Portal** for the upload.

**4. Add them**
Check **Email each candidate their job invitation** if you want to send invitations. Only referrals to a specific job req get one. Then click **Add** (for example **Add 3 Referrals**). Click **Back** to fix the rows first.
The upload file takes these columns:
| Column | Required |
| - | - |
| Referrer First Name, Referrer Last Name, Referrer Email | Yes |
| Candidate First Name, Candidate Last Name, Candidate Email | Yes |
| Referrer User ID | No. Links the referrer to that person's employee record. |
| Candidate Phone | No |
| Job Req or Job ID | No. Leave both blank for a general referral. |
| Note | No |
## Change many statuses at once
With **Manage Referrals**, check the boxes next to the referrals you want, then click **Change Status** in the bar above the list. Choose **Active** or **Denied** and click **Change Status**.
Denying referrals works the same as denying one at a time: their unpaid payouts become ineligible and each referrer is told. See [Review, credit and Reward Status](/referrals/review-and-credit).
## Row actions
Click the menu at the start of a row for:
* **View Details** or **Edit** to open the referral. See [Referral details and milestones](/referrals/referral-details).
* **View Candidate Profile** and **View Application**, which open in a new tab.
* **Delete** to remove the referral. This can't be undone, and a referral with paid payouts can't be deleted.
## Referrals on a candidate's record
Referrals also show in the **Referrals** card on the Candidate Profile and on the **Details** tab of the Candidate Application. Each one shows who referred the candidate, the job req, how it came in and its status.
From the card you can change the status, edit the referrer and note, link the referral to one of the candidate's applications with **Associated Application**, or delete it. To add one, click **New Referral** on the Candidate Profile or **Add** on the Candidate Application.
## FAQ
> [accordion] Why can't I see the New Referral button or change statuses?
>
> Those need the **Manage Referrals** permission. With only **View Referrals**, you can see and export the list but not change it. See [Permissions and portal admins](/referrals/permissions).
> [accordion] Why do I only see some referrals?
>
> If your security role doesn't have **All Referral Portals Access**, you only see referrals from the referral portals you're an admin of.
> [accordion] Which job reqs can I pick in New Referral?
>
> Active job reqs. If the job you need isn't listed, choose **General Referral** or check the job req's status.
> [accordion] What happens if I add a referral for someone who already applied?
>
> Journeyfront warns you first. If you add it anyway, the referral is linked to their existing application, and it's flagged **Needs Review** because the person applied before the referral. You then decide whether it counts.
> [accordion] Does a bulk upload stop if one row has a problem?
>
> No. Rows with errors are skipped and the rest are added. Rows with warnings are added too, so check them on the results screen before you click **Add**.
> [accordion] Why is the Reward column blank on some referrals?
>
> The referral has no reward program, usually because it's a general referral or its job req doesn't offer a reward. Its **Reward Status** shows **No Reward**.
> [accordion] Can I undo a delete?
>
> No. Deleting a referral removes it for good. To stop a referral from paying without losing its history, set its status to **Denied** instead.
## Related
> [card] [Review, credit and Reward Status](/referrals/review-and-credit)
>
> Decide which referrals count and see what each has paid.
> [card] [Referral details and milestones](/referrals/referral-details)
>
> Open a referral to see its reward and record milestones.
> [card] [Referrers](/referrals/referrers)
>
> See every employee who refers and what they've earned.
> [card] [Rewards on job reqs](/referrals/job-req-rewards)
>
> Choose which reward a job req's referrals earn.
# Referrers
Source: https://help.journeyfront.com/referrals/referrers
See every employee who refers, whether they still work here, and what they have earned.
> [!NOTE]
>
> **Who can do this:** *View Referrals* to see referrers. *Manage Referrals* to add, edit and upload referrers and remove portal photos. *Manage Referral Payouts* to see a referrer's payouts and pay amounts.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
The **Referrers** tab lists everyone who has referred someone to your company, with their employment status and what they've been paid and are owed. Journeyfront links each referrer to their employee record, so their rewards follow their real employment without anyone keeping a separate list.
To get there, click **Referrals** in the top navigation, then the **Referrers** tab. Everyone who refers someone appears here automatically.

## What each column shows
| Column | What it shows |
| - | - |
| **Referrer** | The referrer's name. Click it to open their details. |
| **Email** | The referrer's email. |
| **User ID** | The User ID of the employee record they're linked to. Blank when they aren't linked. Click to copy. |
| **Referrer Status** | **Active**, **Exited** or **Unknown**. See below. |
| **Start Date** | Their start date, from their employee record. |
| **Referrals** | How many people they've referred. |
| **Hires** | How many of those were hired. |
| **Paid** | What they've been paid. |
| **Owed** | Earned and overdue payouts not yet paid. |
| **Overdue** | The part of **Owed** that has waited longer than your overdue setting. |
| **Upcoming** | Payouts scheduled but not earned yet. |
**Paid**, **Owed**, **Overdue** and **Upcoming** are pay data, so they only show for people who also have **Manage Referral Payouts**. Without it, they aren't in the list or **Edit Columns**, the export leaves them out and you can't sort by them.
Amounts in different currencies are never added together. A referrer paid in two currencies shows both, for example **CA\$250 + \$200**.
Click **Edit Columns** to add **Turnover Date**, **Employee Record** (**Linked** or **Not Linked**), **Last Referral** and **Note**.
## Search, filter and export
* **Search** by name, email or User ID.
* Click **Filters** to filter by **Referrer Status**, **Employee Record** and, with **Manage Referral Payouts**, **Overdue Payouts** (**Has Overdue Payouts**). Add filters for **Start Date** and **Turnover Date** too.
* Click **Save as New View** to keep your columns and filters as your own tab.
* Click **Export** to download the list as you see it.
> [!TIP]
>
> Filter to **Overdue Payouts** to find the employees who've waited too long to be paid. Then open **View Payouts** from their row to see exactly which installments are late.
## Referrer Status and the employee record
A referrer's status comes from the employee record they're linked to, so it changes on its own when your HR system or your team updates that record.
| Referrer Status | Chip | What it means |
| - | - | - |
| **Active** | Green | They have an open employee record. |
| **Exited** | Red | All of their employee records have ended. The **Turnover Date** shows when. |
| **Unknown** | Grey | They aren't linked to an employee record. |
Journeyfront links a referrer to an employee record in your account:
1. **By User ID**, when one is entered on the referrer or in an upload.
2. **By email** otherwise, matching the referrer's email to the person's email.
If someone was rehired, any open record makes them **Active**.
Employment matters for payouts. If the referrer leaves before an installment is earned, that payout becomes **Ineligible** with the reason **Referrer left before it was earned**. A referrer with **Unknown** status is treated as still employed, because Journeyfront can't show they left.
> [!TIP]
>
> When a referrer shows **Unknown** but you know they work here, their referral email probably differs from the email on their employee record. Edit the referrer and enter their **User ID** to link them.
See [Employee records](/employees/employee-records) and [HRIS integrations](/integrations/hris) for how employee records are kept up to date.
## Add a referrer
Referrers are created automatically when someone makes a referral. Add one yourself when you want to set them up ahead of time.
**1. Open New Referrer**
On the **Referrers** tab, click **New Referrer**.
**2. Enter their details**
Enter **First Name**, **Last Name** and **Email**. Add a **User ID** to link them to a specific person, if their email doesn't match, and a **Note** if you'd like.
**3. Create the referrer**
Click **Create Referrer**.
If no one in your account has the User ID you entered, Journeyfront tells you and nothing is saved.
## Upload referrers
Use an upload to add or update many referrers at once, for example people your HR system doesn't cover.
**1. Open Upload Referrers**
On the **Referrers** tab, click **Actions**, then **Upload Referrers**.
**2. Choose your file**
Pick a CSV or Excel file (up to 10 MB) with the columns **Email**, **First Name**, **Last Name** and **User ID**. Employment isn't uploaded. It always comes from the linked employee record.

**3. Upload**
Click **Upload**. Each row updates an existing referrer with the same User ID, then the same email, or adds a new one. A User ID links the referrer to that person. When it's done, Journeyfront shows how many referrers were added and updated.
If any row has a problem, such as a missing email, the same email twice or a User ID that isn't in your account, nothing is imported. Journeyfront lists each problem by row so you can fix the file and upload it again.
## The referrer's details
Click a referrer's name, or open the row's menu and click **View Details**.

| Card | What it shows |
| - | - |
| **Referrer Details** | **Email**, **User ID**, **Note** and, if they added one on the referral portal, their **Portal Photo**. |
| **Employment** | **Employee Record** (**Linked** or **Not Linked**), **Start Date** and **Turnover Date**. Click **View Candidate Profile** to see their employee records and applications together. |
| **Rewards** | **Referrals** and **Hires**, plus **Paid** and **Owed** with **Manage Referral Payouts**. |
| **Referrals** | Their recent referrals with the candidate, job req, referred date and application status. Click **View in Referrals** for the full list. |
| **Payouts** | Their recent payouts with the hire, installment, amount, **Earned On** date and status. Only with **Manage Referral Payouts**. Click **View in Payouts** for the full list. |
With **Manage Referrals**, click **Edit** to change their name, email, **User ID** or **Note**, then click **Save**.
### Remove a portal photo
Employees can add a profile photo on the referral portal, and coworkers see it there, for example on the leaderboard. If a photo isn't appropriate, click **Remove Photo**, then **Remove** to confirm. The photo is removed for everyone. Admins can remove a photo but can't add or change one.
## Row actions
Open the menu at the start of a row for **View Details**, **Edit**, **View Referrals** (the **Referrals** tab filtered to this referrer) and, with **Manage Referral Payouts**, **View Payouts**.
## FAQ
> [accordion] Why does a referrer show Unknown?
>
> They aren't linked to an employee record. Usually their referral email doesn't match the email on their employee record, or they don't have one yet. Edit the referrer and add their **User ID** to link them.
> [accordion] Do I need to update a referrer's employment myself?
>
> No. Employment comes from the employee record they're linked to. When that record ends, the referrer shows **Exited** and their unearned payouts are updated on their own.
> [accordion] Does an Unknown referrer still get paid?
>
> Yes. Journeyfront treats them as employed, because it can't show they left. Link them to their employee record so their payouts follow their real employment.
> [accordion] Can I delete a referrer?
>
> No. Referrers can't be deleted, so their referrals and payouts always show who made them. You can edit a referrer's details at any time.
> [accordion] Why are some amounts shown in two currencies?
>
> The referrer has rewards in more than one currency. Journeyfront never adds different currencies together, so each currency gets its own total.
> [accordion] Why did my upload import nothing?
>
> Uploads are all or nothing. If any row has a problem, no rows are imported. Fix the rows listed and upload the file again.
## Related
> [card] [The Referrals page](/referrals/referrals-page)
>
> Every referral and who made it.
> [card] [Payouts](/referrals/payouts)
>
> Each installment and its status.
> [card] [Employee sign-in and access](/referrals/portal-access)
>
> Who can sign in to the referral portal.
> [card] [Badges](/referrals/badges)
>
> Recognize your top referrers.
# Review, credit and Reward Status
Source: https://help.journeyfront.com/referrals/review-and-credit
How Journeyfront flags referrals for review, decides which referral gets credit for a hire, and shows what each referral has paid.
> [!NOTE]
>
> **Who can do this:** *View Referrals* to see statuses and Reward Status. *Manage Referrals* to change a status, mark a referral reviewed or move the credit.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
Every hire pays one referral, and only referrals that deserve it. Journeyfront flags the referrals that might not, such as a second referral for the same person, so your team makes the call before anything is paid. The **Reward Status** then tells you, at a glance, what each referral has paid.
## Referral statuses
A referral's **Status** says whether it counts. It's separate from the candidate's application status.
| Status | Chip | What it means | Who sets it |
| - | - | - | - |
| **Needs Review** | Amber | The referral might not deserve the credit. Its payouts wait until someone decides. | Journeyfront, automatically |
| **Active** | Blue | The referral counts and can earn its reward. | Journeyfront, or anyone with **Manage Referrals** |
| **Denied** | Red | The referral doesn't count. Its unpaid payouts won't be paid. | Anyone with **Manage Referrals** |
You can't set **Needs Review** by hand. It only comes from the checks below.
## Why a referral needs review
When a referral is added or linked to an application, Journeyfront checks it. It's flagged **Needs Review** for any of these reasons:
| Reason | When it applies |
| - | - |
| **Someone else referred them** | Another employee referred the same person for the same application, and that other referral has the credit. |
| **Applied before the referral** | The candidate already had an application for this job, or an open application for another job, before the referral was made. |
| **Referred themselves** | The candidate's email is the same as the referrer's. |
Each one is a policy call with exceptions. A past applicant may have come back only because a coworker reached out, for example. That's why these referrals wait for a person instead of being denied.
On the **Referrals** tab, hover a **Needs Review** chip to see its reasons. Open the referral to act on them.
> [!TIP]
>
> Save a view of the **Referrals** tab filtered to **Status** is **Needs Review** and check it before each payout batch. Payouts from these referrals are left out of payout batches until someone decides.
## Review a flagged referral
**1. Open the referral**
On the **Referrals** tab, click the candidate's name. The **Needs Review** box at the top lists the reasons.

**2. Decide**
Choose one:
* **Mark Reviewed:** the referral counts as it is and becomes **Active**.
* **Keep Current Credit** (for a duplicate): this referral becomes **Active**, but the other referral keeps the credit, so this one's payouts aren't paid.
* **Give This Referral the Credit** (for a duplicate): this referral gets the credit and the payouts. The other referral's payouts are no longer paid.
* **Denied:** change the status chip in the header to **Denied** so the referral doesn't count.
Once you've decided, the checks leave the referral alone. It won't be flagged again for the same reason.
## Who gets the credit
When several employees refer the same person for the same application, only one referral is paid:
* **The first referral wins.** Unless someone chooses otherwise, the earliest referral gets the credit.
* **You can move the credit.** Click **Give This Referral the Credit** on another referral of the same application. Every referral of that application is then marked reviewed.
* **Credit can't move once paid.** If the other referral already has a paid payout, Journeyfront stops you, so the same hire is never paid twice.
* **Denying passes the credit on.** If you deny the referral that has the credit, the next referral in line gets it.
A denied referral can't get the credit, and neither can a referral that isn't linked to an application.
With **Manage Referral Payouts**, you'll see this in the referral's **Reward** card: payouts from a referral without the credit show as **Ineligible**. Hover the chip to see **Credited to another referral**.
## Change a referral's status
With **Manage Referrals**, click the **Status** chip on the **Referrals** tab or in the referral's header, then pick **Active** or **Denied**. The change saves right away.

To change many at once, check their boxes on the **Referrals** tab, click **Change Status**, choose a status and click **Change Status**.

When you deny a referral:
* Its unpaid payouts become **Ineligible**, with the reason **Referral was denied**. Payouts already paid stay paid.
* The referrer can get a **Not Moving Forward** email, depending on the portal's and the employee's notification settings. See [Featured items and email notifications](/referrals/featured-and-notifications).
* If it had the credit, the credit passes to the next referral of the same application.
Setting a denied referral back to **Active** brings its unpaid payouts back on schedule.
## Reward Status
**Reward Status** shows what a referral has paid. Journeyfront works it out from the referral's payouts, so you never set it yourself. It's a column and a filter on the **Referrals** tab.
| Reward Status | Chip | What it means |
| - | - | - |
| **No Reward** | Grey | The referral has no reward program. |
| **Not Hired Yet** | Grey | It has a reward, but the candidate hasn't been hired, so there are no payouts yet. |
| **Upcoming** | Grey | The candidate was hired and payouts are scheduled, but none is earned yet. |
| **Owed** | Amber | At least one payout is earned and not paid yet. |
| **Partly Paid** | Blue | Something has been paid and more is still owed or upcoming. |
| **Rewarded** | Green | Paid, with nothing left to pay. |
| **Not Rewarded** | Red | Nothing will be paid: the referral was denied, the application ended without a hire, or every payout became ineligible. |
With **Manage Referral Payouts**, the **Paid**, **Owed** and **Upcoming** columns show the amounts behind the status. **Owed** means earned and overdue payouts that aren't paid yet.
## FAQ
> [accordion] Does Needs Review stop the referral from earning?
>
> No. Its payouts are still scheduled and can be earned, but they're left out of payout batches until someone marks the referral reviewed, gives it the credit or denies it.
> [accordion] Why was a referral flagged when the candidate applied to a different job?
>
> The candidate had an open application for another job before the referral was made. Applications that ended (not selected, withdrawn or hired) don't count against a later referral for a different job.
> [accordion] I gave a referral the credit by mistake. Can I move it back?
>
> Yes, as long as nothing has been paid on it. Open the other referral and click **Give This Referral the Credit**.
> [accordion] Why can't I move the credit?
>
> The referral that has the credit already has a paid payout. Moving the credit then would pay the same hire twice.
> [accordion] Can I set a referral to Needs Review myself?
>
> No. **Needs Review** only comes from Journeyfront's checks. You can set **Active** or **Denied**.
> [accordion] Why does a referral show Not Rewarded when the hire is still here?
>
> Its payouts became ineligible, for example because another referral has the credit or the referrer left before a payout was earned. Open the referral and hover each payout's status chip to see why.
## Related
> [card] [The Referrals page](/referrals/referrals-page)
>
> Find, filter and manage every referral.
> [card] [Referral details and milestones](/referrals/referral-details)
>
> See a referral's reward and payouts.
> [card] [Payouts](/referrals/payouts)
>
> Every installment, its Earned On date and status.
> [card] [Payout batches](/referrals/payout-batches)
>
> Send what's owed to payroll.
# Reward programs
Source: https://help.journeyfront.com/referrals/reward-programs
Define what a referral pays: the amount, currency, portals and an installment schedule by days or milestones.
> [!NOTE]
>
> **Who can do this:** Anyone with *View Referrals* can see reward programs. Creating and changing them takes *Manage Referral Settings*.
>
> **Availability:** Referrals need to be turned on for your account. Ask your Customer Success Manager.
A reward program is your referral bonus, written down once: how much it pays, in which currency, on which referral portals, and on what schedule. Attach it to your job reqs, and every referral to those job reqs earns it automatically. Journeyfront then works out each payout's date and amount for you.
## The Reward Programs tab
Go to **Referrals**, then **Reward Programs**. Each program is a card that shows:
* its name and status (**Active**, **Draft** or **Archived**)
* the referral portals it's on, or **All Referral Portals**
* the **Total Reward** and its installments, with when each one is due
* its effective dates and how many job reqs and referrals use it

Use the search box to find a program by name or description, and the **Referral Portal**, **Status** and **Currency** filters to narrow the list. Archived programs are hidden until you add **Archived** to the **Status** filter. Click a card to open the program's details.
## Create a reward program
**1. Start a new program**
On the **Reward Programs** tab, click **New Reward Program**.
**2. Fill in the details**
Enter the program's settings. See the table below.

**3. Add the installments**
Under **Installments**, add one row for each payment. Click **Add Installment** for another row. The **Total** at the top of the card adds them up as you go.
**4. Create it or save a draft**
Click **Create Reward Program** to make it active right away, or **Save as Draft** to finish it later.
| Setting | What it does |
| - | - |
| **Name** | Required. Shown to your team and to employees on the referral portal. |
| **Currency** | The currency every installment is paid in. A program has one currency. To pay in another currency, create another program. |
| **Referral Portals** | **All Referral Portals**, or **Specific Referral Portals** and the portals you pick. Employees on a portal only see that portal's programs. |
| **Description** | Shown to employees on the referral portal's rewards page. Use it to explain the bonus in plain words. |
| **Effective Dates** | Optional start and end dates. Only referrals made between these dates earn the program. Leave both blank and the program is always effective. |
Each installment has:
| Field | What it does |
| - | - |
| **Label** | Optional. Leave it blank and the installment is called "Installment 1", "Installment 2" and so on, or by its milestone's name. On the referral portal, an unlabelled installment is named by when it pays instead, such as "Day 180" or "Training Completed". |
| **Amount** | What this installment pays, in the program's currency. |
| **Due** | **Days After Start** or **Milestone**. |
| **Days or Milestone** | For **Days After Start**, the number of days after the hire's start date. For **Milestone**, a name like Training Completed. |
A program can have up to 12 installments. Day-based installments must be in order, earliest first. Milestones can go anywhere in the list.
> [!TIP]
>
> Split a large bonus into installments that line up with how long you want hires to stay, like \$200 after 90 days and \$300 after 180 days. You reward retention, not just the hire, and payroll sees smaller amounts spread over time.
### Days and milestones
A **Days After Start** installment is earned automatically: its **Earned On** date is the hire's start date plus its days.
A **Milestone** installment has no date until someone records that the hire reached it, for example finishing training. You record milestones on the **Payouts** tab, one at a time or by uploading a file, or with **Mark Reached** on the referral. See [Payouts](/referrals/payouts) and [Referral details and milestones](/referrals/referral-details).
Either way, an installment is only earned if the hire and the referrer are both still employed on its date.
## View a program's details
Click a program's card to open its details on the right side of the page.

The panel shows:
* **Reward Program**: the **Total Reward**, **Referral Portals**, **Effective Dates** and **Description**.
* **Payout Schedule**: each installment, when it's due and its amount.
* **Job Reqs**: every job req that uses the program, with how many referrals each one has under it. Click **View in Referrals** to see those referrals on the Referrals tab.
To change the program, click **Edit**. You can also click the menu on a card and choose **Edit**.
## Changes only apply to new referrals
Each referral keeps the program's terms from the day it was made. When you edit a program that referrals already use, a note at the top of the form tells you how many referrals keep their original terms. Your changes apply to new referrals only.
> [!TIP]
>
> To change a bonus going forward, you can edit the program or create a new one and switch your job reqs to it. A new program keeps the history clearer, since each program's name then matches one set of terms.
## Drafts, publishing and archiving
| Status | What it means | What you can do |
| - | - | - |
| **Draft** | Saved but not live. It isn't on any job req or portal. | **Publish** it to make it active, or **Delete** it. |
| **Active** | Live. You can pick it on job reqs, and employees see it on its portals. | **Archive** it when you stop offering it. |
| **Archived** | Retired. It stops paying new referrals and is hidden on the Reward Programs tab. | **Restore** it to make it active again. |
Find **Publish**, **Archive** and **Restore** in the menu on the program's card. A draft's details panel also has a **Publish** button. Once a program is published, it can't go back to being a draft.
Archiving doesn't touch what referrals already earned. Their payouts carry on as before. Job reqs that use an archived program keep showing it, but new referrals to them don't earn it. Pick a new program on those job reqs. See [Rewards on job reqs](/referrals/job-req-rewards).
### Delete a program
You can delete a draft at any time. You can only delete a published program if no job req or referral has used it. Otherwise, archive it instead. To delete, click the menu on the card, choose **Delete**, then click **Delete** to confirm. This can't be undone.
## Programs and portal admins
If your role only covers some referral portals, you only see programs on your portals or on all portals, and new programs you create must be for your own portals. A program that's shared with portals you don't manage shows a lock icon instead of a menu. Only someone who manages all of its portals can change it. See [Permissions and portal admins](/referrals/permissions).
## FAQ
> [accordion] Why can't I change which portals a program is on?
>
> Every job req that uses a program must be posted only on that program's portals. If you try to remove a portal that one of its job reqs is posted on, Journeyfront tells you which job reqs are in the way. Change their portals or their reward program first, then try again.
> [accordion] Why isn't my program in the job req's Reward Program list?
>
> Only **Active** programs can be picked, and only ones that cover every portal the job req is posted on. Publish a draft first, and check the program's **Referral Portals**.
> [accordion] What happens to referrals made outside the effective dates?
>
> They don't earn the program. Employees also stop seeing the reward on the portal once the end date has passed.
> [accordion] Can one program pay in two currencies?
>
> No. Each program has one currency. Create a program for each currency, such as one in USD and one in CAD, and put each on the right portals or job reqs. Totals across currencies are always shown separately, never added together.
> [accordion] Can I pay part of a reward at hire?
>
> Yes. Add an installment with **Days After Start** set to 0. It's earned on the hire's start date.
> [accordion] Why is Delete missing from a program's menu?
>
> The program is active or archived and a job req or referral has used it. Archive it instead, so the history of what it paid stays intact.
## Related
> [card] [Rewards on job reqs](/referrals/job-req-rewards)
>
> Choose which program each job req's referrals earn.
> [card] [Payouts](/referrals/payouts)
>
> Track each installment from upcoming to paid.
> [card] [How referrals work](/referrals/overview)
>
> The big picture and a setup checklist.
> [card] [Permissions and portal admins](/referrals/permissions)
>
> Control who can create and change programs.
# Applicant volume and pipeline
Source: https://help.journeyfront.com/reporting/candidate-overview
See how many people apply, where they stand, how they score and why they're rejected, and how full your hiring classes are.
> [!NOTE]
>
> **Who can do this:** The company **Candidate Overview** and **Hiring Classes** dashboards need *Company Dashboard Access*. A job req's **Overview** tab needs access to that job req.
**The questions it answers:** how many people are applying, where do they stand, how strong are they, and are we filling our hiring classes?
## Company-wide: Candidate Overview
Click **Dashboard** in the top navigation. It opens on **Candidate Overview**, which covers every job req in your account. It has two sheets: **Summary** and **Job Req Detail**. Both count candidates by **Application Date**, the date they started the application.

### The Summary sheet
| Visual | What it shows |
| - | - |
| **# of Job Reqs** | Job reqs with at least one applicant in your date range. |
| **Total Applicants** | Applications started. Someone who applies to two job reqs counts twice. |
| **Hires** | Applications marked hired. |
| **Applicant Hire Percentage** | Hires divided by applications started. |
| **Avg Overall Score of Applicants** and **Avg Overall Score of Hires** | The average overall score, on a 0 to 5 scale, for everyone and for the people you hired. |
| **Candidate Status Distribution** | The share of applications that are **Active**, **Hired**, **New**, **Rejected** or **Incomplete**. |
| **New Applicants Over Time** | Applications by week, with a moving average to smooth out spikes. |
| **Avg. Completion Rate Over Time** | How much of the application candidates completed on average, by month. |
| **Overall Score Distribution** | How many applicants landed at each overall score. |
| **Rejection Reasons** | Rejections by reason. |
| **Applicants Volume by Location** | A map of applicants by the candidate's state or province. |
| **Candidate Details** | A table with one row per application, including the job req, assigned user, current step, time in the current step and status. |
### The Job Req Detail sheet
The same headline numbers, plus a breakdown by job req. Its controls include **Job Profile**, **Job Req**, **Hiring Class**, **Candidate Status**, **Source Type** and the candidate's location.
* **Candidates by Job Req** and **Candidates Over Time by Job Req**: which job reqs draw the most applicants.
* **Completion Rates Distribution Over Time**: the share of applicants at each level of application completion, by month, from red (barely started) to green (finished).
* **Rejection Reasons by Job Req** and **Applicant Status by Job Req**: which job reqs drive each rejection reason, and where the incomplete and active applications sit.

## For one job req
Open the job req and click its **Dashboard** tab. It opens on **Overview**: the same kind of view for that job req, with total applicants, new applicants over time and applicants by status. See [Job req dashboards](/reporting/job-dashboards).
## Hiring Classes
If you hire in classes, the **Hiring Classes** dashboard shows whether they start full. Choose **Hiring Classes** from the **Dashboard** menu. It counts by **New Hire Start Date**, and other controls include **Job Profile**, **Job Req**, **Hiring Class Name**, **Hiring Class Job Title** and **Hiring Class Status**.

| Visual | What it shows |
| - | - |
| **Completed Hiring Classes** and **Active Hiring Classes** | How many classes are complete and how many are active. |
| **Avg. Fill Rate** | How full your completed classes were, on average. |
| **Class Attainment Rate** | The share of completed classes that were filled. |
| **Opening Fill Rate** | The share of openings filled across your completed classes. |
| **Classes Filled & Not Filled** | Filled and unfilled classes, as a donut. |
| **Hiring Classes Over Time** and the three rate charts over time | The same numbers by start date. |
| **Hiring Class Detail** | One row per class, with its job req, job title, fill status, due date, start date, status, fill date, hires and openings. |
See [Hiring classes](/hiring-classes/overview).
## How teams use it
* **Watch volume weekly.** **New Applicants Over Time** is your early warning. A drop shows up here weeks before it shows up in hires.
* **Find abandoned applications.** A growing **Incomplete** slice, or a falling **Avg. Completion Rate Over Time**, means candidates give up partway through. Shorten the application or move questions later. See [Funnel and drop-off](/reporting/funnel-analytics).
* **Learn what a good score is.** **Overall Score Distribution** shows where most applicants land on your account. Use it to set review thresholds and automation rules that fit your real pool.
* **Plan classes from the gap.** **Hiring Class Detail** shows which classes are short and by how many. Pair it with **Candidates per Hire** on Funnel Analytics to see how many more applicants you need.
## Related
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Where candidates leave your process.
> [card] [Hiring classes](/hiring-classes/overview)
>
> Group hires who start together.
> [card] [Source effectiveness](/reporting/source-effectiveness)
>
> Where your applicants come from.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Dashboards overview
Source: https://help.journeyfront.com/reporting/dashboards
Where reporting lives in Journeyfront, who can see it, which page answers your question, and how to filter, drill and bookmark a dashboard.
> [!NOTE]
>
> **Who can do this:** Company dashboards need the *Company Dashboard Access* permission. A job req's **Dashboard** tab needs access to that job req. A job profile's **Dashboard** tab needs access to that job profile. Seeing the employees behind some charts also needs *Performance Access*.
Journeyfront's dashboards answer the questions recruiting teams ask every week: how many people are applying, where they drop out, how fast you hire, which sources work and how your hires do once they start. This page explains where each kind of dashboard lives and how to work with them. The pages that follow are organized by the question you're trying to answer.
## Where reporting lives
There are three places to find dashboards, from widest to narrowest.
| Place | How to open it | What it covers | Who can see it |
| - | - | - | - |
| **Company dashboards** | Click **Dashboard** in the top navigation | Every job req in your account | Users with *Company Dashboard Access* |
| **A job req's dashboards** | Open a job req and click its **Dashboard** tab | That job req only | Anyone who can open the job req |
| **A job profile's dashboards** | Click **Profiles**, open the job profile, then click **Dashboard** | The employees hired into that role | Users with access to the job profile |
Company dashboards show data for every job req in your account. To focus on one role, location or req, use the **Job Profile** and **Job Req** controls at the top of the dashboard.

### Open a company dashboard
**1. Click Dashboard**
Click **Dashboard** in the top navigation. It opens on **Candidate Overview**. If you don't see **Dashboard**, your security role doesn't have *Company Dashboard Access*.
**2. Choose a dashboard**
Click the dashboard's name at the top of the page to open the menu, then pick a dashboard or type in **Search** to find one.
### A job req's Dashboard tab
Every job req has a **Dashboard** tab with six tabs of its own: **Overview**, **Interviews**, **Hiring Process Fidelity**, **Funnel Analytics**, **Language Assessment** and **Source Effectiveness**. They're already filtered to the job req, so there's no job req control to set. See [Job req dashboards](/reporting/job-dashboards).

### A job profile's Dashboard tab
A job profile's **Dashboard** tab compares what you measured during hiring with how the people you hired into that role went on to do. It's the main place for **Turnover**, **Performance**, **Attributes**, **Activities**, **Interview Questions** and **Interviewers**, because those results are most useful for one role at a time. See [Quality of hire](/reporting/turnover-and-performance).

## Which page answers your question?
| Your question | Read | Main dashboards |
| - | - | - |
| How many people are applying, and where do they stand? | [Applicant volume and pipeline](/reporting/candidate-overview) | **Candidate Overview**, **Hiring Classes** |
| Where do candidates drop out of our process? | [Funnel and drop-off](/reporting/funnel-analytics) | **Funnel Analytics** |
| How long does it take us to hire? | [Time to hire](/reporting/time-to-hire) | **Time To Hire**, Funnel Analytics **Time to Hire** sheet |
| Which sources bring in hires, and hires who stay? | [Source effectiveness](/reporting/source-effectiveness) | **Source Effectiveness** |
| How are interviews going, and are interviewers scoring consistently? | [Interview analytics](/reporting/interview-analytics) | **Interview Overview**, a job req's **Interviews** tab, a job profile's **Interviewers** |
| Are hires going through every activity in our process? | [Hiring process fidelity](/reporting/hiring-process-fidelity) | **Hiring Process Fidelity** |
| What is each recruiter doing, and what comes of it? | [Recruiter productivity](/reporting/recruiter-productivity) | **Recruiter Productivity** |
| Do our hires stay and perform, and does what we measure predict it? | [Quality of hire](/reporting/turnover-and-performance) | A job profile's **Turnover**, **Performance**, **Attributes**, **Interview Questions** and **Interviewers** |
| How do candidates answer our screening questions, and do the answers matter? | [Screening question analytics](/reporting/screening-questions-analytics) | **Screening Questions**, Funnel Analytics **Screening Question Fallout** |
| What does our applicant pool look like demographically? | [EEOC reporting](/reporting/eeoc) | **EEOC Dashboard**, when turned on |
| How are candidates scoring on language assessments? | [Language assessment results](#language-assessment-results) | **Language Assessment** |
## Filter a dashboard
Most dashboards have **Controls** at the top. Click a control to narrow the data, for example by **Application Date**, **Job Profile**, **Job Req**, **Source Type**, **Source** or **Hiring Class**. Each dashboard has its own set of controls, and the arrow at the right end of the bar shows the rest. Some dashboards have several sheets, shown as tabs above the controls.
The **Turnover**, **Performance**, **Attributes**, **Interview Questions** and **Interviewers** dashboards have their own filters above their charts instead, such as **From Date** and **To Date**.
> [!TIP]
>
> Check which date a dashboard filters on. Most use the application date, but **Hiring Process Fidelity** and **Hiring Classes** use the start date, **Interview Overview** also has an interview date, and **Time To Hire** charts its trends by hire date. Two dashboards can show different numbers for the "same" month for this reason.
## Drill into a chart
Hover over a chart to see the exact numbers. Charts with **(Drill Up/Down)** in their title let you change the level, for example from job profile down to job req, or from country down to city. On some tables, clicking a row filters the rest of the dashboard: on **Funnel Analytics**, clicking a row on the **Job Reqs** sheet selects that job req. On **Turnover** and **Performance**, click a bar to see the employees behind it.
## Save your filters as bookmarks
Bookmarks save a set of filters on a dashboard, so you don't have to set them again every visit. For example, save "Customer Care Associate, last quarter" on **Funnel Analytics**.

**1. Set your filters**
Open the dashboard and set the **Controls** the way you want them.
**2. Add the bookmark**
Click the bookmark icon in the dashboard's toolbar, then **Add bookmark**. Give it a name that describes the filters and click **Save**.
**3. Use it later**
Click the bookmark icon and choose your bookmark. Its filters are applied right away.
Click the **â‹®** next to a bookmark to update it with your current filters, rename it, make it the default for that dashboard, or delete it.
Bookmarks belong to the dashboard you saved them on, so a bookmark on **Funnel Analytics** doesn't appear on **Time To Hire**. They work the same way on a job req's dashboards. The toolbar also has undo, redo and a reset button that puts the filters back to their defaults. The job profile dashboards with their own filters don't have bookmarks.
## Tables and exporting
Many dashboards end with a table of the candidates, hires or interviews behind the charts, such as **Candidate Details** on Candidate Overview. Use them to check a number or find a specific person.
Dashboards don't have a print or PDF option. For a spreadsheet of candidates or job reqs, export from the **Candidates** or **Job Reqs** page. See [Export data](/lists-and-exports/export-data).
## Language assessment results
If your job reqs use a language assessment, the **Language Assessment** dashboard shows how many tests were taken, how CEFR levels are spread, how candidates at each level moved through hiring, and how levels compare by job req, location and source. A **Language Results** sheet lists every result. It's in the company **Dashboard** menu and on each job req's **Dashboard** tab. See [Language assessments](/assessments/language-assessments).
## FAQ
> [accordion] Why don't I see Dashboard in the top navigation?
>
> Your security role needs *Company Dashboard Access*. Ask your Journeyfront admin to check your role under **Settings**, then **Security**. You can still see a single job req's dashboards on its **Dashboard** tab.
> [accordion] Why is a dashboard empty?
>
> Check the **Controls** first: a narrow date range or filter can leave nothing to show. The **Turnover**, **Performance**, **Attributes**, **Interview Questions** and **Interviewers** dashboards also need employee data, such as end dates and performance reviews. See [Quality of hire](/reporting/turnover-and-performance).
> [accordion] Why don't the numbers match the Candidates page?
>
> Dashboards count by the dates and filters in their **Controls**, and each dashboard counts a little differently, for example by application date or by start date. Match the date range and filters before comparing.
> [accordion] Can I see a dashboard for just my job reqs?
>
> Company dashboards include every job req in your account. Use the **Job Req** control to pick yours, and save the selection as a bookmark. Or use each job req's own **Dashboard** tab.
## Related
> [card] [Job req dashboards](/reporting/job-dashboards)
>
> The six dashboard tabs on every job req.
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Find the step where candidates leave.
> [card] [Quality of hire](/reporting/turnover-and-performance)
>
> How your hires stay and perform, by job profile.
> [card] [Export data](/lists-and-exports/export-data)
>
> Download candidates and job reqs to a spreadsheet.
# EEOC reporting
Source: https://help.journeyfront.com/reporting/eeoc
Ask candidates the voluntary EEOC self-identification questions, and report on your applicant pool.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission turn the questions on for a job req. The EEOC dashboard needs *Company Dashboard Access*.
>
> **Availability:** The EEOC dashboard needs to be turned on for your account. Ask your Customer Success Manager.
Many US employers ask applicants to voluntarily self-identify their ethnicity, race, gender, disability status and veteran status, so they can track the diversity of their applicant pool and meet equal employment opportunity (EEO) reporting requirements. Journeyfront can ask these questions on the application form, keeps the answers apart from your hiring decisions, and reports on them on the EEOC dashboard.
## Ask the questions on a job req
The questions are part of each job req's application form, as the **EEOC Compliance Questions** row. They're **Hidden** on new job reqs.
**1. Open the application form**
Open the job req and go to **Setup**, then **Application Form**.
**2. Turn on the questions**
On the **EEOC Compliance Questions** row, choose **Required**. This row can only be **Required** or **Hidden**; there's no **Optional** choice.
**3. Save**
Click **Save** at the top of the page.
To stop asking, set the row back to **Hidden** and save. See [Application form](/job-reqs/application-form).
> [!TIP]
>
> Which job reqs should ask, and how you use the results, are compliance decisions. Check with your legal or compliance team before you turn the questions on.
## What candidates see
On their application form, candidates see a **Voluntary Self-Identification** section. It explains that answering is voluntary, that their answers are kept confidential and won't be used in employment decisions, and that they're used only for aggregate reporting and compliance. Then it asks:
* **Are you Hispanic or Latino?**
* **Please Identify your Race**
* **Please Identify your Gender**
* **Disability Status**
* **Veteran Status**
Each question has a short note explaining why it's asked, and every question includes the answer "I do not wish to self identify". Candidates must choose an answer for each question before they continue, but declining to self-identify always counts as an answer, so no one has to share this information.
If the job req is posted to Indeed with Easy Apply, Indeed asks the same questions when they're turned on, and the answers come into Journeyfront with the application. See [Indeed](/integrations/job-boards/indeed#control-what-easy-apply-asks-for).

## How the answers are kept
* **One set per person.** The answers belong to the candidate, not to one application. If they answer again on a later application, the new answers replace the old ones.
* **Not shown where your team works with candidates.** Individual answers don't appear on the Candidate Application, the Candidate Profile or the Candidates page, and they're not included in exports.
* **Not part of scoring.** Like the rest of the application form, the answers don't affect any score.
* **Reported on the EEOC dashboard.** The dashboard's charts show totals across candidates. Its **User Data** table lists individual answers, so keep access to it limited.
If your HR system is connected, an admin can map **Ethnicity / Race** (under **EEOC Fields**) in the HR system's field mappings. A hire's answer then fills in that field when you create them in your HR system. See [HRIS integrations](/integrations/hris).
## The EEOC dashboard
The EEOC dashboard is only available when it's turned on for your account. Click **Dashboard** in the top navigation, then choose **EEOC Dashboard** from the dashboard menu. Like the other company dashboards, it covers every job req in your account; use the **Job Profile** and **Job Req** controls to focus. Other controls include **Application Date**, **Candidate Status** and each self-identification question. The **Show Non-Responders** control is set to **No** by default.

For each question (gender, Hispanic or Latino, race, disability status and veteran status) the dashboard shows three things side by side:
| Visual | What it shows |
| - | - |
| **All Applicants** | Applicants by their answer, with the share for each. |
| **Hires** | Hires by their answer. |
| **Distribution Data** | For each answer, how many applicants were and weren't hired, as counts and percentages, with a total. |
Use **Distribution Data** to compare hire rates across groups. How to interpret the results, and what to do about them, are questions for your legal or compliance team.
Below these, the **User Data** table lists individual applications with each candidate's name, email and self-identification answers. Because it shows individual answers, limit *Company Dashboard Access* to the people who need it.
## FAQ
> [accordion] Do candidates have to answer?
>
> When the questions are turned on, candidates must pick an answer for each one, but every question includes "I do not wish to self identify". Sharing the information is always voluntary.
> [accordion] Can recruiters see how a candidate answered?
>
> Not where they work with candidates. Individual answers aren't shown on the Candidate Application, the Candidate Profile or the Candidates page, and they aren't included in exports. The EEOC dashboard's **User Data** table does list individual answers, so only give *Company Dashboard Access* to people who should see them.
> [accordion] Are EEOC answers used in scoring or hiring decisions?
>
> No. They don't affect any score, and candidates are told their answers won't be used in employment decisions.
> [accordion] Why can't I make the EEOC questions Optional?
>
> Every question already lets candidates decline to self-identify, so the section is either shown (**Required**) or not (**Hidden**).
> [accordion] I don't see the EEOC Dashboard in the dashboard menu.
>
> It needs to be turned on for your account, and you need *Company Dashboard Access*. Ask your Customer Success Manager about turning it on.
> [accordion] Can I export EEOC data?
>
> No. EEOC answers aren't included in Journeyfront's exports. Use the EEOC dashboard for aggregate reporting.
> [accordion] Do I need to turn the questions on for every job req?
>
> Yes. The setting is part of each job req's application form. When you duplicate a job req, the copy keeps the original's application form, including this setting.
## Related
> [card] [Application form](/job-reqs/application-form)
>
> Choose which fields candidates fill in, including EEOC.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Find the EEOC dashboard and the rest.
> [card] [Export data](/lists-and-exports/export-data)
>
> What you can download, and what stays in Journeyfront.
> [card] [HRIS integrations](/integrations/hris)
>
> Send hires and their details to your HR system.
# Funnel and drop-off
Source: https://help.journeyfront.com/reporting/funnel-analytics
See how many candidates reach each step of a job req's workflow, where they drop out, why they're rejected and how long each step takes.
> [!NOTE]
>
> **Who can do this:** The company **Funnel Analytics** dashboard needs *Company Dashboard Access*. A job req's **Funnel Analytics** tab needs access to that job req.
**The question it answers:** of everyone who applied, how many made it through each step, where did the rest drop out, and why?
Funnel Analytics follows candidates through a job req's workflow, step by step and activity by activity. Use it to find the step that loses the most people, the assessment that takes too long, or the rejection reason that's doing more work than it should.
## Read it one job req at a time
Each job req has its own workflow, with its own step names and activities. When you look at many job reqs at once, steps from different workflows pile up and the funnel stops meaning much. Look at one job req at a time, or at a few job reqs that share the same workflow.
There are two ways to do that:
* **On the job req:** open the job req, click its **Dashboard** tab, then **Funnel Analytics**. It's already filtered to that job req.
* **On the company dashboard:** pick the job req first, on the **Job Reqs** sheet or in the **Job Req(s)** control. Then read the other sheets.
## Company-wide
Click **Dashboard** in the top navigation and choose **Funnel Analytics**. Like every company dashboard, it starts with data for every job req in your account.
### Pick a job req on the Job Reqs sheet
The dashboard opens on the **Job Reqs** sheet: a table of your job reqs with their job profile, **Candidates**, **Candidates Interviewed** and **Hires**. Click a row to select that job req for the rest of the dashboard, or choose it in the **Job Req(s)** control.

### The sheets
| Sheet | What it shows |
| - | - |
| **Job Reqs** | Your job reqs, to pick the one to analyze. |
| **Compare Job Reqs** | Results, step volume and time in step side by side for the job reqs you select. Useful for job reqs that share a workflow, such as the same role in several locations. |
| **Overview** | Headline numbers, the hiring funnel by step and by activity, and time in each step. |
| **Time to Hire** | Median and average days to hire. See [Time to hire](/reporting/time-to-hire). |
| **Step Analysis** | Each step broken down by the candidate's result in it, and how long candidates sat in each step. |
| **Activity Analysis** | Each activity broken down by status, and how long candidates took to complete it. |
| **Rejection Analysis** | Rejection reasons, where in the process they're used, and how rejected candidates scored. |
| **Screening Question Fallout** | Which screening questions candidates stop at. See [Screening question analytics](/reporting/screening-questions-analytics). |
The controls across the sheets include **Application Date**, **Job Profile**, **Job Req(s)**, **Final Result**, **Step**, **Step Result**, **Activity**, **Activity Status**, **Source Type**, **Source** and **Hiring Class**.
### The Overview sheet
The top of the **Overview** sheet has five headline numbers:
| Metric | What it means |
| - | - |
| **Number of Hires** | Hires among the candidates who applied in your date range. |
| **Candidates per Hire** | How many candidates applied for each hire. |
| **Interviews per Hire** | How many candidates were interviewed for each hire. |
| **Offer Acceptance Rate** | Offers accepted divided by offers created, shown as a ratio (0.88 means 88%). |
| **Average Time to Hire (Days)** | Average days from application to being marked hired. |
Below them are the funnels:
* **Hiring Funnel (Steps)**: how many candidates reached each step, and what share of the first step that is.
* **Hiring Funnel by Step Result**: each step split by what happened to candidates there.
* **Hiring Funnel (Completed Activities)**: the same funnel by activity, such as the application, an assessment or an interview.
* **Hiring Funnel by Activity Status**: each activity split into **Complete**, **Complete - Need Scores**, **In Progress** and **Not Started**.

Further down, **Median Time in Each Step (Days)** and **Average Time in Each Step (Days)** show how long candidates spent in each step, and the completion time charts show how many minutes candidates spent on each activity. History charts show each of these by application month, so you can see whether a change you made sped a step up.
### Step results
**Hiring Funnel by Step Result**, the **Step Analysis** sheet and the **Step Result** control use these results:
| Step result | What it means |
| - | - |
| **Hired** | The candidate was hired from this step. |
| **Moved to Next Step** | The candidate passed this step. |
| **Still In Step - Not Finished** | The candidate is in this step and hasn't finished it. |
| **Still In Step - Step Complete** | The candidate finished the step but hasn't been moved on. |
| **Rejected** | The candidate was rejected in this step. |
**Final Result** describes the whole application instead: **Hired**, **Rejected** or **Still in Funnel**.
> [!TIP]
>
> A big **Still In Step - Step Complete** bar means candidates are done and waiting on your team. A big **Still In Step - Not Finished** bar means candidates stalled, so look at reminders or at how long the step takes.
### The Rejection Analysis sheet
**Rejection Reason Distribution** counts rejections by reason. **Rejection Reason by Step** shows the mix of reasons at each step, so you can see which reasons are used early in the process and which come later. **Step Score Distribution** and **Activity Score by Final Result** show whether rejected candidates really scored lower than the ones you hired.

## For one job req
Open the job req, click its **Dashboard** tab, then **Funnel Analytics**. It has the same sheets as the company dashboard except **Job Reqs** and **Compare Job Reqs**, and no job profile or job req controls. See [Job req dashboards](/reporting/job-dashboards).
## Related numbers on Candidate Overview
The **Candidate Overview** dashboard adds the earliest drop-off: candidates who start the application but don't finish it. **Avg. Completion Rate Over Time** shows how much of the application candidates complete on average, and the **Incomplete** slice of **Candidate Status Distribution** shows how many never submitted. See [Applicant volume and pipeline](/reporting/candidate-overview).
## How teams use it
* **Fix the biggest drop first.** Find the step where the funnel narrows most. If candidates stall there rather than get rejected, shorten the step, add reminders or move it later in the process.
* **Plan applicant volume.** **Candidates per Hire** tells you how many applicants you need for each seat. If a hiring class needs 20 hires and the job req runs at 9 candidates per hire, you need about 180 applicants.
* **Check unscored work.** **Complete - Need Scores** on **Hiring Funnel by Activity Status** is work candidates finished that nobody has scored yet.
* **Compare locations.** Select the same role in several locations on **Compare Job Reqs** to see which site loses more candidates, and at which step.
## FAQ
> [accordion] Why does the funnel look messy with every job req selected?
>
> Each job req's workflow has its own step names, so a funnel across many job reqs mixes steps that don't line up. Pick one job req, or a few with the same workflow.
> [accordion] Why don't the step counts match the Candidates page?
>
> The dashboard counts candidates who applied in the **Application Date** range and reached each step. The Candidates page shows where candidates are right now. Match the date range before comparing.
## Related
> [card] [Time to hire](/reporting/time-to-hire)
>
> How long hiring takes, and which step slows it down.
> [card] [Screening question analytics](/reporting/screening-questions-analytics)
>
> The questions candidates stop at.
> [card] [Rejection and separation reasons](/account-setup/rejection-reasons)
>
> Keep your rejection reasons clear so this report reads well.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Hiring process fidelity
Source: https://help.journeyfront.com/reporting/hiring-process-fidelity
Check that the people you hired went through every activity in your workflow, and find the locations, jobs and activities where steps get skipped.
> [!NOTE]
>
> **Who can do this:** The company **Hiring Process Fidelity** dashboard needs *Company Dashboard Access*. A job req's **Hiring Process Fidelity** tab needs access to that job req.
**The question it answers:** did the people we hired actually go through the process we designed?
You build a workflow with assessments, interviews and checks for a reason. Hiring Process Fidelity looks at your hires and shows what share of their workflow's activities they completed. A score below 100% means some hires skipped activities, for example a recruiter moved someone straight to an offer without the second interview.
**% of activities complete** is the share of the activities in a hire's workflow that they completed. It counts every activity in the workflow, including activities in steps the hire was never moved to, so skipping a whole step lowers the score. For interviews, if a hire completed any interview in a step, that step's interviews count as complete.
## Company-wide
Click **Dashboard** in the top navigation and choose **Hiring Process Fidelity**. It shows hires on every job req in your account; use the **Job Profile**, **Location** and **Job Req** controls to focus. The date control is the hire's **Employee Start Date**, and other controls include **Job Status**, **Hiring Class**, **Source Type**, **Source**, **Activity Name** and **Assigned User**.

| Visual | What it shows |
| - | - |
| **% of All Activities Complete** | Your overall score: the share of workflow activities your hires completed. |
| **Total Candidates Hired** | How many hires the score is based on. |
| **% of Activities Complete by Location** | A table grouped by location and job, with one row per hire and one column per step and activity. Red cells are activities the hire didn't complete. |
| **% of Activities Complete by Activity & Job** | Completion for each activity, by job. Activities that are low everywhere are the ones your team skips. |
| **% of Activities Complete by Start Date** | Your score by the week hires started, so you can see whether it's improving. |
| **% of Activities Complete Based on Start Date** | One line per activity by start month, to see which activity started getting skipped, and when. |
| **% of Activities Complete by Start Date** (table) | Expand a start month to see each activity, then each hire. |

## For one job req
Open the job req, click its **Dashboard** tab, then **Hiring Process Fidelity**. It shows the number of hires and the share of activities they completed for that job req alone, broken down by activity and over time.
## How teams use it
* **Find the skipped activity.** Look at **% of Activities Complete by Activity & Job** for the activity that's low across jobs. That's usually a process problem, like an interview that's hard to schedule, not one person cutting corners.
* **Audit a site.** Filter **Location** and use the table to see exactly which hires skipped what. Share it with the site's leader.
* **Watch after a change.** When you add or move an activity, watch **% of Activities Complete Based on Start Date** for the next few months to confirm teams are following it.
* **Pair it with quality of hire.** If hires who skipped an assessment leave sooner, you have a strong case to enforce it. See [Quality of hire](/reporting/turnover-and-performance).
## FAQ
> [accordion] Why is a hire's score low when they finished every step they were in?
>
> The score counts every activity in the workflow, including steps the hire never reached. If someone was moved past a step, its activities count as not completed.
> [accordion] Why does the dashboard filter on start date?
>
> It looks at people you hired, so it uses the date they started, not the date they applied.
## Related
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Activity status for every candidate, not just hires.
> [card] [Automation rules](/workflows/automation-rules)
>
> Move candidates through steps consistently.
> [card] [Recruiter productivity](/reporting/recruiter-productivity)
>
> What each recruiter is doing.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Interview analytics
Source: https://help.journeyfront.com/reporting/interview-analytics
Track interview volume and scores, compare interview guides and interviewers, and check whether interviewers' scores predict how hires perform.
> [!NOTE]
>
> **Who can do this:** The company **Interview Overview** dashboard needs *Company Dashboard Access*. A job req's **Interviews** tab needs access to that job req. A job profile's **Interviewers** and **Interview Questions** tabs need access to that job profile; seeing the employees behind their charts also needs *Performance Access*.
**The questions it answers:** how many interviews are we doing and how are they going, are some interview guides or interviewers scoring very differently from the rest, and do interview scores predict how hires actually do?
There are three views, from activity to accuracy:
| View | Where | Use it to |
| - | - | - |
| **Interview Overview** | Company **Dashboard** menu | Track interview volume, scores and workload across your account. |
| **Interviews** | A job req's **Dashboard** tab | Do the same for one job req. |
| **Interviewers** and **Interview Questions** | A job profile's **Dashboard** tab | Check interview scores against how hires went on to perform. |
## Company-wide
Click **Dashboard** in the top navigation and choose **Interview Overview**. It shows every job req in your account; use the **Job Profile** and **Job Req** controls to focus. Other controls include **Application Date**, **Interview Date**, **Hiring Class**, **Candidate Status**, **Interview Guide** and **Interviewer Name**.

### Volume and workload
| Visual | What it shows |
| - | - |
| **Completed Interviews** | Interviews marked complete. |
| **Total Interview Guides Submitted** | Interview guides your interviewers submitted. |
| **Total Upcoming Interviews** | Scheduled interviews still to come. |
| **Estimated Total Interview Time (Hours)** | An estimate of the hours your team spent on interviews. |
| **Interviews By Status** | Interviews that are **Complete**, **Scheduled**, **Canceled** or **Not Scheduled**. |
| **Interviews by Type Over Time**, **Interviews by Job Req** and **Interviews by Job Req Over Time** | Where your interview time goes, by interview guide and by job req. |
| **# of Interviews by Interviewer** and **Interviews Over Time by Interviewer** | How the load is spread across interviewers. |
| **Upcoming Interviews** | A table of interviews scheduled for future dates. |
### Scores and calibration
| Visual | What it shows |
| - | - |
| **Average Interview Score** | The average score of submitted interviews. |
| **Interview Score Distribution** | How many interviews got each score. Expect a rounded hump in the middle; a pile-up at the top usually means scores are inflated. |
| **Average Score by Interview** | The average score for each interview guide, with a line for the overall average. |
| **Avg. Score by Interviewer** | The average score each interviewer gives, with the same average line. |
| **Average Score by Interview Over Time** | Each guide's average score by week. |
| **Avg. Score by Interviewer & Status** | Each interviewer's average score, split by the candidate's current status, such as **Hired**. |

### Interview detail tables
At the bottom, **Interviewer Activity by Interviewer** lists every interview. **Interviewer Effort - By Step** and **Interviewer Effort By Interviewer** group interviews by step, guide, interviewer and candidate status; **Interviewer Effort - By Step** includes a link to each scorecard.
## For one job req
Open the job req, click its **Dashboard** tab, then **Interviews**. It shows the same kinds of numbers for that job req: completed and upcoming interviews, guides submitted, the average interview score and estimated interview time, interviews by status, the score distribution and trends over time, average score by interview guide, and interviews completed by each interviewer.
## Interviewer accuracy and interview questions
Calibration tells you whether interviewers agree with each other. Accuracy tells you whether they're right. On a job profile's **Dashboard** tab, two views compare interview scores with how the people you hired went on to perform. They need performance data for your employees. See [Quality of hire](/reporting/turnover-and-performance).
* **Interviewers**: each interviewer's **Accuracy**, which is how closely their interview scores matched the hire's later performance. 100% means their scores predicted performance exactly. Click the chart icon on a row to see each hire's interview score next to their performance.
* **Interview Questions**: which interview questions' scores go with better performance or retention, using the same correlation table as **Attributes**.

Open them under **Profiles**, then the job profile, then **Dashboard**. The same views are also in the company **Dashboard** menu as **Interviewers** and **Interview Questions**, across all job profiles. See [Quality of hire](/reporting/turnover-and-performance#interviewers) for how to read them.
## How teams use it
* **Calibrate guides.** An interview guide that averages far above or below the rest may have questions that are too easy or too hard. Review its scoring guidance before you change the questions.
* **Calibrate interviewers.** An interviewer who scores everyone a point higher than their peers isn't wrong on their own, but their scores can't be compared with anyone else's. Pair them with a calibrated interviewer for a few sessions.
* **Coach on accuracy.** Low **Accuracy** on a job profile's **Interviewers** tab means an interviewer's scores don't track how hires perform. That's a coaching conversation, backed by data.
* **Balance the load.** Use **# of Interviews by Interviewer** and **Upcoming Interviews** to spread interviews before people burn out.
## Related
> [card] [Interview guides](/interviews/interview-guides)
>
> Build the guides and questions interviewers score.
> [card] [Quality of hire](/reporting/turnover-and-performance)
>
> Interviewers and interview questions against performance.
> [card] [Recruiter productivity](/reporting/recruiter-productivity)
>
> Interviews submitted and interview time by person.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Job req dashboards
Source: https://help.journeyfront.com/reporting/job-dashboards
The six dashboard tabs on every job req, what each one answers, and where to learn more.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the job req: its hiring team, and users whose security role has *All Job Req Access*. Job req dashboards don't need *Company Dashboard Access*.
Every job req has a **Dashboard** tab with reports about that job req alone. Use it to check on a role you're hiring for right now. The tabs are already filtered to the job req, so there's no job profile or job req control to set. For trends across all of your job reqs, use the company dashboards; see [Dashboards overview](/reporting/dashboards).
## Open a job req's dashboards
Click **Job Reqs** in the top navigation, open the job req and click its **Dashboard** tab. It opens on **Overview**. Click the other tabs to switch dashboards.

## The tabs
| Tab | The question it answers | Learn more |
| - | - | - |
| **Overview** | How many people have applied, what's their status and how are they scoring? | [Applicant volume and pipeline](/reporting/candidate-overview#for-one-job-req) |
| **Interviews** | How many interviews have happened, how are candidates scoring, and how do interview guides and interviewers compare? | [Interview analytics](/reporting/interview-analytics#for-one-job-req) |
| **Hiring Process Fidelity** | Did the people we hired complete the activities in our workflow? | [Hiring process fidelity](/reporting/hiring-process-fidelity#for-one-job-req) |
| **Funnel Analytics** | Where do candidates drop out, how long does each step take, and how long does it take to hire? | [Funnel and drop-off](/reporting/funnel-analytics#for-one-job-req), [Time to hire](/reporting/time-to-hire#for-one-job-req) |
| **Language Assessment** | How are candidates scoring on language assessments? | [Language assessments](/assessments/language-assessments) |
| **Source Effectiveness** | Which sources bring in candidates and hires for this job req? | [Source effectiveness](/reporting/source-effectiveness#for-one-job-req) |
## Filter, bookmark and reset
Each tab has **Controls** at the top to filter it, for example by **Application Date**, **Source Type** or **Source**. Use the bookmark icon to save a set of filters and come back to it later, and the reset button to go back to the defaults. Bookmarks work the same as on company dashboards; see [Save your filters as bookmarks](/reporting/dashboards#save-your-filters-as-bookmarks).
## FAQ
> [accordion] Why don't I see a job req's Dashboard tab?
>
> You need access to the job req: be on its hiring team, or have *All Job Req Access*. If you can open the job req, the **Dashboard** tab is there.
> [accordion] The Language Assessment tab is empty.
>
> It only has data when the job req's workflow includes a language assessment and candidates have taken it. See [Language assessments](/assessments/language-assessments).
> [accordion] Why doesn't the dashboard match the Candidates tab?
>
> Dashboards count by the date and filters in their **Controls**. Clear the filters or match the date range before comparing.
> [accordion] Can I export a job req's data?
>
> For a spreadsheet of the job req's candidates, open its **Candidates** tab and click **Actions**, then **Export Data**, or use **Export Data** in the job req's own **Actions** menu. See [Export data](/lists-and-exports/export-data).
## Related
> [card] [Dashboards overview](/reporting/dashboards)
>
> Company-wide dashboards across all job reqs.
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Read a job req's funnel step by step.
> [card] [Source effectiveness](/reporting/source-effectiveness)
>
> Which channels bring in hires.
> [card] [Export data](/lists-and-exports/export-data)
>
> Download a job req's candidates to a spreadsheet.
# Recruiter productivity
Source: https://help.journeyfront.com/reporting/recruiter-productivity
See what each recruiter does in Journeyfront, what comes of their candidates, and how long their hires stay.
> [!NOTE]
>
> **Who can do this:** Users with *Company Dashboard Access*.
**The questions it answers:** what is each person on the team doing, how do their candidates turn out, and how long do their hires stay?
Click **Dashboard** in the top navigation and choose **Recruiter Productivity**. It shows every job req in your account; use the **Job Profile** and **Job Req** controls to focus. Other controls include **Date Range**, **Location**, **Source Type**, **Source**, **User** and **Hiring Class**.
The dashboard has three sheets, and they give credit in two different ways:
| Sheet | Counts by | Means |
| - | - | - |
| **Recruiter Productivity** | The user who did the action | What each person did. Actions Journeyfront took automatically show as **System Action**. |
| **Recruiter Effectiveness** | The candidate's current assigned user | How each recruiter's candidates turned out. |
| **Recruiter Outcomes** | The candidate's current assigned user | How long each recruiter's hires stayed. |
> [!NOTE]
>
> **Recruiter Effectiveness** and **Recruiter Outcomes** use whoever is assigned to the candidate now. If you reassign or unassign a candidate, their results move with them right away, including past hires.
## Recruiter Productivity sheet
Each metric has a total per user on the left and a monthly line per user on the right.

| Visual | What it counts |
| - | - |
| **Candidate Steps Changed - By User** | Times a user changed a candidate's step. |
| **Interviews Submitted - By User** | Times a user submitted an interview. |
| **Emails Sent - By User** | Times a user sent an email from Journeyfront. |
| **User Assignments Made - By User** | Times a user assigned a candidate to someone. |
| **Candidates Rejected - By User** | Times a user marked a candidate as rejected. |
| **Candidates Rejected - By Rejection Reason & User** | A heat table of each user's rejections by reason. Darker cells mean more. |
## Recruiter Effectiveness sheet
Each metric has a bar per assigned user and a line by application quarter.
| Visual | What it shows |
| - | - |
| **Number of Hires - By Assigned User** | The user's assigned candidates who were hired. |
| **Average Time to Hire (Days)** and **Median Time to Hire (Days) - By Assigned User** | Days from application to being marked hired, for the user's candidates. See [Time to hire](/reporting/time-to-hire). |
| **Candidates Per Hire - By Assigned User** | The user's assigned candidates divided by their hires. |
| **Interviews per Hire - By Assigned User** | Interviews for all of the user's candidates divided by their hires. |
| **Candidates Interviewed Per Hire - By Assigned User** | The user's interviewed candidates divided by their hires. |
| **Interviews Per Hired Candidate - By Assigned User** | Interviews for the user's hired candidates divided by their hires. |
| **Median Interview Completion Time (Minutes) - By Interviewer** | A heat table of how many minutes each interviewer takes to complete each interview guide, from starting the interview to completing it. |

## Recruiter Outcomes sheet
This sheet needs employee data for your hires, such as start and end dates. See [Quality of hire](/reporting/turnover-and-performance#where-the-data-comes-from). It adds a **Minimum Hires** control, so you can leave out users with only a few hires.
* **Average New Hire Tenure - By Assigned User**: total days employed divided by the number of hires, for each user's hires.
* **New Hire Outcomes - By Assigned User**: a table of each hire with their position, job req, hire date, start date, end date, tenure in days and average overall performance.
## How teams use it
* **Read activity next to results.** Lots of steps changed with few hires can mean a high-volume role, or busywork. Compare **Recruiter Productivity** with **Recruiter Effectiveness** before drawing conclusions.
* **Check rejection habits.** In **Candidates Rejected - By Rejection Reason & User**, a user who leans on one reason far more than their peers may need a refresher on your reasons.
* **Book interviews for the right length.** **Median Interview Completion Time (Minutes) - By Interviewer** shows how long each guide really takes, so you can size interview slots.
* **Reward hires who stay.** **Recruiter Outcomes** shows whose hires last, which is a better measure than hires alone.
## Related
> [card] [Time to hire](/reporting/time-to-hire)
>
> How long hiring takes, including by assigned user.
> [card] [Interview analytics](/reporting/interview-analytics)
>
> Interview scores and interviewer calibration.
> [card] [Quality of hire](/reporting/turnover-and-performance)
>
> Where outcome data comes from.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Screening question analytics
Source: https://help.journeyfront.com/reporting/screening-questions-analytics
See how candidates answer your screening questions, which questions they stop at, and whether an answer goes with getting hired, staying and performing.
> [!NOTE]
>
> **Who can do this:** The company **Screening Questions** and **Funnel Analytics** dashboards need *Company Dashboard Access*. A job req's **Funnel Analytics** tab needs access to that job req.
**The questions it answers:** how do candidates answer each screening question, which questions make them quit, and does an answer actually tell you anything about who gets hired and who succeeds?
Two dashboards cover screening questions:
* **Screening Questions** looks at the answers: how often each answer is given, how many people with each answer were hired, and how those hires did.
* The **Screening Question Fallout** sheet on **Funnel Analytics** looks at the questions themselves: where candidates stop answering and how long each question takes.
## The Screening Questions dashboard
Click **Dashboard** in the top navigation and choose **Screening Questions**. Pick a question in the **Question** control first; the charts show the answers to that one question. Like every company dashboard, it covers every job req in your account, so use the **Job Profile** and **Job Req** controls to focus. Other controls include **Application Date**, **Hiring Class**, **Source Type** and **Source**.

| Visual | What it shows |
| - | - |
| **Responses Over Time** | How many candidates gave each answer, by month. Hover to see the count and average score for each answer. |
| **Total Hires by Answer** | How many candidates with each answer were hired. |
| **Response Count Threshold** | A slider that hides answers with fewer responses than the number you set, so rare answers don't skew the charts below it. |
| **Average Performance Score** and **Average Performance at 30, 60 and 90 Day Evaluation** | How hires with each answer were rated. These need performance data for your employees. |
| **Answer Counts** | Each answer split by candidate status: **Active**, **Hired**, **Incomplete**, **New** and **Rejected**. |
| Tenure by answer | How many hires with each answer stayed 30, 60 and 90 days, based on their start and end dates. |
Tables at the bottom list details for each question and each candidate's response.
## Screening Question Fallout
On **Funnel Analytics**, open the **Screening Question Fallout** sheet. On the company dashboard, pick a job req first; or open a job req's **Dashboard** tab, then **Funnel Analytics**. See [Funnel and drop-off](/reporting/funnel-analytics#read-it-one-job-req-at-a-time).
| Visual | What it shows |
| - | - |
| **Question Response Fallout** | For everyone who reached each question, how many answered and how many didn't, grouped by step and activity. |
| **Median Question Response Time (Sec.)** | The median seconds candidates spent answering each question. |
| **Question Detail** | A table of each question with how many candidates started it, answered it and didn't, the median time and the average score. |

## How teams use it
* **Find the question people quit at.** A question where the not-answered column jumps, or the response time is much longer than the rest, is confusing or asks for too much. Reword it or move it later.
* **Test your knockouts.** If hires with an answer you screen out would have performed as well as everyone else, the knockout is costing you candidates. Check **Average Performance Score** and tenure by answer before you make a question disqualifying.
* **Keep what predicts.** An answer that goes with more hires, better ratings or longer tenure is worth weighting in your scoring. An answer that makes no difference may not be worth asking.
## Related
> [card] [Screening questions](/assessments/screening-questions)
>
> Write and score the questions.
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Where candidates leave the rest of your process.
> [card] [Quality of hire](/reporting/turnover-and-performance)
>
> Where performance and tenure data comes from.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Source effectiveness
Source: https://help.journeyfront.com/reporting/source-effectiveness
See which sources and source types bring in candidates, hires and hires who stay, so you can spend your sourcing budget where it works.
> [!NOTE]
>
> **Who can do this:** The company **Source Effectiveness** dashboard needs *Company Dashboard Access*. A job req's **Source Effectiveness** tab needs access to that job req.
**The question it answers:** which channels bring us candidates who get hired, and hires who stay and perform?
Every Candidate Application has a **Source**, such as Indeed, a job fair or a referral, and each source belongs to a **Source Type**. Source Effectiveness compares them, from applications through to how long hires last. It's only as good as your source data, so record sources consistently. [Magic links](/sourcing/magic-links) tag applicants with a source automatically.
## Source or source type
The **Analysis Level** control switches every chart on the dashboard between single **Source** values and **Source Type** groups. Check which one is set before you read the charts. Start with **Source Type** for the big picture, then switch to **Source** to compare individual channels.
## Company-wide
Click **Dashboard** in the top navigation and choose **Source Effectiveness**. It shows every job req in your account; use the **Job Profile** and **Job Req** controls to focus. It has three sheets: **Effectiveness Analysis**, **Post-Hire Effectiveness** and **Exportable Data**.

### Effectiveness Analysis
| Visual | What it shows |
| - | - |
| **Source Effectiveness (Hire % by Source)** | Hires from each source divided by candidates from that source. |
| **Avg. Overall Score by Source** | The average overall score of candidates from each source. |
| **Candidates Sourced** and **Hires Sourced, by Source** | How many applications and hires each source brought in, as counts and as a share of the total. |
| **Candidates Interviewed, by Source** | Candidates from each source with at least one interview. Several interviews for one candidate count once. |
| **Candidates Sourced Over Time**, **Interviews Sourced Over Time** and **Hires Sourced Over Time** | The same numbers by application month, one line per source. |
| **Candidates Sourced** and **Hires Sourced, by Location & Source** | The source mix at each location. |
| **Candidates Sourced** and **Hires Sourced, by Job Req & Source** | The source mix for each job profile or job req. |
| **Median Time To Hire Over Time, by Source** | How fast candidates from each source get hired. See [Time to hire](/reporting/time-to-hire). |
### Post-Hire Effectiveness
This sheet follows hires from each source after they start. It needs employee data: start dates, end dates and performance results. See [Quality of hire](/reporting/turnover-and-performance#where-the-data-comes-from). Its date control is the hire's **Start Date**.
* **Hires with 30 Days Tenure, by Source** (and 60 days, 90 days and 6 months): the share of each source's hires who made it that long, who left before, and who haven't been there that long yet.
* **Avg. Performance at 30 Days, by Source** (and the other windows): how hires from each source were rated in that window.
* **Avg. Score, by Outcome Attribute & Source**: a heat map of performance results by source. Use the **Time Between Start Date and Evaluation Date** dropdown above it to pick the window.

### Exportable Data
The **Exportable Data** sheet lays the numbers out as tables, such as each source's candidates, average overall score, hires and hire percentage, and how many of each source's candidates reached each step and completed each activity.
## For one job req
Open the job req, click its **Dashboard** tab, then **Source Effectiveness**. It has the **Effectiveness Analysis** and **Exportable Data** sheets, filtered to that job req. There's no **Post-Hire Effectiveness** sheet on a job req; use the company dashboard with the **Job Req** control for that.
## How teams use it
* **Judge channels by hires, not applicants.** A source with lots of applicants and a low **Hire %** costs your recruiters time. A smaller source with a high hire rate and high scores may deserve more budget.
* **Check who stays.** Compare 90-day tenure by source on **Post-Hire Effectiveness**. A source whose hires leave early is more expensive than it looks.
* **Look per location.** The source mix often differs by site. Use **by Location & Source** before moving budget across your whole account.
* **Clean up vague sources.** If a large share of candidates has no source or a catch-all one, use magic links for every ad and post, and keep your source list short.
## FAQ
> [accordion] Why are many candidates missing a source?
>
> Sources come from your links, your integrations and your team. Use [magic links](/sourcing/magic-links) so every channel tags its applicants. See [Sources](/sourcing/sources).
> [accordion] Why is the Post-Hire Effectiveness sheet empty?
>
> It needs employee data: start dates, end dates for people who left, and performance results. See [Quality of hire](/reporting/turnover-and-performance).
## Related
> [card] [Sources](/sourcing/sources)
>
> How sources and source types work.
> [card] [Magic links](/sourcing/magic-links)
>
> Tag every applicant with where they came from.
> [card] [Quality of hire](/reporting/turnover-and-performance)
>
> Turnover and performance by job profile.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Time to hire
Source: https://help.journeyfront.com/reporting/time-to-hire
See how many days it takes to hire, by job, location and recruiter, and find the step that slows you down.
> [!NOTE]
>
> **Who can do this:** The company **Time To Hire** and **Funnel Analytics** dashboards need *Company Dashboard Access*. A job req's **Funnel Analytics** tab needs access to that job req.
**The question it answers:** how long does it take us to hire, where is it slower, and which step is holding it up?
**Time to hire** is the number of days from when a candidate applied to when they were marked as hired in Journeyfront. Every time to hire number on the dashboards uses this definition.
Dashboards show it two ways:
* **Median:** the middle value. Half your hires took less time and half took more. This is the best headline number, because a few very slow hires don't pull it up.
* **Average:** the total days divided by the number of hires. A handful of slow hires can raise it a lot, so a big gap between the average and the median means you have outliers.
## Company-wide
Click **Dashboard** in the top navigation and choose **Time To Hire**. It shows every job req in your account; use the **Job Profile** and **Job Req** controls to focus. Other controls include **From** and **To** (application date), **Candidate Country**, **Candidate Region/State**, **Candidate City**, **Assigned User**, **Source Type** and **Source**.

| Visual | What it shows |
| - | - |
| **Average Time to Hire (Days)** and **Median Time to Hire (Days)** | The headline numbers for your filters. |
| **Avg. Time to Hire by Hire Date** and **Median Time To Hire By Hire Date** | The same numbers by the month people were hired, so you can see the trend. |
| **Time to Hire Distribution (Days)** | How many hires took each number of days. The long tail on the right is your slow hires. |
| **Median Time To Hire By Job** and **Average Time To Hire By Job** | Time to hire per job profile. Drill down to see each job req. |
| **Median Time To Hire by Location** and **Average Time To Hire by Location** | Time to hire by the job req's location. Drill between country, state, city and ZIP code. |

## The Funnel Analytics Time to Hire sheet
The **Funnel Analytics** dashboard has its own **Time to Hire** sheet. It adds two things the Time To Hire dashboard doesn't have:
* **Median Time to Hire by Assigned User**: how fast each recruiter's candidates get hired.
* **Recent Hire Information**: a table of each hire, with their application start, hiring class, hire date, start date, assigned user and days to hire. Use it to check the people behind a number.
On the company dashboard, pick a job req first. See [Funnel and drop-off](/reporting/funnel-analytics#read-it-one-job-req-at-a-time).
## For one job req
Open the job req, click its **Dashboard** tab, then **Funnel Analytics**, then the **Time to Hire** sheet. The **Overview** sheet also shows **Average Time to Hire (Days)** at the top.
## Find the step that slows you down
Time to hire tells you how long; time in step tells you where. On **Funnel Analytics**:
* **Median Time in Each Step (Days)** on the **Overview** sheet shows how long candidates spend in each step.
* **Time in Step Distribution** on the **Step Analysis** sheet shows how many candidates sat in each step for less than 15 minutes, a day, a week and so on, so you can see the long tail.
* **Median Days in Step by Job Req** on the **Compare Job Reqs** sheet compares the same steps across job reqs.
## How teams use it
* **Report the median.** Use **Median Time to Hire** for your monthly number and watch the trend line by hire date. Look at the average only to spot outliers.
* **Find slow sites.** Find the slowest city on the location chart, then compare that site's steps with a fast one's on **Compare Job Reqs**. The difference is often one step, such as a manager interview that waits for availability.
* **Shorten waits, not assessments.** If candidates finish a step quickly but wait days to be moved on, the delay is on your side. Automation rules or faster scheduling can close that gap.
* **Coach by recruiter.** **Median Time to Hire by Assigned User** and the [Recruiter productivity](/reporting/recruiter-productivity) dashboard show whose candidates move fastest.
## FAQ
> [accordion] Does time to hire end when the offer is accepted or when the candidate starts?
>
> Neither. It ends when the candidate is marked as hired in Journeyfront. Start dates are reported separately, for example in **Recent Hire Information**.
> [accordion] Why is the average so much higher than the median?
>
> A few hires that took a very long time pull the average up. The median isn't affected by them, so use it as your headline number.
## Related
> [card] [Funnel and drop-off](/reporting/funnel-analytics)
>
> Where candidates leave, and how long each step takes.
> [card] [Recruiter productivity](/reporting/recruiter-productivity)
>
> Time to hire and more by recruiter.
> [card] [Applicant volume and pipeline](/reporting/candidate-overview)
>
> Applicants, hires and hiring classes.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Where dashboards live and how to filter them.
# Quality of hire
Source: https://help.journeyfront.com/reporting/turnover-and-performance
See how long your hires stay and how they perform, which parts of your hiring predict it, and how to get the outcome data in.
> [!NOTE]
>
> **Who can do this:** A job profile's **Dashboard** tab needs access to that job profile. The company versions need *Company Dashboard Access*. Seeing the employees behind the charts needs *Performance Access*. Recording a separation needs access to the employee's record; the **Employees** page needs *All Employee Access*.
**The questions it answers:** do the people we hire stay and perform, and does what we measure during hiring predict it?
A hiring process is only as good as the people it hires. Quality of hire reporting follows your hires after they start: how long they stay, why they leave and how they perform. Then it turns around and checks which attributes, activities, interview questions and interviewers predicted those results.
## Where the data comes from
Quality of hire reporting reads your employee records: each employee's job, **Start Date**, **End Date** and **Separation Reason**, plus their performance results.
| Data | How it gets into Journeyfront |
| - | - |
| Employees and start dates | Hiring a candidate creates their employee record with a start date. Your HR system's employee sync and **Employee Data Import** add employees too. See [Hire candidates](/onboarding/hire-candidates). |
| End dates and separation reasons | Recorded on the employee record (see below), brought in by your HR system's employee sync, or imported. |
| Performance | Performance reviews your team submits (**Start**, then **Performance Review**), or **Employee Performance Data Import**. See [Performance reviews](/employees/performance-reviews). |
If your HR system is connected and its employee sync is on, an employee who's terminated in your HR system gets an end date in Journeyfront on the next sync, with a separation reason: the one mapped from your HR system, or a general one when your HR system doesn't send a reason. See [HRIS integrations](/integrations/hris#sync-employees-from-your-hr-system).
Imports are under **Settings**, then **Import Data**. See [Importing data](/account-setup/importing-data).
### Record that an employee left
**1. Open the employee**
Click **Employees** in the top navigation and select the employee.
**2. Open Job Info**
Click the **Job Info** tab.
**3. Mark that they no longer work here**
Untick **Employee currently works here** and enter the **End Date**.
**4. Add the reason**
Choose a **Reason for Separation** (required) and add a **Separation Note** if it helps.
**5. Save**
Click **Save**. Turnover reporting includes the change.

Your list of separation reasons is under **Settings**, then **Custom Options**, then **Separation Reasons**. See [Rejection and separation reasons](/account-setup/rejection-reasons).
> [!TIP]
>
> Turnover reporting is only as good as your separation reasons. Keep the list short and clear, and make sure everyone who records separations uses it the same way, so you can tell early resignations from terminations.
## Open a job profile's Dashboard
Quality of hire reads best one role at a time, because what makes a great customer care associate isn't what makes a great collections agent. Click **Profiles** in the top navigation, open the job profile and click its **Dashboard** tab. Then pick a view: **Attributes**, **Activities**, **Interview Questions**, **Interviewers**, **Turnover** or **Performance**. See [Job profiles](/employees/job-profiles#profile-dashboards).
## Turnover
**Turnover** shows when and how fast your hires leave. Set **From date** and **To date**, choose **Month**, **Qtr**, **6 Mo** or **Year**, and filter by **Separation Reason** or by a multiple-choice employee job field with **Job Field**.

| Chart | What it shows |
| - | - |
| **Turnover By Hire Date** | For each group of hires, the share still employed and the share who left within 30, 60 or 90 days, 180 days, a year, two years, or after two years. A second chart shows the same as counts. |
| **Turnover After Hire Date** | How many people left in each month after they started, for the first two years. |
| **Turnover Time of Year** | How many people left in each calendar month. |
Click a bar to see the employees in it, with their job title, start and end dates, tenure and separation reason.
> [!TIP]
>
> Look at **Turnover After Hire Date** first. If many people leave in the first month or two, the problem is often expectations set during hiring, like how the job, pay or schedule was described, rather than the hires themselves.
## Performance
**Performance By Hire Date** groups your employees by when they were hired and shows the share at each performance rating, from **Exceptional** to **Very Poor**, so you can see whether newer groups of hires do better than earlier ones. Choose the **Performance Type** and **Performance Period**, and use the same dates, period and **Job Field** filter as on Turnover. A second chart shows the same as counts. Click a bar to see the employees in it.

## Attributes and activities
**Attributes** ranks the attributes you measure, such as Customer Focus or Problem Solving, by how closely candidates' scores went with how they did after they were hired. **Activities** does the same for the activities in your workflow, such as an assessment or a typing test.
Choose what to compare against in **Top Attributes Correlated with**: **Overall Performance** or **Employee Retention**. For performance, narrow it by **Performance Type**; for retention, by **Separation Reason**. Then set **From Date** and **To Date**.

| Column | What it means |
| - | - |
| **Correlation** | How strongly the score goes with the outcome, from 0 (no relationship) to 1 (a perfect one). One star means the result is significant at the 5% level, two stars at the 1% level; stars appear only when there are at least 30 employees. **Insufficient Data** means there's no relationship to show or fewer than 10 employees. |
| **Statistical Significance** | The p-value: how likely a relationship this strong would show up by chance. Smaller is better; under .05 is the usual bar. |
| **Employees** | How many employees have both a score and an outcome. |
| **−** and **+** | Whether the relationship is negative or positive. The bar is blue when the correlation is 0.3 or more, gray when it's weaker. |
| Chart icon | Shows each employee's score against their outcome. |
Hover over the info icon next to an attribute to see its description. See [Attributes](/scoring/attributes).
> [!TIP]
>
> Look for relationships that are strong, statistically significant and based on plenty of employees. A strong result from a dozen people is a hint to keep watching, not a reason to change your workflow.
## Interview Questions
**Interview Questions** uses the same table for individual interview questions, with an **Attribute(s) Measured** column. Use it to keep the questions whose scores predict performance or retention and to rework the ones that don't predict anything. See [Interview guides](/interviews/interview-guides).
## Interviewers
**Interviewers** lists each interviewer with the number of **Candidates** and **Interviews** behind their result and their **Accuracy**: how closely their interview scores matched the hire's later performance. 100% means their scores predicted performance exactly. Click the chart icon on a row to see each hire's interview score next to their performance. See [Interview analytics](/reporting/interview-analytics).
## The company versions
**Attributes**, **Interview Questions**, **Interviewers**, **Turnover** and **Performance** are also in the company **Dashboard** menu. They work the same way across every job profile in your account, which is useful for an account-wide turnover picture. For attributes, interview questions and interviewers, the job profile's own **Dashboard** tab gives a clearer answer, because it compares people in the same role.
## Other views of quality of hire
| Question | Where |
| - | - |
| Do hires from some sources stay longer or perform better? | **Source Effectiveness**, on the **Post-Hire Effectiveness** sheet. See [Source effectiveness](/reporting/source-effectiveness). |
| How long do each recruiter's hires stay? | **Recruiter Productivity**, on the **Recruiter Outcomes** sheet. See [Recruiter productivity](/reporting/recruiter-productivity). |
| Do hires who gave a certain screening answer perform better or stay longer? | **Screening Questions**. See [Screening question analytics](/reporting/screening-questions-analytics). |
| Do hires score higher than applicants overall? | **Candidate Overview**, comparing **Avg Overall Score of Applicants** with **Avg Overall Score of Hires**. See [Applicant volume and pipeline](/reporting/candidate-overview). |
## Close the loop
Outcome data makes the rest of your hiring smarter:
* **Check what you measure.** Use **Attributes**, **Activities** and **Interview Questions** to keep what predicts success and drop what doesn't.
* **Predict success.** Journeyfront builds predictive models for your roles from your employees' outcomes, such as performance and turnover. Candidates then get a predictive score that can count toward their overall score. See [Predictive models](/scoring/predictive-models).
* **Coach interviewers.** Use **Interviewers** accuracy to calibrate your panel.
> [!TIP]
>
> Even without a predictive model, start collecting outcome data now. Every hire with a start date, an end date or a performance review adds to the history a model can learn from later. The [behavioral assessment](/assessments/behavioral-assessment) is made for exactly this.
## FAQ
> [accordion] Why is the Turnover dashboard empty?
>
> It needs employee records with start dates, and end dates for anyone who left. Check that hires are being recorded (hiring a candidate creates the record) and that separations are entered on the employee's **Job Info** tab, synced from your HR system or imported. Also check your date range and filters.
> [accordion] Why does Attributes say Insufficient Data?
>
> A correlation needs at least 10 employees with both a score and an outcome. Widen the date range, or wait until more of your hires have performance reviews or separations recorded.
> [accordion] Why can't I click into a chart?
>
> Seeing the employees behind the charts needs *Performance Access*. Ask your Journeyfront admin to check your security role.
> [accordion] Where do performance scores come from?
>
> From performance reviews your team submits under **Start**, then **Performance Review**, and from performance data imported under **Settings**, then **Import Data**. See [Performance reviews](/employees/performance-reviews).
> [accordion] Does Journeyfront update end dates from our HR system?
>
> Yes, when your HR system is connected and its employee sync is on. Employees terminated in your HR system get an end date and a separation reason on the next sync. See [HRIS integrations](/integrations/hris).
## Related
> [card] [Predictive models](/scoring/predictive-models)
>
> Turn your outcome data into a predictive score for candidates.
> [card] [Job profiles](/employees/job-profiles)
>
> Where each role's Dashboard tab lives.
> [card] [Performance reviews](/employees/performance-reviews)
>
> Record how employees perform.
> [card] [Employee records](/employees/employee-records)
>
> Where start dates, end dates and separations live.
# AI resume scoring
Source: https://help.journeyfront.com/scoring/ai-resume-scoring
Score every resume against the job's attributes, with the evidence highlighted and your team in control.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission turn on and set up AI resume scoring for a job req. Anyone who can view a Candidate Application can review and edit its resume score.
>
> **Availability:** AI resume scoring needs to be turned on for your account. Ask your Customer Success Manager.
AI resume scoring reads each candidate's resume and scores it against the attributes you've already set for the job, on the same 1 to 5 scale as the rest of the workflow. The score appears next to the resume with the lines that support it, and it counts toward the candidate's overall score like any other activity. When hundreds of people apply, your team can start with the strongest resumes instead of reading every one first.
## People stay in control
* **AI informs decisions; people make them.** A resume score is one input among many. It doesn't hire or reject anyone on its own.
* **Every score shows its reasoning,** and highlights the lines of the resume behind it, so you can check the evidence yourself.
* **Your team can change any score.** Edits are recorded, so you can always tell AI scores from scores a person reviewed.
* **Your data stays yours.** Candidate data isn't used to train the AI provider's models.
## Turn it on for a job req
**1. Open AI Resume Scoring**
Open the job req and go to **Setup**, then **AI Resume Scoring**. Switch it from **Off** to **On**.
**2. Choose when to score**
Turn on **Auto Score New Resumes** to score every new resume as candidates apply. Leave it off to score candidates one at a time.

**3. Choose the attributes**
Under **Attributes to Score**, switch **Score** to **On** for each attribute the resume should be scored on, and set its **Weight**. The weight decides how much the resume counts as a way of measuring that attribute. Attributes are listed by attribute group; switching one **Off** leaves it out of AI resume scoring only.

**4. Add guidance (optional)**
Use an attribute's **Guide** for guidance about that one attribute, or **Additional Resume Scoring Instructions** for guidance that applies to every resume for this job. For example: "This role is fully on-site, so treat remote-only experience as a gap."

**5. Save**
Click **Save**.
> [!TIP]
>
> Give the resume a higher weight for attributes it shows well, like years of customer service experience, and a lower weight for attributes an interview or assessment measures better. The list shows the attributes in the job req's attribute groups. If one you want isn't listed, add it to a group on the job req's **Attributes** page first.
> [card] [Attributes](/scoring/attributes)
>
> Set up the attribute groups that resumes are scored against.
## Where resume scores show up
Once a resume is scored, its score appears in four places.
**Candidate lists.** Sort or filter by the **AI Resume Score** column to start with your strongest applicants. Click a score to open its breakdown on the **Resume** tab.

**The Score tab.** Each attribute group shows the resume's score in its own **Resume** column. Expand an attribute to see the **AI Resume Review** line behind it.

**The Steps tab.** An **AI Resume Review** activity appears under the **Application Form** step, at the top.

**The Resume tab.** The **AI Resume Score** panel sits beside the resume, with the overall resume score, a summary, and each attribute's score and reasoning. The next section walks through it.

## Review a candidate's resume score
**1. Open the Resume tab**
Open the candidate's Candidate Application and select the **Resume** tab. The resume is on the left and the **AI Resume Score** is on the right. Click **Hide** to give the resume the full width, and **AI Resume Score** to bring the panel back.
**2. Read the summary**
At the top you'll see the overall resume score and a short summary of the fit. Below it, each attribute shows its **Score**, its **Weight** and a sentence explaining why.
**3. Check the evidence**
Each attribute has its own color, matching the phrases highlighted in the resume that support its score. All highlights are on to start; click an attribute to turn its highlights off or back on. Highlights appear in the **Parsed Text** view; **Original** shows the file exactly as the candidate uploaded it.
If the candidate hasn't been scored yet, click **Generate score**.

> [!TIP]
>
> A score backed by very little highlighted text is a cue to read that part of the resume yourself. If an attribute scored low and nothing is highlighted, the resume simply doesn't mention it.
## Change a score you disagree with
**1. Edit the attribute**
On the **Resume** tab, hover over the attribute and click the pencil icon, **Edit score and reasoning**.
**2. Enter your score**
Enter a score from 1 to 5 and update the reasoning to explain your judgment.
**3. Save**
Click **Save**. The overall resume score and the summary update, and the attribute is marked as edited by a person.

## When a resume is scored or re-scored
A resume is scored on its own only when **Auto Score New Resumes** is on for the job req. Otherwise, scoring happens when someone on your team asks for it.
| Situation | Auto Score New Resumes on | Auto Score New Resumes off |
| - | - | - |
| A candidate uploads a resume, or a new one is uploaded for them | Scored automatically | Not scored. Click **Generate score** on the **Resume** tab, or **Regenerate** if it already has a score |
| Someone opens the **Resume** tab of a candidate with no score yet | Scored then | Shows **Generate score** |
| The job req's setup changes (attributes, weights, guides, instructions, description or workflow) | Re-scored the next time someone opens the candidate's **Resume** tab | The existing score stays as it is |
| Someone clicks **Regenerate** at the top of the **AI Resume Score** panel | Re-scored right away | Re-scored right away |
> [!WARNING]
>
> Re-scoring replaces the whole score, including any edits your team made, whether you click **Regenerate** or it happens on its own. Note any changes you want to keep first.
## FAQ
> [accordion] Is the AI deciding who gets hired?
>
> No. The resume score is decision support. Your team sees the reasoning and the evidence, can change any score, and makes the call.
> [accordion] Does the resume score change a candidate's overall score?
>
> Yes. It counts like any other measurement, alongside screening questions and assessments, so a strong or weak resume moves where the candidate ranks.
> [accordion] If I change the attributes or instructions, are past scores updated?
>
> Not right away. With **Auto Score New Resumes** on, a candidate is re-scored the next time someone opens their **Resume** tab. With it off, click **Regenerate** on the candidates you want re-scored. Either way, re-scoring replaces any manual edits.
> [accordion] What happens if a candidate has no resume?
>
> No resume score is produced. The **Resume** tab shows that there's no resume on file, and you can upload one from there.
> [accordion] What can't the AI see?
>
> It only judges what's in the resume. It can't confirm that a claim is true, and it can't credit experience the candidate left out. Treat a low score as a prompt to look closer, not a verdict.
> [accordion] Is our candidate data used to train AI models?
>
> No. Customer data is not used to train the AI provider's models.
## Related
> [card] [AI-scored questions](/scoring/ai-scored-questions)
>
> Let AI score video, audio and written screening answers.
> [card] [Attributes](/scoring/attributes)
>
> The traits and skills resumes are scored against.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and how scores roll up.
# AI-scored questions
Source: https://help.journeyfront.com/scoring/ai-scored-questions
Let AI score video, audio and written screening answers against your criteria, with reasoning your team can review and change.
> [!NOTE]
>
> **Who can do this:** Turning AI scoring on for a question needs the *AI Scored Question Control* permission. Scoring a single answer needs *AI Score Single Question*. Editing or deleting AI scores needs *Edit AI Scores*. See [Permissions](#permissions).
>
> **Availability:** AI-scored questions need to be turned on for your account. Ask your Customer Success Manager.
For screening questions answered by video, audio or free-form text, AI can score each answer from 1 to 5 against your scoring criteria and explain why. Your team gets a consistent first read on every answer, without having to watch or read them all first, and the score counts toward the candidate's overall score like any other question.
## People stay in control
* **AI informs decisions; people make them.** An AI score is one input among many. It doesn't hire or reject anyone on its own.
* **Every score shows its reasoning,** so your team can see why an answer scored the way it did.
* **Your team can change any AI score,** with the right permission.
* **Permissions decide who does what.** You choose which security roles can turn AI scoring on, run it, and edit AI scores.
* **Your data stays yours.** Candidate data isn't used to train the AI provider's models.
## Turn on AI scoring for a question
**1. Open the question**
In the screening question builder, choose the **Text**, **Video Response** or **Audio Response** response type. **Score with Ai** only appears on screening questions with one of these response types.
**2. Turn on Score with Ai**
Switch on **Score with Ai**.

**3. Check the scoring criteria**
The AI scores answers against the question, the attribute it measures, that attribute's description and your scoring criteria. Make sure they describe what a weak, average and strong answer look like.

**4. Add instructions (optional)**
Add any extra guidance for this question in the additional instructions box, then save the question.
From then on, every answer to the question is scored automatically when the candidate submits it.
> [!TIP]
>
> The clearer your scoring criteria, the more consistent the scores. Criteria that describe observable behavior ("gives a specific example of calming an upset customer") work better than general labels ("good").
## Review and edit an AI score
**1. Open the Screenings tab**
Open the candidate's Candidate Application and select the **Screenings** tab.
**2. See the reasoning**
AI-scored answers show an **Ai score** label. Click it to see the score and the **Reasoning** behind it.
**3. Change it if you disagree**
Edit the answer's score as you would any other. Editing or deleting AI scores needs the *Edit AI Scores* permission.

## Score a single answer
To score one answer without turning on AI scoring for the whole question, or to score an answer submitted before you turned it on, click **Generate** under the answer's score on the **Screenings** tab. **Generate** shows on video, audio and text answers that don't have an AI score yet. The button shows **Thinking** while it works, and the score appears when it's ready. This needs the *AI Score Single Question* permission.

Changing a question's scoring criteria later doesn't re-score answers that were already scored.
## Permissions
To choose who can use AI-scored questions, go to **Settings**, then **Security**, and edit a security role.
| Permission | What it allows |
| - | - |
| *AI Scored Question Control* | Turn AI scoring on for screening questions. |
| *AI Score Single Question* | Send a single candidate's answer to be scored by AI. |
| *Edit AI Scores* | Edit or delete AI-generated candidate scores. |

## FAQ
> [accordion] Why is an AI-scored answer still pending?
>
> Scoring for video and audio answers starts a couple of minutes after they're submitted, so they take longer than text answers. While the AI works, the answer shows **Thinking**. After you click **Generate**, the score appears on its own when it's ready; for answers scored automatically, refresh the page to see it. If you're still waiting:
>
> * **AI scoring wasn't on when the candidate answered.** Answers are only scored automatically if **Score with Ai** was on when they were submitted. Click **Generate** to score earlier answers one at a time.
> * **The answer can't be AI scored.** Only **Text**, **Video Response** and **Audio Response** answers can be AI scored, and an empty answer isn't scored.
> * **Generate is grayed out.** Generating a score needs the *AI Score Single Question* permission. If you don't see **Generate** at all, AI scoring may not be turned on for your account.
>
> If an answer still shows **Thinking** after several minutes, refresh the page. If nothing changes, contact support with a link to the Candidate Application.
> [accordion] Is the AI making hiring decisions?
>
> No. AI scores are decision support. Your team sees the reasoning, can change any score, and makes the call.
> [accordion] If I change the scoring criteria, are past answers re-scored?
>
> No. Answers keep the score they got when they were scored, and an answer that already has an AI score can't be sent to the AI again. If you disagree with a score, change it by hand (this needs *Edit AI Scores*).
> [accordion] Does the AI watch or listen to the answer?
>
> Yes. For video and audio answers, the AI reviews the recording itself.
> [accordion] What can't the AI see?
>
> It only judges what's in the answer. It can't confirm that a claim is true. Treat a low score as a prompt to look closer, not a verdict.
> [accordion] Is our candidate data used to train AI models?
>
> No. Customer data is not used to train the AI provider's models.
## Related
> [card] [AI resume scoring](/scoring/ai-resume-scoring)
>
> Score resumes against the job's attributes.
> [card] [Screening questions](/assessments/screening-questions)
>
> Build the questions candidates answer.
> [card] [Attributes](/scoring/attributes)
>
> What each question measures.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and how scores roll up.
# Attributes
Source: https://help.journeyfront.com/scoring/attributes
The traits and skills you measure for a job, and how they shape a candidate's score.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* manage the attribute library. Users with the *Manage Job Req Settings* permission set up attributes on a job req.
An attribute is a trait or skill being measured, such as typing ability, communication or customer focus. Every skills test, screening question and interview question measures an attribute. Attributes are how Journeyfront turns very different activities into one clear picture of each candidate, and how you decide what matters most for each job req.
## How attributes fit together
> [card] Your attribute library
>
> Every attribute your account can use, from Journeyfront's standard set and your own.
> [card] Activities measure them
>
> Each question, test and assessment in a workflow measures one or more attributes.
> [card] Each job req picks what counts
>
> You group a job req's attributes and decide how much each one matters.
## The attribute library
Go to **Settings**, then **Attributes** to see every attribute on your account, with its **Name**, **Description** and **Type**. Attributes your team created are marked **Custom**.
* To add an attribute, click **Attribute** at the top of the list, then give it a name and description.
* To find one, search or filter the list by type.
* To change an attribute, click the edit icon on its row, then **Edit**. You can edit and delete only your own **Custom** attributes; Journeyfront's standard attributes are view-only.
* Deleting a custom attribute also removes it from the attribute groups of every job req that uses it.

> [!TIP]
>
> Write clear, specific descriptions. Interviewers rely on them to score consistently, and AI scoring uses them too.
## Measured vs. scored
An attribute is **measured** when something in a job req's workflow, like a screening question or a typing test, is set up to score it. It only counts toward a candidate's score once you add it to an **attribute group** on that job req's **Attributes** page.
That gives you control: a workflow can measure lots of things, and you choose which of them shape the score for this job.
## Set up attributes on a job req
Open the job req and go to **Setup**, then **Attributes**. Your attribute groups are on the left, and the attributes you can add are on the right.

**1. Create a group**
Click **Add Attribute Group** and name it, for example *Culture*, *Experience* or *Skills*.
**2. Add attributes to the group**
Drag an attribute by its handle from the list on the right onto the group, or click **Add** on the attribute and choose the group.
**3. Set how much each one matters**
Give each group, and each attribute in it, a weight that reflects its importance for this job (see below).
**4. Save**
Click **Save changes** to apply everything at once, or **Discard Changes** to start over.

Each attribute tells you four things. The numbers match the screenshot below.
1. **Where it's measured:** the activities that score it, such as *Application Questions* or *Interview*.
2. **Default or Custom:** **Default** attributes come from a standard Journeyfront activity; **Custom** attributes were created for your account.
3. **Whether it's in a group:** **Not added**, or **Added** with the number of groups it's in. The same attribute can belong to more than one group.
4. **How many questions or tests measure it:** once it's in a group, a count appears next to it. Expand the attribute to see each one.

> [!TIP]
>
> Name groups the way your hiring managers talk about the role. When they open a candidate's scores, the groups should match how they already think about a good hire.
### Decide how much each one matters
You can set importance at three levels:
* **Group:** how much the whole group counts compared with your other groups.
* **Attribute:** how much an attribute counts within its group.
* **Question or test:** expand an attribute to see everything that measures it, and decide how much each one counts.
Weights are relative. A higher number counts more than a lower one, and they don't need to add up to any total.

> [!TIP]
>
> When two activities measure the same attribute, give more weight to the one you trust more. A structured interview question on communication often tells you more than a quick screening question on the same attribute.
### Find attributes that aren't scored yet
A number next to **Attributes** in the job req's setup menu shows how many measured attributes aren't in a group yet. Open the **Not added yet** tab to see them.

| Tab | What it shows |
| - | - |
| **Not added yet** | Attributes the workflow measures that aren't in a group, so they aren't scored yet. |
| **In screening plan** | Everything the workflow measures. |
| **All attributes** | Your whole attribute library, including attributes nothing in this workflow measures yet. |
### Create a new attribute from a job req
If the attribute you need doesn't exist yet, open **All attributes** and search for it. Below the results, click **Create Attribute**, then add a name and description and click **Save**. The new attribute joins your library and you can add it to a group straight away.

### Reorder or remove
* Drag a group by its handle, or drag attributes within a group, to change the order. Candidates' scores display in this order.
* Click the trash icon on an attribute to remove it from a group, or on a group's header to delete the group.
Click **Save changes** when you're done. Saving updates the scores of candidates on this job req.
## See a candidate's attribute scores
Open a candidate's Candidate Application and select the **Score** tab. **Candidate Attribute Scores** shows your attribute groups in the order you set, each with its score on the 1 to 5 Job Adaptive Score scale. Expand a group to see its attributes, and expand an attribute to see the questions and tests behind it. Tests measured in their own units show the raw result under their score, such as a typing test's words per minute and accuracy or an internet speed test's Mbps.

Attribute scores are for your hiring team. Candidates don't see them.
## FAQ
> [accordion] Why isn't one of my attributes showing a score?
>
> Most likely it isn't in a group yet. Check the **Not added yet** tab on the job req's **Attributes** page and add it to a group. If it isn't on that tab either, nothing in the workflow measures it yet.
> [accordion] What's the difference between an attribute and an attribute group?
>
> An attribute is one trait or skill, like *Coachability*. An attribute group is a category you create on a job req, like *Skills*, to organize attributes. Attributes only count toward the score once they're in a group.
> [accordion] Can I add an attribute the workflow doesn't measure?
>
> Yes, from the **All attributes** tab. It won't produce a score until something in the workflow measures it.
> [accordion] When do my changes take effect?
>
> When you click **Save changes**. Saving updates the scores of candidates on that job req.
> [accordion] Do changes on one job req affect other job reqs?
>
> No. Groups and weights belong to each job req. Changes to an attribute's name or description in **Settings**, then **Attributes**, apply everywhere that attribute is used.
> [accordion] How do attribute scores become the overall score?
>
> Each attribute's score comes from the questions and tests that measure it. Attribute scores roll up into group scores, and groups roll up into the candidate's overall score, with the weights you set deciding how much each one counts (a weighted average). Only attributes in a group are included. If the job req uses predictive models, the overall score combines this attribute group roll-up with the predictive model roll-up, weighted by the job req's **Scoring Weights** (under **Setup**, then **Configurations**). See [Predictive models](/scoring/predictive-models).
> [accordion] Who can edit attributes?
>
> Admins with *Company Settings Access* manage the attribute library. Users with the *Manage Job Req Settings* permission can set up attributes on a job req. If you can't make changes, ask your Journeyfront admin to check your security role.
## Related
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and how scores roll up.
> [card] [AI resume scoring](/scoring/ai-resume-scoring)
>
> Score resumes against your attributes.
> [card] [AI-scored questions](/scoring/ai-scored-questions)
>
> Let AI score video, audio and written answers.
> [card] [Set up an interview activity](/interviews/interview-activity)
>
> Interview questions that measure attributes.
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
# How scoring works
Source: https://help.journeyfront.com/scoring/how-scoring-works
Raw scores, the Job Adaptive Score, and how to use them to focus your time.
> [!NOTE]
>
> **Who can do this:** Everyone on a job req can see candidate scores.
Scores help you spend your time on the candidates most likely to succeed. Journeyfront scores candidates as they complete activities, and keeps two kinds of score for every result.
## Raw scores and the Job Adaptive Score
* A **raw score** is the actual result, in its own units: words per minute on a typing test, for example.
* The **Job Adaptive Score** standardizes that result to a **1 to 5** scale based on what the job requires.

The Job Adaptive Score is what lets you compare very different activities side by side. A 4 on a typing test and a 4 on an interview question mean the same thing: a strong result for what this job needs.
Because it's based on the job's requirements, the same raw result can earn a different Job Adaptive Score on different job reqs. A typing speed that's strong for one role may be only average for a role that needs faster typists.
## How scores roll up
> [card] Activities
>
> Each scored activity, such as an assessment or skills test, has its own score.
> [card] Attributes
>
> Every activity measures one or more attributes, so scores also roll up by attribute.
> [card] Overall
>
> Attribute groups roll up into one overall score, along with predictive models when the job req uses them.
Scores roll up as weighted averages: each question or test into the attribute it measures, attributes into attribute groups, and attribute groups into the overall score. Users with the *Manage Job Req Settings* permission choose which attributes count for each job req and how much each one matters, under the job req's **Setup**, then **Attributes**. See [Attributes](/scoring/attributes).
You can see the whole roll-up on a candidate's **Score** tab. Click a group, then an attribute, to open the level below it. The **Weight** column shows how much each row counts toward the row above it.

1. **Question or test.** Each question or test that measures an attribute gets a 1 to 5 score. Here, the Verbal Reasoning test scored 4.2, from a raw result of 80%.
2. **Attribute.** The attribute's score is the weighted average of the questions and tests that measure it. Verbal Reasoning has one test, so it's 4.2.
3. **Attribute group.** The group's score is the weighted average of its attributes. Cognitive Aptitude averages Quantitative Reasoning (3.73, weight 3), Spatial Reasoning (4.6, weight 1) and Verbal Reasoning (4.2, weight 2): (3.73 × 3 + 4.6 × 1 + 4.2 × 2) ÷ 6 = 4.03.
4. **Overall score.** **Candidate Attribute Scores** is the weighted average of the groups, here 3.73. It's the score at the top of the Candidate Application and on the Candidates page.
Weights are relative: a weight of 6 counts three times as much as a weight of 2. Raise the weight of what matters most for the role, like Typing Test for a chat support job.
If the job req uses [predictive models](/scoring/predictive-models), the overall score combines two roll-ups: your attribute groups and your predictive models. The job req's **Scoring Weights**, under **Setup**, then **Configurations** (shown when **Use Predictive Model** is on), decide how much each one counts.
> [card] [Attributes](/scoring/attributes)
>
> Choose a job req's attribute groups and set their weights.
## Putting scores to work
* **Sort and filter** the Candidates page by score to work the strongest candidates first.
* **Automate** with rules that act on scores, so strong candidates move forward without waiting on a recruiter.
* **Close the loop.** Journeyfront can connect hiring scores to how people actually perform and how long they stay, so you can see which scores predict success in your roles.
> [!TIP]
>
> Look at attribute and activity scores, not just the overall score. A strong overall score with one weak area is a good topic to raise in the interview.
> [!NOTE]
>
> Scores inform decisions; people make them. Use scores alongside interviews and your team's judgment.
## FAQ
> [accordion] Why doesn't a candidate have a score yet?
>
> Scores appear after a candidate completes a scored activity. An attribute counts only when it's in an attribute group on the job req's **Attributes** page; the **Attributes** menu item shows an orange count when some aren't. If they've finished and a score is still missing after a few minutes, contact support with the candidate's Application ID.
> [accordion] Where can I see the raw result, like typing speed?
>
> Open the candidate's Candidate Application and select the **Steps** or **Score** tab. Tests measured in their own units, like a typing test's words per minute and accuracy or an internet speed test's Mbps, show the raw result under the Job Adaptive Score.
> [accordion] Are scores comparable across job reqs?
>
> Job Adaptive Scores use the same 1 to 5 scale everywhere, but each one reflects that job's requirements. Compare raw scores when you want the same yardstick across roles.
## Related
> [card] [How the pieces connect](/getting-started/how-the-pieces-connect)
>
> How job reqs, workflows, postings, candidates and hiring classes relate.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Where each score shows on a Candidate Application.
# Predictive models
Source: https://help.journeyfront.com/scoring/predictive-models
Use models built from your own employee outcomes to predict which candidates will perform and stay, and include the prediction in their score.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add predictive models to a job req and set how much they count.
>
> **Availability:** Journeyfront builds predictive models for your job profiles from your employee outcome data. To get one for a role, ask your Customer Success Manager.
A predictive model estimates how likely a candidate is to succeed in a role, for example how well they'll perform or how likely they are to stay. Journeyfront builds each model from your own employees' outcomes, such as performance and turnover, in that [job profile](/employees/job-profiles). On a job req, you choose which models to use, and every candidate gets a predictive score that can count toward their overall score.
## How predictive models fit together
**1. Collect outcome data**
Your employees' outcomes in a role, like performance and turnover, are the data a model learns from. The [behavioral assessment](/assessments/behavioral-assessment) is made to go with predictive models.
**2. Journeyfront builds the model**
Each model belongs to a job profile and predicts one outcome. You'll see it under **What it Predicts**, for example **Performance**.
**3. You add it to a job req**
A job req can use the models built for the job profile it's linked to (**Linked to Job Profile**, under **Setup**, then **Details**).
**4. You include it in the score**
Turn on **Use Predictive Model** and set the weights in the job req's **Setup**, then **Configurations**.
> [!TIP]
>
> No model for a role yet? You can still use the behavioral assessment on its own: set the ideal value for each trait you care about, and start collecting the data a model can be built from later. See [Behavioral assessment](/assessments/behavioral-assessment).
## Turn on predictive models for a job req
### 1. Add the models
**1. Open Predictive Models**
Open the job req and go to **Setup**, then **Predictive Models**. The table lists the models the job req already uses, with **Date Created**, **What it Predicts** and **Weight**.
**2. Add a model**
Click **Add Model**. The **Select Predictive Model** window lists the models available for this job req's job profile. Click **Add** next to each one you want, then click **Save**.
**3. Wait for scores to update**
Journeyfront recalculates the scores of the job req's candidates. On a busy job req this can take a few minutes.

If the window shows **No Data**, there's no model for this job req's job profile yet. Check the job req's **Linked to Job Profile** setting, then ask your Customer Success Manager.
If the job req uses more than one model, click **Edit Weights** to decide how much each model counts compared with the others, and click **Save**. A higher weight counts more.
To stop using a model, click the trash icon on its row, then **Confirm**.
### 2. Include the prediction in the overall score
**1. Open Configurations**
In the same job req, go to **Setup**, then **Configurations**, and find the **Scoring & Reporting** card.
**2. Turn on Use Predictive Model**
Switch on **Use Predictive Model**. **Scoring Weights** appear.
**3. Set the weights**
Set **Candidate Predictive Score weight** and **Custom Attributes weight** to decide how much the prediction counts compared with the job req's own attributes. Then click **Save** at the top of the page.
See [Job settings](/job-reqs/job-settings) for the rest of the page.
## How the prediction feeds the overall score
Journeyfront rolls scores up as weighted averages: questions and tests into attributes, attributes into attribute groups, and groups into one score. The weights you set decide how much each piece counts.
| | What makes up the overall score |
| - | - |
| **Use Predictive Model off** | The roll-up of your attribute groups. |
| **Use Predictive Model on** | Two roll-ups: your attribute groups and your predictive models. **Scoring Weights** decide how much each one counts. |
Adding or removing a model, changing a model's weight, or changing **Scoring Weights** recalculates the candidates' scores. To set up the attribute side, see [Attributes](/scoring/attributes).
## See the prediction on a Candidate Application
When **Use Predictive Model** is on and the job req has at least one model, the **Score** tab of each Candidate Application starts with **Candidate Predictive Scores**:
* The first row is the candidate's combined predictive score.
* Below it, each model has its own row and score.
* Expand a model to see the traits it looks at, with the candidate's value next to the ideal value for each one.
The candidate's attribute scores follow underneath, starting with **Candidate Attribute Scores**. See [Reading a candidate's scores](/scoring/reading-scores#the-score-tab).

You can also put predictive scores to work elsewhere:
* **The Candidates page:** add **Predictive Model Scores** with **Edit Columns**, or filter by them. See [The Candidates page](/candidates/candidates-page).
* **Automation rules:** use the **Predictive model score is** condition to act on a model's score. See [Automation rules](/workflows/automation-rules).
> [!NOTE]
>
> A predictive score is one input. Use it alongside interviews, assessments and your team's judgment; people make the hiring decision.
## FAQ
> [accordion] Why don't I see Candidate Predictive Scores on the Score tab?
>
> Two things need to be in place: **Use Predictive Model** is on under **Setup**, then **Configurations**, and at least one model is added under **Setup**, then **Predictive Models**.
> [accordion] Can we build our own predictive model?
>
> Not in the app. Journeyfront builds and maintains predictive models from your outcome data. Talk to your Customer Success Manager about a model for a role.
> [accordion] Why is the Select Predictive Model window empty?
>
> There's no model for the job profile this job req is linked to. Check **Linked to Job Profile** under **Setup**, then **Details**, and ask your Customer Success Manager if you expected a model.
> [accordion] Do we need predictive models to use the behavioral assessment?
>
> No. The behavioral assessment is included in every account. Without a model, set the ideal value for each trait on the job req, and your results become data a model can be built from later. See [Behavioral assessment](/assessments/behavioral-assessment).
> [accordion] Does adding or removing a model change existing scores?
>
> Yes. Adding or removing a model, or changing any of the weights, recalculates the scores of the job req's candidates. It can take a few minutes.
> [accordion] Can candidates see their predictive score?
>
> No. Scores are only visible to your team.
## Related
> [card] [Behavioral assessment](/assessments/behavioral-assessment)
>
> The assessment made to go with predictive models.
> [card] [Job profiles](/employees/job-profiles)
>
> The roles your predictive models are built for.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and how scores roll up.
> [card] [Reading a candidate's scores](/scoring/reading-scores)
>
> Where every score shows on a Candidate Application.
# Reading a candidate's scores
Source: https://help.journeyfront.com/scoring/reading-scores
Find and interpret the scores on a Candidate Application's Score, Steps, Screenings and Assessments tabs.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the Candidate Application can see its scores. Deleting an activity's score needs *Can Delete Scores*, and unlocking an interviewer's submitted feedback needs *Can Unlock Interviews*.
Every Candidate Application shows the same results four ways. The **Score** tab groups them by what you care about for the job, the **Steps** tab follows the order of the workflow, the **Screenings** tab shows each answer, and the **Assessments** tab shows behavioral and system results. Once you know where to look, you can size up a candidate in a minute and spend your time on the right people.
## The overall score
The **Score** tile at the top of the Candidate Application is the candidate's overall score for this job req. It rolls up the candidate's attribute group scores, plus their predictive model scores when the job req uses predictive models. It's the same **Overall Score** you can sort and filter by on the **Candidates** page.
Scores are on a **1 to 5** scale: the [Job Adaptive Score](/scoring/how-scoring-works), which reflects what this job needs. Tests measured in their own units, like words per minute, also show their raw result. Colors run from dark red for low scores to dark green for high ones, so you can scan a table quickly.
| You see | What it means |
| - | - |
| A number from 1 to 5 | The candidate's Job Adaptive Score |
| **NA** | No score yet. The candidate hasn't completed it, it hasn't been scored, or it isn't part of this candidate's results. |
| **KO** | The candidate gave a knockout answer. KO shows in red in place of the score. |
## The Score tab
The **Score** tab shows the candidate's scores by attribute, in the attribute groups your team set up for this job req. It answers "how does this person measure up on what matters for this job?"

* **Candidate Attribute Scores**, the first row, rolls up the candidate's scores across all your attribute groups.
* **Each attribute group** comes next, in the order you set. Click a group to see its attributes, and click an attribute to see every question or test that measured it, labeled with the step number and activity.
* **Columns** show where each score came from: **Assessments**, **Screening Questions**, one column per interviewer under **DATA from INTERVIEWERS**, and **Resume** when the job req uses [AI resume scoring](/scoring/ai-resume-scoring). **Score**, under **TOTAL**, is the combined result for that row.
* **Raw results** appear under the score for tests measured in their own units: words per minute and accuracy for a typing test, and Mbps for an internet speed test.
The **Weight** column shows how much each group, attribute and question counts for this job req. Your admins set weights on the job req's **Attributes** page. See [Attributes](/scoring/attributes).
### Predictive scores
If the job req uses [predictive models](/scoring/predictive-models) and **Use Predictive Model** is on, the **Score** tab starts with **Candidate Predictive Scores**, above the attribute scores:
* The first row is the candidate's combined predictive score.
* Each model follows with its own score. Expand a model to see the traits it looks at, with the candidate's value next to the ideal value for each one.
The overall score then combines the predictive scores with **Candidate Attribute Scores**, in the proportions set for the job req.
> [!TIP]
>
> Read the groups before the total. A candidate with a strong overall score and one weak group is worth a targeted interview question, and a slightly lower total can hide a standout in the group that matters most for the role.
## Interviewer scores and notes
When interviewers submit feedback, each one gets a column under **DATA from INTERVIEWERS** on the **Score** and **Steps** tabs. Up to four interviewers show at a time; use the arrows next to their names to see more.
A comment icon next to an interviewer's score means they left a note. Hover over it to read the note, or click it to open the full **Interview Notes**. For every interviewer's notes in one place, open the **Notes** tab. See [Interview notes](/interviews/interview-notes).
## The Steps tab
The **Steps** tab shows the same results in workflow order: each step, then its activities, then each question or test, then the attributes it measured. Use it to see how a candidate did at each stage, for example the phone screen versus the assessment step.
* Activities scored by AI resume scoring show an **AI Resume Review** line with a sparkle icon.
* Raw results, like words per minute, show under the score just as on the **Score** tab.
### Delete an activity's score
Users with *Can Delete Scores* can remove the score from one activity:
**1. Hover over the score**
On the **Steps** tab, expand the step and hover over the activity's score. It changes to **Delete Score**.
**2. Confirm**
Click it, then click **Yes** at **Delete?**
Language assessment and skills test scores can't be deleted. To let a candidate take an activity again, see [Retakes](/assessments/retakes).
### Unlock an interviewer's feedback
Submitted interview feedback is locked so it can't change after the fact. If an interviewer needs to correct it, someone with *Can Unlock Interviews* can unlock it:
**1. Find the interview**
On the **Steps** tab, expand the step with the interview. Hover over the interviewer's score on the interview's row. It changes to **Unlock Interview**.
**2. Confirm**
Click it, then click **Yes** at **Unlock?** The interviewer can now edit and submit their feedback again.
You can also unlock feedback from **Interviews**, then **My Interviews**. See [Conduct an interview](/interviews/conduct-an-interview#unlock-submitted-feedback).
## The Screenings tab
The **Screenings** tab lists every screening question the candidate was asked, grouped by activity. Each activity shows its status, and each question shows:
| Column | What it shows |
| - | - |
| **Order** | The question's position in the activity |
| **Question** | The question as the candidate saw it |
| **Response** | The candidate's answer, or "Not yet answered". Video and audio answers play right here. |
| **Attributes and Scoring Criteria** | The attribute the question measures and the criteria for each score. Answers that knock a candidate out are marked **KO**. |
| **Score (1 - 5)** | The answer's score |
Click **Order**, **Question** or **Response** to sort.
### Score an answer yourself
Many answers are scored automatically from the question's scoring options. Others, such as free-form text, video and audio answers, wait for a person to score them, unless the question uses [AI scoring](/scoring/ai-scored-questions).
**1. Find the answer**
On the **Screenings** tab, find the answer. Unscored answers show a **Score** button.
**2. Use the scoring criteria**
Read the answer and compare it with the criteria in **Attributes and Scoring Criteria**.
**3. Enter the score**
Click **Score**, enter a number from 1 to 5 (decimals like 3.5 are fine) and click **Save**.
The candidate's scores, including the overall score, update when you save. To change or remove a score you entered, use the edit or trash icon under it.

> [!TIP]
>
> Write scoring criteria that describe what a 1, 3 and 5 answer actually sound like. When several people score the same question, clear criteria keep their scores consistent. Criteria are set on the question; see [Screening questions](/assessments/screening-questions).
## The Assessments tab
The **Assessments** tab shows results that aren't simple question scores.
* **Behavioral assessments:** expand an assessment to see each trait it measured. The slider shows the **Candidate Value**, where the candidate landed from **Low (1)** to **High (5)**, next to the **Ideal Value** your job req is looking for. **Score (1-5)** is the candidate's score for that trait. **Not Scored** means the trait is measured but doesn't count for this job req. A description of the assessment appears beside the table. See [Behavioral assessment](/assessments/behavioral-assessment).
* **System requirements checks** appear under **SRL Assessments**, with the overall result, the score, and each requirement compared with the candidate's system. If results couldn't be retrieved, you'll see **Error Getting Results** and a **Retry** button. See [System requirements](/assessments/system-requirements).
Language assessment results have their own **Language** tab. See [Language assessments](/assessments/language-assessments).
## FAQ
> [accordion] Why does a score say NA?
>
> There's no score to show yet. The candidate may not have reached or finished that activity, an answer may still need someone to score it, or nothing in the workflow measured that attribute for this candidate. On the **Screenings** tab, answers waiting for a person to score them show a **Score** button.
> [accordion] What does KO mean?
>
> The candidate gave an answer marked as a knockout on a screening question. KO replaces the score so knocked-out candidates are easy to spot. See [Screening questions](/assessments/screening-questions).
> [accordion] Why does the same result score differently on two job reqs?
>
> Scores are Job Adaptive Scores, based on what each job needs. The same typing speed can be strong for one role and average for another. Compare raw results, like words per minute, when you want the same yardstick across roles. See [How scoring works](/scoring/how-scoring-works).
> [accordion] How do I see an interviewer's notes?
>
> Hover over the comment icon next to their score on the **Score** or **Steps** tab, or open the **Notes** tab to read every interviewer's notes together.
> [accordion] Can I change a score?
>
> It depends on the score:
>
> * **Screening answers you scored by hand:** use the edit icon under the score on the **Screenings** tab.
> * **AI scores:** users with *Edit AI Scores* can change them. See [AI-scored questions](/scoring/ai-scored-questions).
> * **Interview feedback:** someone with *Can Unlock Interviews* unlocks it so the interviewer can resubmit.
> * **Activity scores:** users with *Can Delete Scores* can delete them on the **Steps** tab.
> [accordion] Why is the Weight column different on each job req?
>
> Weights belong to each job req, so two job reqs can value the same attribute differently. They're set on the job req's **Attributes** page. See [Attributes](/scoring/attributes).
> [accordion] Can candidates see their scores?
>
> Not the scores on this page. Job Adaptive Scores, the overall score and group scores are only visible to your team. Candidates can see some of their own results after a test: their typing speed and accuracy, a report after a skills test, and a profile report after the behavioral assessment unless your account hides it. See [Assessments overview](/assessments/overview).
## Related
> [card] [How scoring works](/scoring/how-scoring-works)
>
> Raw scores, the Job Adaptive Score and how scores roll up.
> [card] [Attributes](/scoring/attributes)
>
> Choose what counts for each job req.
> [card] [The Candidate Application](/candidates/candidate-application)
>
> Every tab, explained.
> [card] [Conduct an interview](/interviews/conduct-an-interview)
>
> How interviewers score and submit feedback.
# Add candidates
Source: https://help.journeyfront.com/sourcing/add-candidates
Add one candidate to a job req yourself, email them an invitation to finish applying, or recover a deleted application.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the job req: its hiring team, and users whose security role has *All Job Req Access*.
>
> **Availability:** You can add candidates while the job req is **Active**.
Use **Add New Candidate** when you've already met or spoken to someone, for example at a walk-in event or after a phone call, and want them on a job req without waiting for them to apply. You enter their email and name, and Journeyfront can email them a link to finish the application.
To have candidates apply on their own, share an invitation link instead. See [Invite candidates](/sourcing/invite-candidates). To add many people at once, see [Import candidates](/sourcing/import-candidates).
## Add one candidate
**1. Open the Add New Candidate window**
Open the job req, click **Actions**, then **Add New Candidate**.
**2. Check the email**
Enter the candidate's **Email** and click **Check Email**. Journeyfront tells you whether this is a **New User** or an **Existing User**.

**3. Fill in the details**
* **New User:** enter their first and last name.
* **Existing User:** their name is filled in for you. If they've applied to this job req before, the window lists each application with its date and status.
**4. Transfer earlier results (optional)**
If the person already completed screening questions or tests on another job req, a **Transfer Data** section appears. Click **Check for Transferrable Data** to reuse those results here. See [Transfer results to the new application](/candidates/add-to-another-job#transfer-results-to-the-new-application).
**5. Choose whether to email them**
Tick **Send email inviting user to complete the application steps** to send them a link to continue. Leave it unticked if you'll contact them another way.
**6. Click Add to Job Req**
The candidate appears on the job req's **Candidates** tab.
Added candidates start at the beginning of the job req's workflow, just like someone who applied.
The invitation uses the **Invitation Applicant Manual Add** system email, which you can edit in **Settings**, then **Templates**, then **E-mail Template**, on the **System Emails** tab. See [Email templates](/communication/email-templates).
> [!TIP]
>
> Candidates you add by hand start with no source. Set it on the Candidate Application's **Details** tab right after you add them, so your source reports stay complete. See [Edit candidate details](/candidates/edit-details).
## Recover a deleted application
If a candidate's application on this job req was deleted, **Add New Candidate** brings it back. Enter their email and click **Check Email**. The deleted application is listed with **Recover deleted application** next to it. Click it to restore the application.
## FAQ
> [accordion] Why can't I find Add New Candidate?
>
> It's in the job req's **Actions** menu, not on the **Candidates** page. Closed and archived job reqs don't show it, and an **Inactive** job req shows a message that you can't add candidates. Activate the job req first. See [Job req statuses](/job-reqs/statuses).
> [accordion] Does the candidate get an email?
>
> Only if you tick **Send email inviting user to complete the application steps**. Otherwise nothing is sent, and you can reach out however you like.
> [accordion] Can I set the source for candidates I add by hand?
>
> Not in the **Add New Candidate** window. After adding them, change the **Source** on the Candidate Application's **Details** tab. See [Edit candidate details](/candidates/edit-details).
> [accordion] Someone already applied to another job req. Should I add them again?
>
> Use **Add to Job Req** instead, so their earlier screening and test results can come with them. See [Add a candidate to another job req](/candidates/add-to-another-job).
## Related
> [card] [Invite candidates](/sourcing/invite-candidates)
>
> Let candidates apply to a job req on their own.
> [card] [Import candidates](/sourcing/import-candidates)
>
> Load a list of candidates into a job req.
> [card] [Add a candidate to another job req](/candidates/add-to-another-job)
>
> Consider someone for another role and reuse their results.
> [card] [The Candidates page](/candidates/candidates-page)
>
> Find and work with the candidates you added.
# External job boards
Source: https://help.journeyfront.com/sourcing/external-job-boards
Get your jobs beyond your career site, onto Indeed, thousands of boards through JobTarget, and programmatic campaigns through Appcast, and see how applicants come back.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* set up job boards and connect job board partners. Anyone who can edit a job req's postings can post it through JobTarget.
>
> **Availability:** Posting through these partners costs nothing extra from Journeyfront. Paid placements, such as sponsored Indeed jobs, paid JobTarget boards and Appcast campaigns, are billed by the partner.
Every job you advertise starts in the same place: a job posting on one of your job boards, the career site Journeyfront hosts for you. From there, job board partners take your postings further, and the candidates they bring in come back to your Journeyfront application, tagged with where they came from.
This page explains how the pieces fit together. For setup, follow the links to each partner's page.
## How your jobs get out
| Where the job appears | How it gets there | Stays in sync with Journeyfront? |
| - | - | - |
| **Your job board** | Automatically, for every active posting set to post to the board | Yes |
| **Indeed** | Automatically, for every active posting on a job board with **Post Jobs to Indeed** turned on | Yes. Edits, deactivations and closures go to Indeed too. |
| **Appcast** | Appcast reads your job board's **Feed URL** and runs your campaigns | Yes. The feed always lists the board's active postings. |
| **Boards you pick through JobTarget**, such as LinkedIn and niche or diversity boards | You choose boards for each posting, one at a time | No. Manage or end these posts in JobTarget. |
| **Any other board or site** | You post the job there yourself, with a magic link to the posting | Not applicable. Take the job down there yourself. |
You can use all of these at once. One job board can go to Indeed, feed Appcast and have its postings promoted through JobTarget.
## Start with a job posting
External boards can only show what your job postings contain, so get the posting right first:
* The job board is turned on, with your branding. See [Job boards](/sourcing/job-boards).
* The job req has an active posting on that board, with **Make job posting page active** and **Post job to job board** set to **Yes**. See [Job postings](/sourcing/job-postings).
* The posting has a clear **Job Title**, a location with a country, and a description. JobTarget also needs a **State/Region** and **Zip**.
* Pay is filled in, with **Show This Field** on where pay must be shown. Partners that read your **Feed URL** receive the pay whether or not it's shown on the posting.
> [card] [Job postings](/sourcing/job-postings)
>
> Create the posting each job board advertises, and choose where it's listed.
## Indeed
Turn on **Post Jobs to Indeed** for a job board and every active posting on it goes to Indeed as a free listing, kept in sync as you edit, deactivate or close jobs. You decide in your Indeed employer account whether to sponsor them.
With **Allow Indeed Easy Apply**, candidates apply with a short form inside Indeed. Journeyfront then adds them to the job req, fills in their application with their Indeed answers and emails them a link to finish. With Easy Apply off, they click through to your Journeyfront posting and complete your full application there.
See [Indeed](/integrations/job-boards/indeed) for setup and for choosing between the two.
> [card] [Indeed](/integrations/job-boards/indeed)
>
> Connect Indeed, choose between the two ways to apply, and check a posting's sync.
## JobTarget
JobTarget gives you a marketplace of more than 25,000 job boards, free and paid, including LinkedIn and niche, industry and diversity boards. Open a posting, click **Post to Job Board** under **External Job Board Posts**, then **Job Post Using Job Target**, and pick boards for that posting. JobTarget handles posting and billing.
> [!WARNING]
>
> JobTarget posts don't follow changes in Journeyfront. Closing or deactivating a job req leaves them running until they expire. End or change them in JobTarget with **Manage Job Post**.
See [JobTarget](/integrations/job-boards/jobtarget).
> [card] [JobTarget](/integrations/job-boards/jobtarget)
>
> Post a job to many boards at once and track spend, clicks and applicants.
## Appcast
Appcast runs programmatic job advertising: it spreads your budget across job sites and adjusts where your jobs appear based on results. Appcast picks up your jobs from a job board's **Feed URL**, and a tracking pixel on the candidate apply pages tells it which clicks turned into applications.
See [Appcast](/integrations/job-boards/appcast) and [Share a job feed](/sourcing/job-boards#share-a-job-feed).
> [card] [Appcast](/integrations/job-boards/appcast)
>
> Advertise your jobs through Appcast using your job feed.
## Other job boards
For a board or site Journeyfront doesn't connect to, post the job there yourself and use a magic link to the job posting as the apply link:
1. Make sure your account has a source for the board. Journeyfront includes default sources for many boards, such as ZipRecruiter, Glassdoor and SimplyHired. Add a custom source with the **Job Board** source type for any other. See [Sources](/sourcing/sources).
2. Open the job req, go to **Setup**, then **Job Postings**, click the **â‹®** menu on the posting, then **Generate Source Link**, and pick that source.
3. Use the link as the apply link when you post the job.
Candidates who apply through it are tagged with that source. See [Magic links](/sourcing/magic-links).
## How applicants come back
However they find the job, candidates end up in your Journeyfront application for the job req and appear on its **Candidates** tab like anyone else.
| Channel | Where the candidate applies | Source on their Candidate Application |
| - | - | - |
| Your job board or a posting | Your Journeyfront application | The source in the link, if it was a magic link |
| Indeed, Easy Apply on | A short form on Indeed, then your application to finish | The source chosen for Easy Apply on the job board, or **Indeed** |
| Indeed, Easy Apply off | Your Journeyfront application, from the posting | Linked to the job posting they came through |
| JobTarget | Your Journeyfront application | Named after the board, such as **JobTarget via LinkedIn**, created automatically |
| Appcast | Your Journeyfront application | Ready-made Appcast sources, such as **Appcast** and **Appcast_Indeed** |
| Another board | Your Journeyfront application | The source in the posting's magic link |
When a candidate came through a job posting, the **Details** tab of their Candidate Application also shows the **Job Board** and **Job Post**. To compare channels, use the **Source Effectiveness** dashboard. See [Dashboards overview](/reporting/dashboards).
## See where a posting has gone
Open the job req, go to **Setup**, then **Job Postings**, and open the posting. **External Job Board Posts** lists the partners the posting has been sent to, with each one's status, such as **Synced** for Indeed.

## Take jobs down
Deactivating, closing or archiving a job req turns off its postings. That takes the job off your job board, expires it on Indeed and drops it from your **Feed URL**, so Appcast stops advertising it. JobTarget posts and jobs you posted yourself on other boards keep running until you end them there. See [Job req statuses](/job-reqs/statuses).
## FAQ
> [accordion] Can Journeyfront post to LinkedIn?
>
> Yes, through JobTarget. Pick LinkedIn from the JobTarget marketplace for each posting you want there. Applicants get the source **JobTarget via LinkedIn**.
> [accordion] Do I need a separate job board for each partner?
>
> No. One job board can go to Indeed, feed Appcast and have its postings promoted through JobTarget, all at once. Use more than one job board when different audiences should see different jobs, for example one per country or brand.
> [accordion] Who bills for sponsored jobs and paid boards?
>
> The partner. Indeed, JobTarget and Appcast manage their own pricing, invoices and accounts. Journeyfront never stores your payment details for them.
> [accordion] Why doesn't my job show on Indeed yet?
>
> Indeed can take up to 48 hours to show a new posting. Check the posting's Indeed row under **External Job Board Posts**, and see [Indeed](/integrations/job-boards/indeed) for what to check if it isn't syncing.
> [accordion] Can I post a job without listing it on our career site?
>
> Yes. Set **Post job to job board** to **No** and keep **Make job posting page active** on. The posting isn't listed on your job board, but anyone with its link can open it and apply, so you can share it on the boards you choose. See [Job postings](/sourcing/job-postings#who-can-see-a-posting).
## Related
> [card] [Job board integrations](/integrations/job-boards)
>
> Compare Indeed, JobTarget and Appcast and set them up.
> [card] [Job postings](/sourcing/job-postings)
>
> Create the postings that go out to every board.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Set up your job boards and their feeds.
> [card] [Magic links](/sourcing/magic-links)
>
> See which boards bring in your hires.
# Import candidates
Source: https://help.journeyfront.com/sourcing/import-candidates
Load a list of candidates from a CSV or Excel file into a job req, check the results and fix rows that didn't import.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the job req: its hiring team, and users whose security role has *All Job Req Access*.
>
> **Availability:** You can import candidates while the job req is **Active**.
Use **Import Candidates** when you have a list of people to bring into one job req: sign-ups from a job fair, candidates from an agency, or a spreadsheet from another system. Each row becomes a Candidate Application, and Journeyfront can email everyone a link to finish applying.
For one person, see [Add candidates](/sourcing/add-candidates). To let people apply on their own, see [Invite candidates](/sourcing/invite-candidates).
## Import a list of candidates
**1. Open the Import Candidate window**
Open the job req, click **Actions**, then **Import Candidates**.
**2. Get the example file**
Click **Download Example File** for a CSV with the right column headers.
**3. Fill in your file**
Add one candidate per row. Save it as a CSV or Excel (.xlsx) file. See [Columns](#columns) below.
**4. Upload it**
Drag the file into the window, or click to select it.
**5. Choose whether to email them**
Tick **Send new candidates invite email** to email everyone in the file a link to complete their application.
**6. Click Import**
Journeyfront processes the file. You can wait for the results or close the window; you'll get an email with the results either way.

Imported candidates start at the beginning of the job req's workflow, just like someone who applied. Anyone already on this job req is skipped.
## Columns
Column headers aren't case sensitive, and columns can be in any order.
| Column | Required | What to enter |
| - | - | - |
| `email` | Yes | The candidate's email address. |
| `first_name` | Yes | First name. |
| `last_name` | Yes | Last name. |
| `phone` | No | Phone number. Include the country code (for example `+1`); without one, Journeyfront assumes the job req's country. |
| `source` | No | Must match the name of a source in your account. See [Sources](/sourcing/sources). |
| `personal_field{Internal Name}` | No | A value for one of your personal fields. Put the field's **Internal Name** inside the braces, for example `personal_field{languages}`. |
| `application_field{Internal Name}` | No | A value for one of your application fields, written the same way. |
| `do_not_hire` | No | `true`, `yes` or `1` flags the person as Do Not Hire. See [Do Not Hire](/candidates/do-not-hire). |
| `do_not_hire_reason` | No | The reason shown with the flag. |
For custom fields, a Multiple Choice value must match one of the field's options, and a Number value can only contain digits. See [Custom fields](/account-setup/custom-fields).
> [!TIP]
>
> Fill in the `source` column, for example with the name of the job fair or agency. Otherwise imported candidates have no source, and your source reports can't count them. See [Magic links](/sourcing/magic-links).
> [!WARNING]
>
> A row with a phone number opts that candidate in to text messages. Only include phone numbers for candidates who have agreed to receive texts from you.
If someone in your file is already in Journeyfront under the same email, they're added to the job req with the name and phone number they already have. The file doesn't change them.
## Check the results
When the import finishes, the window shows **Your Import is Complete** (or **Your Import Failed** if no rows were imported), with:
* **Total candidates successfully imported**
* **Candidates not imported because they are duplicates**, and the file lines they were on
* **Candidates not imported due to an invalid data format**, and the file lines they were on
Click **Download Import Results** for a copy of your file with a **status** column: **Success**, or the reason that row was skipped. The same file is attached to the results email. Line numbers count the header as line 1.
## Fix rows that didn't import
| Status in the results file | What to do |
| - | - |
| **Duplicate email** | The person is already on this job req. Nothing to do. |
| **Duplicate email (deleted user)** | The person has a deleted application on this job req. [Recover it](/sourcing/add-candidates#recover-a-deleted-application) instead. |
| **Invalid email**, **Invalid first name**, **Invalid last name** | The value is missing or isn't valid. Fix it and import those rows again. |
| **Invalid phone number** | Add the country code, or remove the number. |
| **Invalid source** | Use a source name exactly as it appears in your account, or leave the column empty. |
| **Field does not exist:** followed by the column | Check the **Internal Name** inside the braces and the `personal_field` or `application_field` prefix. |
| **Invalid option value for** or **Invalid number value for** | Match the field's options exactly, or use digits only. |
If the whole file fails, check that it's a CSV or .xlsx file and that it has the `email`, `first_name` and `last_name` columns.
> [!TIP]
>
> Before importing a big list, import two or three rows first. Once those look right on the **Candidates** tab, import the rest. Rows that already imported are skipped as duplicates if you upload the same file again, so re-importing a corrected file is safe.
## Importing employees
To bring in employees rather than candidates, admins use **Settings**, then **Import Data**. It has its own templates for employee data and employee performance data. See [Importing data](/account-setup/importing-data).
> [card] [Importing data](/account-setup/importing-data)
>
> Import employees and their performance data from Settings, then Import Data.
## FAQ
> [accordion] Why can't I find Import Candidates?
>
> It's in the job req's **Actions** menu, not on the **Candidates** page. Closed and archived job reqs don't show it, and an **Inactive** job req shows a message that you can't import candidates. Activate the job req first. See [Job req statuses](/job-reqs/statuses).
> [accordion] Do imported candidates get an email?
>
> Only if you tick **Send new candidates invite email** before you import. Otherwise nothing is sent, and you can reach out however you like.
> [accordion] Can I import candidates into several job reqs at once?
>
> No. Each import goes into one job req. Run a separate import from each job req.
> [accordion] Can I undo an import?
>
> There's no undo. To remove imported candidates, select them on the job req's **Candidates** tab and use **Delete**, if your security role allows it. See [Bulk actions](/candidates/bulk-actions).
## Related
> [card] [Add candidates](/sourcing/add-candidates)
>
> Add one person yourself and email them an invitation.
> [card] [Magic links](/sourcing/magic-links)
>
> See which channels bring in your candidates.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Set up the personal and application fields you import into.
> [card] [Importing data](/account-setup/importing-data)
>
> Bring in employee and performance data.
# Invite candidates
Source: https://help.journeyfront.com/sourcing/invite-candidates
Invite candidates straight into a job req: copy its invitation link, then text or email it, share it on social media, or put it on a QR code or poster.
> [!NOTE]
>
> **Who can do this:** Anyone who can open the job req: its hiring team, and users whose security role has *All Job Req Access*.
>
> **Availability:** Candidates can apply through an invitation link while the job req is **Active**.
Every job req has its own invitation link. Anyone who opens it lands on that job req's sign-in page and can apply right away, without browsing your career site or reading a job posting first. It's the quickest way to get someone from a text, an email, a social post or a poster into an application.
## Ways to invite candidates
| You want to | Do this |
| - | - |
| Get someone you're talking to into the application now | [Copy the invitation link](#copy-the-invitation-link) and send it |
| Follow up after a phone screen or an event | [Text or email the link](#text-or-email-the-link) |
| Reach people on Facebook, Instagram, LinkedIn or TikTok | [Share it on social media](#share-it-on-social-media) |
| Invite people in person, at a job fair, in a store or on a bulletin board | [Put it on a QR code or poster](#put-it-on-a-qr-code-or-poster) |
| Add someone yourself, without waiting for them to apply | **Add New Candidate**. See [Add candidates](/sourcing/add-candidates). |
| Load a list from a job fair, an agency or a spreadsheet | **Import Candidates**. See [Import candidates](/sourcing/import-candidates). |
> [!TIP]
>
> To show the job description first, share a job posting link instead. To let candidates choose from all your jobs, share your job board. See [Job postings](/sourcing/job-postings) and [Job boards](/sourcing/job-boards).
## Copy the invitation link
**1. Open the invite window**
Open the job req, click **Actions**, then **Invite Candidates**. The **Invite Participants** window opens.

**2. Pick a source (optional)**
Pick a **Source** before you copy the link and it becomes a magic link: everyone who applies through it is tagged with that source. The list shows your account's enabled sources, grouped by source type; type in the box to search it. See [Magic links](/sourcing/magic-links).
**3. Copy the link**
Under **Invitation Link**, click **Copy**.
**4. Customize what candidates see (optional)**
Write a **Candidate Message** and add an **Image to display**. Click **Save** to keep the message and image. See [Customize the sign-in page](#customize-the-sign-in-page).

The top of the window shows the job req's title, your company name, the employment type and the location, so you can check you're copying the link for the right job.
> [!TIP]
>
> Copy a separate link for each place you invite people, each with its own source: one for texts, one for the job fair poster, one for your Facebook post. See [Magic links](/sourcing/magic-links) for naming tips and what to watch for when you rename a source.
## Text or email the link
Paste the link into a text or email you send from your own phone or inbox, for example right after a phone screen, or to a list of people who signed up at a hiring event. Keep the message short: the job, why they'd like it, and the link.
For people who are already candidates in Journeyfront, use **Email** or **Message** with the `{{job_invite_link}}` template variable instead. It gives each candidate their own link to their application. See [Email candidates](/communication/email-candidates), [Text messages](/communication/text-messages) and [Template variables](/communication/template-variables).
> [!NOTE]
>
> The **Invite Participants** window doesn't send anything. To have Journeyfront email someone an invitation, add them with **Add New Candidate** or **Import Candidates** and tick the email option.
## Share it on social media
Paste the link into a post, a story, a group or your profile, or use it as the destination of an ad. Pick a social source, such as **Facebook** or **TikTok**, before you copy it. For Facebook and Instagram lead ads, which bring candidates in without a link, see [Social media](/sourcing/social-media).
## Put it on a QR code or poster
Turn the link into a QR code with any QR code tool, then print it on flyers, posters, table tents or business cards so people can scan it with their phone and apply on the spot. Give each event or location its own source, so you can see which ones bring in candidates.
You can also give a link with its own source to each partner or agency that sends you candidates.
## Customize the sign-in page
Two settings in the **Invite Participants** window change what candidates see when they open the link:
* **Candidate Message:** a welcome note, shown below the job title. Use it to set expectations, for example how long the application takes or what happens next.
* **Image to display:** shown at the top of the page. Upload a JPEG or PNG with the upload icon, or paste an image URL. Leave it empty to use your company logo.
Click **Save** to keep them. The message and image belong to the job req, so they appear for everyone who opens its invitation link, whatever source the link carries. Your company logo comes from **Settings**, then **Company Details**. See [Company details](/account-setup/company-details).
## What candidates see
**1. The sign-in page**
The candidate sees your image (or your company logo), the job req's **External Job Title**, your company name with the job req's city and state, and your **Candidate Message**. They can switch the page to English, Spanish or French.
**2. Email and name**
They enter their email address. New candidates then enter their first and last name.
**3. Password**
New candidates set a password. People who already have a Journeyfront profile enter theirs.
**4. The application**
They click **Continue** and start the job req's application at the first step of its workflow, just like someone who applied from a job posting.
If the candidate already has an application on this job req, signing in takes them back to it. No second application is created.
If the job req isn't **Active**, the link shows "This position is not accepting new applications at this time." instead of the sign-in.
## When the link works
| Job req status | **Invite Candidates** in the Actions menu | What the link does |
| - | - | - |
| **Active** | Shown | Candidates can sign in and apply |
| **Inactive** | Shown | Shows that the position isn't accepting applications |
| **Closed** or **Archived** | Not shown | Shows that the position isn't accepting applications |
The link itself doesn't change. If you deactivate a job req and activate it again later, links you've already shared start working again. See [Job req statuses](/job-reqs/statuses).
## FAQ
> [accordion] Does the link expire?
>
> No. It works whenever the job req is **Active**, for as long as the job req exists.
> [accordion] Is the invitation link the same as a job posting link?
>
> No. A job posting link opens the job description first, and the candidate clicks **Apply to position** to continue. The invitation link skips the description and goes straight to sign-in. Use a posting link when candidates need to read about the job, and the invitation link when they already know about it.
> [accordion] Can one link cover several job reqs?
>
> No. Each job req has its own invitation link. To let candidates choose from several jobs, share a job board link instead. See [Job boards](/sourcing/job-boards).
> [accordion] I chose a source, but the candidate has no source. Why?
>
> Check that you picked the source before clicking **Copy**, that the source hasn't been renamed or deleted since, and that the link wasn't cut short when it was pasted. If the candidate had already applied to this job req, their original source stays. See [Magic links](/sourcing/magic-links).
> [accordion] Can I use a different message for each link?
>
> No. The **Candidate Message** and image belong to the job req, so every link for that job req shows the same ones. Only the source differs from link to link.
> [accordion] Where do candidates who use the link show up?
>
> On the job req's **Candidates** tab, and on the **Candidates** page, like anyone else who applied. See [The Candidates page](/candidates/candidates-page).
## Related
> [card] [Magic links](/sourcing/magic-links)
>
> Make links that tag every applicant with a source.
> [card] [Add candidates](/sourcing/add-candidates)
>
> Add one person yourself and email them an invitation.
> [card] [Import candidates](/sourcing/import-candidates)
>
> Load a list of candidates into a job req.
> [card] [Social media](/sourcing/social-media)
>
> Bring in candidates from your social posts and ads.
# Job boards (career site)
Source: https://help.journeyfront.com/sourcing/job-boards
Set up, brand and share your job boards: the career sites where candidates find and apply to your jobs.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission create and edit job boards. Job postings are added from each job req; see [Job postings](/sourcing/job-postings).
In Journeyfront, your career site is called a **job board**: a branded page, hosted by Journeyfront, that lists your open job postings. Candidates search it, filter by location or remote option, open a posting and apply. You can run more than one job board, for example one per country or brand, embed a board in your own website, and share a feed of its jobs with job advertising partners.
## Job boards and job postings
| | **Job board** | **Job posting** |
| - | - | - |
| What it is | Your branded careers page that lists jobs | The ad for one job: title, location, pay and description |
| Where you set it up | **Settings**, then **Job Boards** | On the job req, under **Setup**, then **Job Postings** |
| How often | Once, then update the branding when you need to | For each job req. A job req can have several postings. |
You set up the board once. Each job req then gets one or more postings, and each posting is linked to one board. See [Job postings](/sourcing/job-postings).
## Create a job board
**1. Open Job Boards**
Go to **Settings**, then **Job Boards**. The list shows each board's **Status** and how many **Active Postings** and **Published Postings** it has.

**2. Create the board**
Click **Create New Board**, enter a **Job Board Name** and click **Save**.

**3. Open the board's settings**
Click the **â‹®** menu next to the board, then **Edit Job Board**. The board opens on its **General** tab.

**4. Turn it on**
Set **Enable Job Board** to **Yes**. New boards start turned off, so candidates can't see them until you do this.
**5. Add your details and save**
Fill in the **Home Website** and upload a **Header Logo** (see below), then click **Save** at the top of the page.
**6. Brand it (optional)**
Open the **Customize** tab to add your banner text, background image and colors. See [Customize the look](#customize-the-look).
> [!TIP]
>
> Use more than one board when different audiences should see different jobs, for example a board per country or per brand. Each posting is linked to one board, so candidates only see the jobs that are meant for them.
## General settings
The **General** tab holds the board's address and the basics.

| Setting | What it does |
| - | - |
| **Enable Job Board** | Turns the board on or off. A board that's turned off can't be opened by candidates, and **View Page** is unavailable. |
| **Job Board Name** | The board's name inside Journeyfront. |
| **Job Board URL** | The board's public address. Journeyfront creates it and it doesn't change, even if you rename the board. Use the copy icon in the field to copy it, or **View Page** next to it to open the board candidates see (see [What candidates see](#what-candidates-see)). |
| **Feed URL** | A feed of the board's jobs for job advertising partners. See [Share a job feed](#share-a-job-feed). |
| **Home Website** | Your company's website. Candidates reach it from the **Company Website** button on the board. |
| **Header Logo** | Your logo at the top of the board. Upload a PNG or JPEG file; click the trash icon to remove it. |
| **Enable Iframe** | Lets you embed the board in your own website. See [Embed the board in your website](#embed-the-board-in-your-website). |
| **Iframe URL** | The embed code to paste into your website. |
| **External Job Board Partners** | Sends the board's postings to Indeed. See [Indeed](/integrations/job-boards/indeed). |
> [!NOTE]
>
> If Indeed is activated for your account, a new job board starts with **Post Jobs to Indeed** and **Allow Indeed Easy Apply** already checked. Uncheck them on the **General** tab if this board shouldn't go to Indeed.
## Customize the look
The **Customize** tab is a visual editor. Settings are on the left and a live preview of the board is on the right. Your changes show in the preview as you make them, and go live when you click **Save**. Click **Cancel** to throw away changes you haven't saved.

| Section | What you can change |
| - | - |
| **Content** | **Hero Title** and **Hero Subtitle** (the banner text at the top), **Board Heading** (the heading above the job list; leave it empty to hide it) and a **Background Image** for the banner |
| **Hero** | **Show Hero** to turn the banner on or off, plus its **Height**, **Text Alignment**, **Vertical Position**, **Horizontal Padding**, **Content Gap**, **Overlay Color** and **Overlay Opacity** |
| **Typography** | **Font Family** (Lato by default), **Title Size**, **Subtitle Size** and **Text Shadow** |
| **Colors** | **Primary Color (Buttons)**, **Button Text Color**, **Nav Background**, **Hero Text Color** and **Hero Background** (shown when there's no background image) |
| **Settings** | **Show Results Count** above the job list, and **Multi-Language**. See [Multi-language](#multi-language). |
Use the buttons above the preview to see the board on a desktop, tablet or phone, and the refresh button to reload it.
> [!TIP]
>
> Use a background image that still reads well with text on top, and add an overlay if your title is hard to see. Check the phone view before you save: many candidates apply from their phones.
### Multi-language
Turn on **Multi-Language** to add a language menu to the board, so candidates can switch between English, Spanish and French. The board also opens in the candidate's browser language when it's one of these.
The menu translates Journeyfront's own text, like the search and filter labels and buttons. It doesn't translate what you write, such as job titles, job descriptions or the hero text.
## What candidates see
Candidates see your logo, the banner and your open jobs, newest first. They can:
* Search by **Job Title**, and filter by **Location** and **Remote Option**.
* Click **Company Website** to go to your **Home Website**.
* Click **View Job** to open a posting, then **Apply to position** to start the job req's application.

A board lists a posting when the posting is active and set to post to the board.
> [card] [Job postings](/sourcing/job-postings)
>
> Create the posting for each job req and choose whether it shows on the board.
## Embed the board in your website
**1. Turn on Enable Iframe**
On the board's **General** tab, set **Enable Iframe** to **Yes**, then click **Save** at the top of the page.

**2. Copy the embed code**
Click the copy icon at the end of the **Iframe URL** field. The code shows the board at the full width of the space it's placed in, 600 pixels tall.

**3. Add it to your careers page**
Paste the code into your website's careers page, or send it to whoever manages your website. You can change the height in the code to fit your page.
> [!WARNING]
>
> The embedded board only shows while **Enable Iframe** is on. If you turn it off, the board stops loading inside your website, but its own **Job Board URL** keeps working.
## Share a job feed
Each board has a **Feed URL**: an XML feed of the board's jobs that job advertising partners, such as Appcast, can read to advertise them. Copy it from the board's **General** tab and send it to your partner. The feed updates itself as you open and close postings. See [Appcast](/integrations/job-boards/appcast).
The feed lists the board's active postings on Active job reqs, with each job's title, location, employment type, remote option, description, pay and links to the posting and the application.
> [!NOTE]
>
> The feed always includes each posting's pay, even when **Show This Field** is off for **Pay** on the posting. If you don't want pay shared with a partner, leave the pay fields empty on that posting.
## Track where candidates come from
To see which channel brings in applicants, share a source link instead of the plain board address. Anyone who applies after opening that link has the source recorded on their Candidate Application.
**1. Open Generate Source Link**
In **Settings**, then **Job Boards**, click the **â‹®** menu next to the board, then **Generate Source Link**.

**2. Pick a source and generate**
Choose a source under **Select Source**, then click **Generate**.

**3. Copy the link**
Click the link or its copy icon to copy it, then share it in that channel.

> [card] [Magic links](/sourcing/magic-links)
>
> Tag applicants with the channel they came from.
## FAQ
> [accordion] Can I change my job board's URL?
>
> No. Journeyfront creates the address when you create the board, and it stays the same even if you rename the board. That way links you've already shared keep working.
> [accordion] Why can't candidates open my job board?
>
> Check that **Enable Job Board** is set to **Yes** on the board's **General** tab, and that you clicked **Save**. New boards start turned off.
> [accordion] Why isn't a job showing on my board?
>
> A job shows on the board when its posting is linked to this board, **Make job posting page active** is on and **Post job to job board** is on. Deactivating, closing or archiving the job req turns its postings off. See [Job postings](/sourcing/job-postings).
> [accordion] Can I delete a job board?
>
> There's no delete option. Set **Enable Job Board** to **No** to take a board offline.
> [accordion] Does Multi-Language translate my job descriptions?
>
> No. It translates Journeyfront's own labels and buttons. Job titles, descriptions and your hero text appear exactly as you wrote them.
> [accordion] My embedded board shows a blank space. What's wrong?
>
> Make sure **Enable Iframe** is set to **Yes** on the board's **General** tab and saved. Without it, browsers won't show the board inside another website.
> [accordion] Can I have different branding for different boards?
>
> Yes. Every board has its own logo, colors, fonts and banner.
## Related
> [card] [Job postings](/sourcing/job-postings)
>
> Create the posting for each job req and publish it to a board.
> [card] [Magic links](/sourcing/magic-links)
>
> Tag applicants with the channel they came from.
> [card] [Job board integrations](/integrations/job-boards)
>
> Send your postings to Indeed, JobTarget and Appcast.
> [card] [Sources](/sourcing/sources)
>
> Manage the list of sources your links can use.
# Job postings
Source: https://help.journeyfront.com/sourcing/job-postings
Create the public posting for a job req and publish it to your job boards.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission, on job reqs they can access. Setting up the job boards themselves needs *Company Settings Access*; see [Job boards](/sourcing/job-boards).
A job posting is the public ad for a job req: the title, location, pay and description candidates read before they apply. The job req is where your team manages candidates; the posting is what candidates see. When someone clicks **Apply to position** on a posting, they start the job req's application.

> [card] [What candidates see after they click Apply](/sourcing/invite-candidates#what-candidates-see)
>
> The sign-in page, then the job req's application, the same as from an invitation link.
A job req can have more than one posting. Use that to advertise the same job in different ways, for example with a different title for each city or on different job boards, while every applicant lands in the same job req.

## Before you start
You need at least one job board, set up under **Settings**, then **Job Boards**. See [Job boards](/sourcing/job-boards).
## Create a job posting
**1. Open Job Postings**
Open the job req and go to **Setup**, then **Job Postings**. Click **New Job Posting**.
**2. Name it and pick a job board**
Enter a **Job Post Name**. Only your team sees it, so make it easy to tell postings apart, like "Customer Service Rep, Dallas, Indeed". Choose the job board under **Link to Job Board**.
**3. Choose who can see it**
Set **Make job posting page active** and **Post job to job board** (see the table below).

**4. Fill in the job details**
Enter the **Job Title** candidates will see. It can be different from the job req's name. Then fill in the location, remote option, pay, employment type and posted date (see [Job details](#job-details)).
**5. Write the description**
Write the job description under **Job Page Body**. A posting can't be saved without one.
**6. Save**
Click **Save**. You go back to the list of postings. To make changes later, open the posting and click **Update**.
## Who can see a posting
Two switches decide whether candidates can reach a posting.
| **Make job posting page active** | **Post job to job board** | What happens |
| - | - | - |
| **Yes** | **Yes** | The posting is live and listed on its job board. |
| **Yes** | **No** | The posting isn't listed on the job board, but anyone with its link can open it and apply. |
| **No** | (turns off too) | The posting is offline. Its link shows that the posting is no longer active, with a link to your other openings. |
The job board itself must be turned on for candidates to see any of its postings.
> [!TIP]
>
> Use an active posting that isn't posted to the job board for private recruiting, like a referral drive or a hiring event: send the link to the people you want, without listing the job publicly.
## Job details
| Section | Fields |
| - | - |
| **Location** | **Country**, **City**, **State/Region** and **Zip/Postal code** |
| **Remote Options** | **In-Office**, **Hybrid** or **Remote** |
| **Pay** | **Compensation Currency**, **Compensation Type** (**Annually**, **Monthly** or **Hourly**) and the pay. Click **Switch To Range** to enter a minimum and maximum, or **Switch To Base** for a single rate. |
| **Employment Type** | Full-time, part-time and so on |
| **Job Posted Date** | The date shown to candidates |
| **Job Page Body** | The job description, in a rich text editor |
Each section except the body has a **Show This Field** switch. When it's set to **No**, Journeyfront keeps the value but doesn't show it on the posting. All of them start at **No**, so turn on the ones you want candidates to see.
> [!NOTE]
>
> Pay is still shared in your job board's feed when **Show This Field** is off. See [Share a job feed](/sourcing/job-boards#share-a-job-feed).
> [!TIP]
>
> Many places require pay ranges on job ads. Check the rules where you're hiring before you turn off **Show This Field** for **Pay**.
### Write the description with AI
The **Job Page Body** editor has an AI menu (the sparkles button). Use **AI Generate** to draft text, or select text first to **Shorten** it, **Lengthen** it, fix spelling and grammar, or give your own instruction with **Write Prompt**. Always read the result before you save.
### The job page URL
Once the posting is saved, **Job Page URL** shows its public address. Click the copy icon to copy it, or **View Job Page** to open it. The address is created once and doesn't change when you edit the title.

## Manage your postings
**Setup**, then **Job Postings** lists every posting on the job req with its **Job Board**, **Active Status** (**Active** or **Inactive**) and **Publish Status** (**Published** or **Not Published**). Click the **â‹®** menu on a posting to:
* **Edit Job Posting**
* **View Live Page**
* **Generate Source Link**: a link that records where applicants came from. See [Magic links](/sourcing/magic-links).

To send a posting to Indeed or to boards through JobTarget, open it and scroll to **External Job Board Posts**. See [Job board integrations](/integrations/job-boards).
## When the job req's status changes
Deactivating, closing or archiving a job req turns off all of its postings and takes them down from job boards. Reactivating the job req doesn't turn them back on: open each posting and turn on **Make job posting page active** and **Post job to job board** again. See [Job req statuses](/job-reqs/statuses).
Duplicating a job req doesn't copy its postings. Create new ones on the copy.
## What candidates see
A posting shows the job title, the sections you've chosen to show, the description and an **Apply to position** button. Clicking it starts the job req's application. If your job board has more than one language turned on, the posting uses the language the candidate chose on the board.
After someone applies, their Candidate Application shows the **Job Board** and **Job Post** they came through on its **Details** tab.
## FAQ
> [accordion] What's the difference between a job req and a job posting?
>
> The job req runs your hiring process: its workflow, team and candidates. The posting is the public ad for it. Every applicant from any of a job req's postings goes into the same job req.
> [accordion] Why isn't my job showing on the job board?
>
> Check that **Make job posting page active** and **Post job to job board** are both **Yes**, that the posting is linked to the right board, and that the job board is turned on. If the job req was deactivated, closed or archived, its postings were turned off; turn them back on after you reactivate it.
> [accordion] Can I change the posted date?
>
> Yes. **Job Posted Date** only changes the date candidates see. It doesn't change when the posting or the job req was created.
> [accordion] Can I tell which posting a candidate applied through?
>
> Yes. The **Job Post** field on the **Details** tab of their Candidate Application shows it.
> [accordion] Can I delete a posting?
>
> There's no delete option. Set **Make job posting page active** to **No** to take it down.
> [accordion] Why can't I save my posting?
>
> **Job Post Name**, **Link to Job Board**, **Job Title**, **Compensation Currency**, **Employment Type** and the **Job Page Body** are required. When you use a pay range, both the minimum and maximum are required too.
> [accordion] I don't see the Setup tab on my job req.
>
> The **Setup** tab needs the *Manage Job Req Settings* permission. Ask your Journeyfront admin to check your security role.
## Related
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Set up and brand the job boards your postings appear on.
> [card] [Magic links](/sourcing/magic-links)
>
> Tag applicants with the channel they came from.
> [card] [Job board integrations](/integrations/job-boards)
>
> Send postings to Indeed, JobTarget and Appcast.
> [card] [Job req statuses](/job-reqs/statuses)
>
> What deactivating, closing and archiving do to your postings.
# Lead ads
Source: https://help.journeyfront.com/sourcing/lead-ads
Turn lead ad form submissions into candidates on your job reqs automatically, with their answers, source and the ad they came from.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* link and manage lead forms, under **Settings**, then **Meta Lead Ads**, or from a job req's **Setup** tab (which also needs *Manage Job Req Settings*). Recruiters work with lead ad candidates like any other applicant.
>
> **Availability:** Lead ads need to be turned on for your account. Ask your Customer Success Manager.
A lead ad shows a short form right inside a social app, already filled in with the person's name and contact details. Candidates tap, check their details, answer a question or two and submit without leaving the app, which is why lead ads tend to bring in many more applicants than ads that send people to a website.
Journeyfront brings those submissions straight in, usually within seconds. Each lead becomes a Candidate Application on the job req you choose, keeps the campaign and ad it came from, and can get a one-tap email to finish applying with their answers already filled in.
No more exporting spreadsheets from an ads manager, and fewer leads going cold before anyone contacts them. Because every candidate keeps their campaign and ad, you can see which ads lead to hires, not just clicks.
[Meta Lead Ads](https://www.youtube.com/embed/BgILz2H277w)
## Supported platforms
Journeyfront brings in lead ads from **Meta**: lead forms on your Facebook Pages, whether the lead was submitted on Facebook, Instagram, Messenger or the Audience Network. An admin connects your Meta Business account once, and your forms then appear under **Settings**, then **Meta Lead Ads**.
> [card] [Connect Meta Lead Ads](/integrations/meta-lead-ads)
>
> Connect your Meta Business account and choose the Pages whose lead forms come into Journeyfront.
## How it works
1. **You build the lead form and ad** in the platform's ads manager, as you normally would.
2. **You link the form to a job req** in Journeyfront and map its questions to your fields and screening questions.
3. **Someone submits the form.** Journeyfront creates a Candidate Application on the linked job req. It starts at the beginning of the job req's workflow, like any other applicant.
4. **The candidate gets one invitation email**, if you turned it on, to finish the full application.
Every lead is logged, so you can see what came in, what didn't and why, and bring in leads that failed once you've fixed the cause.
## Link a lead form to a job req
Go to **Settings**, then **Meta Lead Ads**. Your lead forms appear automatically. Journeyfront checks for new forms every day; click **Refresh from Meta** to check now.
**1. Open the form's menu**
Find the form and open its actions menu, then choose **Connect to job req**.
**2. Pick the job req**
In **Job req**, choose where new candidates should go. A form links to one job req at a time.
**3. Check the source**
By default, the source is set from where each lead was submitted. To use one of your own sources instead, click **Add source override**. See [Sources for lead ad candidates](#sources-for-lead-ad-candidates).
**4. Choose whether to send an invitation**
**Send application invitation email** is on by default. Each new candidate gets one email with a link to finish their application.
**5. Connect**
Click **Connect**.
> [!TIP]
>
> Turn the invitation email off for broad awareness campaigns where you'd rather screen leads before contacting them, and leave it on for campaigns aimed at people ready to apply.
To send a form's leads to a different job req later, use the same menu and pick the new job req. New leads go to the new job req; candidates already created stay where they are.
### Link a form from the job req
You can also work from the job req. Open it, go to **Setup**, then **Lead Ads**. The tab lists every form linked to this job req with its status, Page, source, when it was linked and when it last synced, plus the **Send application invitation email** switch for each form.
**1. Open the picker**
Click **Link a form**.
**2. Find the form**
Search by form name, ID or Page. **Available** lists forms that aren't linked yet; **Linked to other reqs** lists forms already feeding another job req.
**3. Link it**
Click **Link**. For a form on another job req, click **Link here**, then **Link to this job req** to move it. Future leads come to this job req instead; leads already brought in on the other job req aren't affected.
Each form's menu on the tab has **Edit field mapping**, **Edit source** and **Unlink**.
## Map the form's questions
Mapping tells Journeyfront where each answer on your lead form should go.
**1. Open the mapping**
In the form's actions menu, choose **Edit field mapping**.
**2. Review the suggestions**
Each form question is listed with a suggested destination. Contact questions like full name, email and phone are matched automatically, and questions whose wording matches a screening question on the job req are matched to that question.
**3. Adjust anything that's off**
Send an answer to a standard field, a [personal or application field](/account-setup/custom-fields), a screening question on the job req, or choose **Don't import**. For multiple-choice questions, match each form answer to a Journeyfront answer.
**4. Save**
Name and email must be mapped before you can save. Click **Save mappings**.

* **Apply auto-map** appears when your choices differ from the suggestions. Click it to go back to the suggestions.
* Click the info icon next to a screening question to preview the full question before you map to it.
* If a question changes on the lead form later, its row is flagged so you know to check it. The other rows stay as they are.
> [!TIP]
>
> Map screening questions wherever you can. Candidates' answers then count toward screening right away, and they don't have to answer the same question twice.
That's it. The next lead submitted on that form becomes a candidate on the job req.
## Sources for lead ad candidates
By default, each lead's source is set from where it was submitted: **Meta Lead Ad - Facebook**, **Meta Lead Ad - Instagram**, **Meta Lead Ad - Messenger** or **Meta Lead Ad - Audience Network**. The form shows **Automatic** as its source.
To give every lead from a form one source of your own, for example to compare two campaigns, choose **Edit source** from the form's menu and pick it. The source then shows an **Override** badge. Sources are managed under **Settings**, then **Sources**.
> [card] [Sources](/sourcing/sources)
>
> Add your own sources and see how a candidate's source gets set.
## Form statuses
The **Meta Lead Ads** page lists every form with its status. Hover over a status to see what it means for that form.
| Status | What it means |
| - | - |
| **Active** | Linked to a job req and has brought in a lead in the last 30 days. |
| **Silent** | Linked, but the last lead was more than 30 days ago. |
| **Connected** | Linked, but no leads yet. |
| **Needs mapping** | Linked, but name and email aren't mapped, so every lead fails. Open **Edit field mapping** and save. |
| **Unconnected** | Not linked to a job req, so its leads don't become candidates. |
| **Disabled** | Paused by your team. New leads aren't brought in. |
| **Archived** | Archived in Meta; it can't receive new leads. |
The list also shows each form's Page and a **Leads** count (imported out of received). A warning icon on the count means some leads haven't made it in; hover over it for details. Use the search box, the **Status** and **Page** filters, and **Refresh from Meta** to find what you need.

## Check a form's health
Click a form's name (or **Open form** in its menu) to open its details panel. It has three tabs:
* **Overview:** the linked job req, source and invitation setting, lead counts, and the form's Page. Use **Edit field mapping** or **Edit source** from here.
* **Health:** click **Run health check** to check the whole path from the platform to Journeyfront for this form. Each check shows **OK**, **Check**, **Problem** or **Skipped**, with a suggested fix. The check also lists the most recent leads the platform has for the form and whether each one was received.
* **Logs:** the most recent lead deliveries for this form. Click **View all logs for this form** for the full log.
If the health check finds leads that never arrived, click **Import missing leads** (it shows the number, such as "Import 2 missing leads") to bring them in. Each import handles up to 200 leads; run it again for more.
To test the setup end to end, click **Send test lead** on the **Health** tab. A test lead is sent through the normal path. If the form is linked, a test candidate is created on the job req (and gets the invitation email if that's on). Delete the test candidate afterwards.

## Fix common problems
| What you see | What to do |
| - | - |
| A banner saying a Page isn't subscribed, or **Not subscribed** next to a form's Page | Leads from that Page aren't reaching Journeyfront. Choose **Repair Page subscription** from the form's menu. See [Fix connection problems](/integrations/meta-lead-ads#fix-connection-problems). |
| A banner listing forms that are receiving leads but aren't linked | Link each form to a job req, then choose **Retry failed leads** from its menu (it shows the number of leads, such as "Retry 3 failed leads") to bring in the leads that already arrived. |
| **Needs mapping** | Open **Edit field mapping**, make sure name and email are mapped, and click **Save mappings**. |
| A warning icon on a form's **Leads** count | Open the form and run the health check on the **Health** tab. |
| The health check shows leads marked **Never received**, but **Page sends lead notifications** is **OK** | Your Meta Business may be blocking Journeyfront in Leads Access. [Allow Journeyfront in Leads Access](/integrations/meta-lead-ads#allow-journeyfront-in-leads-access), then click **Import missing leads**. |
> [card] [Meta Lead Ads](/integrations/meta-lead-ads)
>
> Fix connection problems on the Meta side, such as Page subscriptions, permissions and Leads Access.
## Review the lead log
Go to **Settings**, then **Meta Lead Ads**, and click **View all logs**. Every lead delivered to Journeyfront is logged with its status, contact details, form and job req. To see one form's leads, choose **View Logs** from that form's menu.
* Filter by status (successes or failures), by when the lead was received, or search by email, name or form.
* Click **Download CSV** to download the filtered log.
* Open a row's actions menu and choose **View lead details** to see the lead's answers, campaign, ad and platform, read live from the platform.
* Choose **Retry** to process a failed lead again once you've fixed the cause. It's treated like a new submission: the candidate is created and gets the invitation email if that's on.
Common statuses:
| Status | What it means |
| - | - |
| **Success** | The candidate was created. |
| **Received** | The lead arrived and is being processed. |
| **Missing info** | The lead didn't include a first name, last name and email, which Journeyfront needs to create a candidate. |
| **Duplicate** | The person already has an application on that job req, so no second one was created. |
| **No mapping** | The form isn't linked to a job req. Link it, then retry. |
| **Form disabled** | The form was paused when the lead arrived. Activate it, then retry. |

## Pause or unlink a form
To pause new leads from a form, for example while a campaign is on hold, choose **Disable** from its menu. New leads are logged as **Form disabled** and don't become candidates. Choose **Activate** to start again.
Disabling keeps the link to the job req. To remove the link, choose **Unlink from job req** from the form's menu, or **Unlink** from the form's menu on the job req's **Lead Ads** tab. Future leads from the form stop creating candidates on that job req, and you can link it again any time.
> [!TIP]
>
> Leads that arrive while a form is disabled are still logged. After you activate the form, you can retry them from the log so no one is lost.
## Where lead details show on a candidate
Lead ad candidates appear on the linked job req like any other applicant. On their Candidate Application's **Details** tab you'll see the **Source** and where the lead came from: the platform, lead form, campaign, ad set and ad, and when they submitted. Answers mapped to screening questions appear with the candidate's other screening results.
## What candidates see
If the invitation email is on, the candidate gets one email (not a series) with a link to finish their application. The link works for 30 days and signs them in, and the answers they gave on the lead form are already filled in, so they only complete what's left.
## FAQ
> [accordion] Does this work for Instagram lead ads too?
>
> Yes. Instagram lead forms run on the same Meta lead ads system, so forms on your connected Pages come in the same way, whether the lead was submitted on Facebook, Instagram, Messenger or the Audience Network.
> [accordion] How quickly do candidates appear?
>
> Usually within seconds. Each lead is sent to Journeyfront as soon as it's submitted.
> [accordion] Will candidates get a lot of emails?
>
> No. The invitation is a single email, and you choose for each form whether it's sent.
> [accordion] What happens to leads from a form that isn't linked yet?
>
> They're logged as **No mapping** and don't become candidates. After you link the form, choose **Retry failed leads** from its menu to bring them in. Leads submitted before you connected Meta at all aren't brought in.
> [accordion] Can one lead form feed more than one job req?
>
> Not at the same time. A form links to one job req. If you move it to a different job req, new leads go there.
> [accordion] What if we change a question on the lead form?
>
> Journeyfront checks your forms daily. Changed or new questions are flagged in the mapping editor so you can review them; the rest of the mapping stays in place.
> [accordion] Can Journeyfront create lead forms or ads for us?
>
> No. You build lead forms and ads in the platform's ads manager. Journeyfront brings in the forms from the Pages you connect, and can't post to your Page or change your ads.
> [accordion] How is this different from job boards?
>
> Job boards send your job postings out to people browsing job sites. Lead ads bring people in from the social ads you're already running. Both end up as Candidate Applications on your job reqs.
## Related
> [card] [Meta Lead Ads](/integrations/meta-lead-ads)
>
> Connect your Meta Business account and Pages.
> [card] [Social media](/sourcing/social-media)
>
> Every way candidates reach you from social media.
> [card] [Custom fields](/account-setup/custom-fields)
>
> Create the personal fields you map lead form answers to.
> [card] [Job boards](/integrations/job-boards)
>
> Post your job reqs where candidates are looking.
> [card] [Employee referrals](/referrals/overview)
>
> Let employees refer people they know.
> [card] [Integrations overview](/integrations/overview)
>
> Everything Journeyfront connects to.
# Magic links
Source: https://help.journeyfront.com/sourcing/magic-links
Share links that tag every applicant with where they came from, then see which channels bring in your hires.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* create magic links for job boards. Users with *Manage Job Req Settings* create them for job postings, and anyone who can open a job req can copy its invitation link with a source. Company-wide source reports need *Company Dashboard Access*.
A magic link is a link to your jobs that tags every applicant who uses it with a source. Share it in an ad, a post, a text or on a flyer, and anyone who applies after opening it gets that source on their Candidate Application automatically. Nobody has to ask "where did you hear about us?", and nobody has to remember to answer it.
Every Candidate Application has a **Source**: where the candidate came from, such as Indeed, a job fair or your newsletter. When sources are recorded consistently, you can see which channels bring in candidates who get hired and stay, and spend your budget there.
A magic link is your normal job board, posting or invitation link with the source added to the end. In the app, the menu option that makes one is called **Generate Source Link**.
## Kinds of magic links
| Magic link | Where it takes candidates | Where you make it |
| - | - | - |
| **Job board** | Your whole career site, so candidates can pick a job | **Settings**, then **Job Boards**, then **Generate Source Link** |
| **Job posting** | One job's posting, with its description and an **Apply to position** button | The job req's **Setup**, then **Job Postings**, then **Generate Source Link** |
| **Invitation link** | Straight into one job req's application | The job req's **Actions**, then **Invite Candidates**, with a **Source** picked |
| **Referral links** | A job or your career site, shared by an employee | Each employee's referral portal. See [Referral links](#referral-links). |
## Make a magic link
> [tab] Job board
>
> Use this for links to your whole career site.
>
> 1. Go to **Settings**, then **Job Boards**.
> 2. Click the **â‹®** menu next to the board, then **Generate Source Link**.
>
> 
> 3. Choose a source under **Select Source** and click **Generate**.
> 4. Click the link to copy it.
>
> The source stays with the candidate as they browse from the board to a posting and apply.
> [tab] Job posting
>
> Use this to promote one job.
>
> 1. Open the job req and go to **Setup**, then **Job Postings**.
> 2. Click the **â‹®** menu on the posting, then **Generate Source Link**.
>
> 
> 3. Choose a source under **Select Source** and click **Generate**.
> 4. Click the link to copy it.
> [tab] Invitation link
>
> Use this to send candidates straight into the job req's application, for example in a text or an email.
>
> 1. Open the job req and click **Actions**, then **Invite Candidates**.
>
> 
> 2. Under **Source**, choose a source before you copy the link.
> 3. Under **Invitation Link**, click **Copy**.
>
> Choosing a source changes only the link you copy. It isn't saved on the job req, so the next person who opens the window starts with **No Source Selected**. See [Invite candidates](/sourcing/invite-candidates).

> [!TIP]
>
> Make a separate magic link for every place you share a job: one for your Facebook post, one for the job fair flyer, one for the newsletter. Then your reports can tell them apart.
> [!WARNING]
>
> A magic link records the source by its name. If you rename or delete that source under **Settings**, then **Sources**, links that already use the old name stop recording it. Make new links after you rename a source.
> [!TIP]
>
> Keep source names to letters, numbers and spaces. Characters like `&` and `#` can cut a link short, so the source isn't recorded.
## Referral links
Employees get their own magic links on your referral portal: a **Personal Link** to all your open jobs, and a link for each job they **Share**. Anyone who applies through an employee's link is recorded as that employee's referral, with the portal's **Referral Source** (**Referral** unless you choose another). You don't make these links yourself; each employee's portal makes them. See [Using the referral portal](/referrals/employee-portal#find-and-share-jobs) and [Set up a referral portal](/referrals/portal-setup).
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Choose the portal's Referral Source and give employees links to share.
## Sources and reporting
A magic link is one of several ways a candidate's source gets set; integrations, referral portals and imports set it too. To manage your list of sources, see or correct a candidate's source, and compare which sources bring in hires, see [Sources](/sourcing/sources).
> [card] [Sources](/sourcing/sources)
>
> Manage your sources, see or correct a candidate's source, and compare which sources bring in hires.
## FAQ
> [accordion] Why do some candidates have no source?
>
> Usually because they applied through a link that isn't a magic link: the job req's invitation link copied without choosing a **Source**, or a plain job board or posting link. Candidates you add by hand also start with no source. Use magic links everywhere you share a job, and set the source yourself when you add someone by hand.
> [accordion] Can candidates change their own source?
>
> No. The source comes from the link they used, and only your team can change it on the Candidate Application.
> [accordion] A candidate used a magic link, but no source was recorded. Why?
>
> The name in the link has to match a source in your account. This happens when the source was renamed or deleted after the link was made, or when the link was cut off or edited. Make a fresh link.
> [accordion] The candidate had already applied before using my magic link. Does the source change?
>
> No. A magic link only sets the source when the candidate's application to that job req is created.
> [accordion] Do magic links expire?
>
> No. A magic link keeps working as long as the job board, posting or job req it points to is live and the source keeps its name.
> [accordion] How do I add a new source, like a specific job fair?
>
> An admin adds it under **Settings**, then **Sources**, with a **Source Type**. It's then available when you make links. See [Sources](/sourcing/sources).
> [accordion] Can I tell which job posting a candidate applied through?
>
> Yes. The **Job Post** field on the **Details** tab of their Candidate Application shows it, alongside the source.
## Related
> [card] [Sources](/sourcing/sources)
>
> Add and organize the sources your links use.
> [card] [Invite candidates](/sourcing/invite-candidates)
>
> Share a job req's invitation link by text, email, social or poster.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Find the Source Effectiveness dashboard and the rest.
> [card] [Job req dashboards](/reporting/job-dashboards)
>
> Source results for a single job req.
# Social media
Source: https://help.journeyfront.com/sourcing/social-media
Recruit on Facebook, Instagram, LinkedIn, TikTok and X with lead ads, tracked job links and employee sharing, then see which networks bring in hires.
> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access* set up lead ads and manage sources. Users with *Manage Job Req Settings* create magic links for job postings, and anyone who can open a job req can copy its invitation link.
For high-volume hiring, social media is often where your next candidates are scrolling. Candidates reach Journeyfront from social media in three ways, and every one of them ends up as a Candidate Application on a job req, tagged with where it came from.
| How it works | Best for | What lands in Journeyfront |
| - | - | - |
| **Lead ads:** candidates fill in a short form without leaving Facebook or Instagram | Paid campaigns that need lots of applicants fast | A candidate on the job req you chose, with their form answers, the platform, campaign and ad |
| **Job links in your posts and ads:** a magic link to a job posting, your job board or a job req's application | Organic posts, paid ads on any network, groups, pages and profile links | A candidate who applied through the link, tagged with the link's source |
| **Employees sharing jobs** from your referral portal | Reaching your employees' friends and family | A referral, credited to the employee who shared |
## Organic or paid
Most teams use both. They do different jobs:
| | Organic | Paid |
| - | - | - |
| **What it is** | Posts on your own pages and profiles, in community groups, and shared by your employees | Ads you pay the network to show, including lead ads and ads that link to a job |
| **Cost** | Free, but takes time to post regularly | You pay per view or click, set by your budget |
| **Reach** | People who already follow you, and their networks when they share | People who don't know you yet, in the area you choose |
| **Best for** | Steady, always-on hiring and building a local reputation as an employer | Filling a hiring class by a date, opening a new site, or a role that's hard to fill |
| **What to use in Journeyfront** | Magic links, and employees sharing from the referral portal | Lead ads, or magic links as the ad's destination |
A practical pattern for high-volume roles: keep organic posts going all the time with a magic link in each, and turn on paid campaigns when a hiring class needs to fill fast. Lead ads are usually the quickest way to get a lot of applicants from paid social, because candidates apply without leaving the app.
> [!NOTE]
>
> Ad networks have their own rules for job ads. Meta, for example, asks advertisers to run ads for job opportunities under its **Employment** special ad category, which limits how you can target by age, gender and location. Check each network's advertising policies before you launch a campaign.
## Lead ads
A lead ad shows a short form right inside Facebook or Instagram, already filled in with the person's name and contact details. Candidates tap, check their details, answer a question or two and submit, all without leaving the app.
With lead ads set up, each form submission lands in Journeyfront within seconds:
* **A Candidate Application** on the job req you linked the form to. It starts at the beginning of the job req's workflow, like any other applicant.
* **Their answers.** Contact details fill in the candidate's profile, and you can map other answers to your personal and application fields or to screening questions on the job req, so candidates don't answer the same question twice.
* **The source,** set automatically from where the lead was submitted: **Meta Lead Ad - Facebook**, **Meta Lead Ad - Instagram**, **Meta Lead Ad - Messenger** or **Meta Lead Ad - Audience Network**. You can choose one of your own sources for a form instead.
* **The campaign, ad set and ad,** shown on the Candidate Application's **Details** tab, so you can see which ads lead to hires, not just clicks.
* **An optional invitation email,** sent once, with a link that signs the candidate in so they can finish the full application. The answers they gave on the lead form are already filled in.
Your lead forms and ads are built in Meta Ads Manager. In Journeyfront, an admin [connects your Meta Business account](/integrations/meta-lead-ads), then links each lead form to a job req and maps its questions. Lead ads need to be turned on for your account.
> [!TIP]
>
> Map lead form questions to screening questions wherever you can. Candidates' answers then count toward screening as soon as they arrive, and your team can act on the strongest leads first.
> [card] [Lead ads](/sourcing/lead-ads)
>
> Link lead forms to job reqs, map their questions and follow every lead.
## Share job links in your posts and ads
For an organic post, a paid ad on any network, a group, or a link in your profile, share a magic link: a link that tags candidates with a source. Anyone who applies after opening it is tagged automatically.
**1. Check you have a source for the channel**
Journeyfront includes default sources for **Facebook**, **LinkedIn (Social Media)**, **X (Twitter)** and **TikTok**, all with the **Social Media** source type. For anything else, such as Instagram or a specific campaign, an admin adds a custom source under **Settings**, then **Sources**, with the **Social Media** source type. See [Sources](/sourcing/sources).
**2. Pick the right link**
* **One job, with its description:** a magic link to a job posting. Open the job req, go to **Setup**, then **Job Postings**, click the **â‹®** menu on the posting, then **Generate Source Link**.
* **All your open jobs:** a magic link to a job board. Go to **Settings**, then **Job Boards**, click the **â‹®** menu next to the board, then **Generate Source Link**.
* **Straight into one job req's application:** the job req's invitation link, with a **Source** picked before you copy it. See [Invite candidates](/sourcing/invite-candidates).
**3. Post it**
Paste the link into your post or ad. To compare two networks or campaigns, give each its own source and its own link.
For more on each kind of magic link, see [Magic links](/sourcing/magic-links).
> [!TIP]
>
> Job posting links work best for posts where people discover the job, because they show the pay, shift and description first. Invitation links work best when your post or ad already explains the job and you want people applying in one tap.
> [!WARNING]
>
> Links record the source by its name. If you rename or delete the source later, links already in your posts stop recording it. Keep source names to letters, numbers and spaces.
> [card] [Magic links](/sourcing/magic-links)
>
> Every kind of link that tags candidates with a source, and how to make each one.
## Let employees share jobs
Your employees' own social networks are a strong channel for high-volume roles. On your referral portal, employees click **Share** on any job to get their own link to it, and send it with WhatsApp, Facebook, LinkedIn, Messenger, Telegram, email, text or their phone's own share menu. They also have a personal link to all your open jobs, with a QR code.
Anyone who applies through an employee's link is recorded as that employee's referral, with the portal's **Referral Source** (**Referral** unless you choose another). That means these candidates show up in your referral reporting and can earn the employee a reward, rather than counting as social media. See [Using the referral portal](/referrals/employee-portal#find-and-share-jobs) and [Set up a referral portal](/referrals/portal-setup).
> [card] [Set up a referral portal](/referrals/portal-setup)
>
> Give employees a portal where they share jobs with their own tracked links.
## Tips by network
A few habits work everywhere: lead with the pay, the shift and the location, keep the post short enough to read on a phone, use a real photo of your site or team, and put one magic link in every post so you know where applicants came from.
### Facebook
* **Your company Page.** Post open roles regularly, and pin a post for the jobs you're hiring for most. Use a job posting link so people see the details before they apply.
* **Local groups.** Community, neighborhood and local job groups reach people near your site. Read each group's rules first, since many limit job posts to certain days or formats. Give groups their own source, such as "Facebook Groups", if you want to compare them with your Page.
* **Paid campaigns.** For volume, run lead ads so people apply without leaving Facebook. See [Lead ads](/sourcing/lead-ads).
### Instagram
* **Posts.** Links in Instagram captions aren't clickable, so point people to the link in your bio.
* **Stories.** Add a link to a story so people can tap straight through to the job. Stories suit time-sensitive news, such as a hiring event or a new hiring class.
* **Bio link.** Keep a magic link to your job board in your profile so it's always there. Create an **Instagram** source first, since there's no default one.
* **Ads.** Instagram lead ads come in through your Meta connection, the same as Facebook, with the source **Meta Lead Ad - Instagram**.
### LinkedIn
* **Company page and team posts.** Post from your company page and ask recruiters, site leaders and team leads to reshare. Reshares from real people usually reach further than the company page alone.
* **Best fit.** LinkedIn tends to work best for team lead, supervisor, trainer and other experienced roles. For entry-level hourly roles, Facebook, Instagram and TikTok usually bring in more applicants.
* Use the **LinkedIn (Social Media)** source so these applicants don't get mixed up with job board traffic.
### TikTok
* **Profile link.** TikTok videos don't carry clickable links, so put a magic link to your job board in your profile and tell viewers to tap it.
* **Short, real videos.** A quick day-in-the-life clip from an agent or a site tour often does better than a polished ad. Say the pay and the shift in the first few seconds.
* Use the **TikTok** source to see what TikTok brings in.
### X
* **Short posts with a link.** Post the role, pay and location with a job posting link, and pin your main hiring post to your profile.
* **Timely news.** X suits quick updates, such as a hiring event this week or a new site opening.
* Use the **X (Twitter)** source.
## Measure what social media brings in
Track more than applications. A network that brings in lots of applicants who never finish applying, or who drop out before their start date, can cost you more than a smaller channel that fills seats.
| What to measure | Where to find it |
| - | - |
| Candidates from each network | The **Candidates** page, filtered by the **Social Media** source type or by single sources such as **Meta Lead Ad - Instagram**, with the **Source** and **Source Type** columns added. See [The Candidates page](/candidates/candidates-page). |
| Interviews and hires by source, and how candidates from each source score | The **Source Effectiveness** dashboard, by single source or by source type. See [Dashboards overview](/reporting/dashboards). |
| How long hires from each source stay and how they perform | The post-hire view of the **Source Effectiveness** dashboard. |
| One job req's results | The job req's **Dashboard** tab, on **Source Effectiveness**. See [Job req dashboards](/reporting/job-dashboards). |
| Which campaign or ad a lead came from | The **Details** tab of a lead ad candidate's Candidate Application, which shows the platform, lead form, campaign, ad set and ad. |
| Leads received compared with candidates created | The **Leads** count on each lead form under **Settings**, then **Meta Lead Ads**. See [Form statuses](/sourcing/lead-ads#form-statuses). |
> [!TIP]
>
> To compare campaigns, not just networks, give each campaign its own source: a separate magic link for organic posts, or **Edit source** on a lead form. Keep the list short so reports stay easy to read.
> [card] [Dashboards overview](/reporting/dashboards)
>
> Compare social media with your other channels by candidates, interviews and hires.
## FAQ
> [accordion] Do I need lead ads to recruit on Facebook or Instagram?
>
> No. You can post job links on Facebook and Instagram, or run ads that send people to a job posting, without connecting anything. Lead ads are worth setting up when you run paid campaigns and want candidates to apply without leaving the app.
> [accordion] Can Journeyfront bring in lead forms from LinkedIn or TikTok?
>
> No. Lead ads come in from Meta: Facebook, Instagram, Messenger and the Audience Network. For LinkedIn, TikTok and other networks, share job links with a source.
> [accordion] Can Journeyfront post to our social media pages for us?
>
> No. You post on your own pages and accounts. Journeyfront gives you the links to share and records where applicants came from. Connecting Meta doesn't let Journeyfront post to your Page or change your ads.
> [accordion] A candidate came from Facebook but has no source. Why?
>
> They probably applied through a link without a source, such as a plain job board address or an invitation link copied without picking a **Source**. Use magic links in every post. See [Magic links](/sourcing/magic-links).
> [accordion] Should every post get its own source?
>
> Not necessarily. Sources are for comparing channels, so keep the list short: one source per network, or per network and campaign when you want to compare campaigns. Too many near-identical sources make reports harder to read. See [Sources](/sourcing/sources).
## Related
> [card] [Lead ads](/sourcing/lead-ads)
>
> Link lead forms to job reqs and follow every lead.
> [card] [Magic links](/sourcing/magic-links)
>
> Make links that tag applicants and see which channels work.
> [card] [Invite candidates](/sourcing/invite-candidates)
>
> Send people straight into a job req's application.
> [card] [Employee referrals](/referrals/overview)
>
> Let employees refer and share jobs with people they know.
# Sources
Source: https://help.journeyfront.com/sourcing/sources
Set up the places your candidates come from, see where each candidate came from, and measure which sources bring in your hires.
> [!NOTE]
>
> **Who can do this:** Admins with the *Company Settings Access* permission manage the list of sources. Anyone who can edit a candidate can change that candidate's source.
A source records where a candidate came from: a job board, a referral, a job fair, an agency. Each Candidate Application has one source, and your dashboards, filters and exports group candidates by it. The list your team, your links and your integrations choose from lives in **Settings**, then **Sources**.
A short, consistent list is what makes source reporting useful. If the same channel shows up under three slightly different names, you'll never get a straight answer to "where do our best hires come from?"
## Sources and source types
The **Sources** page has two lists:
* **Custom Sources:** sources your team added, such as a local college, an agency or a radio campaign.
* **Default Sources:** sources built into Journeyfront, such as Indeed, LinkedIn, ZipRecruiter, Referral, Internal Applicant and the Meta Lead Ad sources. You can turn these on or off, but not rename or delete them.
Every source has a **Source Type**, which groups similar sources together in reports and filters:
| Source Type | Use it for |
| - | - |
| **Agency** | Candidates sent by a recruiting or staffing agency |
| **Company Marketing** | Your own marketing: your website's jobs page, newsletters, email campaigns |
| **Event** | Job fairs, campus recruiting, meetups and other events |
| **Job Board** | Job boards such as Indeed, LinkedIn or ZipRecruiter |
| **Internal** | Current employees applying for a promotion or transfer |
| **Prospecting** | Candidates your team found and reached out to |
| **Referral** | Candidates referred by employees or partners |
| **Social Media** | Facebook, Instagram, TikTok, X and other social channels |
| **Other** | Anything that doesn't fit the types above |

## Add a custom source
**1. Open Sources**
Go to **Settings**, then **Sources**.
**2. Click Add Source**
The **Add Source** window opens.
**3. Choose the type and name**
Pick a **Source Type**, then enter the **Source Name**, for example "Spring Hiring Fair 2026".
**4. Click Save**
The new source appears under **Custom Sources**, and your team can pick it straight away.
Each source needs its own name, and you can't reuse the name of a default source.
> [!TIP]
>
> Agree on a naming pattern before you add sources, such as "Event name + year" or "Agency name". Name the channel, not the campaign detail: one "Spring Hiring Fair 2026" source beats separate sources for each booth or flyer.
## Edit or delete a custom source
* **Edit:** click the edit icon, change the **Source Type** or **Source Name**, and click **Update**. Candidates who already have the source show the new name.
* **Delete:** click the trash icon, then **Delete**. You can only delete a source that no candidate has. If any candidate has it, you'll see "Cannot delete source because it is assigned to one or more candidates."
> [!WARNING]
>
> Source links carry the source's name. If you rename a source, links you've already shared with the old name stop tagging new candidates. Create fresh links after a rename. See [Magic links](/sourcing/magic-links).
## Turn default sources on or off
Use the **Status** switch next to each default source. Turning a source **Off** removes it from the lists your team picks from, such as the **Invite Candidates** window, a candidate's **Details** tab and the job board and referral portal settings.
Turning a source off doesn't change candidates who already have it, and links that already use it keep working.
> [!TIP]
>
> Turn off the default sources your company never uses. A shorter list means faster picking and fewer candidates tagged with the wrong source.
## How a candidate's source gets set
| How the candidate arrives | Source they get |
| - | - |
| A career site or job board link made with **Generate Source Link** | The source you picked for the link. See [Magic links](/sourcing/magic-links). |
| A job req's invite link, copied after picking a **Source** | That source. See [Magic links](/sourcing/magic-links#make-a-magic-link). |
| Indeed Easy Apply | The source set for Indeed Apply candidates in the job board's settings, or **Indeed** if none is set. See [Indeed](/integrations/job-boards/indeed). |
| A referral portal | The portal's referral source, or **Referral** if none is set. See [Set up a referral portal](/referrals/portal-setup). |
| Lead ads | A Meta Lead Ad source for the platform the lead came from, such as **Meta Lead Ad - Facebook** or **Meta Lead Ad - Instagram**, unless the form has a source override. See [Lead ads](/sourcing/lead-ads#sources-for-lead-ad-candidates). |
| A candidate import | The value in the file's `source` column, which must match a source name in your account. See [Import candidates](/sourcing/import-candidates#columns). |
| Added by hand | Whatever your team picks on the Candidate Application's **Details** tab, or in the **Source** column on the Candidates list. See [Edit candidate details](/candidates/edit-details). |
Some integrations can also send candidates with a source name that isn't on your list yet. Journeyfront then adds that source under **Custom Sources** with the type **Other**. Check your list now and then, and give those sources the right type.
## See or change a candidate's source
Open the Candidate Application and go to the **Details** tab. The **Application Details** card shows the **Source**, plus the **Job Board** and **Job Post** the candidate applied through, when they came from a posting.
To correct the source, choose a different one from the **Source** field. You can also change it right in the list on the **Candidates** page, by clicking a cell in the **Source** column. The change is recorded in the candidate's activity history.
## See which sources work
| Where | What it shows |
| - | - |
| **Candidates** page | Add the **Source** and **Source Type** columns, or filter by **Sources** and **Source Types**. See [The Candidates page](/candidates/candidates-page). |
| **Source Effectiveness** dashboard (company-wide) | Which sources and source types bring in candidates, interviews and hires, how their candidates score and move through your process, and, when you have employee data, how long hires from each source stay and how they perform. See [Dashboards overview](/reporting/dashboards). |
| **Source Effectiveness** on a job req's **Dashboard** tab | The same view for one job req. See [Job req dashboards](/reporting/job-dashboards). |
| Automation rules | Use the **Source** condition to treat candidates differently by where they came from. See [Automation rules](/workflows/automation-rules). |
Both Source Effectiveness dashboards let you switch between single sources and source types, and filter by dates, status and more.
## FAQ
> [accordion] Why do some candidates have no source?
>
> They applied through a link that didn't carry one, for example a job req's invite link copied without picking a **Source**, or a career site link shared without making a source link. Use a separate source link for each place you advertise. See [Magic links](/sourcing/magic-links).
> [accordion] Why can't I delete a source?
>
> Some candidates have it. Rename it instead, or turn it into the source you want to keep by changing its name and type. Default sources can't be deleted; turn them off.
> [accordion] We have two sources for the same channel. How do I combine them?
>
> There's no merge. Pick the one to keep, then change the source on the other's candidates (on each Candidate Application's **Details** tab, or in the **Source** column on the Candidates list). Once no candidate has the extra source, delete it.
> [accordion] Why does a candidate have a source that isn't on the Sources page?
>
> Candidates who apply through a JobTarget posting get a source named after the job board they came from. Those sources are created automatically, don't appear on the **Sources** page, and can't be changed on the candidate.
> [accordion] Can I change a candidate's source after they apply?
>
> Yes, on the Candidate Application's **Details** tab or in the **Source** column on the Candidates list. Sources set by some integrations, like JobTarget, can't be changed by hand. See [Edit candidate details](/candidates/edit-details).
> [accordion] Does turning off a default source affect old candidates?
>
> No. Candidates who already have it keep it, and it still appears in your reports and filters. It just stops appearing in the lists your team picks from.
## Related
> [card] [Magic links](/sourcing/magic-links)
>
> Create links that tag candidates with a source.
> [card] [Dashboards](/reporting/dashboards)
>
> Compare sources in Source Effectiveness.
> [card] [Invite candidates](/sourcing/invite-candidates)
>
> Pick a source for a job req's invitation link.
> [card] [Job boards (career site)](/sourcing/job-boards)
>
> Your job boards and their source links.
# Activities you can add
Source: https://help.journeyfront.com/workflows/activities
Every activity type a workflow step can include, who completes it, what it needs and where to learn more.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add activities to a job req's workflow.
>
> **Availability:** Some activities are add-ons or need something set up for your account first. The table below notes which.
Activities are what candidates (and your team) actually do in each step of a workflow: answer screening questions, take a test, meet an interviewer, sign an offer. You add them in the workflow editor: open the job req, go to **Setup**, then **Workflow**, and click **Create New Version** (or **Edit Draft** if there's already a draft). Every activity type is listed in the building blocks on the left, and you drag the one you want into a step. To learn how steps and activities are added and arranged, see [Build a workflow](/workflows/build).

## Activity catalog
| In the building blocks | Who does it | What it's for | Availability | Learn more |
| - | - | - | - | - |
| **Screening Questions**: **New Screening Questions**, or one of your saved templates | Candidate | Questions candidates answer online, scored against the attributes the job needs. | Every account | [Screening questions](/assessments/screening-questions) |
| **Interviews**: **New Interview**, or one of your saved interview templates | Interviewer | A structured interview your team runs with an interview guide, plus self-scheduling. | Every account | [Interview activity](/interviews/interview-activity) |
| **Skills Tests**: one block per skills test on your account | Candidate | Tests of the specific skills a role needs. Dropping one in adds its latest version. | Only the skills tests set up for your account. Ask your Customer Success Manager. | [Skills tests](/assessments/skills-tests) |
| **New Behavioral Assessment** | Candidate | An assessment of work-related behaviors and traits. | Every account | [Behavioral assessment](/assessments/behavioral-assessment) |
| **New Typing Test** | Candidate | Typing speed and accuracy. Candidates need a computer with a keyboard. | Every account | [Typing test](/assessments/typing-test) |
| **New Emmersion Assessment** or **New Hallo Assessment** | Candidate | A language assessment from one of Journeyfront's partners. | Add-on. Listed only once a language assessment partner is turned on for your account, and uses credits. | [Language assessments](/assessments/language-assessments) |
| **System Requirements Test** | Candidate | Checks a remote candidate's computer and internet connection against your requirements. | Add-on. You choose one of your account's requirement sets. | [System requirements test](/assessments/system-requirements) |
| **Internet Speed Test** | Candidate | Measures the candidate's download and upload speed. | Every account | [Internet speed test](/assessments/internet-speed-test) |
| **Offer** | Your team sends it; the candidate signs | The candidate's offer: terms, documents and e-signature. | Every account. Sending offers for signature uses the E-Signatures add-on. | [Offers overview](/offers/overview) |
| **Onboarding Form** | Your team sends it; the new hire fills it in | A form that collects onboarding details from new hires. | Every account | [Onboarding forms](/onboarding/onboarding-forms) |
| **Checkr Background Check** | Your team orders it | A background check your team orders from the Candidate Application. | Ordering checks needs an admin to connect your Checkr account first. | [Background checks](/onboarding/background-checks) |
On the Workflow page, each activity's line shows its type and **Completed by**: **Interviewer** for interviews and **Candidate** for everything else. Offers, onboarding forms and background checks are worked from the Candidate Application by your team.
> [!TIP]
>
> Match the activity to the decision. Use screening questions and short tests early to narrow a large applicant pool, and save interviews, which cost your team's time, for the candidates who make it through.
## Set up an activity
After you drag an activity into a step, click it to open its settings on the right. Every activity has a name you can change at the top, and most have **Estimated Time (Minutes)**. The rest depends on the type:
| Activity | What you set up |
| - | - |
| Screening questions | **Time Limit**, **Instructions**, **Supporting Content** and the **Questions** (**Add Question**) |
| Interview | **Instructions for Interviewer**, the **Questions**, and scheduling under **Interview Scheduler** |
| Behavioral assessment | The assessment to use (**Add Assessment**) |
| Typing test | The typing test to use (**Add Typing Test**) and its scoring |
| Language assessment | The partner's test (**Add Assessment Test**) and its scoring |
| Skills test | Which version of the test to use and its scoring by section |
| System requirements test | The **Requirement Set**, then its instructions and scoring |
| Internet speed test | **Instructions** and **Scoring** |
| Offer | The **Offer Package** and how strictly offers follow it |
| Onboarding form | The default onboarding form and whether candidates are invited to it automatically |

Your changes are part of the workflow draft. They reach candidates when you publish. See [Publish workflow changes](/workflows/publish).
## Choosing activities for a step
* **One step can hold several activities.** Candidates complete them in the order listed, unless the job req allows them to take activities out of order. See [Job settings](/job-reqs/job-settings).
* **Candidates only see activities in their current step.** Your team or an automation rule moves them to the next step. See [Build a workflow](/workflows/build#how-candidates-move-between-steps).
* **Most activities produce a score** that feeds the candidate's overall score and can be used in [automation rules](/workflows/automation-rules). See [How scoring works](/scoring/how-scoring-works).
> [!TIP]
>
> Keep the total candidate time in a step reasonable. Each step on the Workflow page shows its total estimated minutes, and long steps lose candidates. Preview the step on a phone before you go live.
## FAQ
> [accordion] Why don't I see a language assessment in the building blocks?
>
> Language assessments only appear once a partner is turned on for your account. Ask your Customer Success Manager. See [Add-ons and credits](/account-setup/add-ons).
> [accordion] I see Checkr Background Check, but we don't use Checkr. Can I add it?
>
> The building block is listed on every account, but checks can only be ordered once an admin connects your Checkr account. See [Checkr](/integrations/background-checks/checkr).
> [accordion] Why isn't the skills test I need listed?
>
> **Skills Tests** only lists the skills tests set up for your account. Ask your Customer Success Manager which skills tests are available for your roles. See [Skills tests](/assessments/skills-tests).
> [accordion] Where's AI resume scoring?
>
> AI resume scoring isn't an activity in a step. When it's turned on for your account, you set it up on the job req under **Setup**, then **AI Resume Scoring**. See [AI resume scoring](/scoring/ai-resume-scoring).
> [accordion] Can I preview an activity before candidates see it?
>
> Yes. On the Workflow page, click the eye icon (**Preview Activity**) on the activity. Partner assessments can't be previewed. See [Build a workflow](/workflows/build#preview-what-candidates-see).
> [accordion] Do offers and onboarding forms need to be in the workflow?
>
> Yes. The Offer tab and onboarding forms on a Candidate Application come from Offer and Onboarding Form activities in the job req's workflow. Put them in the step where your team makes offers or onboards new hires.
## Related
> [card] [Build a workflow](/workflows/build)
>
> Add steps and arrange activities.
> [card] [Assessments overview](/assessments/overview)
>
> How Journeyfront's assessments compare.
> [card] [Automation rules](/workflows/automation-rules)
>
> Act on candidates when they complete an activity.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> Turn on add-ons and track credits.
# AI agents
Source: https://help.journeyfront.com/workflows/ai-agents
Set up AI agents that follow up with stalled candidates, with your team approving what they send.
> [!NOTE]
>
> **Who can do this:** Four permissions, set on each security role:
>
> * *Manage AI Agents*: create and set up agents.
> * *Assign AI Agents*: turn agents on for a job req and assign candidates to them. Turning an agent on for a job req also needs *Manage Job Req Settings*.
> * *Approve AI Agent Actions*: approve, edit or reject the messages agents propose.
> * *View AI Agent Tasks*: see what agents have done, read-only.
>
> Assigning, approving and viewing only cover the job reqs you have access to.
>
> **Availability:** AI agents need to be turned on for your account. Ask your Customer Success Manager. Agents use [AI credits](#ai-credits).
Candidates stall all the time: an assessment left half done, an interview invite never booked. An **AI agent** is a named teammate that follows up for you. It looks at each candidate you assign to it, works out whether they have something left to do, and sends a short, personal email, text or WhatsApp message to get them moving again. Most of the time, the right call is to do nothing, and that's what it does.
People stay in control. You choose which candidates an agent works on and which channels it can use, and for each channel, whether it sends on its own or waits for someone on your team to approve every message. An agent can only send messages: it can't move, reject or score anyone. Every action it takes is logged with its reasoning.
## How an agent works
On its schedule, and whenever something happens to a candidate (they apply, finish an activity or move to a new step), the agent looks at each candidate assigned to it:
* **Where they are:** their current step, and which activities in it are theirs to do, like screening questions, an assessment, a typing test, an interview they've been invited to book, or an onboarding form that's been sent to them.
* **What's already been said:** every email and text in their history, from anyone on your team, your automation rules or the agent itself.
Then it decides to send a nudge, hold a message for your approval, hand the candidate off to your team, or do nothing. It's built to follow up promptly when a candidate first stalls, space later follow-ups further apart, and stop after several tries with no response.
## What an agent never does
These rules are always on and can't be turned off. Most of them are also listed under **Guardrails** in every agent's settings.
* It only acts on candidates you've assigned to it.
* It never messages a closed application: hired, rejected or withdrawn. It never messages a blocked candidate.
* It only texts or WhatsApps candidates who have opted in to that channel. Email doesn't need an opt-in.
* It's outbound only. Sending messages is the only action it takes. It can't change a candidate's step, reject them, score them or assign them.
* It works only from hiring workflow data, never protected characteristics like age, gender or race.
* It leaves offers and background checks alone. To remind a candidate about an offer, see [E-signatures](/offers/e-signatures).
* Every action is logged, with the agent's reasoning.
## Before you start
1. **Turn on AI agents.** Ask your Customer Success Manager.
2. **Give people the permissions.** Go to **Settings**, then **Security**, and turn on the AI Agents permissions for the right roles. See [Security roles](/account-setup/security-roles).
3. **Set up texting, if you want it.** Email works right away. To let an agent send texts or WhatsApp messages, your account needs a number for that channel in **Settings**, then **Phone Numbers**, and WhatsApp messages also need approved WhatsApp templates. See [Text messages](/communication/text-messages) and [WhatsApp](/communication/whatsapp).
4. **Check your AI credits.** See [AI credits](#ai-credits).
## Create an agent
**1. Open AI Agents**
Go to **Settings**, then **AI Agents**, and click **New agent**.

**2. Choose the type and name it**
Choose the **Type**: **Candidate Management** sends candidates reminders and nudges to finish the steps that are theirs to complete. Give the agent a **Name** and, if you like, a short **Description** for the agents list.
**3. Click Create agent**
The agent is created **Paused**, and its settings open so you can finish setting it up.

> [!TIP]
>
> Name your agent like a teammate, for example "Riley" or "US Sales Candidate Manager". The name appears on every message it sends and every entry in a candidate's history, so your team always knows what the agent did.
## Set up the agent
Click an agent in the list to open its settings.

* **Name** and **Description.**
* **Instructions:** your own guidance on top of the agent's built-in role, such as tone, things to mention, or things to avoid. For example: "Keep messages warm and concise. Mention our 24-hour response promise." Instructions can narrow what the agent does; they can't switch off its guardrails.
* **Tools:** what the agent is allowed to do. **Read candidate process** is always on. Turn **Send SMS**, **Send WhatsApp** and **Send email** on or off, and choose when each needs your approval (see [Approval settings](#approval-settings)).
* **Send settings for each channel:**
* **Send SMS** and **Send WhatsApp:** **Send from**, the number the agent messages from.
* **Send email:** **From name**, the sender name candidates see (your company name if you leave it empty), and **Reply-to email**, where candidate replies go: the default address, or a **Custom email address**.
* **How often should the agent run:** **Every hour**, **Every 2 hours**, **Every 4 hours** (the default), **Every 6 hours**, **Every 12 hours** or **Once a day**. This is how often it looks over its candidates, not how often it messages them.
Click **Save changes**. When you're ready for the agent to start working, turn on the switch at the top of its settings. It changes from **Paused** to **Active**.
> [!TIP]
>
> Set **Reply-to email** to an inbox your team checks. The default is Journeyfront's support address, so without a custom address, candidates' replies to the agent's emails won't reach you.
### Approval settings
For each channel, **When should this need your approval?**

| Setting | What happens |
| - | - |
| **Don't ask** | The agent sends on its own, without checking in first. Every message still appears in its activity log. |
| **Ask when unsure** | The agent sends on its own when it's confident, and holds the message for you when it isn't sure. This is the default. |
| **Always ask** | The agent drafts each message and holds it for your approval. Nothing sends until someone approves it. |
Until you click **Save changes** on a new agent's settings, it holds every message for approval, the same as **Always ask**.
> [!TIP]
>
> Start with **Always ask** on every channel and a small group of candidates. Once your team trusts the drafts, move email to **Ask when unsure** and keep texts on **Always ask**, or loosen further as you go. You can change the setting at any time.
## Turn an agent on for a job req
An agent only works on job reqs where it's turned on.
**1. Open the job req's AI Agents settings**
Open the job req and go to **Setup**, then **AI Agents**. Each agent shows **Enabled** or **Off** for this job req.

**2. Turn the agent on**
Click the agent and turn on **Enabled on this requisition**.
**3. Choose auto-assign (optional)**
Turn on **Auto-assign new candidates** to assign every new applicant to this job req to the agent automatically.

## Assign candidates
An agent only works on the candidates assigned to it. A candidate can have more than one agent.
* **One candidate, from the list:** on the job req's **Candidates** tab, click the sparkle in the candidate's **AI Agent** column and pick an agent. Pick it again to unassign it. If you don't see the column, add it with **Edit Columns**.
* **One candidate, from their application:** open the Candidate Application and click the **AI Tasks** tab. **AI agents on this candidate** lets you add or remove agents.
* **Many candidates at once:** on the job req's **Candidates** tab, switch to the classic layout with **Back to Classic**, select the candidates, click **Assign AI Agent**, choose the agent, and click the **Assign to** button, which shows how many candidates you selected.
* **Every new candidate:** turn on **Auto-assign new candidates** for the job req.

Only agents turned on for the job req can be assigned. An agent that's still assigned to a candidate but no longer available, for example because it was turned off for the job req, is marked **Off**, so you can still unassign it.
## Review and approve
Everything agents do, or want to do, is on the **AI Agent Tasks** page. Click the sparkle icon in the top navigation (a number shows how many messages are waiting), or **Agent activity** in **Settings**, then **AI Agents**.

**1. Pick an agent**
The list on the left shows **All agents** and each agent, with how many of its messages are waiting. Narrow the list with **Search candidate**, **Job Req** and **Task type** (Email, Text or WhatsApp).
**2. Open a message**
On the **Awaiting approval** tab, click a task to see **Why the agent recommends this** and the draft.
**3. Edit it if you like**
Change the **Message**, and for emails the **Subject**, **From name** and **Reply-to email**. Add an **Approval note (optional)** for the record. **Reset to draft** puts back the agent's version.
**4. Approve or reject**
Click **Execute** to send the message, or **Reject** to drop it. To decide on several at once, tick them and click **Approve selected** or **Reject selected**.

The other tabs show what happened next:
| Tab | What's in it |
| - | - |
| **Awaiting approval** | Messages waiting for someone to approve or reject them |
| **Completed** | Messages that were sent, whether the agent sent them on its own or someone approved them, and candidates the agent handed off to your team, marked **Escalated** with its reason |
| **Rejected** | Messages someone rejected, with who rejected them and when |
| **Failed** | Messages that were approved but couldn't be sent, with the reason |
While a message for a candidate is waiting for approval, the agent doesn't propose another one for them. The same list for one candidate is on the **AI Tasks** tab of their Candidate Application, with a count of messages waiting.
People with *View AI Agent Tasks* but not *Approve AI Agent Actions* see the same pages without the approve and reject controls.
> [!TIP]
>
> Make reviewing the queue part of the daily routine, like checking email. A message that sits waiting for a day loses most of its value, and the agent won't follow up with that candidate until it's decided.
## What candidates see
Candidates get an ordinary email, text or WhatsApp message from your company: the email from the agent's **From name**, texts from your number. Messages usually include a link straight back to what they need to do, like their application or their interview booking link.
Every message an agent sends appears in the candidate's history on the **Comments & Activities** tab, with the agent's name and avatar, just like messages from your team. Messages waiting for approval don't appear until they're sent.
Agents don't hold conversations. Candidate replies come to your team as usual: texts in the message panel, and emails at the **Reply-to email** address. When a candidate needs a person, for example because they replied with a question, the agent is built to hand them off to your team instead of answering.
## AI credits
Each message an agent lines up uses one AI credit, whether it sends on its own or waits for approval. Rejecting a message doesn't give the credit back. When an agent looks at a candidate and decides nothing is needed, or hands a candidate off to your team, no credit is used.
When your AI credits run out, agents stop lining up new messages until more credits are added. To see your balance and which agent is using credits, go to **Settings**, then **Add-Ons**, then **AI Credits**. See [Add-ons and credits](/account-setup/add-ons).
## AI agents and automation rules
They work well together.
| | Automation rules | AI agents |
| - | - | - |
| **Decides** | A fixed rule: when this happens, do that | Looks at each candidate and decides what helps |
| **Message** | The same template for everyone | Written for each candidate's situation |
| **Timing** | Every time the rule matches | Chooses when, and often chooses not to send |
| **Actions** | Can move, reject, assign and message candidates | Can only send messages |
| **Oversight** | Runs on its own | Reasoning on every action, with optional approval |
Use automation rules for the steps every candidate should go through the same way, and agents for the follow-ups that need judgment. See [Automation rules](/workflows/automation-rules).
## FAQ
> [accordion] Can an agent reject or move candidates?
>
> No. Sending messages is the only thing it can do. When a candidate needs a decision, it's built to hand them off to your team, and you'll see them on the **Completed** tab marked **Escalated**.
> [accordion] Will an agent message candidates we've hired or rejected?
>
> No. It never messages a hired, rejected or withdrawn application.
> [accordion] Will it text candidates who haven't opted in?
>
> No. Texts and WhatsApp messages only go to candidates who opted in to that channel. Email doesn't need an opt-in.
> [accordion] Why isn't my agent doing anything?
>
> Check that:
>
> * The agent is **Active**, not **Paused**.
> * It's **Enabled on this requisition** for the job req.
> * Candidates are assigned to it.
> * At least one send tool is on, and for texts, the candidates have opted in.
> * The candidates have something left to do in their current step. Waiting on your team isn't something to nudge about.
> * There isn't a message for them already waiting on the **Awaiting approval** tab.
> * You have AI credits left.
>
> Remember that doing nothing is often the right call. Every message it does send is on the **AI Agent Tasks** page.
> [accordion] Can I change a message before it goes out?
>
> Yes, when it's waiting for approval. Edit it on the **AI Agent Tasks** page or the candidate's **AI Tasks** tab, then click **Execute**.
> [accordion] How often will a candidate hear from the agent?
>
> There's no fixed schedule. The agent reads each candidate's history, including messages from your team, and is built to space follow-ups further apart over time and to stop when a candidate doesn't respond. To control every message, use **Always ask**.
> [accordion] Why don't I see AI Agents?
>
> AI agents need to be turned on for your account, and each part needs its permission: **Settings**, then **AI Agents** for *Manage AI Agents*, the job req's **Setup**, then **AI Agents** and the **AI Agent** column for *Assign AI Agents*, and the **AI Agent Tasks** page for *View AI Agent Tasks* or *Approve AI Agent Actions*.
## Related
> [card] [Automation rules](/workflows/automation-rules)
>
> Fixed rules that act on every candidate the same way.
> [card] [Text messages](/communication/text-messages)
>
> Phone numbers, opt-in and message templates.
> [card] [Add-ons and credits](/account-setup/add-ons)
>
> Your AI credit balance and usage.
> [card] [Security roles](/account-setup/security-roles)
>
> Give people the AI Agents permissions.
# Automation rules
Source: https://help.journeyfront.com/workflows/automation-rules
Act on candidates automatically when something happens in a job req's workflow: move them, message them, assign them or route them.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission.
>
> **Availability:** The text message action needs text messaging set up for your account, and the WhatsApp action appears only once WhatsApp is connected. See [Text messages and WhatsApp](/communication/text-messages).
Automation rules do the repetitive work on a job req for you. Each rule waits for something to happen, like a candidate finishing an activity, checks the conditions you set, and then takes one or more actions: moving the candidate to the next step, sending an email or text, assigning a recruiter, rejecting, or adding them to another job req. It's how a small team keeps up with thousands of applicants and treats every one of them the same way.
Every rule has three parts:
* **Trigger:** the event that starts it. Each rule has exactly one.
* **Conditions:** optional checks the candidate must meet. With no conditions, the actions run every time the trigger happens.
* **Actions:** what Journeyfront does. A rule can have several, and they all run.
[Automations | Journeyfront Feature Walkthrough](https://www.youtube.com/embed/hJMSs9qjwXw)
## Where rules appear
On the job req's Workflow page (**Setup**, then **Workflow**), each rule is a purple bar with a lightning bolt. It sits next to whatever its trigger points to:
* Under **START**: rules that run when a Candidate Application is created.
* Under an activity: rules that run when candidates complete it or its status changes.
* At the bottom of a step: rules that run when candidates move into, complete or spend a set time in that step.
* Under **HIRED** or **REJECTED**: rules that run when a candidate is hired or rejected.
Each bar shows the rule's name, its delay and its actions, then an **ON/OFF** switch, a pencil to edit it and a trash can to delete it. Click a bar to see the whole rule in the panel on the right: **TRIGGER**, **DELAY**, **CONDITION(S)** and **ACTION(S)**.

## Create an automation rule
**1. Open the Workflow page**
Open the job req and go to **Setup**, then **Workflow**.
**2. Click a lightning bolt**
Click the lightning bolt (**Add Automation**) next to where the rule belongs: **START**, a step's name, an activity, **HIRED** or **REJECTED**. The automation editor opens with a trigger already chosen for that spot. You can change it.

**3. Name it**
Type a name at the top that says what the rule does, like "Advance strong screeners".
**4. Set the trigger**
Click **TRIGGER** in the flow on the right. Pick the **Trigger** and, depending on the trigger, the **Activity**, **Status** or **Step** it applies to.

**5. Set the delay**
Click **DELAY**. **Delay before evaluating conditions** is how many minutes Journeyfront waits after the trigger before checking conditions. The default is 2 minutes, which gives scores and statuses time to settle.
**6. Add conditions (optional)**
Click **CONDITION(S)**, then **+ Add Condition**. Pick the **Condition**, then fill in what it compares, like the activity, operator and score. For each extra condition, choose **And** (all must be true) or **Or** (any one can be true) with **Change to Or** or **Change to And**.
**7. Add actions**
Click **ACTION(S)**, then **+ Add Action**. Pick the **Action Type** and fill in its details. Add as many actions as you need.
**8. Turn it on and save**
New rules start off. Switch **Enabled** to **On**, then click **Save**. A rule that's off never runs.
While a rule is on, any required field you've left empty shows **Missing Data**, and Journeyfront won't save or switch on a rule that's incomplete. You can save a rule that's off with fields still empty, so build it with **Enabled** off and turn it on when it's ready.
To change a rule later, click its pencil, or click the bar and then **Edit**. To turn it off without deleting it, flip its **ON/OFF** switch. To delete it, click its trash can, then **Delete**.
> [!TIP]
>
> Name each rule after what it does ("Reject: no work authorization", "Text reminder: typing test"). When a candidate's history shows that an automation acted on them, the name is what your team sees.
## Rules and workflow versions
Rules belong to a version of the workflow, and each candidate is checked against the rules of the version they're on.
* **On the Workflow page,** adding, editing, switching and deleting rules saves straight away to the version you're looking at. On the **Latest** version, that means the change is live right away.
* **In the workflow editor** (**Create New Version** or **Edit Draft**), rules are part of your draft, like steps and activities. They take effect when you publish. See [Publish workflow changes](/workflows/publish).
> [!TIP]
>
> Check the version name at the top of the Workflow page before you change a rule. To try a new rule on future applicants only, add it in the editor and publish it with a new version.
## Triggers
| Trigger | Runs when | You also choose |
| - | - | - |
| **Candidate Application is Created** | A new Candidate Application is created on this job req: someone applies, or your team adds or imports them. | Nothing else |
| **Candidate Completes Activity** | A candidate finishes the chosen activity. | **Activity** |
| **Activity Status Changes To** | The chosen activity reaches the chosen status, for example an interview becoming **Scheduled** or an offer becoming **Offer Accepted**. The statuses depend on the activity type. | **Activity** and **Status** |
| **Candidate Moved to Step** | Someone moves the candidate into the chosen step, for example with **Change Step**. | **Step** |
| **Candidate Completes Step** | A candidate finishes all the activities in the chosen step. | **Step** |
| **Candidate is Hired** | The candidate is hired. | Nothing else |
| **Candidate is Rejected** | The candidate is rejected. | Nothing else |
| **Candidate Time in Step Reaches** | A candidate has been in the chosen step for the time you set. | **Step**, and the time in **Days** and **Hour** |
> [!TIP]
>
> When an activity is scored after the candidate submits it, like screening questions your team or AI scores, its status is **Complete - Need Scores** until scoring is done. **Candidate Completes Activity** runs as soon as the candidate submits. To act on the final score, use **Activity Status Changes To** with the status **Complete** instead.
## Conditions
All scores in conditions use the 1 to 5 scale. Score conditions compare with **Greater than**, **Greater than or equal to**, **Equal to**, **Between**, **Less than or equal to** or **Less than**.
| Condition | What it checks |
| - | - |
| **Overall score is** | The candidate's overall score on this job req. |
| **Activity score is** | The score on one activity you choose. |
| **Attribute Score is** | The score on one attribute you choose. See [Attributes](/scoring/attributes). |
| **Attribute group score is** | The score on one attribute group you choose. Also offers **Is Highest**: true when this is the candidate's highest attribute group score (ties count). |
| **Predictive model score is** | The score from one of the job req's predictive models. Also offers **Is Highest**. See [Predictive models](/scoring/predictive-models). |
| **Activity Status is** | Whether one activity you choose has a particular status, like **Not Started** or **Complete**. |
| **Status is** / **Status is Not** | The application's status: **Incomplete**, **New**, **Active**, **Hired**, **Rejected** or **Withdrawn**. |
| **Source** | Where the candidate came from. |
| **Hiring Class** | The candidate's hiring class on this job req. |
| **Assigned User** | Who the candidate is assigned to. |
| **Fraud Risk Level** | The application's fraud risk level: **Low**, **Medium** or **High**. See [Fraud flags](/candidates/fraud-flags). |
| **Candidate Country**, **Candidate State/Region**, **Candidate City**, **Candidate Zip Code** | The location from the candidate's address. Pick a country or state from the list; type a city or zip code. |
| **Application Field** / **Personal Field** | One of your account's custom fields. Pick the field, then a value; what you can enter depends on the field type. See [Custom fields](/account-setup/custom-fields). |

**Source**, **Hiring Class**, **Assigned User**, **Fraud Risk Level** and the location conditions use **Is** or **Is Not**, plus **Is Set** and **Is Not Set** to check whether there's a value at all. For example, **Fraud Risk Level Is Not Set** matches applications that haven't been checked yet.
## Actions
Actions are what the rule does once the trigger has happened and the conditions are met: move the candidate, message them, assign them, set their hiring class, reject them or add them to another job req. In the automation editor, click **ACTION(S)**, then **+ Add Action**, and pick the **Action Type**. Each type then asks for its own details, listed below. A rule can have several actions, and they all run.

| Action | What it does | You fill in |
| - | - | - |
| **Assign User** | Assigns the candidate to a user, replacing anyone already assigned. With **Multiple Users(Random)**, Journeyfront picks one of the users you list at random each time. | **Assign Method** (**Single User** or **Multiple Users(Random)**) and **Select Users** |
| **Change candidate step to** | Moves the candidate to another step. Tick **Send email inviting user to complete the next step** to email the candidate a link to continue. | **Step** |
| **Reject candidate** | Rejects the candidate with the reason you choose. It doesn't email the candidate; add a **Send Email to Candidate** action for that. | **Reject Reason** and optional **Reject Notes** |
| **Send Email to Candidate** | Sends one of your email templates. | **Email template**, and optional **Delay Days** and **Delay Hours** |
| **Send SMS to Candidate** | Sends one of your text message templates. It isn't sent to candidates who aren't opted in to texts or who are blocked. | **Message template**, **From Phone Number**, optional delay |
| **Send WhatsApp Message to Candidate** | Sends one of your approved WhatsApp templates, to candidates opted in to WhatsApp. Only listed once WhatsApp is connected. | **Message template**, **From Phone Number**, optional delay |
| **Set Hiring Class** | Puts the candidate in one of this job req's active hiring classes. | **Hiring Class** |
| **Add to Other Job Req** | Creates a Candidate Application on another job req. Skipped if the candidate already has an application there, or if that job req's re-apply waiting period hasn't passed. | **Target Job Req**, **Transfer Data** (**Transfer All Applicable Data** or **Don't Transfer Data**), and whether to **Send email inviting candidate to complete the application steps** |
See [Candidate assignment](/workflows/candidate-assignment), [Reject candidates](/candidates/reject), [Email templates](/communication/email-templates) and [Add candidates to another job req](/candidates/add-to-another-job) for more on each.
## Common recipes
These examples use made-up names and scores. Set your own based on how your roles and candidates perform.
> [accordion] Advance candidates who do well on screening questions
>
> * **Trigger:** **Activity Status Changes To**, Activity "Screening Questions", Status **Complete**.
> * **Condition:** **Activity score is**, Activity "Screening Questions", **Greater than or equal to** 4.
> * **Action:** **Change candidate step to** "Assessments", with **Send email inviting user to complete the next step** ticked.
>
> Candidates who score lower stay where they are for your team to review.
> [accordion] Nudge candidates who haven't started a test
>
> * **Trigger:** **Candidate Time in Step Reaches**, Step "Assessments", 2 **Days**.
> * **Condition:** **Activity Status is**, Activity "Typing Test", **Not Started**.
> * **Action:** **Send SMS to Candidate** with a friendly reminder template and the link to continue.
> [accordion] Route candidates by location
>
> * **Trigger:** **Candidate Application is Created**.
> * **Condition:** **Candidate State/Region** **Is** the state your regional recruiter covers.
> * **Action:** **Assign User**, **Single User**, that recruiter.
>
> Make one rule per region. Or use **Add to Other Job Req** to send candidates in a region to that region's job req.
> [accordion] Reject and notify candidates who don't meet the bar
>
> * **Trigger:** **Candidate Completes Step**, Step "Assessments".
> * **Condition:** **Overall score is** **Less than** 2.
> * **Actions:** **Reject candidate** with the matching reason, and **Send Email to Candidate** with your rejection template, with a **Delay Days** of 1 so the reply doesn't feel instant.
> [!TIP]
>
> Start with rules that move, message and assign candidates. Before you automate rejections, run the rule with a softer action (like assigning the candidates to a reviewer) for a few weeks, and check that it picks the people you expect.
## Check that a rule is working
There's no test mode, so watch the first candidates after you turn a rule on. Each time a rule acts on a candidate, their Candidate Application's **Comments & Activities** tab shows an **Automation Ran** entry with the rule's name.

## FAQ
> [accordion] Why did a candidate move or get rejected?
>
> Open their Candidate Application and check the **Comments & Activities** tab. An **Automation Ran** entry names the rule that acted. Then open the job req's Workflow page and click that rule to see its trigger and conditions. Conditions are checked once, after the delay, using the candidate's scores at that moment; later changes to a score don't undo the action.
> [accordion] Can one automation trigger another?
>
> No. Actions taken by an automation don't start other automations. If a rule moves a candidate to a step, a second rule with the **Candidate Moved to Step** trigger won't run for that move. Put all the actions you need in the same rule instead.
> [accordion] Do new rules apply to candidates who are already in the job req?
>
> Only to events that happen after the rule is turned on. A rule doesn't look back at candidates who already completed the activity or reached the step. **Candidate Time in Step Reaches** acts on candidates as they reach the time you set, not on those already past it.
> [accordion] A rule didn't act on a candidate who should have matched. Why?
>
> Check that the rule is on, and that it's on the version of the workflow the candidate is on. Then check whether the score was ready when conditions were checked. If an activity is still waiting on scores, use **Activity Status Changes To** with **Complete**, or increase the delay. Also check that another rule didn't move the candidate first, since automations don't trigger each other.
> [accordion] How quickly do rules run?
>
> After the delay you set (2 minutes by default), plus a short time for processing. Rules that share the same trigger are checked together, after the shortest delay among them, so give them the same delay. Emails and texts with **Delay Days** or **Delay Hours** go out later, as scheduled.
> [accordion] Can I have more than one rule on a job req?
>
> Yes, as many as you need, each with its own trigger, conditions and actions.
> [accordion] Why does my rule appear under a different step or activity than where I added it?
>
> A rule's place in the flow follows its trigger. If you change the trigger to point at a different step or activity, the rule moves there.
> [accordion] Are rules copied when I duplicate a job req?
>
> Yes. Duplicating a job req copies its automation rules along with its steps and activities. Check them on the copy, especially rules that assign specific users or send candidates to another job req.
> [accordion] Which job reqs can Add to Other Job Req send candidates to?
>
> Any active or inactive job req in your account, other than the one the rule is on. Closed and archived job reqs aren't listed. The candidate's application on the current job req stays as it is.
## Related
> [card] [Build a workflow](/workflows/build)
>
> Steps and activities your rules act on.
> [card] [Publish workflow changes](/workflows/publish)
>
> How rule changes in a draft reach candidates.
> [card] [Candidate assignment](/workflows/candidate-assignment)
>
> Default assignees, bulk assignment and automation.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What the scores in your conditions mean.
# Build a workflow
Source: https://help.journeyfront.com/workflows/build
Add, name and order the steps of a job req's workflow, then add the activities candidates complete in each step.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission. The **Setup** tab only appears for people with this permission.
A job req's workflow is the path every candidate follows: a series of **steps**, each holding the **activities** candidates complete, like screening questions, a typing test or an interview. You build and change it in the workflow editor. Your changes are saved as a draft and only reach candidates when you publish them. For how steps, activities and automation fit together, start with the [Workflows overview](/workflows/overview).
## Open the editor
**1. Go to the Workflow page**
Open the job req and go to **Setup**, then **Workflow**.
**2. Open the editor**
Click **Create New Version** at the top right. The editor opens full screen.

If the job req already has a draft, the button reads **Edit Draft**, or **Edit Scheduled Version** when a version is scheduled, and the editor opens that version. Otherwise **Create New Version** starts you from a copy of the live version, and your changes become a new draft when you save.
The editor has three columns:
* **Building blocks** on the left: a **Search** box, **New Step**, and every type of activity you can add, in groups you can collapse. Your saved question templates sit under a collapsed **Templates** row in their group.
* **The title** at the top: the version's name. Click it to rename the version.
* **The flow** in the middle: **START**, your steps and their activities, then **HIRED** and **REJECTED**.
* **Settings** on the right for whatever you select in the flow.

## Add and arrange steps
**1. Add the step**
Drag **New Step** from the building blocks into the flow, to where the step belongs. An outlined **New Step** slot shows where it will land.

**2. Name it**
Type the name in the step's name field. Candidates see step names on their progress page, so use names that make sense to them, like "Assessments" or "Interview".

**3. Put it in order**
Drag the step by its handle (the dotted grip to the left of its name) to where it belongs. Candidates move through steps from top to bottom.
To **rename** a step, click its name in the flow and type. To **remove** a step, click its trash can. Removing a step also removes its activities and the automation rules attached to them from your draft.
### How candidates move between steps
Candidates stay in their current step until your team moves them with **Change Step** or an [automation rule](/workflows/automation-rules) moves them (the job req's **Gate Steps** setting, on by default).
> [card] [Move candidates through steps](/candidates/move-through-steps)
>
> Change Step, bulk moves and what candidates see when they move.
> [!TIP]
>
> Plan your steps around the decisions your team makes. A new step makes sense wherever you'd review candidates before letting them continue, for example between a quick screen and a longer assessment.
## Add activities to a step
With your steps in place, fill each one with the activities candidates complete there. Every type of activity is a block in the building blocks column, and you add one by dragging it into a step.
**1. Find the activity**
Find it in the building blocks, or type in **Search**. Your saved screening question and interview templates are under **Screening Questions** and **Interviews**: click **Templates** to show them (the number is how many you have), or search by name and matching templates show on their own. Click the eye icon next to a template to preview its questions before you add it. [Activities you can add](/workflows/activities) lists every option.
**2. Drag it into a step**
Drag the block into the step, at the position where candidates should take it. An outlined slot shows where it will land.

**3. Set it up**
Click the activity to open its settings on the right. Change its name at the top, then finish its setup, such as its questions, instructions or the test to use. Each activity type's guide covers the details.

Most activities have these settings:
* **Estimated Time (Minutes):** how long the activity takes. Offers and onboarding forms don't have one.
* **Time Limit** (screening questions only): turn it **On** and candidates have only the estimated time to finish the whole activity; anything unanswered when time runs out is submitted as not answered.
* **Instructions:** what candidates read before they start. **Supporting Content** (screening questions) is what they see while they answer, and interviews have **Instructions for Interviewer**. These sections start collapsed and show **Added** or **Not added**; click one to open it, and hover its info icon for a reminder of who sees it.
* **Questions** (screening questions and interviews): click **Add Question** to pick from your question library or **Create New Question**. Drag questions to reorder them.
For an interview, open **Interview Scheduler**, then **View and Edit Details** to set up scheduling. A newly added interview needs to be saved in your draft first. See [Set up an interview activity](/interviews/interview-activity).
To **reorder** activities, drag them by their grip within a step or into another step. To **remove** one, click its trash can.
Candidates complete a step's activities in the order listed, unless the job req allows them to take activities out of order. See [Job settings](/job-reqs/job-settings).
> [!TIP]
>
> Put quick, decisive activities first. Short screening questions before a longer assessment let candidates who aren't a fit find out fast, and keep everyone else moving.
## Save your changes
**1. Check the version name**
The title at the top is the version's name. A new version is named for you from the last one (**Workflow 2.0** becomes **Workflow 3.0**). Click it to rename it, like "Added typing test". Each version on the job req needs a different name.

**2. Save the draft**
Click **Save Draft**. Journeyfront saves your draft, confirms with a message, and you stay in the editor to keep working.
**3. Publish when you're ready**
Nothing changes for candidates until you publish. Click **Publish**; any unsaved changes are saved first. See [Publish workflow changes](/workflows/publish).
To leave without saving, click **Exit**. If you have unsaved changes, Journeyfront asks whether to **Save Draft** or **Discard** them. To throw away a saved draft entirely, open the editor and click **Delete Draft**; this can't be undone.
## Get notified when an activity is completed
Each activity has a bell (**Notify Users**) on the Workflow page. Everyone on its list gets an email whenever a candidate completes that activity on this job req, so whoever reviews it, for example a skills test you check by hand, hears right away.
**1. Open the Workflow page**
Open the job req and go to **Setup**, then **Workflow**.
**2. Click the bell**
Click the bell (**Notify Users**) on the activity. The **Get Notified** window opens.

**3. Choose who's notified**
Click **Notify Me** to add yourself, or **Add User** to search for someone else. Click the trash icon to take someone off the list. Changes save as you make them.

> [!TIP]
>
> Notifications work best on activities your team acts on right away, like a final assessment or an interview. On a high-volume job req, a notification for every application adds up quickly.
To get an email when a candidate finishes their whole application instead, turn on **Candidate completes application** for yourself on the job req's hiring team.
> [card] [Hiring team](/job-reqs/hiring-team)
>
> Who works on a job req, and the email when a candidate finishes applying.
## Preview what candidates see
On the Workflow page, click the eye icon (**Preview Activity**) on an activity. The preview opens on that activity.
* Use the **Previewing** menu to jump to any activity, or the arrows to move through them in order.
* Switch between the mobile, tablet and desktop views to check each screen size.
* Click **Back** to return to the Workflow page.

The preview shows screening questions, behavioral assessments, interviews and typing tests the way candidates see them. Language assessments from partners show a message that they can't be previewed, with a button to continue. Other activities, like offers and onboarding forms, don't have a candidate preview. Nothing you enter in the preview is saved.
> [!TIP]
>
> Before you start sending candidates to a new job req, preview it on the mobile view. Many high-volume candidates apply from a phone, so long instructions or wide tables are worth catching early.
## FAQ
> [accordion] Can I change the workflow after candidates have applied?
>
> Yes. Your changes stay in a draft until you publish them as a new version. Candidates already in progress stay on the version they started with, so their interviews and offers aren't affected. See [Publish workflow changes](/workflows/publish).
> [accordion] Why don't I see the Setup tab on a job req?
>
> The Setup tab needs the *Manage Job Req Settings* permission. Ask your Journeyfront admin to check your security role.
> [accordion] Why can't I save my draft?
>
> Check the title at the top: the version needs a name that no other version on the job req uses. A note under the title tells you if the name is taken. A System Requirements Test also needs a requirement set chosen before the draft can be saved.
> [accordion] I removed something by mistake. Can I get it back?
>
> If you haven't saved yet, click **Exit** and choose **Discard** to throw away everything since your last save. Nothing reaches candidates until you publish, so the live version is never affected while you work.
> [accordion] Why isn't the skills test I need in the building blocks?
>
> **Skills Tests** lists the skills tests set up for your account. Ask your Customer Success Manager which skills tests are available for your roles. See [Skills tests](/assessments/skills-tests).
> [accordion] How do candidates get to the next step?
>
> Your team moves them with **Change Step**, or an automation rule moves them when they meet the conditions you set. See [Move candidates through steps](/candidates/move-through-steps) and [Automation rules](/workflows/automation-rules).
> [accordion] What does Completed by mean?
>
> It shows who completes each activity: the interviewer for interviews, and the candidate for the others. A step's line shows everyone who completes its activities and their total estimated minutes.
> [accordion] Are my answers saved when I preview?
>
> No. The preview shows each activity as a candidate sees it, but nothing you enter is saved.
> [accordion] Can I copy a workflow from another job req?
>
> Yes, by duplicating the job req. The copy starts with the same steps, activities and automation rules, which you can then adjust. See [Create a job req](/job-reqs/create).
## Related
> [card] [Activities you can add](/workflows/activities)
>
> Every activity type and where to set it up.
> [card] [Publish workflow changes](/workflows/publish)
>
> Take your draft live, now or on a date you choose.
> [card] [Automation rules](/workflows/automation-rules)
>
> Move, message and route candidates automatically.
> [card] [Job settings](/job-reqs/job-settings)
>
> Activity order, re-applying and other candidate experience settings.
# Candidate assignment
Source: https://help.journeyfront.com/workflows/candidate-assignment
Decide which recruiter owns each candidate: automatically as they apply, by hand, in bulk or with an automation rule.
> [!NOTE]
>
> **Who can do this:** Setting a job req's default assignment needs the *Manage Job Req Settings* permission. Anyone with access to a job req can assign its candidates, one at a time or in bulk.
Every Candidate Application can have one **assigned user**: the person on your team responsible for that candidate. Assigning candidates spreads the work across your recruiters, makes it clear who follows up with whom, and lets each person filter to their own candidates.
You can assign candidates four ways:
* **Automatically as they arrive,** with the job req's **Default Assigned User** setting.
* **One at a time,** from the candidate list or the Candidate Application.
* **In bulk,** with the **Assign User** action.
* **With an automation rule,** when candidates meet conditions you set.
## Who can be assigned
The list of people you can assign comes from the job req's team. To make someone assignable, add them to the job req under **Setup**, then **Team**. See [Hiring team](/job-reqs/hiring-team).
## Assign new candidates automatically
**1. Open Configurations**
Open the job req, click **Setup**, then **Configurations**. The first card is **Candidate Assignment**.
**2. Choose the method**
Under **Default Assigned User**, choose **Single User** to give every new candidate to one person, or **Multiple Users(Round Robin)** to take turns between several people. Changing the method clears the users you'd picked.
**3. Add the users**
Click the **+** button, search by name or email, and pick a user. For round robin, add up to 20 users in the order you want them to take turns. To remove someone, hover over their initials and click the **x**.
**4. Save**
Click **Save** at the top of the page.

How it works:
* **It applies when a new Candidate Application is created on the job req,** whether someone applies or your team adds or imports them. It doesn't change candidates who are already in the job req.
* **It only fills an empty spot.** If a candidate already has an assigned user when their application is created, they keep that person.
* **Round robin goes in order.** Each new candidate goes to the next user in the list, and after the last user it starts again with the first. You can add the same person more than once to give them a bigger share.
* **Saving restarts the rotation.** Each time you save the Configurations page, round robin starts again from the first user in the list.
> [!TIP]
>
> Use round robin to share high volume evenly, and **Single User** when one recruiter owns a job req. Assignment by region, source or score works better as an automation rule (see below).
## Assign one candidate
* **From the candidate list:** click the candidate's **Assigned User** cell (their assignee's initials, or the **+** if nobody's assigned yet). Search by name or email and pick a user.
* **From the Candidate Application:** open the **Details** tab and change **Assigned User** in the **Application Details** card.

To remove an assignment, pick **Unassigned**. A candidate has one assigned user at a time, so picking someone new replaces the current assignee.
## Assign many candidates at once
**1. Select the candidates**
On the job req's candidate list or the **Candidates** page, tick the candidates you want to assign.
**2. Click Assign User**
In the bar above the list, click **Assign User**. The **Assign User to Candidate** window opens.
**3. Pick the user and confirm**
Click the **+**, pick the user (or **Unassigned**), then click **Assign User**. That person replaces whoever was assigned to each selected candidate.
**Assign User** only appears when all the selected candidates belong to the same job req, because each job req has its own list of people you can assign.

## Assign with an automation rule
An automation rule's **Assign User** action assigns candidates when something happens and they meet your conditions, for example routing every candidate from one state to the recruiter who covers it. Choose:
* **Single User:** always the same person.
* **Multiple Users(Random):** one of the users you list, picked at random each time.
The rule replaces whoever is assigned at that moment, including someone set by the default assignment. See [Automation rules](/workflows/automation-rules).
## See who's assigned
* **Filter by assignee:** use the **Assigned User** filter on the job req's candidate list or the **Candidates** page to see one person's candidates.
* **Add the column:** the **Assigned User** column shows each candidate's assignee at a glance.
* **Check the history:** every change is recorded on the Candidate Application's **Comments & Activities** tab as **User Assigned**, with who it changed from and to.
> [!TIP]
>
> Have each recruiter save a view of the Candidates page filtered to themselves as **Assigned User**. It becomes their daily worklist.
## FAQ
> [accordion] Candidates were assigned to someone who isn't in our Default Assigned User list. Why?
>
> Something else assigned them after the default assignment ran. Check:
>
> * **Automation rules** on the job req with an **Assign User** action. They run after the candidate is created and replace the default assignee.
> * **Manual changes.** The candidate's **Comments & Activities** tab shows every **User Assigned** change and who made it.
> * **Where the job req came from.** A duplicated job req starts with the original's Default Assigned User list. Review it under **Setup**, then **Configurations**.
> [accordion] Does changing the default reassign candidates already in the job req?
>
> No. The default only applies to new Candidate Applications. To reassign existing candidates, select them and use **Assign User**.
> [accordion] Can a candidate have more than one assigned user?
>
> No. Each Candidate Application has one assigned user. The same person can have different assignees on different job reqs.
> [accordion] Is the assigned user notified?
>
> No email is sent when a candidate is assigned. Recruiters find their candidates with the **Assigned User** filter.
> [accordion] Why can't I find someone in the list of users?
>
> The list comes from the job req's team. Add the person under **Setup**, then **Team**, and they'll appear.
> [accordion] Why is Assign User missing from the bulk actions?
>
> Your selection includes candidates from more than one job req. Select candidates from a single job req, or filter the Candidates page to one job req first.
> [accordion] Why did round robin start over with the first user?
>
> Saving the Configurations page restarts the rotation from the top of the list, even when you only changed a different setting on that page.
## Related
> [card] [Automation rules](/workflows/automation-rules)
>
> Assign candidates based on location, source or score.
> [card] [Job settings](/job-reqs/job-settings)
>
> Everything else under Setup, then Configurations.
> [card] [Hiring team](/job-reqs/hiring-team)
>
> Add the people who work on a job req.
> [card] [Bulk actions](/candidates/bulk-actions)
>
> Everything you can do to many candidates at once.
# Workflows overview
Source: https://help.journeyfront.com/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.

## 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](/workflows/publish).
* **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](/workflows/build).
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. |

## 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](/job-reqs/create).
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](/workflows/activities).
> [!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](/workflows/automation-rules).
## 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](/workflows/publish).
## 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](/workflows/publish).
> [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](/workflows/build)
>
> Add steps and activities in the workflow editor.
> [card] [Publish workflow changes](/workflows/publish)
>
> Drafts, versions and when changes reach candidates.
> [card] [Automation rules](/workflows/automation-rules)
>
> Move, message and route candidates automatically.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What the scores from each activity mean.
# Publish workflow changes
Source: https://help.journeyfront.com/workflows/publish
Save workflow changes as a draft, review them and publish a new version, now or at a time you choose, and know what happens to candidates already in progress.
> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission.
Changes to a job req's workflow don't reach candidates the moment you make them. You make them in a draft, check what's different, and publish the draft as a new version, either right away or at a date and time you choose. Candidates already in progress stay on the version they started with.
## How versions work
Every published change to a job req's workflow is a **version** with its own name. The job req has one live version, marked **Latest**, that new candidates follow. You change the workflow by editing a draft, and the draft becomes the new Latest version when you publish it.
On the Workflow page (**Setup**, then **Workflow**), the version name at the top is a menu. Click it to look at any version:

| Label | What it means |
| - | - |
| **Latest** | The live version. The date beside it shows when it was published. |
| **Draft** | Changes you've saved but not published. The date beside it shows when it was last saved. |
| **Scheduled** | A version set to go live later, shown with when it goes live, for example "Goes live Tue, Nov 17, 2026 at 9:00 AM MST". |
| **Inactive** | An earlier version. Candidates who started on it may still be on it. |
A job req has one draft or scheduled version at a time. When it has one, the Workflow page opens on it.
**Review Changes**, under the version name, lists everything that's different from the version before the one you're looking at, step by step. The number on the button is how many changes there are.

## Make and publish changes
**1. Open the editor**
On the Workflow page, click **Create New Version** to start from a copy of the Latest version. If there's already a draft, the button reads **Edit Draft** (or **Edit Scheduled Version** for a scheduled one) and opens that version instead.

**2. Make your changes**
Add, remove and rearrange steps, activities and automation rules. See [Build a workflow](/workflows/build). Nothing changes for candidates while you work.
**3. Name the version**
The version's name is the title at the top of the editor. A new version is named for you from the last one, so **Workflow 2.0** is followed by **Workflow 3.0**. To rename it, click the title and type, like "Added typing test, Oct 2026". Each version on the job req needs a different name.
**4. Save the draft**
Click **Save Draft** as often as you like. Journeyfront saves the draft and you stay in the editor.
**5. Review your changes**
Click **Review Changes** to compare your draft with the Latest version.
**6. Publish**
Click **Publish**. If you have unsaved changes, Journeyfront saves them first. In the **Publish Workflow** window, choose when the version goes live (below), then click **Publish Now** or **Schedule Publish**.

If saving fails, for example because another version already uses the name, the **Publish Workflow** window doesn't open. Fix the problem and click **Publish** again.
To leave without publishing, click **Exit**. If you have unsaved changes, Journeyfront asks whether to **Save Draft** or **Discard** them. To throw a draft away entirely, click **Delete Draft** in the editor; this can't be undone.
### Choose when it goes live
* **Publish now:** the version goes live right away.
* **Schedule:** pick a **Go live** date and time, in half-hour steps. Times are in your own time zone, which the window names, and a summary underneath shows exactly when it goes live, for example "Goes live Tue, Nov 17, 2026 at 9:00 AM MST". The time has to be in the future. The version shows as **Scheduled** until then.
To change when a scheduled version goes live, click **Edit Scheduled Version** on the Workflow page, then **Edit Publishing Details**. The new time replaces the old one. To cancel a scheduled version, open it the same way and click **Delete Draft**; it won't go live.
When the version goes live, the version it replaces becomes **Inactive**. If the job req is **Inactive**, it becomes **Active**.
### Who follows the new version
A new version is for candidates who apply from the moment it goes live.
* **Candidates already in progress** stay on the version they started with and keep their scores, interviews and offers.
* **Hired, rejected and withdrawn candidates** stay where they are.
* **New candidates** follow the new version.
This is the same whether you publish now or schedule: only candidates who apply after the version goes live follow it. The **Publish Workflow** window says so under the go-live time.
## Candidates on different versions
On the job req's candidate list, the **Job Version** column shows which version each candidate is on. **Change Step**, **Send Offers** and **Compare** work on one version at a time, so they're hidden when your selection mixes candidates from different versions.
Automation rules belong to a version too. Each candidate is checked against the rules of the version they're on.
> [card] [Automation rules](/workflows/automation-rules)
>
> How rules act on candidates, and which version's rules apply.
## A new job req's first version
A new job req starts with a draft named **Workflow 1.0**, holding its starter workflow, and stays **Inactive**. Change the draft as you need, then publish it. Publishing the first version makes the job req **Active**, so candidates can apply. See [Create a job req](/job-reqs/create).
## FAQ
> [accordion] Why is the Publish button greyed out?
>
> Publish needs something to publish: changes in the editor or a saved draft. The version also needs a name that isn't used by another version on the job req. An empty title turns its underline red, and a name that's already used shows a note under it.
> [accordion] Can I have more than one draft?
>
> A job req has one draft or scheduled version at a time. When you open the editor, it picks up where that version left off.
> [accordion] Can I go back to an earlier version?
>
> You can view earlier versions from the version menu on the Workflow page. To go back to an earlier process, make the same changes in a new draft and publish it.
> [accordion] Do candidates see anything when a new version goes live?
>
> No. Candidates already in progress stay on their version, so nothing changes for them, and nothing is sent to anyone when you publish. Candidates who apply after the version goes live see its steps and activities.
> [accordion] Can I change automation rules without publishing?
>
> Yes, on the Workflow page itself. Changes you make to rules there save straight to the version you're viewing, so on the Latest version they're live right away. Changes made in the editor (**Create New Version** or **Edit Draft**) are part of your draft and take effect when you publish.
> [accordion] Can I move candidates who are already in progress to the new version?
>
> Not yet. Candidates already in progress stay on the version they started with, so their interviews and offers are never affected by a publish.
> [accordion] What time zone is the go-live time in?
>
> Yours. The **Publish Workflow** window names your time zone, and the version goes live at that moment everywhere. A teammate in another time zone sees the same moment in their own time.
## Related
> [card] [Build a workflow](/workflows/build)
>
> Add steps and activities.
> [card] [Automation rules](/workflows/automation-rules)
>
> Rules that act on candidates for you.
> [card] [Workflows overview](/workflows/overview)
>
> How steps, activities and automation fit together.
> [card] [How scoring works](/scoring/how-scoring-works)
>
> What rescoring means for a candidate.