Identity and access management
YouForce to Omada integration: Visma Raet as the authoritative source for identities in Omada Identity
With an integration between Visma Raet YouForce and Omada Identity, Omada reads every employee from YouForce as an identity, with department, job, manager, temporary assignment and a status that follows from the end date of the last employment. KoppelHet combines the YouForce data per employee into one record, so Omada assigns roles and revokes access based on a complete and accurate source.
What the integration does
Organisations that use YouForce for HR and Omada for roles, access requests and reviews often have Omada read a database view or export. For employees with two employments one department is then picked at random, and managers get reviews for people who no longer work for them.
- The organisation grants KoppelHet read access to YouForce through Visma.
- KoppelHet fetches persons, employments, assignments, organisation units and role assignments and determines the main employment and the manager per person.
- KoppelHet offers one record per employee through its own secured address, with a status that follows from the end date.
- Omada's REST collector reads that address as the authoritative source, and Omada assigns roles based on department and job.
- After the end date of the last employment the status becomes inactive and Omada revokes access.
What to watch for with Visma Raet YouForce and Omada
- Omada requires a business key, a unique ID, a name and a status for every identity. YouForce has no status field for a person with several employments. KoppelHet derives the status from the end date of the last employment, so someone ending one of two contracts stays active.
- Omada warns that a status from the HR system can overwrite a status change made in Omada itself. We agree with you up front which side leads, for example that a block by security in Omada stays until security lifts it.
- Omada's REST collector can fetch nested data, but then only calls the first element of each list, and that costs speed. Persons and employments sit in separate lists in YouForce. KoppelHet therefore merges them into one record per employee, so Omada does not need to nest and misses no second employment.
- Deleted records in YouForce are only visible for seven days. An employee who was entered and then deleted can therefore silently drop out of the source. KoppelHet keeps track of those deletions itself and passes them on, and we set a threshold in Omada on the number of deletions per import, which is off by default.
- A temporary assignment to another team is separate from the employment in YouForce. KoppelHet supplies it with start and end date, so Omada can grant extra roles for that period and revoke them on the end date, and the review reaches the right manager.
- Omada's REST collector signs in with, among other methods, OAuth2 client credentials. KoppelHet gives Omada its own key for KoppelHet's address; access to YouForce stays with KoppelHet, so Omada needs no rights in YouForce.
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
Who decides the roles?
Omada. KoppelHet makes sure department, job and manager are right; the rules that turn them into roles live in Omada.
Does Omada see private data from YouForce?
No. KoppelHet only requests basic data; BSN and home address fall under a separate permission we do not request.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- YouForce is read through the Youforce IAM API with the Youforce-IAM:Get_Basic scope (Persons, Employments, Assignments, Organization Units, Role Assignments, Job Profiles), on latestSync, with isActive for deleted records (visible for seven days).
- Omada reads through the REST collector (Content: Identity data) with OAuth2 Client Credentials and paging through Link header or continuation token. Required identity fields Business key, Unique ID, Name and Status. Thresholds for new, modified and deleted objects as percentages (default 0, so off).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Omada | Notes |
|---|---|---|
Persoonsnummer | Business key en Unique ID | Required in Omada |
Naam volgens gebruik | Name | Required in Omada |
Einddatum laatste dienstverband | Status | Required in Omada; derived by KoppelHet |
Organisatie-eenheid van het hoofddienstverband | Afdeling | |
Functie (job profile) | Functie | |
Rolverdeling op de organisatie-eenheid | Leidinggevende | |
Inzet (begin, einde, eenheid) | Tijdelijke afdeling met datums | |
Organisatie-eenheden van andere dienstverbanden | Extra afdelingen |
Related
ADP Workforce Now → Visma Raet YouForce
ADP Workforce Now to YouForce integration: requests for new Dutch hires and contract changes
Bullhorn → Visma Raet YouForce
Bullhorn to YouForce integration: a placement becomes a hire request
Carerix → Visma Raet YouForce
Carerix to YouForce integration: a placed candidate starts the hire workflow in YouForce
Darwinbox → Visma Raet YouForce
Darwinbox to YouForce integration: hires and pay changes from Darwinbox as a request in YouForce