Identity and access management
Factorial to Omada integration: employees, entities and teams from Factorial as identities in Omada
With an integration between Factorial and Omada Identity, Omada reads every employee from Factorial as an identity, with legal entity, teams, manager and the moment access ends according to Factorial. KoppelHet delivers the identities to Omada's REST collector and keeps them current with Factorial's webhooks.
What the integration does
Organisations that use Factorial for HR and Omada for identity governance often load employees from an export. A departure or a move to another entity then only reaches Omada with the next export, and teams from Factorial play no part in the policies.
- Factorial gets a company token for KoppelHet and webhook subscriptions on employees and contract versions.
- KoppelHet stores only the fields for Omada per employee and keeps the state current.
- In Omada the administrator creates a system with the REST collector for identity data, with OAuth2 Client Credentials to KoppelHet.
- Omada reads identities, contexts and assignments and calculates roles per entity and team.
- At go-live we set a threshold on deleted identities.
What to watch for with Factorial and Omada
- KoppelHet offers Omada's REST collector one address with identities, contexts and assignments from Factorial.
- On a termination in Factorial HR chooses a date on which access to Factorial stops, separate from the contract end date. KoppelHet gives Omada the access date as the end of the identity, so accounts elsewhere do not stay open longer than Factorial itself.
- A scheduled termination cannot be changed in Factorial; HR reverts it and enters it again. Factorial then sends one notification for the revert and one for terminating again. KoppelHet processes both and only gives Omada the latest state, so Omada does not see a rehire.
- If an employee moves to another legal entity, Factorial creates a new contract effective on a date, and the employee stays with the old entity until that day. KoppelHet moves the assignment in Omada on that date, so roles of the new entity do not arrive too early.
- An employee can be in more than one team in Factorial, and Omada's REST collector only uses the first element of nested lists. KoppelHet therefore delivers a separate assignment per team, so Omada sees all of an employee's teams.
- A webhook subscription in Factorial only sees employees the token may see, and a notification has no ID of its own. KoppelHet subscribes with a company token and processes every notification as the employee's new state, so a repeated notification does not cause a duplicate change in Omada.
- Factorial notifications can contain personal and financial fields, such as bank details and identity numbers. KoppelHet stores only the fields Omada needs and discards the rest straight away, so that data never reaches the identity environment.
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
Which end date does Omada use?
The date on which access to Factorial stops. The contract end date can come along as an extra attribute.
Do bank details or salary reach Omada?
No. KoppelHet only stores and delivers the fields from the design.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Factorial through the Factorial API (version 2026-10-01 in the path): employees with active, is_terminating, terminated_on, legal_entity_id, manager_id and company_identifier, contract versions, teams and legal entity changes. Webhooks employees/employee/create_with_contract, update, terminate and unterminate and contracts/contract_version/create and update; up to twenty attempts in 48 hours, then switched off and can be re-enabled; no ID per delivery.
- Omada reads through the REST collector (Content: Identity data) with OAuth2 Client Credentials: identities with Business key, Unique ID, Name and Status, contexts with Business key, Name and Type, context assignments and identity owners. With nested URLs only the first element of a list; thresholds for new, modified and deleted objects.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in Omada | Notes |
|---|---|---|
id | Business key en Unique ID | |
full_name | Name | |
active, is_terminating en terminated_on | Status en geldig tot | |
legal_entity_id | Context (type entiteit) | |
Teams | Context assignments (type team) | |
manager_id | Owner UID | |
company_identifier | Extensieattribuut personeelsnummer | |
email | Extensieattribuut werkadres |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll