What Oleria discovers
Once connected, Oleria continuously discovers and maps the following from HiBob:- Employees and people - the full worker population, including inactive and terminated employees, with start date, termination date, title, department, and lifecycle status.
- Departments - your Bob department list, including the parent-child department hierarchy. Archived departments are included and labelled as archived, so former employees’ departments still appear.
- Manager relationships - the reporting line for each employee, used to build your organization hierarchy.
- Department assignments - which department each employee currently belongs to.
HiBob is a system of record for the worker, not for application access. Bob doesn’t expose permission groups, MFA or SSO settings, or an audit log through its API. Because of this, Oleria doesn’t model Bob logins as accounts and doesn’t discover groups, roles, or activity from HiBob - those come from your identity provider and SaaS integrations instead.
Prerequisites
- Administrator permission on the Oleria workspace
- A Bob administrator who can create service users and permission groups
- Your Bob environment: your live Bob account (production) or a Bob sandbox
Bob leaves out any field the service user isn’t allowed to view instead of returning an error. Oleria checks that the service user can read employees’ work email and lifecycle status before saving the integration, so a missing permission is caught at setup instead of silently showing leavers as still employed.
Create a service user in HiBob
1
Create the service user
In Bob, go to System settings -> Integrations. From the All categories list, select Automation, then select Manage on the Service users tile. Select + New service user and create a service user, for example “Oleria”. Copy the service user’s ID and Token. Bob shows the token only when it’s generated, so store it securely. If it’s lost, generate a new one and update the integration in Oleria.
2
Grant permissions
Add the service user to a permission group with the following permissions:
The integration is read-only, so the service user doesn’t need any Employee management permissions.
Connect HiBob to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations -> select HiBob.
2
Complete the connection form
3
Authenticate
Select Authenticate to validate and save the integration. Oleria signs in as the service user and checks that it can read employees before saving.
Verify the integration
Confirm the HiBob instance appears on the Connected tab of your Oleria Integrations page. After the first sync completes, review the discovered employees, departments, and manager relationships in your Oleria workspace.Known limitations
- Activity isn’t synced. Bob has no audit-log API.
- Large companies sync more slowly. Bob allows 50 API requests per minute, so Oleria reads employees in batches and paces its requests.
- Departments missing from the department list are created from the department name on the employee record, so every employee’s department still appears.