HiBob

The HiBob integration makes your people directory available in client work. Ask who a consultant reports to, who is in a department, or who is out the week of a client workshop, and Hebno answers from Bob with each employee record cited. The integration reads only. Hebno never writes to HiBob and never reads salary, bank details, national identifiers or performance data.

​

At a glance

​

Before you start

You need:

• An owner or admin role in Hebno.
• A HiBob admin who can create service users and permission groups.

Set up the service user in Bob:

1. Open Settings → Integrations → Automation → Service users and select Create service user. Name it, for example Hebno, and copy the service user ID and token. The token appears once.
2. Open Settings → Account → Permission groups and create a group for the service user, for example Hebno integration. Add the service user as its only member.
3. Under People’s data, give the group View access to the Basic info and Work categories for all employees. Leave Payroll, Compensation, Bank, Identification and Performance without access.
4. Under Time off, give the group View access to who is out and approved requests for all employees.

HiBob has no scopes. The service user can read only what its permission group allows, so the group is the boundary for what Hebno can read.

​

Connect HiBob

The card shows Connected with the HiBob company name. Access is fixed to Read only. Members do not link their own HiBob accounts: every read goes through the service user and your data areas.

​

Data areas

Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of the service user’s permission group in HiBob. To keep time off visible to resource managers only, open the HiBob card in Admin → Connectors, select Time off and choose the teams that should see it.

​

What Hebno reads

Reads are live. Hebno queries HiBob when a request needs it and does not copy the directory into Hebno. Only what a reply used is stored with the conversation as its sources. Hebno never reads salary, payroll, bank details, identification numbers, performance reviews, time off reasons or employee documents.

​

Hebno reads only

Hebno does not write to HiBob. It does not create or approve time off requests, edit employee records, or change departments, managers or sites. To book a consultant once you know they are free, use a resourcing integration such as Float.

​

Link a project to its team

Linking marks which HiBob employees work on a project, so you can ask “who on the team is away?” without naming everyone.

1. Open the project and select Brain.
2. Under Linked records, select Link record, then HiBob.
3. Search by name or department, and select each employee. You can link a whole department instead.

In chats tagged to the project, Hebno starts with the linked people for any availability or reporting line question. See Linked records.

​

Use HiBob in chat

• Attach: open the + menu, choose Sources → HiBob, and pick an employee, a department or a who’s out period. Or type / and choose HiBob.
• Ask: name the person, team or period in your request. For example:

  Who in the pricing team is out between 16 and 20 November?

  List the Contoso project team with titles, sites and managers for the kickoff deck.

  Who reports to Sarah Chen, and is anyone away next week?

• Research runs show a Checking HiBob step, with a chip for each employee and who’s out period it read.
• Agents can read HiBob on a schedule, for example a Monday list of who is out on each active project this week.

​

Troubleshooting

​

Related

• How integrations work
• Permissions and access
• Linked records
• BambooHR
• Workday