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

# HiBob

Connect Bob for modern HR management with automated IT provisioning and org chart syncing

{% hint style="warning" %}
**This integration is being retired.** HiBob no longer permits Service User based marketplace integrations. If your workspace is connected through this page, reconnect with [HiBob (OAuth)](/integrations/hris/hibob-oauth.md) by following the [Migrating HiBob to OAuth](https://docs.harmony.io/guides/people-management/migrating-hibob-to-oauth) guide.
{% endhint %}

HiBob (Bob) is a modern HR management platform designed for dynamic, distributed workforces. Connecting Bob to Harmony enables automated IT provisioning based on HR events, intelligent employee lifecycle management, and seamless synchronization of organizational data for optimal IT operations.

#### What the HiBob integration enables

| Capability            | Description                                                                    |
| --------------------- | ------------------------------------------------------------------------------ |
| Employee Data Sync    | Sync employee profiles, departments, roles, position levels, and org structure |
| Automated Onboarding  | Trigger IT provisioning when new employees are added                           |
| Offboarding Workflows | Automate access revocation when employees are terminated                       |
| Department Routing    | Route IT requests based on employee department and location                    |
| Lifecycle Automation  | Automate IT tasks for role changes, transfers, and promotions                  |

#### Prerequisites

* **HiBob Administrator Access**: Admin role with API access permissions
* **HiBob Subscription**: Active Bob account for your organization
* **Harmony Account**: Active Harmony workspace

#### Connect HiBob to Harmony

**Step 1: Create Service User in HiBob**

1. Log in to Bob at `https://app.hibob.com`
2. Navigate to **System Settings** > **Integrations** and open **Service Users** (in the **Automation** section)
3. Create a service user: enter a name (for example, `Harmony Integration`) and a display name, then click **Save**
4. Copy the service user's **ID** and **Token** - the token is shown only once
5. Go to **System Settings** > **Account** > **Permission groups**, create a permission group for Harmony, and add the service user to it. A new service user has no permissions until it belongs to a permission group
6. In the group's **People's data** tab, set **Access data for** to **Everyone**. Then, under **People's fields**, enable **View** on these categories:

   * **About**
   * **Basic info**
   * **Employment**
   * **Lifecycle** (required for employment status and termination dates)
   * **User data**
   * **Work**
   * **Work contact details**

   Also enable **Edit** on the **Email** field.
7. Under the **Features** tab, enable the following **Time off** permissions:
   * **Settings**: Manage company's time off settings
   * **Settings**: See company's time off settings
8. Under the **People's data** tab, enable the following **Time off** permissions:
   * **See who's out today**: See who's out
   * **Balance**: See selected people's time off and sick leave balances
   * **Requests**: Create, edit all fields, and cancel people's requests that haven't been approved yet
   * **Requests**: Edit all fields and cancel people's future requests that have been approved
   * **Requests**: Edit all fields and cancel people's past requests that have been approved
   * **Requests**: Upload, edit and view attachments in people's requests
   * **Requests**: View all fields, approve or decline requests that are pending approval of others
9. If you use the **Create Employee** or **Update Employee** workflow blocks, also enable **People** > **Add new people to the company** under the **Features** tab, and **Edit** on the employee fields those blocks change
10. Save the permission group

**Step 2: Navigate to Integrations**

1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **HiBob** under **HRIS** (or search for it by name) and click its card

![Navigate to HiBob integration in Harmony dashboard](https://1160081901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fow5hkvoGYRymkbqRTEvW%2Fuploads%2Fgit-blob-4401dd44327d6f225f07f3a9fe61c6cea7d4feb2%2Fhibob-connect.png?alt=media)

**Step 3: Enter API Credentials**

1. Enter your **Service user ID**
2. Enter your **Service user token**
3. Click **Connect**

![Enter HiBob credentials to connect](https://1160081901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fow5hkvoGYRymkbqRTEvW%2Fuploads%2Fgit-blob-1f1524c52c0831662d62ad582155ad7fa95cf6e3%2Fhibob-integrations.png?alt=media)

#### What Harmony Syncs

**From HiBob:**

* Employee profiles and personal information
* Employment details (job title, department, employment type)
* Organizational data (manager, direct reports, hierarchy)
* Work information (location, phone, time zone)
* Employment dates (start date, end date)
* Custom fields relevant to IT operations
* Department structure and sub-departments
* Status changes (active, terminated, etc.)
* Position level (Individual Contributor, Management, Senior Management, or Executive Leadership), mapped from HiBob's org level data

#### Position Level Sync

Harmony automatically syncs each employee's position level from HiBob into their Harmony profile. Levels are standardized into four categories mapped directly from HiBob's org level data:

| HiBob Org Level (API value) | Harmony Position Level |
| --------------------------- | ---------------------- |
| `individualContributor`     | Individual Contributor |
| `firstLevelManager`         | Management             |
| `midLevelManager`           | Senior Management      |
| `topLevelManager`           | Executive Leadership   |

This means your support workflows and automations can reference an employee's seniority tier without any manual data entry.

#### Using HiBob Blocks in Agent Workflows

HiBob blocks in the Agent workflow builder expose proper inputs and outputs, making it straightforward to connect them to other steps in your workflows. You can:

* **Pass data into HiBob blocks** - supply context from earlier steps to filter or enrich queries
* **Use results downstream** - feed employee data returned by a HiBob block into subsequent workflow logic
* **Resolve employees automatically** - blocks support Employee ID resolution, so Harmony can identify and look up the right employee record as part of a running workflow

HiBob blocks behave consistently with all other blocks in the builder, giving you a reliable and predictable building experience.

#### Use Cases

<details>

<summary>Automated New Hire Provisioning</summary>

Trigger complete IT setup when HR adds new employees to HiBob

</details>

<details>

<summary>Role-Based Access Management</summary>

Automatically adjust access permissions when employee roles change

</details>

<details>

<summary>Department-Based Request Routing</summary>

Route IT tickets to appropriate teams based on employee department

</details>

<details>

<summary>Seamless Offboarding</summary>

Automate access removal and asset recovery when employees are terminated

</details>


---

# 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.harmony.io/integrations/hris/hibob.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.
