Skip to main content

Make HiBob documentation available as an AI-ready knowledge source

  • Oct 15, 2026 6:38 AM UTC
  • 10 replies
  • 225 views
  • Translate All

Hi AI Innovators,

One idea I would love HiBob to explore is making its product documentation available as an AI-ready knowledge source for customers' own enterprise AI platforms, such as Microsoft 365 Copilot.

The use case is not primarily about asking simple questions such as “How do I configure X in Bob?” The bigger opportunity is using Copilot as a design partner for HR processes, while giving it sufficient HiBob product knowledge to understand what is actually possible.

For example, imagine that I want to redesign our Performance Review process.

I could work with Copilot on our requirements, process design, review cycle, forms, workflows, communications and internal documentation. However, for Copilot to provide really useful recommendations, it also needs to understand the possibilities, terminology and constraints of HiBob.

Ideally, I could tell Copilot:

“Help me design our new Performance Review process based on these business requirements, but make sure the proposed solution can actually be implemented in HiBob.”

Copilot could then combine:

  • our internal company context and requirements
  • our policies and existing Microsoft 365 content
  • HiBob product knowledge
  • the specific process we are designing

It could help us design the process, identify requirements that may not fit HiBob's capabilities, suggest alternative approaches, and help create implementation and user documentation.

I think this requires two things from HiBob

1. Make the documentation easily available to customers

Today, we can access HiBob's documentation through the Help Center and other resources. But for this use case, I would like a simple way to obtain the complete documentation, for example through a “Download all documentation” option or a regularly updated PDF/document package.

The important part is that I can bring this knowledge into my own Microsoft 365 Copilot environment and use it as a knowledge source for my agents and chats. Today, the process is Print page + Save to PDF for every bit of heartcorehr.hibob.com-knowledge I want my agent to read, and thats an exhausting process.

2. Make the documentation AI-ready

Simply combining the existing Help Center pages into one large PDF would only solve part of the problem.

The knowledge available to us today comes in different forms: written user guides, screenshots, videos, known limitations and practical details discussed in forum posts, and information about upcoming functionality in release documentation.

For a human user, it is possible to navigate between these different sources and build an understanding of how something works. For an AI agent, however, the quality and structure of the underlying knowledge becomes extremely important.

I would therefore love HiBob to use AI, human expertise, or a combination of both to create documentation specifically structured for consumption by AI agents.

For example, the AI-ready documentation could bring together:

  • what a feature does
  • how it is configured
  • important terminology and concepts
  • prerequisites and dependencies
  • known constraints and limitations
  • relevant information currently communicated through screenshots or videos
  • useful knowledge currently found in community/forum discussions
  • relevant changes or upcoming functionality from release documentation

The goal would be a structured and comprehensive representation of HiBob product knowledge that an AI agent can understand and reason from, rather than simply a collection of Help Center articles.

Why does this need to live in our own AI environment?

Because much of the value comes from combining HiBob knowledge with sensitive internal company information.

I may want Copilot to consider our organizational structure, internal processes, policies, existing documentation and other confidential information when helping us design an HR process.

For that reason, a chatbot on top of the public HiBob Help Center would not solve the same problem. I want the HiBob knowledge to come to my enterprise AI environment, rather than having to send our sensitive business context to an external chatbot.

The ideal combination would be:

Our company data and requirements + our Microsoft 365 Copilot + AI-ready HiBob product knowledge

This could move us from simply searching HiBob documentation to using HiBob product knowledge while actually designing, implementing and documenting better HR processes.

Performance Reviews are just one example. I could see the same concept being valuable when designing onboarding, compensation processes, workflows, employee lifecycle processes and many other areas of HiBob.

For customers already experimenting with Copilot and AI agents, I think having access to official, comprehensive and AI-ready HiBob product knowledge could be incredibly valuable.

Best regards, 
Øyvind

10 replies

Petr Hnida

100% Yvind.

Great post, fully agree with the principle: AI is only useful when it combines HiBob knowledge with our own company context.

I’d add the mirror view, from the employee side:

Source of truth: Bob, holding both our HR data and our internal HR guides and policies (Bob Docs).
Front doors:

  • Inside Bob → Bob’s AI assistant
  • In Teams / Copilot → via Bob MCP
    Your piece: HiBob product knowledge → AI-ready → our Copilot

One source of truth, any AI front door, the same answer.

The knowledge stays in Bob, where it already lives; only the place people ask from changes. Whether an employee asks in Bob or in Teams, they should get the same company-specific answer, not a generic Help Center one.

Does anyone else see this two-way need? And where do you keep your internal HR guides: in Bob or elsewhere?

Many thanks

Petr

 

Translate

Hi ​@Øyvind Loftheim - LOVE this post and discussion points!

I’m very interested to learn what we may have planned for this - and I will reach out to our Product Teams to find out! ​@Josh Rod  👀

My two-pence worth…

As ​​​​@Petr Hnida rightly pointed out, you can leverage Bob’s MCP to connect your Bob platform/data to your external AI tools (eg Claude, ChatGPT)

And all clients will soon be able to use Bob Companion (in system AI agent) to surface information via sources such as the Help Centre and Heartcore, and importantly with the added context of who your company is, who’s asking the question, and only surfacing information and data as controlled by the access and permissions that you have set-up in Bob

BUT - it would be interesting to see if there’s plans to combine both the above functionality!

Standby ​@Øyvind Loftheim !

Translate

Josh Rod
Bobber
  • Bobber
  • Oct 15, 2026 2:11 PM UTC

Thanks ​@Øyvind Loftheim , really useful feedback.
We’re already using HiBob product knowledge internally to help our teams access and navigate product information, and customers can also access product knowledge through Bob Companion.
I really like the idea of making this knowledge available through MCP as well, so customers could bring the same HiBob product context into the AI tools they’re already using.
We’ll take this back to the relevant Product teams and do some discovery around what that could look like. Thanks for raising it!

Translate

Thanks, ​@Petr Hnida , ​@Samantha Bond and ​@Josh Rod !

Really appreciate the input and ideas here.

For us, though, Bob Companion does not quite solve the use case I had in mind.

A huge amount of the context I need when designing HR processes already lives in Microsoft 365, and realistically it will never all live in Bob.

For example, imagine I am designing a new performance review process. Maybe our CEO had experience with a particular model in a previous company and wants us to build on that. At the same time, I may have input from HR and Country Managers across our different locations about what will or will not work locally, cultural considerations, previous discussions and decisions, existing company policies, etc.

That context could be spread across emails, Teams conversations, meeting transcripts, SharePoint documents and other M365 content.

What I would love to do is bring all of that context together in Copilot and say something like:

"Help me design a performance review process based on this company context, but also make sure we design it in a way that takes full advantage of the functionality available in Bob Talent."

That last part is where the gap is for me.

Copilot can know an enormous amount about our company, but it does not know enough about how Bob works.

Another example would be our annual salary process in Bob Compensation. The process needs to work across different countries, budgets, inflation levels, unions and local legal requirements. There may be different agreements or considerations depending on the country or even the union involved.

Much of the information I need to design that process is already available to Copilot through our Microsoft 365 environment. But Copilot does not know enough about Bob Compensation to help me translate all of that company-specific context into the best possible process and configuration in Bob.

And maybe even more importantly: Briding the gap between performance reviews and compensation events in my company’s context.

Again, that is the gap I would love to close: Copilot understands our organization and our requirements, while HiBob's documentation explains what is possible in Bob and how to make it work.

Today I can bridge that gap manually. I have actually given Copilot screenshots from Bob Help Center pages, and that already takes us surprisingly far! But taking screenshots, saving pages as PDFs and manually keeping that knowledge available to Copilot is exactly the kind of manual work that becomes slightly painful when you are enthusiastic about AI. 😉

There is another very practical use case for us: end-user and HR documentation.

We spend a lot of time creating our own “How to” guides for Bob. The flexibility of Bob is one of its greatest strengths, but it also means generic training material does not always look like our Bob.

For example, we do not use Time Off in Bob, we have made choices around displaying birthdays and work anniversaries on the home page for privacy/GDPR reasons, and we have configured Bob around our own processes. So an employee watching a generic product video may see functionality, buttons or processes that they simply do not recognize from our environment.

Being able to give Copilot Bob's product documentation together with our own configuration/process context would make it incredibly useful for creating customized step-by-step guides.

This becomes even more valuable for us because we operate globally. Instead of screen-sharing with HR colleagues in very different time zones and walking through functionality manually, we could create high-quality step-by-step guides tailored to how we use Bob.

And importantly, I don't think customers should necessarily need to have a Bob MCP connection established to benefit from this.

MCP is incredibly exciting, but I also think it is still quite a “next level” step for many organizations. And it is not only a technical question. When HR data is involved, you are potentially talking about some of the most sensitive personal data in the company. That naturally brings questions around privacy, GDPR, security, permissions and data flows.

The technical teams may be completely comfortable with how this is secured, but getting the same level of comfort across HR, Legal, IT and senior leadership can be a different journey. So if accessing Bob product documentation requires establishing the full MCP connection first, I think we may be raising the bar unnecessarily.

Product documentation is different. There is no need to expose our employee data just to let Copilot understand how Bob works.

Simply making HiBob's product documentation available as an AI-ready knowledge source would already be hugely valuable. It would allow customers to combine Bob product knowledge with all the company-specific context their AI already has access to, without having to manually copy, screenshot or save Bob documentation.

For us, that would make a real difference both when designing HR processes and when creating end-user documentation and training.

So yes, I am very happy to hear this is something you will take back to the Product teams. Thanks again for engaging with the idea!

Translate

As always, thanks so much for the added insights as to what’s important and needed for Corvus Energy, and I am very sure you are also talking on behalf of many other customers needs too ​@Øyvind Loftheim !

​@Josh Rod - it would seem instead of my initial thinking of MCP + “MosaicAI” (our internal AI that brings together all our HiBob resources), actually, it would seem that it’s “just” the Mosaic AI tool that ​@Øyvind Loftheim would value - with the ability to connect this to their existing AI tools like Copilot 🤔💡

Translate

Petr Hnida

This would help Packeta Group as well ​@Samantha Bond and back to MCP it be great to have the connector like u guys did for Claude, Cursor…. Is this something u guys are considering or planning? 

Translate

​@Petr Hnida great to hear this would be useful for Packeta Group too

Can I just check what you mean about having the MCP connector, and what specifically you’re asking if we are considering/planning? Which external AI tool are you wanting to use the MCP for that’s not currently available so I can ensure you get the relevant update?

 

Translate

Petr Hnida

Thanks ​@Samantha Bond, Bob MCP can be now connected to Claude, Cursos, Chat GPT.  » Use Bob MCP Connector – Bob Help Center

I would appreciate if it can be connected to Microsoft Copilot as well. 

 

Translate

​@Petr Hnida thanks for confirming!

I understand we are currently in the planning stage to connect MCP with Copilot as well as Gemini, although no confirmed timelines are available to share on this just yet

Translate

As always, thanks so much for the added insights as to what’s important and needed for Corvus Energy, and I am very sure you are also talking on behalf of many other customers needs too ​@Øyvind Loftheim !

​@Josh Rod - it would seem instead of my initial thinking of MCP + “MosaicAI” (our internal AI that brings together all our HiBob resources), actually, it would seem that it’s “just” the Mosaic AI tool that ​@Øyvind Loftheim would value - with the ability to connect this to their existing AI tools like Copilot 🤔💡

Yes! MosaicAI sounds like exactly what I’m after!

We would of course set up the MCP with Microsoft Copilot the second it becomes available as well, but that would be a different use case. 

Thank you so much as always, Samantha!

Translate