Skip to content
Help Center
Workspace, Team & Billing

Record capture settings

Control when Kepler creates records automatically — and keep your database deliberate.

Settings → Record capture governs when Kepler creates people and companies from your team's synced email and calendars, so you choose the balance between a self-growing database and a strictly curated one. Owners and admins can change it, and each choice saves as you click. Changes are not retroactive.

Who becomes a record

  • Everyone — anyone in your team's email or calendar events.
  • People you contact (recommended) — people your team emails or invites to events.
  • Nobody — disables automatic creation; email and events still link to existing records.

Record type

Choose what each new person becomes: AI decides (recommended — contact or candidate, from the email or event), Always a contact or Always a candidate.

Companies and addresses

Create companies from email domains — when off, email still links to existing companies.

Protected recipients — click Manage to add email addresses or domains whose email creates no records, stays out of shared history and isn't used for AI suggestions. To hide their email from Kepler entirely, an owner can use Blocked addresses in Settings → Security & data.

Attachments and CVs

Files people send your team by email or WhatsApp, from new messages only:

  • Save attachments to records (on by default) — files documents onto the sender's candidate or contact. A CV is filed as their CV. Signature images, calendar invites and quoted email history are skipped.
  • Include photos (off by default) — also files photos and scans. Small images are always skipped.
  • Create a candidate when someone new sends a CV (on by default) — Kepler creates the candidate from the CV and notifies whoever received it.

The last two only work while Save attachments to records is on.

Other ways records arrive

  • CVs you add yourself — a CV uploaded with Add candidate becomes a candidate as soon as it's read, unless someone needs to look first: it may already be in Kepler, the file couldn't be read or the reading needs checking, it has no name, no email or phone, or it doesn't look like a CV. Those wait for you to decide, and one still waiting after 30 days is removed. See Import candidates from CVs.
  • LinkedIn on every new candidate — when a candidate arrives without a LinkedIn profile (from Add candidate, a CV filed from email, a job board application or a CSV import), Kepler searches the web for it. The search is free. A sure match is added with Undo; anything less certain waits on the record for you to pick. This is on by default; turn off Search the web for LinkedIn when a candidate is added under Automatic in Settings → Enrichment.
  • Things you accept — accepting an inbound applicant or adding someone yourself is an explicit action, and isn't affected by the settings on this page.

Can't find what you need?

Send us the details and we will get back to you. Response times vary by request.

Contact support
Contact support