OIIdentity and access management
BambooHR to One Identity integration: employees from BambooHR in One Identity Manager
With an integration between BambooHR and One Identity Manager, employees, departments and managers from BambooHR are ready every day in fixed files that One Identity Manager's CSV connector reads. One Identity Manager uses them to create accounts and permissions, and sees a departure on the termination date HR recorded in BambooHR.
What the integration does
Organisations that use One Identity Manager and have BambooHR as their HR system often load employees with a report someone exports from BambooHR. A job change HR enters in advance then shows up in One Identity Manager too early or too late, and a departure only arrives with the next export.
- BambooHR gets a separate user for the integration with its own API key, without access to pay and personal data.
- KoppelHet creates two files with a fixed layout, employees and departments, in the place the synchronisation server reads.
- The One Identity Manager administrator sets up the CSV connector with both files in one system connection.
- After each notification from BambooHR KoppelHet updates that employee's row, so the next synchronisation picks up the change.
- A leaver stays in the file with the termination date, until after the retention period.
What to watch for with BambooHR and One Identity
- One Identity's Starling Connect documentation, up to the release notes of February 2026, lists no connector for BambooHR. One Identity Manager therefore cannot read BambooHR itself. The CSV connector, which ships with One Identity Manager, is the route; KoppelHet delivers BambooHR in a fixed layout.
- BambooHR stores job, department and location in the jobInfo table, with an effective date per row. HR often enters a transfer weeks in advance. KoppelHet only puts the row that applies today in the file, so One Identity Manager only grants the new rights on the effective date.
- The termination date is in BambooHR's employment status history and can also be entered in advance. KoppelHet puts that date as ExitDate in the row as soon as HR enters it, so One Identity Manager processes the departure on that day and IT can see in advance who is leaving.
- When a former employee returns, BambooHR has the original hire date besides the new one. KoppelHet keeps the existing ID as the key and fills the first hire date, so One Identity Manager reactivates the existing person instead of creating a second one.
- Division and department are separate text fields in BambooHR. The CSV connector can read one column as a path in a hierarchy and loads parent units first. KoppelHet combines division and department into such a path, so the same department name in two divisions stays two departments.
- In a synchronisation from another system's file, One Identity Manager cannot mark missing persons as outstanding. KoppelHet therefore keeps a leaver in the file, with the termination date filled in, instead of removing them.
- A custom field in BambooHR, such as a cost centre or contract type, becomes an extra column in the file. The columns are fixed in the synchronisation project. KoppelHet only adds a new field after the administrator has adjusted the mapping in One Identity Manager, so the synchronisation does not break.
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
Can the work email go back to BambooHR?
Yes, but not through the files. That can follow later as an extension, with write access to the work email in BambooHR.
Does salary data go to One Identity Manager?
No. The user behind the API key sees no pay, and the file only contains the fields from the design.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads BambooHR through event-based webhooks (employee.created, employee.updated with monitor fields, signed with HMAC SHA-256), the changed-employees endpoint and the jobInfo and employmentStatus tables; fields such as originalHireDate, terminationDate and supervisorEId. The API key belongs to a user and carries that user's rights.
- One Identity Manager reads two files in one system connection through the CSV connector (UTF-8, header row, text delimiters), with a key column in the employee file and a department column with Hierarchical sort order. The synchronisation step has Data import on, 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 BambooHR | Field in One Identity | Notes |
|---|---|---|
id | Sleutelkolom PersonnelNumber | |
firstName of preferredName | FirstName | |
lastName | LastName | |
jobInfo (jobTitle) | Kolom functie | |
jobInfo (division en department) | Afdelingspad (hiërarchische sortering) | |
jobInfo (location) | Kolom locatie | |
supervisorEId | Kolom leidinggevende | |
hireDate | EntryDate | |
terminationDate | ExitDate | |
originalHireDate | Kolom eerste datum in dienst |
Related
Ashby → BambooHR
Ashby to BambooHR integration: hire, changed start date and employment status in BambooHR
BambooHR → 4PS Construct
BambooHR to 4PS Construct integration: employees from BambooHR in the 4PS company of their location
BambooHR → Active Directory
BambooHR to Active Directory integration: accounts in your own domain from HR
BambooHR → ADP iHCM
BambooHR to ADP iHCM integration: salary, bonuses and commissions to Dutch payroll