Platform · Knowledge bases

Every answer links to its page.

Nobody can defend an agent that cannot show its source. Knowledge bases exist so every answer arrives with the passage it came from attached.

Point Liba at your documents and the whole retrieval pipeline is handled in one step: parsing, chunking, embedding, hybrid search, and citations carried through to the output. There is no separate vector database to run, tune and explain to your security team.

Permissions come first

Retrieval respects the document permissions each user already holds. If a reader cannot open a file in SharePoint, no agent will surface its contents to them.

This is the failure that ends pilots. An assistant that quietly flattens years of carefully maintained access control is an incident rather than a productivity gain, and it tends to surface in front of exactly the wrong person.

Grounded in your material

A grounded agent answers from your material or says that it cannot. For a resident contact centre, that is the difference between quoting a published bylaw and inventing one.

When it cannot answer, it hands off to a human rather than improvising.

What goes in

Whatever the process actually runs on: bylaws, procedures, service pages, contracts, credit policies, audit programmes, past tender awards, archives. If your people read it to do the job, the agent can stand on it.