Identity and access management
HiBob to Omada integration: Bob as the authoritative source for Omada Identity
With an integration between HiBob and Omada Identity, every employee from Bob arrives in Omada as an identity, with department, job title, manager and the start and end dates, so roles, reviews and revoking access run on HR data. KoppelHet prepares the data in a form Omada's REST collector imports, including new colleagues and leavers.
What the integration does
Organisations that use HiBob as their HR system and Omada for identity governance often use an export someone in HR makes as the source, with leavers who disappear from the export instead of getting an end date.
- In Bob we create a service user with read rights on the required categories and on all employees, including those who have left or not yet started.
- KoppelHet reads all employees and keeps them current with the notifications from HiBob.
- KoppelHet prepares one row per employee with key, name, status, department, manager and dates.
- In Omada we create a REST system for identity data that reads these rows and processes them as identities and contexts.
- KoppelHet checks every delivery for missing fields before Omada reads it.
What to watch for with HiBob and Omada
- KoppelHet delivers to Omada's REST collector, which imports identities from a prepared list.
- In principle Omada's REST collector can call HiBob's search itself. But HiBob does not page there and advises large companies to first fetch only IDs and then work in batches. Omada can only do that per row with a nested call, which Omada itself calls slow. KoppelHet therefore prepares the complete list and Omada reads it in one go.
- Without an extra setting HiBob returns only employed staff. Departed and not-yet-started colleagues only come along with a separate option and if the service user's permission group is not limited to employed staff. KoppelHet sets up both, so a leaver gets an end date in Omada instead of silently disappearing.
- HiBob leaves out fields the service user has no right to, without an error. An identity without a department loses its context in Omada and with it roles. KoppelHet compares each row with the expected fields and keeps an employee with gaps at the previous state, with an alert to HR.
- Omada warns that a status from the HR source can overwrite a status set in Omada itself, and advises not passing that field on to the portal in that case. With you we agree whether HiBob or Omada leads for the status, so a block by security does not disappear at the next import.
- Custom fields in Bob, such as a cost centre or a contract type that matters for roles, are not in HiBob's default fields. KoppelHet requests them separately with rights on the right category, and prepares them as an extension attribute for the role rules in Omada.
- A HiBob notification about a changed employee only contains the fields that changed. KoppelHet then fetches the employee in full, so the row for Omada is always complete and never half updated.
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
Why does Omada not read HiBob directly?
It is technically possible, but HiBob does not page and advises batches for large companies. A prepared list is faster and keeps leavers and missing fields under control.
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 (no paging, at most 400 field IDs, filters only on root.id and root.email with equals, showInactive true plus a permission group with access beyond Employed; fields without rights are omitted without warning; custom fields requested separately).
- Omada REST collector (Content: Identity data) with OAuth2 Client Credentials or API Key to the KoppelHet endpoint; required identity mapping Business key, Unique ID, Name and Status; contexts with Business key, Name and Type, context assignments with Identity UID; thresholds per import for new, modified and deleted objects.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in Omada | Notes |
|---|---|---|
root.id | Business key en Unique ID | |
root.firstName, root.surname | Name, FirstName, LastName | |
Naamgevingsregel of root.email | Email | |
internal.status en vertrekdatum | Status, ValidTo | |
work.startDate | ValidFrom | |
work.department | Context (afdeling) en context assignment | |
work.reportsTo | Identity owner en context owner | |
work.title | JobTitle | |
Soort dienstverband | EmploymentType (extensieattribuut) |
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