> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.confirm.global/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.confirm.global/_mcp/server.

# Key Concepts

This page defines the terms you'll see throughout the portal and these docs.

## Organization

Your company workspace. Everything in CONFIRM — jobs, candidates, templates, the knowledge base, and settings — belongs to your organization. Team members are invited to the organization with one of five roles: **Administrator**, **Recruiter**, **Hiring Manager**, **Viewer**, or **Calendar Only**. The role controls what each person can see and change. See [Team & Roles](/settings/team-and-roles).

## Job

A position you're hiring for. Each job has its own details, screening questions, hiring pipeline, interview scheduling, and knowledge base documents. Jobs have one of five statuses: **Draft**, **Active**, **Paused**, **Filled**, and **Closed**. Filled and closed jobs can be reopened. See [Creating a Job](/jobs/creating-a-job) and [Managing Jobs](/jobs/managing-jobs).

## Posting

A job promoted on a specific job board, such as Indeed or LinkedIn. One job can have many postings — for example, the same role on Indeed and LinkedIn at the same time. Each posting has its own status, run dates, and applicant count. See [Postings Overview](/postings/postings-overview).

## Candidate and application

A **candidate** is a person applying for your jobs. Candidates arrive from job board applications or are added by your team. An **application** is a candidate's connection to one specific job; if a candidate is considered for two jobs, each application moves through its own job's pipeline independently. See [The Candidate List](/candidates/candidate-list).

## Screening

The AI voice call at the heart of CONFIRM. Every job screens its applicants automatically: the voice agent calls the candidate (or takes their inbound call), asks the job's screening questions, checks knockout requirements, and answers candidate questions. Each screening produces a transcript, a recording, and per-question answers. See [How Screening Works](/screening/how-screening-works).

## Screening questions and knockouts

**Screening questions** are what the agent asks on the call — generated from your job details or written by you. A question can be marked as a **knockout**: a must-have requirement such as work authorization or a required license. A candidate who fails a knockout doesn't move forward automatically — depending on the job's pipeline, they either go to your review queue or are rejected. See [Screening Questions](/jobs/screening-questions) and [Knockout Criteria](/jobs/knockout-criteria).

## Hiring pipeline

The steps a candidate goes through after screening, configured per job. Every pipeline starts with AI screening and ends with a hire decision. In between you choose the steps: **Review** (someone on your team decides), **Interview round**, **Assessment**, and — where available — **Background check** and **Intro video gate**. The pipeline decides what happens to a candidate who passes screening, for example whether they wait for your approval or go straight to interview booking.

## Status

Where a candidate stands right now. Statuses are grouped into phases you'll see in filters and on the dashboard, such as **Applied**, **Outreach**, **Awaiting Review**, **Ready for Interview**, **Interview Scheduled**, **Past Interview**, and **Hired**, plus outcomes like **Rejected**, **Did Not Meet Requirements**, **No-Show**, and **Do Not Contact**. Rows in the candidate list also show the specific pipeline step, such as an interview round and whether it's being booked, scheduled, or done. The full list is in the [Status Reference](/candidates/status-reference).

## Fit tier

A chip summarizing how a candidate compares to the job at a glance:

| Tier             | Meaning                                                                                      |
| ---------------- | -------------------------------------------------------------------------------------------- |
| **Strong fit**   | Strong match signals                                                                         |
| **Moderate fit** | Mixed signals — worth a closer look                                                          |
| **Limited fit**  | Weak match signals                                                                           |
| **Pending**      | The candidate hasn't finished screening yet                                                  |
| **Ineligible**   | Ruled out by a process rule, such as a failed knockout, the distance limit, or the blocklist |

You can filter the candidate list by tier. The tier is a review aid — you remain the decision-maker.

## Knowledge base

Information the voice agent uses to answer candidate questions during calls. There's an organization-wide knowledge base under **Settings → Knowledge Base** (which also holds your company name pronunciation), and each job can add its own documents. See [Job Knowledge Base](/jobs/job-knowledge-base).

## Talent pool

A named collection of candidates that can span multiple jobs — for example, "Qualified Warehouse Workers." Pools make it easy to revisit strong candidates when new positions open. See [Talent Pools](/candidates/talent-pools).

## Saved view

A named snapshot of your candidate list filters, so you can return to the same slice of candidates with one click. See [Filters & Saved Views](/candidates/filters-and-saved-views).