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

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 using a service user authenticated via the HiBob API.

Prerequisites

• A HiBob account with admin access.
• Permission to create service users and permission groups in HiBob.
• Access to JupiterOne with permission to configure integrations.

Set Up in HiBob

Step 1: Create a Service User

1. Log in to your HiBob account as an administrator.
2. Navigate to Settings > Integrations > Service Users.
3. Click Add a New Service User and provide a name (e.g., "JupiterOne").
4. Generate an API token for the service user.
5. Copy the Service Account ID and Token — save them securely. You will need both when configuring the integration in JupiterOne.

Refer to the HiBob Service Users documentation for more details.

Step 2: Configure Service User Permissions

By default, HiBob service users have no access permissions. You must create a dedicated permission group and assign the appropriate permissions for the integration to work correctly.

1. In HiBob, go to Settings > Permissions > Permission Groups.
2. Create a new permission group (e.g., "JupiterOne Integration").
3. Add the service user you created in Step 1 to this group.
4. Grant the following permissions:

People's Data Permissions (Required)

The integration needs View access to employee data categories to read employee profiles, departments, and management hierarchy.

Permission Category	Access Level	Purpose
Basic Info (root)	View	Access employee names and core identity fields
About	View	Access personal information fields
Employment	View	Access employment-related data
Work	View	Access department, job title, site, start date, and manager (reports-to) information
Lifecycle	View	Access employee status and lifecycle status
Personal > Communication	View	Access work phone and mobile phone numbers
Time Off > See who's out today	View	Access time-off requests (select See who's out)

note

HiBob permissions are assigned at the category level, not at the individual field level. Granting View access to a category provides access to all fields within that category.

note

HiBob returns a 200 OK response even when permissions are incomplete — fields the service user cannot access are silently omitted from the response. Verify that all expected data appears in JupiterOne after the first ingestion.

Feature Permissions (Required)

Feature	Permission	Purpose
Time Off > Settings	Manage company's time off settings	Access time-off policy types and policy definitions

Access Rights

Under Access Rights, ensure the service user has access to Everyone (all active employees).

tip

The integration fetches only active employees (showInactive: false). You do not need to grant access to inactive employees.

Data Volume Configuration

Control how much historical time-off request data is ingested from HiBob.

Field	Description	Default
Time Off Requests Ingest Since Days	Number of days of historical time-off request data to ingest	365

Increasing this value will ingest more time-off request data, which increases the number of entities stored in JupiterOne.

Configure Integration in JupiterOne

1. In JupiterOne, go to the left navigation menu and click Integrations.

2. Scroll to the HiBob integration tile and click it.

3. Click Add Configuration and fill in the fields:

   Field	What to Enter
   Account Name	A friendly name to identify this HiBob account in JupiterOne (stored in tag.AccountName)
   Description	Optional notes to help identify this integration instance
   Polling Interval	How often to collect data (or choose DISABLED to run manually)
   Service Account ID	The Service Account ID from your HiBob service user
   Service Account Token	The API token generated for your HiBob service user
   Time Off Requests Ingest Since Days	Optional — number of days of time-off request history to ingest (default: 365)

4. 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.

Data Model

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