Identity and access management
Deel to Omada integration: employees, EOR and contractors from Deel as identities in Omada
With an integration between Deel and Omada Identity, Omada reads everyone working for you through Deel as an identity, with type of work relationship, entity, department, manager and a start and end date. KoppelHet prepares one row per person that Omada's REST collector reads.
What the integration does
Organisations that hire people in several countries through Deel and use Omada for access governance often miss exactly the contractors and EOR staff in Omada. They are not in the own payroll, so not in the source Omada already reads, while they do have accounts and rights.
- Deel gets an organisation token with read rights only on people, contracts and organisation structure.
- KoppelHet processes Deel's notifications and keeps one row per person, with the contract that applies today.
- In Omada the administrator creates a system with the REST collector for identity data, with OAuth2 Client Credentials to KoppelHet.
- Omada reads identities, entities and departments, and links each identity to its manager.
- At go-live we set thresholds on deleted and modified identities.
What to watch for with Deel and Omada
- Omada also has a SCIM collector, and Deel has a SCIM API. Still, that is not a route. The SCIM collector reads users as accounts, not as identities, and since Omada 14.0.7 can only map a list to an extension attribute. The contracts of a person are exactly a list at Deel.
- Someone who moves from contractor to EOR or own employee gets a new contract in Deel. KoppelHet keeps the person's Deel ID as business key and only passes the type of work relationship again, so Omada keeps the same identity and only recalculates the roles.
- With employer of record, Deel or a partner is the legal employer. For those people KoppelHet sets the own entity or the country as context, so policy and reviews in Omada keep working per business unit and do not end up at an outside employer.
- Deel gives the manager as a work email, and Omada links an owner through the business key of another identity. KoppelHet translates the address to the manager's Deel ID, so approvals and reviews reach the right person, even if they work in another country.
- Someone who has not yet started in Deel is NOT_STARTED. KoppelHet already delivers them with the start date as valid from, so Omada can prepare rights without them becoming active before the start.
- Deel pauses notifications to an address after ten failed attempts. Omada, on the other hand, reads on its own schedule. KoppelHet monitors the notifications and compares all people in Deel with the rows for Omada every night, so a missed departure is in Omada by the next morning at the latest.
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
Do contractors also reach Omada?
Yes. Everyone in Deel who needs to work gets an identity, with the type of work relationship as an attribute for roles and reviews.
Can Omada then create accounts in Entra ID or Google Workspace itself?
Yes, with Omada's connectors. KoppelHet only supplies the HR source.
Does salary data go to Omada?
No. The token has no rights on payments and the row only contains 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.
- Deel through the HRIS People API and contracts (worker_id, hiring_type, person_status ACTIVE, NOT_STARTED or INACTIVE, client_legal_entity, termination_last_day, direct_manager.work_email) with an organisation token, plus webhooks signed with x-deel-signature. The Deel SCIM API (GET /scim/Users, scope Users:read) returns contracts as an employments list and responds with 429 to too many requests.
- 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, owners through Owner UID. Omada's SCIM collector imports users as accounts and since v14.0.7 only maps lists to extension attributes. Thresholds for new, modified and deleted objects.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Omada | Notes |
|---|---|---|
worker_id | Business key en Unique ID | |
Voornaam en achternaam | Name | |
person_status en termination_last_day | Status | |
hiring_type | Soort identiteit | |
client_legal_entity | Context (entiteit) | |
department | Context (afdeling) | |
direct_manager.work_email | Identity owner | Translated to the manager's business key |
start_date en termination_last_day | Valid from en Valid to |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions