Identity and access management
ADP GlobalView to SailPoint integration: identities from all GlobalView countries in SailPoint
With an integration between ADP GlobalView and SailPoint, every employee from GlobalView becomes an identity in SailPoint, with country, legal entity, personnel area, organisational unit, job title and manager. KoppelHet delivers all countries together as one file to a Delimited File source, with the dates from which SailPoint calculates the lifecycle state.
What the integration does
Organisations that run payroll for several countries through ADP GlobalView and govern access with SailPoint load employees per country with separate exports. A country missing for a day suddenly shows hundreds of people as departed in SailPoint, and a move to another entity produces a second identity.
- GlobalView gets a communication user and the ADP Consumer Application Registry the scope for Worker Demographics; SailPoint gets a Delimited File source with an identity profile.
- KoppelHet reads all employees per country in pages of a hundred and checks whether each country is complete.
- KoppelHet writes one row per employee with the primary assignment and the manager's User Name.
- SailPoint aggregates the file and calculates the lifecycle state with a transform.
- Roles and certifications in SailPoint follow country, entity and organisational unit.
What to watch for with ADP GlobalView and SailPoint
- GlobalView only returns a list for one country per request. A Delimited File source expects all accounts at every aggregation. If one country fails, KoppelHet delivers no new file, so SailPoint does not see that country's employees as departed.
- SailPoint requires a User Name that is unique across all identities. On a move to another entity or a rehire GlobalView issues a new employee number. KoppelHet therefore uses the ADP ID as User Name, so the move does not produce a second identity with an identity exception.
- The organisation in GlobalView consists of SAP units such as personnel area, personnel subarea and organisational unit, as a list with a type code. A SailPoint transform only takes the first value of a list. KoppelHet puts each type in its own column, so roles per site and per department work reliably.
- SailPoint finds the manager through manager correlation on an account in the same source. GlobalView refers to the manager by their ADP ID, even when they work in another country. Because all countries are in one file and the ADP ID is the User Name, SailPoint finds that manager without extra translation.
- GlobalView indicates per assignment whether the contract is permanent or fixed-term, with an expected end date when known. KoppelHet delivers those as columns next to the hire and termination date, so SailPoint can give temporary staff their own lifecycle state and a reminder for the manager.
- The business email address in GlobalView is a separate communication record and is often empty for a new employee, while SailPoint requires a work email for every identity. KoppelHet fills in the address according to the naming rule; writing it back to GlobalView is not possible, because the Worker API is read-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 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
Does pay data go to SailPoint?
No. KoppelHet only uses the Worker Demographics API, without pay, address or date of birth.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- ADP GlobalView through GET /hr/v2/worker-demographics with header ADP-Context-ExpressionID country='XX' (one country per list request), OData $top (at most 100), $skip, $filter and $count; scope …/workerDemographic.read in the Consumer Application Registry; Communication User (Practitioner). Fields include associateOID, legalName, businessCommunication (emails 0010), workAssignments (primaryIndicator, legalEntityID, homeOrganizationalUnits with WERKS, BTRTL and ORGEH, jobCode, jobTitle, assignmentTermCode, expectedTerminationDate, reportsTo, hireDate, terminationDate).
- SailPoint Identity Security Cloud with a Delimited File source as authoritative source. Required identity attributes uid (unique across all profiles), email and lastname; Manager Name with manager correlation; Lifecycle State through a transform on the dates and the contract type.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in ADP GlobalView | Field in SailPoint | Notes |
|---|---|---|
associateOID | uid (User Name) | Not the employee number |
businessCommunication.emails (0010) of naamgevingsregel | email (Work Email) | |
legalName.familyName1 | lastname | |
legalName.givenName of nickName | firstname | |
assignedWorkLocations.address.countryCode | Identity attribute land | |
legalEntityID | Identity attribute entiteit | |
homeOrganizationalUnits (WERKS, BTRTL, ORGEH) | Identity attributes personeelsgebied, -deelgebied en eenheid | |
jobTitle en jobCode | Identity attributes functie | |
reportsTo.associateOID | Manager Name | |
hireDate, terminationDate, assignmentTermCode | Lifecycle State (via transform) |
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 → Google Workspace
ADP GlobalView to Google Workspace integration: Google accounts per country from payroll
ADP GlobalView → Okta
ADP GlobalView to Okta integration: Okta users from all countries in GlobalView