Identity and access management
Simployer to Google Workspace integration: Google accounts from Simployer One, from onboarding to departure
With an integration between Simployer One and Google Workspace, a new employee gets a Google account with job title, department, manager and the organisational unit of their country. On the departure date in Simployer, KoppelHet suspends the account.
What the integration does
Organisations that use Simployer One as their HR system and Google Workspace as their workplace often create new Google addresses by hand. Job title, department and organisational unit stay empty in Google, and IT suspends leavers by hand.
- HR creates the new employee in Simployer One with work email, country and start date.
- KoppelHet creates the Google account.
- KoppelHet adds job title, department, employee number and manager and puts the account in the unit of the country.
- Changes in Simployer One go through to Google every hour.
- On the departure date KoppelHet suspends the account; after the retention period the files go to the manager.
What to watch for with Simployer and Google Workspace
- KoppelHet also puts job title, department and manager in Google, so the organisation structure in Google and in Gmail address books is right.
- With several countries with their own domains, KoppelHet chooses the domain and the organisational unit from the country of employment in Simployer One.
- KoppelHet suspends the account on the departure date from Simployer One, and only deletes after transferring the Drive files.
- KoppelHet works with a service account with domain-wide delegation, limited to users, groups and file transfer, so no personal super admin account is tied to the integration.
- A Simployer One access token gives owner rights on the whole account. KoppelHet only uses read calls with that token for the fields of the Google account, and advises a dedicated token for this integration that you can revoke separately.
- For a relation of type manager Google expects the manager's email address. Simployer One only gives managerEmployeeId for an employee. KoppelHet looks up the manager's work email for that ID and puts it in 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
Does this also work with Simployer Classic?
This integration reads Simployer One. For Classic we check per customer which data is available.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Read Simployer One through the HRM One API (api.alexishr.com/v1, employee with employeeNumber, workEmail, employmentCountry, endDate and offboardDate; filter on updated) with an access token as bearer. To Google through the Admin SDK Directory API (users with externalIds, orgUnitPath, organizations, relations type manager and suspended) and the Data Transfer API, with a service account with domain-wide delegation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Simployer | Field in Google Workspace | Notes |
|---|---|---|
employeeNumber | externalIds (type organization) | |
Voornaam en achternaam | name.givenName en name.familyName | |
workEmail | primaryEmail | |
Functie | organizations.title | |
Afdeling | organizations.department en groepen | |
employmentCountry | orgUnitPath | |
managerEmployeeId | relations (type manager) | Converted to the manager's work email |
offboardDate of endDate | suspended = true |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → ADP iHCM
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll