# Resumes & documents

> Upload CVs, let the parser structure them, and manage every file on a candidate record.

_Collection: Companies, Contacts & Candidates (records) — Kepler Help Center. Canonical: https://keplercrm.com/support/articles/resumes-and-documents/_

Keep original CVs and other documents on the candidate record, and use the **AI resume parser** when you want to extract structured details. Storing a file, extracting its details and choosing it as the candidate’s profile source are separate choices.

## Uploading documents

Open a candidate’s **Documents** tab. Use **Upload CV** in **CVs** for a CV, or **Upload Document** in **Other documents** for another file. CVs can be PDF, DOC, DOCX or TXT.

After a manual CV upload, Kepler asks what to do with it:

  - For a candidate without a profile yet: **Just store it** keeps the file without changing anything, and **Use as profile source** reads the CV and builds the profile from it.

  - For a candidate who already has a profile: **Just store it**, **Merge with profile** (Kepler reads the CV, then you choose what to keep from it and from the current profile, change by change) or **Replace profile** (the CV's experience, education and skills replace what's there).

To use a stored CV later, choose **Compare and update profile** from its **⋯** menu; a CV that hasn't been read yet is read first. A CV that has been read also offers **View extraction**. Each CV row has its own **Download** button, and labels such as **Profile source** or **Not read into profile** show how it relates to the profile.

## Where documents come from

  - **Manual upload** on the Documents tab.

  - **Bulk CV import** — files uploaded via [Adding candidates from CVs](/support/articles/import-candidates-from-cvs/) attach to the created candidate.

  - **Email and WhatsApp attachments** — with **Save attachments to records** on under **Settings → Record capture**, files from a known candidate or contact are filed on their record (signature images, invites and email history are skipped). A candidate's own CV is filed as a CV: it becomes their profile if they had none; otherwise it's stored for you to compare. A CV from someone new can create the candidate (**Create a candidate when someone new sends a CV**).

  - **Portal & LinkedIn applications** — an applicant's CV is attached automatically when you accept or store them from the Applicants page.

## What the parser extracts

| Data | Result |
| --- | --- |
| Contact details | Structured into profile fields |
| Work history & tenure | Structured experience entries on the Profile tab |
| Skills & languages | Searchable attributes |
| Qualifications & certifications | Searchable attributes |
| Salary, notice & right to work | Match-ready fields |
| Your custom attributes | Filled for columns that read the Primary CV, following each column's rule |

## Updating the profile from a CV, and recovering an earlier profile

**Use as profile source** and **Replace profile** make that CV the primary source for the candidate’s structured profile: its experience, education, skills and other profile data replace the current profile, and recruiter-owned fields are protected. Review this choice carefully when the existing profile contains details from other sources.

**Merge with profile** and **Compare and update profile** open the profile as it will read, with each change marked in place and listed by number. For each one, keep the current version or take the CV's; a role that's only in the current profile stays unless you remove it, because CVs often leave out older roles. Switch between **With changes**, **Before** and **After** to check the result before you apply it.

When a CV newer than the one the profile uses is on file, the Profile tab shows **A newer CV hasn't been applied**, with **Compare and update profile** or **Dismiss**.

If the result is wrong, click **Undo** on the *Profile updated from …* message that appears after the update. Later, open the **Profile** tab, click **Profile history** (filter it by **CV updates** or **Hand edits**), find the update you want to undo and choose **Restore before this** to return to the profile from before that update. The Profile tab also shows, in one line, which file the profile came from. These controls let you recover a prior profile without re-uploading the original CV.

Custom columns follow their own [fill settings](/support/articles/custom-fields/); proposed changes that need review arrive in [Notifications](/support/articles/ai-suggestions/).

## Deleting a CV

Choose **Delete file** from a CV's **⋯** menu. If AI filled fields from that CV, the dialog lists them with **Keep** or **Undo** for each (Keep is the default, and **Undo all** sets the lot). A value someone has changed since stays as it is. Suggestions from the CV that are still waiting can be accepted in the same dialog; the rest are withdrawn with the file. Deleting a note or meeting notes works the same way.

## Previewing and downloading

For a branded client copy, see [Formatting and sending a CV](/support/articles/formatting-and-sending-cvs/).

Click a document to preview or download it. Kepler hands out a short-lived signed link rather than a public URL, and only members of the workspace the file belongs to can request one.

> **NOTE:** Parsing runs to structure your database. For current information on subprocessors, retention and training use, see AI & data privacy or contact your workspace administrator.