Visma Raet YouForce logoOI

Identity and access management

YouForce to One Identity integration: employees and departments from Visma Raet in One Identity Manager

With an integration between Visma Raet YouForce and One Identity Manager, employees, departments and managers from YouForce are prepared every day in fixed files, which One Identity Manager reads as the source for roles and rights. Leavers stay in those files with their end date, so One Identity Manager revokes their access instead of losing sight of them.

What the integration does

Organisations that use YouForce for HR and payroll and One Identity Manager for accounts and rights often feed One Identity Manager with a home-made export. After a restructuring the department tree no longer matches, and synchronisation stops at every duplicate row of an employee with two employments.

  1. The organisation grants KoppelHet read access to YouForce through Visma, and a folder on a server that One Identity Manager's synchronisation server can read.
  2. KoppelHet fetches persons, employments, organisation units and role assignments and chooses the main employment per person.
  3. KoppelHet writes a department file with the full path of each department and an employee file with one row per person.
  4. One Identity Manager reads the files with the CSV connector and adjusts roles and rights.
  5. A leaver stays in the file with their end date until the agreed retention period has passed.
Visma Raet YouForce → KoppelHet → One IdentitySOURCEVisma Raet YouForceTARGETOne IdentityOne IdentityKoppelHetmapping · logging · monitoringVisma Raet YouForce → KoppelHet → One IdentitySOURCEVisma Raet YouForceTARGETOne IdentityOne IdentityKoppelHetmapping · logging · monitoring
Out: File with employees and their main employment · File with departments in tree order · Manager per department · Start and end date

What to watch for with Visma Raet YouForce and One Identity

  • One Identity Manager's CSV connector has no project template; the administrator builds the mappings between columns and fields in the Synchronization Editor. KoppelHet therefore supplies files with a fixed structure and a description per column, so those mappings are set up once and do not break afterwards.
  • An employee can have several employments at once in YouForce. On a duplicate key One Identity Manager can stop or arbitrarily take the first or last row. KoppelHet supplies one row per person with the main employment, and puts the departments of other employments in a multi-value column.
  • One Identity Manager can read a column as a path in a tree and then loads the parent departments first. KoppelHet builds the full path for each organisation unit from YouForce, so a new department under a new sector lands correctly in one run.
  • Persons disappear after a set period from what YouForce supplies for IAM. When importing from a source like this, One Identity Manager cannot mark missing persons as outstanding. KoppelHet therefore keeps leavers in the file with their end date itself, so One Identity Manager sees a departure and not just a missing row.
  • One Identity Manager reads dates according to the language set for the file. KoppelHet writes dates in one fixed format and the file in UTF-8, so 03-04 does not accidentally become 4 March and names with a diaeresis come through correctly.
  • In YouForce the manager is a role on the department, not on the employee. KoppelHet puts the manager in the department file, so One Identity Manager knows them as the department's manager and approvals for requests reach the right person.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Why files and not a direct connection?

One Identity Manager often uses the CSV connector for HR data, and it works without a direct connection to the source system. KoppelHet makes sure the files are right and ready on time.

What if the file is not ready one day?

KoppelHet then reports it before the synchronisation runs. One Identity Manager does not then re-read the previous version as a new state.

Can the username go back to YouForce?

Yes, with separate write rights in YouForce for contact details. We only request them if you want it.

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, Organization Units, Role Assignments, Job Profiles), on latestSync with the from parameter. Persons outside the historicaldays are not returned.
  • One Identity Manager reads through the CSV connector: synchronisation project without a template, key columns per file, Uniqueness violation behavior set to Throw error, Hierarchical sort order on the department path (such as Department.FullPath), an MVP column for extra departments and the Data import option in the synchronisation step (MarkAsOutstanding is not available there). The synchronisation server must be able to read the files directly.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in Visma Raet YouForceField in One IdentityNotes
PersoonsnummerSleutelkolom medewerker (Person)
Roepnaam, voorvoegsel en achternaam volgens gebruikVoornaam, tussenvoegsel en achternaam
Functie (job profile)Functie
Organisatie-eenheidAfdeling (Department) met volledig pad
Rolverdeling op de organisatie-eenheidLeidinggevende van de afdeling
Organisatie-eenheden van andere dienstverbandenKolom met meerdere waarden
Begin- en einddatum dienstverbandDatum in en uit dienstIn a fixed format

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.