OIIdentity and access management
Remote to One Identity integration: employments from Remote in One Identity Manager, with the work email back to Remote
With an integration between Remote and One Identity Manager, everyone who works for you through Remote is in a fixed file every day, with employment type, country, department, manager and the confirmed end date, which One Identity Manager's CSV connector reads. KoppelHet writes the work email One Identity Manager issues back to Remote where Remote allows it.
What the integration does
Organisations with One Identity Manager and people in several countries through Remote often keep those people out of One Identity Manager's HR source. Accounts for EOR employees are then made by hand, and the work email IT issues is not in Remote, so Remote still mails the private address.
- Remote gets a Customer API token with read scopes and write rights on employments only for the work email.
- KoppelHet places a UTF-8 file with fixed columns where the synchronisation server reads.
- The One Identity Manager administrator sets up the CSV connector with the employment ID as key.
- After the synchronisation KoppelHet reads the new work email back and puts it in Remote for employees with an invited or active employment.
- A leaver stays in the file with the confirmed end date, until after the retention period.
What to watch for with Remote and One Identity
- One Identity's Starling Connect release notes up to February 2026 list Workday, SuccessFactors and Oracle Fusion as HR sources, and not Remote. Remote's SCIM endpoint can only be read and filters in the form field eq value. KoppelHet therefore builds the file for the CSV connector from Remote's webhooks and API.
- Through the API Remote can only update the work email for an invited or active employment, and not for contractors. KoppelHet writes the address One Identity Manager issues back for employees, and puts contractors on a list for HR, so Remote uses the right address everywhere.
- One Identity Manager derives a file's character set from the workstation, unless it is fixed in the connection. Names from Remote come from many countries, with characters such as ł, ő or ñ. KoppelHet always delivers UTF-8 and we fix the encoding in the connection, so a Polish or Hungarian name does not end up garbled in One Identity Manager.
- On an offboarding Remote first checks the country's rules, and the end date can still move afterwards. KoppelHet only fills ExitDate once Remote has processed the offboarding, and keeps the row afterwards, because with a file from another system One Identity Manager cannot mark a vanished row as outstanding.
- Remote leaves confidential offboardings out of the normal list. KoppelHet requests them separately and only puts the end date in the file, without a reason or marker, so One Identity Manager administrators cannot tell from the file that a departure is confidential.
- An employment in Remote stays a long time at steps such as invited, onboarding and review before becoming active. KoppelHet includes an employment from invited onwards, with the Remote status in its own column, so One Identity Manager can prepare an account and only release it at active.
- If Remote sets the user to inactive because the employment is suspended, Remote sends its own webhook. KoppelHet puts that in the status column without filling ExitDate, so One Identity Manager can pause access without treating someone as having left.
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
Why does the work email not go back for contractors?
Remote does not allow it through the API. HR fills in the address for contractors themselves, KoppelHet supplies the list.
Does pay data end up in the file?
No. Only the columns from the design, without salary or allowances.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Remote through the Remote API (gateway.remote.com) with a Customer API token: GET /v1/employments (status invited to active, archived; type; country; engaged_by_legal_entity_id), SCIM GET /v1/scim/v2/Users (read only, filter 'attribute eq value') for department and manager, webhooks with X-Remote-Signature and include_confidential. Write-back with PATCH /v1/employments/{employment_id} (work_email for invited and active, not for contractors).
- One Identity Manager reads one file through the CSV connector with fixed encoding UTF-8, language for dates, header row, delimiter and text qualifier, and PersonnelNumber as key column. Synchronisation step with Data import, without MarkAsOutstanding; access directly or through a remote connection server.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Remote | Field in One Identity | Notes |
|---|---|---|
employment id | Sleutelkolom PersonnelNumber | |
Voornaam en achternaam | FirstName en LastName | |
type | Kolom soort dienstverband | |
country en engaged_by_legal_entity_id | Kolommen land en bedrijf | |
department (SCIM) | Kolom afdeling | |
manager (SCIM) | Kolom leidinggevende | |
Startdatum | EntryDate | |
Bevestigde einddatum offboarding | ExitDate | |
Centraal werkadres (One Identity Manager) | work_email | Back to Remote |
Related
Greenhouse → Remote
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
Recruitee → Remote
Recruitee to Remote integration: hires abroad straight into an employment at Remote
Remote → 4PS Construct
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries