Skip to main content

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.

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​

  1. Log in to your HiBob account as an administrator.
  2. Go to the Service Users section in Bob and create a new service user (for example, "JupiterOne").
  3. Copy the service user's ID and Token.
caution

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.

  1. In HiBob, create a new permission group (for example, "JupiterOne Integration").
  2. 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:

CategoryAccessPurpose
rootViewCore identity fields
aboutViewPersonal information fields
employmentViewEmployment-related fields
workViewDepartment and manager (reports-to) fields
LifecycleViewEmployee status and lifecycle status (status, lifecycleStatus)
Personal > CommunicationViewWork and mobile phone numbers

The work category is required for the department entities and the employee reports-to (manager) relationships the integration builds.

note

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.

note

The integration fetches only active employees. You do not need to grant access to inactive employees.

Time-off permissions (required)​

PermissionPurpose
Features > Time off > Settings > Manage company's time off settingsRead time-off policy types and policies
People's data > Time off > See who's out today > See who's outRead 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 nameRead 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​

  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.

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 DISABLED to 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​

FieldDescriptionDefaultOptions
Time Off Requests Ingestion WindowHow far back, in days, to ingest time-off requests. A larger window ingests more history and stores more entities in JupiterOne.18030, 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.