HiBob
Visualize HiBob employees, departments, and time-off data in the JupiterOne graph. Map employees to their managers to build an organization chart, track time-off policies and requests, and monitor changes through custom queries and alerts.
- Installation
- Authorization
- Data Model
- Release Notes
HiBob Integration Installation in JupiterOne
Overview
This guide walks you through how to connect your HiBob account with JupiterOne to ingest and monitor your HR data.
The integration pulls employee profiles, departments, organizational hierarchy, time-off policies, and time-off requests from HiBob. It authenticates as a HiBob service user using basic access authentication against the HiBob API.
Prerequisites
- A HiBob account with admin access, or someone who can ask a Bob admin to create a service user and permission group on your behalf.
- Access to JupiterOne with permission to configure integrations.
Set Up in HiBob
Step 1: Create a Service User
- Log in to your HiBob account as an administrator.
- Go to the Service Users section in Bob and create a new service user (for example, "JupiterOne").
- Copy the service user's ID and Token.
You can only copy the token at the time it is generated. If you lose it, you must generate a new one.
Store the ID and Token securely — you will need both when configuring the integration in JupiterOne.
Refer to the HiBob Service Users documentation for more details.
Step 2: Create a Permission Group
By default, HiBob service users have no access permissions. Create a dedicated permission group so you can grant only the access this integration needs.
- In HiBob, create a new permission group (for example, "JupiterOne Integration").
- Add the service user you created in Step 1 to this group.
Step 3: Assign Permissions
Grant the following permissions to the permission group you created.
Employee data (required)
Under People's data > People's fields, grant View on the field categories the integration reads. HiBob permissions are assigned at the category level (by categoryId), not per individual field. To read the default People-search fields, assign View on the following categories:
| Category | Access | Purpose |
|---|---|---|
| root | View | Core identity fields |
| about | View | Personal information fields |
| employment | View | Employment-related fields |
| work | View | Department and manager (reports-to) fields |
| Lifecycle | View | Employee status and lifecycle status (status, lifecycleStatus) |
| Personal > Communication | View | Work and mobile phone numbers |
The work category is required for the department entities and the employee reports-to (manager) relationships the integration builds.
HiBob returns a 200 OK response even when a field permission is missing — fields the service user cannot access are silently omitted with no warning. Verify that all expected data appears in JupiterOne after the first ingestion.
Access rights (required)
Under People's data > Access rights (Access data for), select Everyone to let the integration read all active employees.
The integration fetches only active employees. You do not need to grant access to inactive employees.
Time-off permissions (required)
| Permission | Purpose |
|---|---|
| Features > Time off > Settings > Manage company's time off settings | Read time-off policy types and policies |
| People's data > Time off > See who's out today > See who's out | Read time-off requests |
| People's data > Time off > See who's out today > See who's out because of a private policy or policies with a custom name | Read time-off requests made under private or custom-name policies |
Step 4: Authenticate
The integration authenticates each request with the service user's ID and Token using basic access authentication. No further setup is required in HiBob beyond the service user and its permissions. See the HiBob authorization documentation for details.
Configure Integration in JupiterOne
- In JupiterOne, go to the left navigation menu and click Integrations.
- Scroll to the HiBob integration tile and click it.
- Click Add Configuration.
Creating an instance requires the following:
- Account Name: A friendly name to identify this HiBob account in JupiterOne.
- Description: Optional notes to help identify this integration instance.
- Polling Interval: How often JupiterOne collects data, or
DISABLEDto run the integration manually. - Service Account ID: The HiBob service account ID used for API authentication.
- Service Account Token: The HiBob service account token used for API authentication.
Data Volume Configuration
Ingestion Windows
| Field | Description | Default | Options |
|---|---|---|---|
| Time Off Requests Ingestion Window | How far back, in days, to ingest time-off requests. A larger window ingests more history and stores more entities in JupiterOne. | 180 | 30, 90, 180 |
Click Create Configuration to save.
JupiterOne will begin pulling data from HiBob based on the polling interval you set.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Permissions
IAM permissions that must be granted to the integration principal for data ingestion.
Show Permissions (6)
Features > Time off > Settings > Manage company's time off settingsPeople's Data > Time off > See who's out today > See who's outPeople's Data > Time off > See who's out today > See who's out because of a private policy or policies with a custom name (for requests under private or custom-name policies)People's data > Access rights (Access data for): Everyone (to read all active employees)People's data > People's fields: View on the root, about, employment and work categories (work is required for department and reports-to data)People's data > People's fields: View on the work category (the manager/reports-to field is a Work field, read by fetch-employees)
Endpoints
API endpoints that the integration makes requests to.
Show Endpoints (4)
https://api.hibob.com/v1/people/searchhttps://api.hibob.com/v1/timeoff/policy-typeshttps://api.hibob.com/v1/timeoff/policy-types/{policyType}https://api.hibob.com/v1/timeoff/requests/changes
Documentation Links
Links to provider documentation relevant to setup and configuration.
Show Documentation Links (5)
Per-Data-Source Breakdown
Authorization required by the steps that make up each data source. Steps that depend on a data source are listed in the Per-Step Breakdown; the complete lists are in the sections above.
Show all data sources (3)
| Data Source | Permissions | Endpoints |
|---|---|---|
| Employees | People's data > Access rights (Access data for): Everyone (to read all active employees), People's data > People's fields: View on the root, about, employment and work categories (work is required for department and reports-to data), People's data > People's fields: View on the work category (the manager/reports-to field is a Work field, read by fetch-employees) | https://api.hibob.com/v1/people/search |
| Time Off Policies | Features > Time off > Settings > Manage company's time off settings | https://api.hibob.com/v1/timeoff/policy-types, https://api.hibob.com/v1/timeoff/policy-types/{policyType} |
| Time Off Requests | People's Data > Time off > See who's out today > See who's out, People's Data > Time off > See who's out today > See who's out because of a private policy or policies with a custom name (for requests under private or custom-name policies) | https://api.hibob.com/v1/timeoff/requests/changes |
Per-Step Breakdown
Detailed authorization requirements for each ingestion step.
Show all steps (2)
| Step | Permissions | Endpoints |
|---|---|---|
| Fetch: Time Off Requests | People's Data > Time off > See who's out today > See who's out, People's Data > Time off > See who's out today > See who's out because of a private policy or policies with a custom name (for requests under private or custom-name policies) | https://api.hibob.com/v1/timeoff/requests/changes |
| Relationships: Employee -> MANAGES -> Employee | People's data > People's fields: View on the work category (the manager/reports-to field is a Work field, read by fetch-employees) | - |
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| HiBob Account | hibob_account | Account |
| HiBob Department | hibob_department | Group |
| HiBob Employee | hibob_employee | User |
| HiBob Time Off Policy | hibob_time_off_policy | Policy |
| HiBob Time Off Request | hibob_time_off_request | Record |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
hibob_account | HAS | hibob_employee |
hibob_account | HAS | hibob_department |
hibob_account | HAS | hibob_time_off_policy |
hibob_department | HAS | hibob_employee |
hibob_employee | MANAGES | hibob_employee |
hibob_employee | HAS | hibob_time_off_request |
hibob_time_off_policy | HAS | hibob_time_off_request |
Release Notes
- 2026-02-25 — New HiBob integration: ingests employees, departments, time-off policies, and time-off requests with manager hierarchy relationships.