BiAccounts in applications
Nmbrs to Bitwarden integration: Bitwarden members per company and department from Nmbrs
With an integration between Nmbrs and Bitwarden, a new employee from Nmbrs is invited to the Bitwarden organisation on their start date, in the group of their company and department. If they move to another department or company, the groups move along, and after the end date the integration revokes the member, so the licence seat is freed.
What the integration does
Organisations that run payroll for one or more companies in Nmbrs and keep shared logins in Bitwarden usually add members when someone asks. Anyone moving to another company within the group keeps the collections of their old company, and leavers stay members until IT cleans up a list.
- Together we decide which companies and departments get a Bitwarden group, and whether functions get an extra group.
- Someone with access to the employers in Nmbrs gives the integration consent once, for reading only.
- On the start date KoppelHet invites the employee at their work address, in the group of their company and department. An administrator confirms the member after acceptance.
- Another department, function or company switches the groups on the effective date; the member and their own vault remain.
- After the end date KoppelHet revokes the member, and after the period you choose it removes the member from the organisation.
What to watch for with Nmbrs and Bitwarden
- Departments in Nmbrs are a list per company, and a Finance department often occurs at several companies. KoppelHet creates a separate Bitwarden group per company and department, so one company's banking logins do not become visible to another company's finance department.
- An employee number in Nmbrs is only unique within a company. Bitwarden looks up members and groups by an external ID; KoppelHet puts the company code in front of the number, so two employees with the same number at different companies never become the same member.
- A move to another company appears in Nmbrs as a leave at one company and a hire at the other. KoppelHet recognises the same person and moves the existing member to the new company's groups, instead of revoking it and sending a second invitation.
- A function or department applies per payroll period in Nmbrs. KoppelHet switches the Bitwarden groups on the first day of that period, not when payroll enters the change, which is sometimes weeks earlier or later.
- When a former employee returns under the same employee number and the member is still revoked in Bitwarden, KoppelHet restores it on the new start date. Bitwarden then needs no new invitation or confirmation, and revoked members have cost no licence seat in the meantime.
- KoppelHet only requests read rights from Nmbrs for personal data, employment, organisational structure and company data, and no rights for pay or bank accounts. If payroll runs through an accounting firm, the firm gives the integration access to your companies only.
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 Bitwarden not use Entra ID and SCIM?
Yes, if Entra ID is already filled from Nmbrs and the groups per company and department are right. This integration fits when Nmbrs is the only place that knows the right company and department.
What if the work email is not in Nmbrs yet?
Then KoppelHet waits with the invitation and alerts HR after the start date. We do not send an invitation to a personal address.
Can KoppelHet see the content of the vault?
No. Bitwarden's Public API manages members, groups and collections, not vault items.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 (identityservice.nmbrs.com, authorisation code flow with consent from an Nmbrs user and refresh token) with read-only scopes: employee.info.read, employee.employment.read, employee.orgstructure.read and company.info.read; read per company. The SOAP API stops on 1 March 2027.
- Bitwarden is written through the Bitwarden Public API (api.bitwarden.com or api.bitwarden.eu) with the organisation API key (client_id organization.ClientId, grant_type client_credentials, scope api.organization; token 3600 seconds). Members and groups with externalId, revoke and restore through the member endpoints, lists with continuationToken. Available to Teams and Enterprise organisations.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Bitwarden | Notes |
|---|---|---|
Bedrijfscode en personeelsnummer | externalId van het lid | Number is only unique per company |
Werk-e-mailadres | email | Not the personal address |
Bedrijf en afdeling | Groep: externalId en name | |
Functie | Extra groep via een tabel die HR beheert | |
Datum in dienst | Moment van uitnodigen of herstellen | |
Datum uit dienst | Lid intrekken, na een termijn verwijderen |
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