Accounting & HR
Set up HiBob
Connect Bob to make the employee directory searchable — who works here, in what role, which department and site, who they report to — plus a rolling who's-out note. Read-only.
Before you start
- The credential is a service user ID and token, created together as a pair in Bob under Settings → Integrations → Automation → Service Users → New service user. Bob shows both once — copy them immediately.
- Put the service user in a permission group that may VIEW the people fields and time-off. What that group can see is exactly what syncs — nothing more.
- The service user can only read. There is no write scope to grant, and none is used.
- Bob → Settings → Integrations → Automation → Service Users → create the service user, in a permission group that can view people fields and time-off.
- Documents → HiBob: paste the Service user ID and the Service user token.
- Choose access groups, Test, then Sync.
What comes in
- Each employee becomes one situated record: name, title, department, site, work email, start date and who they report to.
- A rolling "Who's out" note lists everyone away in the next 90 days. Leave under a plainly generic name — holiday, vacation, PTO, annual leave, time off — is named; anything else, such as medical or parental leave, shows only as "away", never the policy name.
Access
Bob exposes no per-person sharing to mirror, so only the access groups chosen on this source decide who can ask about a given employee — allow-only, same as everywhere else. People records are personal data: choose narrowly.
Test runs a one-record probe, not the full directory, so it confirms the credential fast. The who's-out calendar needs its own read permission on the service user — if that permission is missing, employee records still sync and a note in the sync summary says the who's-out list was skipped, nothing fails silently. A directory beyond 5,000 people is capped; the people already in stay put rather than reading as removed.
Last updated 20 Sep 2026