OIIdentity and access management
Deel to One Identity integration: employees, EOR and contractors from Deel in One Identity Manager
With an integration between Deel and One Identity Manager, everyone working for you through Deel is in a fixed file every day, with type of work relationship, entity, country, manager and last working day, which One Identity Manager's CSV connector reads. One Identity Manager uses it to assign accounts and rights to employees, EOR staff and contractors, and processes a departure on the last day from Deel.
What the integration does
Organisations that use One Identity Manager and hire people abroad through Deel often do not load those people at all, or load them by hand. Their own HR source only contains employees on their own payroll, so contractors and EOR staff have accounts One Identity Manager cannot link to a person.
- Deel gets an organisation token with read rights only on people, contracts and organisation structure.
- KoppelHet creates a file with a fixed layout and places it where the synchronisation server reads.
- The One Identity Manager administrator sets up the CSV connector, with the Deel ID as key and a multi-value column for the contract types.
- After each notification from Deel KoppelHet updates that person's row.
- After a departure the row stays with the last working day, until after the retention period.
What to watch for with Deel and One Identity
- Deel does not appear in One Identity's Starling Connect documentation up to the release notes of February 2026, and Deel writes that it does not provision to identity systems itself. One Identity Manager's CSV connector is therefore the route, with KoppelHet as the middle layer that delivers Deel in a fixed layout.
- Someone can have several contracts at once in Deel, for example as a contractor for two entities. The CSV connector supports multi-value columns with their own delimiter. KoppelHet puts all running contract types in such a column, so One Identity Manager reads one row per person and still knows all relationships.
- If a contractor moves to EOR or to the own company, Deel creates a new contract. KoppelHet uses the person's ID as the key column, not the contract, so One Identity Manager keeps the same Person and only the type of work relationship changes.
- With employer of record, Deel or a partner is the employer on paper. For those people KoppelHet fills the company column with the own entity or the country they work for, so departments and companies in One Identity Manager do not fill up with the names of outside employers.
- With a file from another system, One Identity Manager cannot mark a person who disappears as outstanding. A leaver therefore stays in KoppelHet's file, with the last day from Deel as ExitDate.
- Deel gives the manager as a work email. In the file the manager column points to another row's key. KoppelHet translates the address to the manager's Deel ID, so One Identity Manager can set the line even if the manager is a contractor too.
- Deel limits the number of requests and returns an error when there are too many. KoppelHet builds the file from Deel's notifications and only fetches all people once at night, so other integrations on Deel are not affected by the synchronisation.
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 One Identity Manager?
Yes. Everyone in Deel who needs to work is in the file, with the type of work relationship as a column for your rules.
Does payment data go to One Identity Manager?
No. The token has no rights on payments, and the file only contains the columns 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. With too many requests Deel responds with 429.
- One Identity Manager reads one file through the CSV connector (UTF-8, header row, text delimiters) with PersonnelNumber as key column and an MVP column with its own delimiter for the contract types. Synchronisation step with Data import, without MarkAsOutstanding; access directly or through a remote connection server.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in One Identity | Notes |
|---|---|---|
worker_id | Sleutelkolom PersonnelNumber | |
Voornaam | FirstName | |
Achternaam | LastName | |
hiring_type van lopende contracten | Kolom soort arbeidsrelatie (meerdere waarden) | |
client_legal_entity | Kolom bedrijf | |
Land van het contract | Kolom land | |
direct_manager.work_email | Kolom leidinggevende | Translated to the manager's Deel ID |
start_date | EntryDate | |
termination_last_day | ExitDate |
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