> 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/jobdiva-it-setup-guide.md).

# JobDiva — IT Setup Guide

One-time setup steps to connect JobDiva to SIA

This guide is for IT administrators and JobDiva account owners. It covers obtaining a Client ID, creating a dedicated user, connecting JobDiva to SIA, and optionally setting up custom fields and candidate stage mapping.

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

{% hint style="info" %}
**Note:** Unlike some other ATS integrations, JobDiva doesn't have a self-service "generate an API key" screen — connecting requires a Client ID from JobDiva Support and a dedicated login you'll enter into SIA. Connecting JobDiva to SIA connects it for your **entire organisation.**
{% endhint %}

### Before you begin

To connect JobDiva to SIA, you'll need to complete three steps — and optionally two more:

1. Obtain your JobDiva Client ID from JobDiva Support
2. Create a dedicated JobDiva user account for Senseloaf
3. Connect JobDiva in the SIA Connectors page
4. Create the Senseloaf custom fields in JobDiva *(optional — the Senseloaf team can help)*
5. Set up candidate stage mapping *(optional)*

### Step 1 — Obtain your JobDiva Client ID

A Client ID authorises Senseloaf to access your JobDiva environment.

1. Contact JobDiva Support at [**support@jobdiva.com**](mailto:support@jobdiva.com), or reach out to your JobDiva account manager
2. Request your organisation's **Client ID**
3. JobDiva Support will provide your unique Client ID — record it securely

### Step 2 — Create a dedicated JobDiva user for Senseloaf

JobDiva authenticates with a username and password rather than a generated key, so Senseloaf needs its own dedicated login rather than a personal one.

1. Log in to JobDiva as an admin
2. Go to **Settings → My Team → Add User**
3. Create a new user specifically for Senseloaf:
   * **Recommended username:** senseloaf\_integration
   * **Recommended email:** <team@senseloaf.com>
4. Assign the following permissions:
   * Access to the **ATS Module**
   * Access to **Custom Fields Configuration**
5. Set a secure password and save the user

### Step 3 — Create custom fields in JobDiva *(optional)*

Senseloaf writes its output into a set of custom fields on the candidate record. Creating these is optional, but if you do, they must exist with the **exact names** below for Senseloaf to update them. You can create these yourself, or reach out to the Senseloaf team and they'll help you set them up.

| **Field name**  | **Stores**                                                                                                     |
| --------------- | -------------------------------------------------------------------------------------------------------------- |
| **SIA\_Score**  | The overall candidate score from Senseloaf's AI agents — resume matching, prescreening, and interview combined |
| **SIA\_Report** | A link to the candidate's Senseloaf report card                                                                |

**Quick reference**

| **Level** | **Name**    | **Type**   |
| --------- | ----------- | ---------- |
| Candidate | SIA\_Score  | Number     |
| Candidate | SIA\_Report | Text / URL |

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

JobDiva tracks a candidate's pipeline position as a status on their submittal, for example: Submitted, Interviewing, Offered, Placed, Rejected, whatever statuses your organisation already has set up.

If you'd like Senseloaf to automatically move candidates between statuses based on their AI evaluation outcome (AI Matching, AI Prescreening, or AI Interview), let the Senseloaf team know which of your existing statuses should correspond to each outcome during onboarding.

There's no fixed set of stages to create — Senseloaf works with as many or as few statuses as your organisation already uses, so you don't need to add anything new to your pipeline for this.

### Step 4 — Connect JobDiva to SIA&#x20;

**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 **JobDiva** and click **Connect** — this opens the pop-up for entering credentials

**B. Enter your JobDiva credentials**

* **Client ID** — from Step 1
* **Username** and **Password** — the dedicated user created in Step 2

**C. Connect JobDiva**

1. Verify the credentials are correct
2. Click **Connect**
3. SIA establishes the connection with your JobDiva account

### What happens once connected

Once JobDiva 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 JobDiva - 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/jobdiva-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.