> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/hibob.md).

# HiBob

<figure><img src="/files/lMBJf4SdScQwcjeQ9fz6" alt=""><figcaption></figcaption></figure>

### What you get

* **Live People directory** — Bob employees, departments, sites, and reporting lines appear in Siit automatically.
* **Lifecycle triggers** — Start date, End date, Probation end, Work anniversary, and Birthday all flow into Siit as workflow triggers.
* **Manager chain** — Bob's reporting structure powers auto‑selected approvals in Siit workflows.
* **Custom fields** — import any custom Bob field into Siit (cost center, legal entity, work pattern, etc.).
* **Pre‑hires** — future employees with a start date in Bob appear in Siit ahead of Day 1, so pre‑boarding workflows can run early.

### What syncs from HiBob

| Category        | Fields                                                          |
| --------------- | --------------------------------------------------------------- |
| Identity        | Display name, first name, surname, work email, employee ID      |
| Role            | Job title, department, team, job level                          |
| Org structure   | Manager, site (location), company / legal entity                |
| Employment      | Employment type (employee, contractor), status (active, leaver) |
| Lifecycle dates | Start date, termination date, date of birth                     |
| Custom          | Any custom Bob field you select during mapping                  |

Work email is used as the canonical identifier across systems.

### Before you connect

* You'll need **Bob admin permissions** to generate a service user and API token.
* Make sure work email is filled in for every active employee in Bob.
* Decide whether Bob or your IdP should be the source of truth for overlapping fields (title, department). You can configure this after connecting in **Settings → People → Fields**.

### Connect HiBob

1. In Bob, create a **service user** for Siit:
   * Go to **Settings → Integrations → Service Users**.
   * Click **New service user**, name it "Siit", and grant it read access to People, Employment, Work, and Lifecycle categories.
   * Copy the **Service user ID** and **token** shown.
2. In Siit, go to **Settings → Integrations**.
3. Find **HiBob** in the HRIS section and click **Connect**.
4. Paste the service user ID and token, then click **Authorize**.
5. Siit runs an initial import and shows a preview of imported people.
6. Review field mapping and click **Finish setup**.

> **Tip** — Give the service user read‑only access to the People categories Siit needs. Avoid using a personal admin account; a dedicated service user survives employee changes.

### After the connection

* **Check your People list** in Siit — the count should match your active + upcoming employees in Bob.
* **Set source of truth** in **Settings → People → Fields**, picking HiBob for HR‑owned fields.
* **Map custom fields** — in **Settings → Integrations → HiBob**, add any custom category or field you use in Bob.
* **Build workflows** — start with a Day‑1 onboarding workflow using the Start date trigger.

### Sync frequency

HiBob data refreshes automatically every few hours. Use **Settings → Integrations → HiBob → Sync now** to force an immediate refresh.

### Common workflows

**Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign app bundles by department, order equipment, DM the hiring manager.*

**Offboarding on leave date.** *Trigger: End date. Actions: revoke sessions, remove app access, open an equipment return request, send handover reminder to manager.*

**Welcome message by site.** *Trigger: Start date, Condition: site = Paris. Action: send the local welcome pack.*

### Troubleshooting

**Missing employees.** Check that the service user has access to the employee's department. Bob permissions are category‑scoped, so missing access means missing data in Siit.

**Manager field empty.** In Bob, confirm the employee has a manager set in the **Work** category. Siit reads from that field.

**Custom field not imported.** Make sure the custom field is enabled in the API and within the service user's category permissions, then re‑run mapping in Siit.

**"Unauthorized" on connect.** The service user token is invalid or the service user was deleted. Regenerate the token in Bob and paste it back into Siit.

>