> For the complete documentation index, see [llms.txt](https://docs.senseloaf.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senseloaf.ai/integrations/lever-it-setup-guide.md).

# Lever — IT Setup Guide

One-time setup steps to connect Lever to SIA

This guide is for IT administrators and Lever Super Admins. It covers generating an API key, connecting Lever to SIA, and optionally setting up candidate stage mapping.

Once setup is complete, your HR team can start using SIA's hiring intelligence directly from Lever — see the Lever HR Workflow Guide for what they can do from there.

{% hint style="warning" %}
**Note:** Connecting Lever to SIA connects it for your **entire organisation** — confirm with your team before switching connectors, as SIA only keeps one ATS active at a time. Senseloaf writes results back as notes on the candidate, so there is no custom field setup required.
{% endhint %}

### Before you begin

To connect Lever to SIA, you'll need to complete two steps — and optionally a third:

1. Generate an API key in Lever
2. Connect Lever in the SIA Connectors page
3. Set up candidate stage mapping *(optional)*

### Step 1 — Generate an API key in Lever

{% hint style="info" %}
Only **Super Admins** can generate and manage API keys in Lever.
{% endhint %}

1. Log in to Lever with a Super Admin account
2. Go to **Settings → Integrations → API Credentials**
3. Click **Generate New Key** and give it a name — for example, *Senseloaf Integration*
4. Copy the key immediately and store it securely — it is only shown once

{% hint style="warning" %}
**Note:** You can have multiple API keys active at once, so generating a new key for Senseloaf won't disturb any other integration's key. This is the only connection method SIA supports for Lever right now — sign-in-and-approve is not available yet.
{% endhint %}

### Step 2 — Candidate stage mapping *(optional)*

Senseloaf can automatically move candidates between your existing Lever pipeline stages based on their AI evaluation outcome. You are not limited to a fixed set of stages — Lever's pipeline stages are whatever your organisation already has configured, and Senseloaf reads that list directly, so there is nothing new to create.

If you'd like this enabled, let the Senseloaf team know which of your existing stages should correspond to each outcome (matching, prescreening, interview) during onboarding.

### Enable automatic syncing

To enable automatic syncing of your Lever data with SIA, reach out to the Senseloaf team at <support@senseloaf.com>. The team will configure and enable the bidirectional sync for your organisation.

### Step 3 — Connect Lever to SIA

**A. Open Connectors in SIA**

1. Log in to your SIA account
2. Click your **Profile icon** in the bottom-left corner
3. Click **Connectors** from the menu
4. Search for **Lever** and click **Connect** — this opens the pop-up for entering credentials

**B. Enter your Lever credentials**

* **API Key** — paste the key generated in Step 1

**C. Connect Lever**

1. Verify the API key is correct
2. Click **Connect**
3. SIA establishes the connection with your Lever account

### What happens once connected

Once Lever is connected, SIA begins syncing jobs and candidates automatically — no further setup required from IT. For a full overview of what the HR team can do from here, see the Lever - HR Workflow Guide.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.senseloaf.ai/integrations/lever-it-setup-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.