Accounts in applications
YouForce to Slack integration: Slack account with name, team and start date from Visma Raet
With an integration between Visma Raet YouForce and Slack, a new employee from YouForce gets a Slack account on their start date, with the name they use, their job, department, manager and start date. A temporary assignment puts them in the other team's user group for that period, and after the last employment the integration deactivates the account.
What the integration does
Organisations that run HR in YouForce and work internally in Slack usually create Slack accounts as soon as the manager asks. Names in Slack differ from what is in YouForce, user groups lag behind the department structure, and leavers stay active until someone checks a list.
- Together we select the organisation units that get a Slack user group, and the employment types that come in as guests.
- KoppelHet fetches the changed persons, employments, assignments and role assignments from YouForce.
- On the start date KoppelHet creates the Slack account with name, job title, department, manager and start date, and adds it to the unit's user group.
- A name change, new job or move updates the profile and the user group on the effective date.
- After the end date of the last employment KoppelHet deactivates the Slack account.
What to watch for with Visma Raet YouForce and Slack
- YouForce records the name usage per person, for example own name, partner's name or a combination, with a fixed table for the order. KoppelHet builds the Slack display name from it. If the name usage changes after a marriage or divorce, the Slack name follows on the same day.
- A Slack username may have at most 21 characters and only periods, underscores and hyphens as punctuation. Long Dutch surnames with a prefix or double names do not always fit. KoppelHet shortens the name by a fixed rule and checks that it does not already exist.
- Slack accepts a Slack ID, an email address or a username as manager. YouForce knows the manager as a role on the organisation unit. KoppelHet looks up the manager of each employee's unit and passes on their work email; for the manager themselves, the role on the unit above counts.
- A temporary assignment to another team has its own start and end in YouForce. KoppelHet adds the employee to that team's user group for the period, so colleagues reach them with the group mention, and removes only that membership on the end date.
- Slack refuses a new account if the email address already belongs to a deactivated user. When a former employee returns under the same person number in YouForce, KoppelHet finds the old Slack account by that number and makes it active again.
- KoppelHet recognises interns and other temporary staff by the employment type in YouForce. On a Slack Enterprise plan they become a multi-channel guest with their employment end date as expiry date; on Business+ they get a regular account that is deactivated on that date.
- If one value in Slack's custom profile fields is invalid at creation, Slack drops all profile fields. KoppelHet therefore checks the values from YouForce in advance, so an error in one field does not wipe out a new colleague's job title and department.
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
Doesn't Slack already run through Entra ID for us?
Then Entra ID stays the source for Slack and YouForce supplies the right data to Entra ID. Directly from YouForce fits when name usage, start date, assignments and manager must be right in Slack and Entra ID does not pass them on.
Can the integration also set the @ group mention?
No. Slack does not allow a user group's mention handle to be set through SCIM. The Slack administrator sets it once per group; the integration keeps the members up to date.
What happens to a leaver's messages?
Slack does not delete users, it deactivates them. Messages and files stay according to the retention policy of your Slack environment.
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, Role Assignments, Job Profiles and the Name Assemble Order and Employment Types tables, on latestSync. The work email only with Youforce-IAM:GetPrivateContactDetails.
- Slack is written through the Slack SCIM API v2 (api.slack.com/scim/v2) with an OAuth token with the admin scope from an Owner or Admin. Users with POST, PATCH and DELETE (deactivate, 204), reactivation with active = true; enterprise extension with employeeNumber, department and manager.managerId; startDate through urn:ietf:params:scim:schemas:extension:slack:profile:2.0:User; guests through urn:ietf:params:scim:schemas:extension:slack:guest:2.0:User (type multi, expiration). User groups through /Groups with PATCH on members.
- The SCIM API is available on Slack Business+ and Enterprise; guests through SCIM only on Enterprise. On too many calls Slack returns HTTP 429; lists are fetched in pages of at most 1,000.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Slack | Notes |
|---|---|---|
Persoonsnummer | enterprise.employeeNumber | Fixed key |
Roepnaam en achternaam volgens naamgebruik | name.givenName, name.familyName en displayName | |
Naamgevingsregel | userName | At most 21 characters |
Zakelijk e-mailadres | emails | |
Functie (job profile) | title | |
Organisatie-eenheid | enterprise.department en lidmaatschap user group | |
Rol leidinggevende op de eenheid | enterprise.manager.managerId | As the manager's work email |
Startdatum dienstverband | startDate (Slack-profielextensie) | |
Einddatum laatste dienstverband | Deactiveren (DELETE /Users) |
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