OIIdentity and access management
HiBob to One Identity integration: Bob as the HR source for One Identity Manager
With an integration between HiBob and One Identity Manager, employees and departments from Bob arrive in One Identity, which bases accounts and rights in Active Directory and other systems on them. One Identity has no HiBob connector; KoppelHet delivers a fixed HR file that One Identity Manager's CSV connector imports, with new colleagues, leavers and their dates.
What the integration does
Organisations that use HiBob as their HR system and One Identity Manager for accounts and rights often have HR make an export by hand for the IAM team. Columns shift when someone adjusts a report in Bob, and a leaver who drops out of the export is not processed as a departure in One Identity.
- In Bob we create a service user with read rights on the required categories and on all employees.
- KoppelHet reads the employees and keeps them current with the notifications from HiBob.
- KoppelHet writes a file for employees and one for departments, with fixed columns, to a location the synchronisation server can read.
- In the Synchronization Editor the administrator maps the columns to Person and Department, with a read-only connection.
- KoppelHet monitors whether the files are complete and reports an employee with missing fields to HR.
What to watch for with HiBob and One Identity
- One Identity has connectors for cloud HR systems through Starling Connect, but HiBob is not in the administration guide or in the release notes up to February 2026. KoppelHet therefore delivers through the CSV connector, which One Identity Manager ships as standard.
- If the files come from another system, One Identity Manager sets up the synchronisation as a data import. A person who disappears from the file can then not be marked as outstanding. KoppelHet therefore keeps leavers in the file with their leaving date, instead of leaving them out.
- Without an extra setting HiBob only returns employees who are employed. For leavers and new colleagues before the start KoppelHet switches on the option for inactive employees and lets the service user's permission group see beyond employed staff. Otherwise exactly the people IAM is about are missing.
- The CSV connector can use one column for the position in a hierarchy, so parent departments are loaded first. KoppelHet puts the full path of the Bob department in it, so One Identity Manager builds the department tree before employees are linked to it.
- HiBob leaves out a field the service user has no right to, without an error. In a CSV file that becomes an empty column, and One Identity Manager can process an empty department as a change. KoppelHet checks every row and puts no employee with missing fields in the file.
- With duplicate rows the CSV connector can stop or pick a row. KoppelHet uses the fixed Bob ID as the key column and delivers exactly one row per employee, so the choice is never made by the connector.
- The file's columns are fixed in the synchronisation project; an extra column or a different order breaks the synchronisation. KoppelHet only adds a new field from Bob once the administrator has adjusted the mapping in the Synchronization Editor.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Where does the file go?
In a location the One Identity synchronisation server can read, which KoppelHet fills over an outbound connection. The exact location is agreed with your IT.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob through webhooks (employee.created, employee.updated, employee.joined, employee.left) and POST /v1/people/search (showInactive true, permission group with access beyond Employed; fields without rights are omitted without warning; no paging, fetching in batches on root.id).
- One Identity Manager CSV connector: synchronisation project with CSV system connection (path, encoding, language, behaviour on non-unique rows, Read-only access), file structure with header line, delimiter, key columns and one column with Hierarchical sort order; synchronisation step with the Data import option (no MarkAsOutstanding); a remote connection server with RemoteConnectPlugin if needed.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in One Identity | Notes |
|---|---|---|
root.id | Person.CentralAccount of eigen sleutelkolom | Key column in the CSV connector |
root.firstName, root.surname | Person.FirstName, Person.LastName | |
work.title | Person.Title | |
Afdelingspad | Department.FullPath | Column with Hierarchical sort order |
work.reportsTo | Person.UID_PersonHead | |
work.site | Locality | |
work.startDate | Person.EntryDate | |
Vertrekdatum | Person.ExitDate |
Related
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
Carerix → HiBob
Carerix to HiBob integration: successful match becomes a new employee in Bob
Greenhouse → HiBob
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob