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

# Job Knowledge Base

Candidates ask questions on screening calls — about benefits, training, schedules, what the job is really like. The knowledge base gives the AI agent your real answers, so it responds with your information instead of deflecting.

There are two levels:

* **Organization-wide** — **Settings → Knowledge Base**. Information that's true for every job: company background, benefits, and how to pronounce your company name.
* **Per job** — the **Knowledge Base** section of a job's console. Documents and details specific to one role.

The knowledge base isn't part of job setup; add job documents from the console once the job exists.

## Organization-wide knowledge base

**Settings → Knowledge Base** has three parts:

* **Company name pronunciation** — spell your company name the way it should sound out loud, and the AI agent says it that way on every call. Leave it blank if it's pronounced exactly as spelled. It applies to your whole company, on every job. (The same setting appears on the Job Details step when you create a job.)
* **Company-wide Sources** — documents shared across all your jobs. Click **Upload document**.
* **Company Knowledge Profile** — AI-analyzed sections built from your uploaded documents. Click **Analyze documents** to build or refresh it, and edit any section. Jobs inherit these sections unless a job overrides them.

## A job's knowledge base

Open the job and go to **Knowledge Base**. You'll see:

* **Company Knowledge Profile** for this job — what the AI agent knows for this job. Sections without an override are inherited from the organization-wide profile; you can create an override for a section to change it for this job only.
* **Job Documents** — the source files that feed the profile and that the agent can reference when answering candidate questions.

### Uploading documents

1. Open the job and go to **Knowledge Base**.
2. Under **Job Documents**, click **Upload document** and choose a file.
3. The document is processed and becomes available to the agent for future calls.

Supported file types: PDF, DOCX, TXT, MD, CSV, and JSON, up to 10 MB per file.

### Managing documents

Each document is listed with its name, size, and upload date.

* **View content** — preview what the agent will read from the document.
* **Delete** — click the trash icon and confirm. The document is removed from the agent's knowledge base for future calls.

> **Note**
>
> Who can change the knowledge base: Administrators and Recruiters. Viewers can see the organization-wide knowledge base in Settings but not change it, and Hiring Managers don't see the Knowledge Base settings.

## What makes good knowledge base content

The agent answers best from focused, factual documents:

* **Benefits summaries** — health coverage, PTO, retirement, perks
* **FAQ sheets** — the questions candidates actually ask, with your approved answers
* **Company culture and "about us" documents**
* **Role logistics** — training programs, typical schedules, dress code, parking

> **Tip**
>
> Split large documents into focused, topic-specific files — a separate "Benefits Overview," "Training Program," and "Company Culture" beats one long handbook.

A few things to avoid:

* Don't upload anything you wouldn't want repeated to a candidate — the agent treats the content as approved answers.
* Keep documents current; outdated pay or benefits information will be relayed as fact.
* Skip internal-only material such as margins, internal policies, or other candidates' data.

Use the organization-wide knowledge base for information that's true everywhere, and job documents for role-specific details.