ACAccounts in applications
YouForce to Atlassian integration: Jira and Confluence access through groups from Visma Raet
With an integration between Visma Raet YouForce and Atlassian Cloud, an employee from YouForce gets a managed Atlassian account with job title and department, and joins the groups that belong to their job and organisation unit. Those groups decide who gets a Jira or Confluence licence; a move or temporary assignment changes them on the effective date, and after the last employment the account is deactivated.
What the integration does
Organisations that keep HR in YouForce and manage projects or knowledge in Jira and Confluence often grant access at a team lead's request. Licences pile up because nobody withdraws them after a move, and anyone joining a project for a few months simply keeps access to that space afterwards.
- Together we decide which jobs and units get an Atlassian group, and which group gives access to Jira or Confluence.
- KoppelHet fetches the changed persons, employments, planned changes and assignments from YouForce.
- On the start date KoppelHet creates the account in the Atlassian directory, or links an existing account with the same work email, and adds it to the groups.
- A planned move or temporary assignment changes the groups on the effective date and back again on the end date.
- After the last employment KoppelHet deactivates the account; pages and issues stay in place.
What to watch for with Visma Raet YouForce and Atlassian Cloud (Jira en Confluence)
- Atlassian only allows accounts to be created from an external source with Atlassian Guard Standard. KoppelHet checks that subscription and the verified domains before anything from YouForce is passed on, because without Guard the integration cannot create managed accounts.
- In YouForce every employee has a job from a fixed list. Only jobs you select, such as developer or project lead, get a group that grants a Jira or Confluence licence. A new job in YouForce therefore does not produce a paid licence by itself.
- An assignment to another team is separate from the employment in YouForce, with its own end date. KoppelHet adds the employee to that team's Atlassian group for the period and removes them on the end date, so access to that team's Jira projects does not linger.
- Groups created through provisioning are read-only in Atlassian and cannot be renamed. Organisation units in YouForce have a fixed ID next to their name; KoppelHet puts that ID in the group name and only creates a new group on a real reorganisation, moving the members across.
- A synced display name in Atlassian also overwrites first and last name. KoppelHet builds that name from the name usage in YouForce, so someone who uses their partner's name after marriage appears in Jira and Confluence the same way as in HR.
- Planned changes of job or unit are visible in YouForce before HR processes them. KoppelHet only adjusts the groups on the effective date, and uses PATCH instead of a full update, because Atlassian clears every field not sent in a full update.
- A leaver disappears from YouForce's IAM data after the configured number of historical days. Because removing in Atlassian means deactivating, KoppelHet keeps track of which accounts come from YouForce and deactivates on the end date itself, regardless of what YouForce returns later.
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
We already connect Atlassian with Entra ID. Is this needed then?
Usually not. Then let Entra ID stay the source for Atlassian and fill the groups in Entra ID from YouForce. One source per directory avoids duplicate accounts.
Does the integration also handle permissions within Jira projects?
No. The integration fills groups; which group sees which projects and spaces you set in Jira and Confluence yourselves.
What happens to external users?
Anyone not in YouForce stays outside the integration. Their access does not change.
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 (api.youforce.com/IAM) with the Youforce-IAM:Get_Basic scope for Persons, Employments, Employment Planned Changes, Assignments, Organization Units and Job Profiles, on latestSync with take and nextLink. The work email only with Youforce-IAM:GetPrivateContactDetails.
- Atlassian through the User provisioning REST API (SCIM 2.0) at https://api.atlassian.com/scim/directory/{directoryId}, with the directory API key as bearer token. Users with POST and PATCH; DELETE sets active to false. Groups: an existing name returns 409, renaming not supported, default group names are not synced. Limits: 150,000 users per directory, 35,000 per group. Paging with cursor.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Atlassian Cloud (Jira en Confluence) | Notes |
|---|---|---|
Persoonsnummer | externalId en employeeNumber | Fixed key |
Roepnaam en achternaam volgens naamgebruik | name en displayName | |
Zakelijk e-mailadres | userName en emails | |
Functie (job profile) | title en groep per functie | |
Organisatie-eenheid | department en groep per eenheid | |
Inzet bij een andere eenheid | Lidmaatschap van de groep van die eenheid, voor de duur van de inzet | |
Einddatum laatste dienstverband | active = false |
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