Does HiBob connect to Power BI?

HiBob has no built-in Power BI connector. We use the Bob API with a read-only service user, load the data into Azure on a schedule and build the reports on top, so refreshes never depend on someone exporting a report.

What access do you need in Bob?

Your Bob admin creates a service user and gives it view access to the categories the reports use, including history where needed. It cannot change anything in Bob, and you can remove it at any time.

Can we see headcount and turnover for past months?

Yes. We keep Bob’s history tables, so you can see headcount, starters, leavers and turnover for any month, by department, site or employment type.

Can we add payroll and finance data?

Yes, and that is usually where the most useful reports come from. Joining Bob to payroll and your accounts system gives cost per head, salary cost against budget and the cost of vacancies.

Can managers see only their own teams?

Yes. Row-level security in Power BI means each manager sees their own people and nobody else’s, while HR and the leadership team see everything.

Is our people data kept safe?

Everything stays in your own Microsoft tenant. Sensitive fields such as salary can be left out entirely or limited to the people who should see them.

Which Power BI licence do we need?

People who view shared reports usually need a Power BI Pro licence, which is included in some Microsoft 365 plans. If many managers need access, a capacity licence can work out cheaper. We will tell you the most economical option.

As a fixed-price project agreed before work starts. A short reporting review comes first, so you know what is worth building and what it will cost.

HiBob reporting in Power BI

Bob runs your people. Reporting is where it gets harder.

Bob’s reports and dashboards answer the questions about today well. As the business grows, the questions are about trends, cost and the rest of the business.

Headcount over time

Bob shows who works here today. Seeing how headcount moved month by month means running history reports and stitching them together.

Turnover in a spreadsheet

Leavers are exported, joined to headcount in Excel and the turnover maths done by hand, every month and for every board pack.

Reports in different places

Some figures sit in analytics, some in dashboards, some in time off. Reports can be slow to load and fiddly to change.

HR on its own

Cost per head, overtime and hiring spend need payroll, finance and recruitment figures that Bob does not hold.

Absence patterns

Days off are recorded, but spotting repeat short absences or comparing teams means more exporting and more formulas.

Connecting Bob is fiddly

Teams that try the API on their own run into service user permissions, separate history tables and custom fields that arrive as codes.

What the reports cover

Five report pages, set up around your departments, sites and custom fields. Try the first four on sample data below, then see them on your own.

Workforce

Headcount, starters and leavers over time by department, location and employment type, with tenure and gender split.

Retention

Turnover and retention by team, reasons for leaving and how long leavers stayed, so you see where people are not staying.

Hiring

Time to hire and time to fill, open roles, where hires come from and which teams take longest to fill.

Leave and absence

Days taken by month and team, allowance used, people with days left to take, and repeat short absences.

Cost per head

Bob joined to payroll and the finance ledger, so headcount, salary cost and budget sit in one view.

See them on your own HiBob data

Book a reporting review

Try the report

A working HiBob report on sample data for a 426-person company in two countries. Change the year or location, or click any bar to filter the rest of the page.

Home page of the HiBob sample report, with workforce, retention, hiring and leave

Open the live report

From Bob to the report

01
Connect

A read-only service user in Bob, set up by your Bob admin with exactly the fields the reports need. Nothing in Bob can be changed.
02
Store

People, work history, time off and hiring data land in a database in your own Microsoft tenant, with history kept so every month can be compared.
03
Report

Power BI reports in Teams or the browser, refreshed automatically, with row-level security so managers see their own teams only.

History, not just today

We load Bob’s work, salary and lifecycle history tables, so headcount and turnover are correct for any past month, including changes with a back-dated effective date.

Custom fields with real names

Your custom fields and lists are mapped once to their proper names, so reports read “Cost centre: Operations” instead of a long number.

HR reporting we have delivered

People data is only useful when HR trusts the numbers. Every report we build is checked against the source system before anyone relies on it.

Charities & care

HR analytics pipelines for a national charity

Fortnightly manual extracts from the HR and payroll systems became automatic daily updates into one organised set of figures, with each manager seeing only their own teams.

Read the case study

Questions about HiBob reporting

Does HiBob connect to Power BI?: HiBob has no built-in Power BI connector. We use the Bob API with a read-only service user, load the data into Azure on a schedule and build the reports on top, so refreshes never depend on someone exporting a report.
What access do you need in Bob?: Your Bob admin creates a service user and gives it view access to the categories the reports use, including history where needed. It cannot change anything in Bob, and you can remove it at any time.
Can we see headcount and turnover for past months?: Yes. We keep Bob’s history tables, so you can see headcount, starters, leavers and turnover for any month, by department, site or employment type.
Can we add payroll and finance data?: Yes, and that is usually where the most useful reports come from. Joining Bob to payroll and your accounts system gives cost per head, salary cost against budget and the cost of vacancies.
Can managers see only their own teams?: Yes. Row-level security in Power BI means each manager sees their own people and nobody else’s, while HR and the leadership team see everything.
Is our people data kept safe?: Everything stays in your own Microsoft tenant. Sensitive fields such as salary can be left out entirely or limited to the people who should see them.
Which Power BI licence do we need?: People who view shared reports usually need a Power BI Pro licence, which is included in some Microsoft 365 plans. If many managers need access, a capacity licence can work out cheaper. We will tell you the most economical option.
How is it priced?: As a fixed-price project agreed before work starts. A short reporting review comes first, so you know what is worth building and what it will cost.

We are a global company