Connecting BambooHR, HiBob, COINS, or BrightHR
TrainMeUK can add people, keep their details up to date, and disable leavers from BambooHR, HiBob, COINS, or BrightHR. The result is the same kind of automatic directory you get from Microsoft Entra. The way the first import is approved, and who is allowed to disable someone, is different.
Who this applies to
Admins whose employee list lives in BambooHR, HiBob, COINS, or BrightHR. Microsoft 365 organisations that already use Entra provisioning should stay on that, unless the HR system is the list you want TrainMeUK to follow.
Required permissions
- TrainMeUK: Admin for System Settings → SSO & Provisioning
- BambooHR, HiBob, COINS, or BrightHR: an account that can read the employee list and nothing else
How this compares with Entra
Both paths create a learner, update the details the source actually sends, and can disable someone who has left. Training, certificates, and assignment history stay. A job title never becomes an admin or manager role. A person you have disabled yourself is not switched back on.
| Microsoft Entra (SCIM) | HR system | |
|---|---|---|
| Who starts the update | Entra pushes changes to TrainMeUK | TrainMeUK reads the HR system about once an hour |
| First import | Start provisioning in Entra | Preview the list in TrainMeUK, then apply it |
| Someone leaves | Entra disables them, or they leave the assigned group | Only a person the HR file marks as a leaver can be disabled |
| Missing from the file | Removed from the Entra assignment | Left as they are. Absence is not treated as leaving |
| Sign-in | Usually Microsoft sign-in | Microsoft sign-in can stay on. It is separate from who adds people |
| Together | One source adds people | Turn SCIM off before applying an HR import |
Note
The same steps for every HR system
Open the HR system card
Go to Admin → System Settings → SSO & Provisioning. The HR system card is under the Microsoft settings.
Save, test, then preview
- Choose BambooHR, HiBob, COINS, or BrightHR and enter the details for that system.
- Save, then Test. The test reads the list and does not change anyone.
- Preview opens the people who would be added, updated, disabled, or held for a decision. Search that list before you apply it.
Apply, then leave the hourly update running
Apply writes the preview. If the HR file or the connection settings change before you apply, preview again. After a successful apply, TrainMeUK reads the HR system about once an hour. Preview changes stays on the card, and Sync now is on that preview, so a manual sync is checked before it writes. Test connection, recent syncs, and replacing the key are in the menu. For COINS and BrightHR, automatic offboarding is in that menu too. Disconnect stops the hourly update. People and their training stay.
What a new person receives
A read that fails changes nobody
What each system sends
| BambooHR | HiBob | COINS | BrightHR | |
|---|---|---|---|---|
| Name, email, job title | Yes | Yes | When the page includes them | Yes |
| Department, location, manager | Yes | Yes | When the page includes them | No. Those stay editable in TrainMeUK |
| Leaver update | On, from Inactive | On, from Terminated | Off until you turn it on | Off until you turn it on |
| Fields it does not send | Left as they are | Left as they are | Left as they are | Left as they are |
A blank that the HR system deliberately sends can clear that field. A field the system does not send is left alone. Payroll, salary, National Insurance numbers, addresses, and dates of birth are not imported.
BambooHR
- In BambooHR, create an API key for TrainMeUK.
- The company subdomain is the first part of the BambooHR address. For acme.bamboohr.com, enter acme. Do not paste the full address.
- Save the subdomain and API key, test, preview, then apply.
Active employees are employed. Inactive employees are leavers and can be disabled. Give the key access to name, work email, job title, department, location, manager, status, and employee id. If BambooHR hides a field, TrainMeUK leaves the existing value in place.
HiBob
- Create a HiBob service user and copy its id and token.
- In the permission group, set Access data for to include inactive employees. Without that, leavers are not in the file and TrainMeUK will not disable them.
- Save the service user id and token, test, preview, then apply.
Employed, leave, garden leave, and parental leave stay active. Hired but not started is skipped. Terminated is a leaver and can be disabled. Department, site, job title, and manager are updated when HiBob returns a name rather than an internal number.
COINS
- Create a COINS user that can only read personnel for the companies that should sync. Payroll access is not enough.
- Publish a read-only REST page. Send the personnel sequence as personKey. Include a field only when COINS should overwrite it. Leave salary, National Insurance numbers, addresses, and dates of birth off the page.
- Copy the page path from that environment's REST documentation. The page must require a sign-in.
- In TrainMeUK, enter the host name, environment, username, password, and page path. Test then reads the companies in that page. For each status code it finds, choose employed, on leave, has left, or don't import.
You do not type company codes or status codes yourself. A company that disappears from a later read is held for review. Automatic offboarding stays off until you turn it on. Leave stays employed. The leaving date is treated as the last day worked, using the organisation timezone.
Note
BrightHR
- In BrightHR, open API Management and create an application for TrainMeUK.
- Copy the client ID. Create a secret and copy it immediately. BrightHR does not show the secret again.
- Save the client ID and secret in TrainMeUK. There is no BrightHR address to enter.
- Test, preview, then apply.
BrightHR sends name, work email, and job title. Department, location, and manager stay editable in TrainMeUK. Automatic offboarding stays off until you turn it on. A person is treated as a leaver only when BrightHR says they are terminated and any end date is today or earlier. A future end date, or an end date without a terminated flag, is left undecided and nobody is disabled from that row.
Note
If something does not look right
- Apply says Microsoft provisioning is on. Turn SCIM off in TrainMeUK and stop provisioning in Entra, then preview again.
- The preview is out of date. The HR file or the connection settings changed. Preview again before applying.
- A person was not added. They need a work email, and their employment status has to be clear. A leaver who is not already in TrainMeUK is not created.
- A leaver is listed for review instead of disabled. Automatic offboarding is off for that connection. Turn it on only after a preview shows the right leavers, then preview again.
- An import stopped halfway. Use Resume. People already imported stay. Abandon stops the import and lets Microsoft sign-in create anyone who has not been imported yet.
Related guides
- Azure AD SSO and SCIM — Microsoft sign-in, and Entra provisioning when the HR system is not the source
- Managing inactive users — what happens to training when an account is disabled
- Assigning courses — training given to people after they are added