Identity and access management
ADP GlobalView to Google Workspace integration: Google accounts per country from payroll
With an integration between ADP GlobalView and Google Workspace, a new employee from GlobalView automatically gets a Google account in the organisational unit of their country, with job title, department, personnel area and manager. After the termination date in GlobalView, KoppelHet suspends the account, for every country GlobalView processes for you.
What the integration does
Organisations that run payroll in several countries through ADP GlobalView and use Google Workspace as their workplace often create Google accounts by hand per country. Departures then reach IT by email or not at all, and accounts of former employees in smaller countries remain active.
- Together with ADP you set up the communication user in GlobalView and the registration of the integration.
- KoppelHet fetches the workers per country and compares them with the previous run.
- A new worker gets a Google account in the organisational unit of their country, with an address according to your naming rule.
- Job title, department, personnel area and manager are updated on every run.
- After the termination date KoppelHet sets the account to suspended; deleting or archiving remains a step for IT.
What to watch for with ADP GlobalView and Google Workspace
- GlobalView only returns a list of workers per country, with the country code in a separate header. KoppelHet therefore goes through every country GlobalView handles for you, and uses that same country code to place the Google account in the right organisational unit.
- GlobalView has two surname fields, among others for countries where people carry two surnames. Google has one surname of at most sixty characters. KoppelHet joins them and shortens where needed, so a Spanish or Mexican colleague appears in the directory with their full name.
- In Google the manager points to an email address, in GlobalView to the manager's ADP ID. That manager may work in another country. KoppelHet therefore processes all countries first and only then sets the relations, so a manager in another country is still found.
- The business address is a separate communication record in GlobalView, which is usually empty for a new worker. KoppelHet creates the Google address according to your rule and writes nothing back, because GlobalView's Worker API only reads.
- GlobalView can hold a company mobile number. Google requires a recovery number with country code and plus sign. KoppelHet converts the number and leaves it out when that fails, so a wrong number does not block the account.
- A move to another legal entity or a rehire gets a new personnel number in GlobalView, and the old assignment then disappears from the API. KoppelHet stores the ADP ID in the external IDs of the Google account and keeps its own record of which account belongs to whom, so a move does not create a second account.
- Besides the full Worker API, GlobalView has a variant without sensitive data. KoppelHet uses it where possible, so date of birth, address and pay do not reach KoppelHet or Google.
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
We also have a global HR system. Is GlobalView the right source then?
Usually not. If everyone is in an HR system such as Workday or HiBob, that is the source. This integration fits when GlobalView is the only complete record per country.
Are leavers' accounts deleted?
No, suspended. Transferring data, archiving or deleting is done by IT. A fixed period for that can be added later as an extension.
Can we start with a few countries?
Yes. We start with the countries with the most employees; the rest can follow later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- ADP GlobalView Worker API: GET /hr/v2/worker-demographics (or /hr/v2/workers) with header ADP-Context-ExpressionID country='XX', OData $top (at most 100), $skip, $filter and $count. Fields include associateOID, legalName (givenName, familyName1, familyName2, nickName), businessCommunication (emails 0010, mobiles 0021), workAssignments (jobTitle, homeOrganizationalUnits with ORGEH and WERKS, hireDate, terminationDate, reportsTo). Scope through the Consumer Application Registry; in GlobalView a Communication User (Practitioner).
- Google is written through the Admin SDK Directory API (users with primaryEmail, name.givenName and name.familyName of at most 60 characters, externalIds, organizations with name, title and department, relations with type manager and an email address, recoveryPhone in E.164, orgUnitPath and suspended). 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 ADP GlobalView | Field in Google Workspace | Notes |
|---|---|---|
workers/associateOID | externalIds (type organization) | Fixed key for the account |
legalName/givenName of nickName | name.givenName | |
legalName/familyName1 en familyName2 | name.familyName | Combined, at most 60 characters |
Landcode uit ADP-Context-ExpressionID | orgUnitPath | |
workAssignments/jobTitle | organizations.title | |
homeOrganizationalUnits (ORGEH) | organizations.department | |
homeOrganizationalUnits (WERKS, personeelsgebied) | organizations.name | |
reportsTo/associateOID | relations (manager, e-mailadres) | |
businessCommunication/mobiles (0021) | recoveryPhone | Only in E.164 format |
workAssignments/terminationDate | suspended |
Related
ADP GlobalView → Active Directory
ADP GlobalView to Active Directory integration: domain accounts per country from outsourced payroll
ADP GlobalView → Microsoft Entra ID
ADP GlobalView to Entra ID integration: accounts per country from international payroll
ADP GlobalView → Okta
ADP GlobalView to Okta integration: Okta users from all countries in GlobalView
ADP GlobalView → SailPoint
ADP GlobalView to SailPoint integration: identities from all GlobalView countries in SailPoint