> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HiBob

> Connect HiBob to Oleria to bring employees, departments, and manager relationships into your identity and access graph as the authoritative worker record.

Connect HiBob (Bob) to Oleria to bring your workforce data into your identity security posture. Oleria reads employees, departments, and reporting lines from Bob and uses them as the authoritative worker record that IdP and SaaS access is reconciled against, so a leaver who still holds access somewhere else is visible.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from HiBob:

* **Employees and people** - the full worker population, including inactive and terminated employees, with start date, termination date, title, department, and lifecycle status.
* **Departments** - your Bob department list, including the parent-child department hierarchy. Archived departments are included and labelled as archived, so former employees' departments still appear.
* **Manager relationships** - the reporting line for each employee, used to build your organization hierarchy.
* **Department assignments** - which department each employee currently belongs to.

<Note>
  HiBob is a system of record for the worker, not for application access. Bob doesn't expose permission groups, MFA or SSO settings, or an audit log through its API. Because of this, Oleria doesn't model Bob logins as accounts and doesn't discover groups, roles, or activity from HiBob - those come from your identity provider and SaaS integrations instead.
</Note>

## Prerequisites

* Administrator permission on the Oleria workspace
* A Bob administrator who can create service users and permission groups
* Your Bob environment: your live Bob account (production) or a Bob sandbox

<Note>
  Bob leaves out any field the service user isn't allowed to view instead of returning an error. Oleria checks that the service user can read employees' work email and lifecycle status before saving the integration, so a missing permission is caught at setup instead of silently showing leavers as still employed.
</Note>

## Create a service user in HiBob

<Steps>
  <Step title="Create the service user">
    In Bob, go to **System settings** -> **Integrations**. From the **All categories** list, select **Automation**, then select **Manage** on the **Service users** tile. Select **+ New service user** and create a service user, for example "Oleria". Copy the service user's **ID** and **Token**. Bob shows the token only when it's generated, so store it securely. If it's lost, generate a new one and update the integration in Oleria.
  </Step>

  <Step title="Grant permissions">
    Add the service user to a permission group with the following permissions:

    | Permission | Notes |
    | :- | :- |
    | **People's data** -> **Access data for** | All employees, including inactive employees. |
    | **View** on the **Basic info**, **Work**, and **Lifecycle** categories | Oleria needs these to read work emails, departments, managers, and termination dates. |

    The integration is read-only, so the service user doesn't need any **Employee management** permissions.
  </Step>
</Steps>

## Connect HiBob to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations** -> select **HiBob**.
  </Step>

  <Step title="Complete the connection form">
    | Field | Notes |
    | :- | :- |
    | Service user ID | Required. The ID of the service user you created. |
    | Service user token | Required. The service user's token. When you edit the integration later, leave it blank to keep the stored token. |
    | Environment | Required. **Production** for your live Bob account, or **Sandbox** for a Bob sandbox. You can't change it after the integration is saved. |
  </Step>

  <Step title="Authenticate">
    Select **Authenticate** to validate and save the integration. Oleria signs in as the service user and checks that it can read employees before saving.
  </Step>
</Steps>

## Verify the integration

Confirm the HiBob instance appears on the **Connected** tab of your Oleria **Integrations** page. After the first sync completes, review the discovered employees, departments, and manager relationships in your Oleria workspace.

## Known limitations

* **Activity isn't synced.** Bob has no audit-log API.
* **Large companies sync more slowly.** Bob allows 50 API requests per minute, so Oleria reads employees in batches and paces its requests.
* **Departments missing from the department list** are created from the department name on the employee record, so every employee's department still appears.

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.