Skip to main content

​
After this article

You will be able to connect HiBob to Lumos to sync users, and set HiBob as a source of user data.

​
Capabilities

​
Required plan and roles

  • HiBob role: you must have Administrator permissions in your company’s HiBob instance, or have an administrator share their access with you.
  • Provider: Lumos connects to HiBob through Merge.dev. See the Merge.dev documentation for provider requirements.

​
Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode this connector offers. The capabilities matrix has no Provision row marked Yes. Lumos only syncs HiBob user records through Merge.dev and does not create, update, or deprovision accounts in HiBob. What read-only requires. The same Administrator permissions in your HiBob instance described above (or delegated access from an administrator), then follow the steps below to connect. Watch out for. There is no provisioning variant of this connector to switch to. If you need to create, deactivate, or remove HiBob accounts, that has to happen in HiBob directly or through another path, since this connection only ever reads user data into Lumos.

​
Instructions

Phase 1: Connect in Lumos
  1. Click the HiBob card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Click Connect HiBob.
  3. Follow the instructions in the pop-up that appears to finish connecting the integration.
Phase 2: Set as a source of user data (optional)
  1. After connecting, set HiBob as a source of user data in Lumos and configure your Source of Truth settings.

​
Troubleshooting

Can’t connect the integration. Make sure you have Administrator permissions in your company’s HiBob instance, or that someone with those permissions has shared their access with you. Some user fields are missing. HiBob synced through Merge can arrive without the Employment Type and Title fields for users. This is a known limitation.