Nmbrs logoGoogle Workspace logo

Identity and access management

Nmbrs to Google Workspace integration: Google accounts per company from payroll

With an integration between Nmbrs and Google Workspace, a new employee in Nmbrs gets a Google account with their company's domain and organisational unit, with job title and department. After the end date the account is suspended, and the licence is released once mail and files have been handed over.

What the integration does

Organisations with several BVs in Nmbrs, each with its own email domain in Google Workspace, often create accounts by hand. With many joiners and leavers and employees who change location that falls behind, and suspended accounts of leavers keep costing licences for months.

  1. Someone with the right Nmbrs login grants the integration read access to the companies once.
  2. Payroll enters a new employee in Nmbrs. KoppelHet creates the Google account in the company's organisational unit, with that company's domain.
  3. Job and department decide the groups, such as the location's group and a group per job.
  4. After the end date KoppelHet suspends the account and transfers the files to the manager.
  5. After the agreed period KoppelHet deletes the account, so the licence is released.
Nmbrs → KoppelHet → Google WorkspaceSOURCENmbrsTARGETGoogle WorkspaceKoppelHetmapping · logging · monitoringNmbrs → KoppelHet → Google WorkspaceSOURCENmbrsTARGETGoogle WorkspaceKoppelHetmapping · logging · monitoring
Out: Google account with work address · Domain and organisational unit per Nmbrs company · Job title and department · Groups per job · Licence

What to watch for with Nmbrs and Google Workspace

  • One Nmbrs environment often holds several BVs, and in Google each BV often has its own domain. The company in Nmbrs therefore decides the domain and organisational unit of the new account, so policy and apps can differ per BV.
  • Google charges a suspended account the same as an active account. KoppelHet suspends right after the end date, but deletes the account after a fixed period and after the file transfer, so leavers do not cost licences for months.
  • Employee numbers are unique per company in Nmbrs. KoppelHet stores the number in Google with a company code in front, so two employees with the same number at different BVs never end up on one account.
  • A job change in Nmbrs applies per payroll period. The groups in Google therefore change on the first day of that period, not on the day payroll enters the change.
  • When a former employee returns, they get a new employment in Nmbrs under the same employee number. If the Google account is still suspended, KoppelHet re-enables it; if it has already been deleted, a new account is created with the same address.
  • If KoppelHet writes the Google address back to Nmbrs, notifications from Nmbrs can go to that address. After departure that account is suspended, so we agree that HR records a personal address for leavers for the final payslip and the annual statement.
  • The integration uses Nmbrs' new interface, which requires its own login at employer level. If payroll runs through an accounting firm, the firm gives the integration access to your companies only.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

We use Nmbrs through our accounting firm. Is that possible?

Yes. The firm creates an employer-level login for the integration; a general firm login does not work for this.

How long does a suspended account remain?

As long as you agree, for example thirty days. During that time the manager can still reach mail and files.

What about the GDPR?

You are the controller and KoppelHet is the processor, under a data processing agreement. The integration reads no salary, BSN or bank details from Nmbrs.

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 and read-only scopes for employee and employment data and the company structure, per company; webhooks on changes. The SOAP API stops on 1 March 2027.
  • Google is written through the Admin SDK Directory API (externalIds, name, primaryEmail, orgUnitPath, organizations, relations, suspended; delete after the period), groups and members, and the Data Transfer API for Drive. Access through a service account with domain-wide delegation.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in NmbrsField in Google WorkspaceNotes
Bedrijf en personeelsnummerexternalIds (type organization)With company code, because numbers are unique per company
Roepnaamname.givenName
Achternaam volgens naamstellingname.familyName
Naamgevingsregel met domein per bedrijfprimaryEmailCan go back to the business email in Nmbrs
BedrijforgUnitPath
Functieorganizations.title en groepen
Afdelingorganizations.department
Leidinggevenderelations (type manager)
Datum uit dienstsuspended = true, later verwijderen

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.