Connecting BambooHR or HiBob

BambooHR and HiBob are HR systems, not identity providers, but they hold the same underlying fact an identity provider does: who is employed here right now, and what their attributes are. Both connectors are read-only directory pulls, in the same family as pulling your directory from Okta, JumpCloud or another identity provider - they list users, derive groups, and feed the same directory-sync path those identity-provider connectors use. The difference is only where the data comes from: HR software instead of a directory or IdP.

BambooHR

1. 1

   Create an API key

   In BambooHR, open your account menu (top right) -> API Keys -> Add New Key.

2. 2

   Note your BambooHR subdomain

   This is the company name in your own BambooHR URL.

3. 3

   Connect it in Qorionix

   Under Integrations -> Catalog -> BambooHR, choose Directory sync, enter the subdomain and the API key, press Test and save, then run the first sync.

The connector reads from BambooHR's Custom Report endpoint rather than the more limited Employee Directory endpoint, specifically because the custom report can be asked to include employment status - active versus terminated - which the directory endpoint does not expose at all. Without that field, a terminated employee could keep showing as active in Qorionix indefinitely.

HiBob

1. 1

   Create a Service User

   In HiBob, open Settings -> Integrations -> Service Users -> Add Service User, granting it read access to People.

2. 2

   Copy the service user's id and token

   Both are shown once, at creation.

3. 3

   Connect it in Qorionix

   Under Integrations -> Catalog -> HiBob, choose Directory sync, paste the service user id and token, press Test and save, then run the first sync.

HiBob authenticates over HTTP Basic as well, but with a real credential pair - the Service User's id as the username and its token as the password - HiBob's own "Service user" scheme, rather than BambooHR's fixed-password shape above. The connector pulls the full people list in one call and reads each person's department and employment status the same way the BambooHR connector does.

Why a large org's HR sync can take longer than an IdP sync

Neither vendor's chosen endpoint - BambooHR's custom report, HiBob's people listing - supports a modified-since filter, so both connectors do a full listing sync every single time, not an incremental one. The sync cursor Qorionix records after each run is only the timestamp the sync itself started at; it is not a true incremental marker the way an identity provider's own change cursor is, because there is nothing upstream to hand that cursor back to. In practice this means a BambooHR or HiBob sync re-reads every employee on every run, so a sync against a large organisation's full headcount will take longer than an incremental sync against the same size of Okta or JumpCloud tenant, where only records changed since the last run are re-read.

Workday and SAP SuccessFactors are not built