Training and certificates
YouForce to LinkedIn Learning integration: one licence per person, groups per organisation unit
With an integration between Visma Raet YouForce and LinkedIn Learning, every employee from YouForce who qualifies under your rules automatically gets one LinkedIn Learning licence, even with several employments, and sits in the group of their organisation unit. When the last employment ends, the integration sets the licence to inactive.
What the integration does
Organisations that process HR and payroll in YouForce and hand out LinkedIn Learning licences often add learners by email address and set leavers to inactive by hand. People with two employments in YouForce, or with a new address after a name change, then appear twice in LinkedIn Learning.
- You decide which units, jobs or types of employment get a licence.
- KoppelHet retrieves daily what YouForce has processed and determines per person whether there is an active employment that meets the rule.
- KoppelHet builds the file with one row per person and sends it to LinkedIn Learning.
- LinkedIn creates learners, updates groups and switches licences on or off; KoppelHet reads the result and reports errors.
What to watch for with Visma Raet YouForce and LinkedIn Learning
- YouForce separates persons from employments, and a person can have several at the same time. LinkedIn Learning counts licences per learner. KoppelHet sends one row per person and keeps the licence active as long as at least one employment meets your rule, so nobody gets two licences.
- LinkedIn Learning needs at least an email address per learner. The YouForce Learning API only returns email addresses with the contact details scope, which also opens the citizen service number and private address. KoppelHet only uses the business address from that data and puts nothing else in the file.
- After a name change in YouForce the business address often changes. LinkedIn treats a different address without a fixed unique ID as a new learner. With the person number or the sign-in ID as unique ID it stays the same learner; if that ID ever has to change too, KoppelHet does it in a separate upload, because LinkedIn does not allow ID and email to change at once.
- Every organisation unit from YouForce becomes a group column in the file, and LinkedIn creates a missing group itself. An administrator can thus assign courses or learning paths to a department and report per department, without filling groups by hand.
- The Learning API only shows what HR Core has processed and keeps deleted records available for about seven days. A termination that becomes visible after processing is turned into an inactive licence by KoppelHet at the next daily round.
- A learner added as inactive gets no welcome email from LinkedIn. If a new employee is already in YouForce before their start date, KoppelHet first adds them as inactive and activates them on the start date, so the invitation does not land in their inbox weeks too early.
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
Can LinkedIn Learning certificates go into the digital file?
That can be added later as an extension. The YouForce Learning API accepts documents of type certificate; first it has to be clear which certificates you want to keep.
What do we need to arrange with Visma Raet?
Access for the KoppelHet application to the Learning API, including the contact details scope because of the email address, and our fixed IP addresses on the allow list if you use one.
Do we need Entra ID or Okta?
Not for the licences; KoppelHet delivers those directly from YouForce. For single sign-on you do use your own identity provider.
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 Learning API (api.youforce.com/learning) with OAuth 2.0 via Visma Connect, read-only - persons, employments, organizationUnits and jobProfiles, with from and to on latestSync and isActive. For email the Youforce-Learning:GetPrivateContactDetails scope.
- LinkedIn Learning HTTPS Org Sync in manual mode (media/upload with enterprise_csv_upload, enterpriseUploadJobs for processing and resultStats), or SFTP Org Sync if you already use it. CSV in UTF-8 with lowercase headers, unique_user_id, group/<name> and the product's licence column.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in LinkedIn Learning | Notes |
|---|---|---|
Persoonsnummer (personCode) | unique_user_id | Or the ID your single sign-on uses |
Zakelijk e-mailadres | primary_email_address | |
Roepnaam | preferred_first_name | |
Voorvoegsel + Achternaam | preferred_last_name | |
Functie (jobProfile) | work_title | |
Organisatie-eenheid | group/<eenheid> | 0 or 1 |
Licentieregel en dienstverbanden | Licentiekolom van het product (active of inactive) |
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