Identity and access management
Nmbrs to JumpCloud integration: employees of every company in Nmbrs as JumpCloud users
With an integration between Nmbrs and JumpCloud, every employee from Nmbrs becomes a user in JumpCloud, with department, job title and company, and JumpCloud suspends the user after the end date. KoppelHet holds the connection with Nmbrs and offers JumpCloud one list across all companies, which JumpCloud's Custom API import fetches.
What the integration does
Organisations that run payroll in Nmbrs, often with several companies, and use JumpCloud for accounts and devices often update JumpCloud by hand. IT maintains users based on messages from HR, and someone who moves to another company in the group sometimes appears twice in JumpCloud.
- An Nmbrs administrator gives KoppelHet's app consent with read-only rights on employees, employments and companies.
- KoppelHet reads all companies and builds one record per person, with the company where they are currently employed.
- In JumpCloud we set up the Custom API import on KoppelHet's address, with its own key.
- We set the mapping and the status rule on the dates and link users to their applications through groups.
- After the end date JumpCloud suspends the user; KoppelHet monitors whether the scheduled import succeeds.
What to watch for with Nmbrs and JumpCloud
- Nmbrs grants access to the REST API through an authorisation code flow, where an Nmbrs user signs in and gives consent, with tokens that are refreshed later. JumpCloud's Custom API import does not support refresh tokens. JumpCloud therefore cannot read Nmbrs directly; KoppelHet holds that connection and gives JumpCloud its own key.
- In Nmbrs employees are stored per company, while JumpCloud expects one endpoint with all users. KoppelHet goes through every company the consent covers and puts them together in one list.
- Employee numbers in Nmbrs are only unique within a company, and two companies can both have a number 1001. KoppelHet puts the company code in front of the number in employeeIdentifier, so JumpCloud does not merge two employees.
- A move to another company is a leave and a hire in Nmbrs. KoppelHet recognises the same person and supplies one record with the new company. With reactivation on update switched on in JumpCloud, the user keeps their devices and access, even if the old employment ends slightly earlier.
- KoppelHet only requests the read scopes for employee data, employments and company data from Nmbrs, and no payment scope. Pay and bank details therefore never end up in the list for JumpCloud.
- An imported user only gets access to an application in JumpCloud once they are in a user group bound to that application. KoppelHet supplies company and department, so you can fill groups per company and a subsidiary keeps its own applications.
- A scheduled suspension in JumpCloud must be at least an hour in the future and runs in ten-minute rounds. KoppelHet does not use it, but supplies the end date to the import's status rule; that way the suspension is anchored in Nmbrs and not in separate manual actions.
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 gives consent in Nmbrs?
An Nmbrs user with rights on the companies that should be included. That choice decides which companies reach JumpCloud.
Is a leaver deleted?
No, suspended. Deleting remains a step for IT, for example after a laptop has been returned.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the Nmbrs REST API with OAuth 2.0 (identityservice.nmbrs.com, authorisation code flow with consent from an Nmbrs user and refresh token) and read-only scopes, such as employee.info.read, employee.employment.read and company.info.read; read per company.
- JumpCloud: Custom API import with Bearer Token or API Key on the KoppelHet address (OAuth refresh token not supported), method GET, required mapping Company email and Username, State through EXPR with manageUserState, Allow reactivation of users on update, scheduled import hourly or daily.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in JumpCloud | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | employeeIdentifier | Employee number is unique per company |
Zakelijk e-mailadres | Company email en Username | Required in JumpCloud |
Roepnaam, tussenvoegsel en achternaam | firstname en lastname | |
Functie | jobTitle | |
Afdeling | department | |
Bedrijf | company | |
Datum uit dienst | State via manageUserState |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll