Skip to content

Answers from your own data, within each person's access

AI assistants and enterprise search that only show what each person may see

We build AI chatbots and enterprise search over your own documents and data: answers that cite their source, retrieval that respects each user's permissions, and an evaluation set that shows when answers get worse. On Databricks that means AI Search indexes governed by Unity Catalog, Genie for questions about tables, and apps that query as the signed-in user.

Who it is for
IT and data leaders asked for a company assistant that can't leak
Bench
115+ engineers, averaging 15 years each
6 common questions, answered below ↓

A chatbot that answers from a folder of documents takes an afternoon now. The hard part arrives the first time it answers with a paragraph from a document the person asking was never allowed to open. Permissions have to travel with the data into the index and back out through the app, and that's where most of these projects stall.

What we work out first

  • Which questions people actually ask, taken from the help desk queue, a shared inbox or a week of search logs
  • Where the answers live: documents in SharePoint, tables in the lakehouse, records in the ERP or the CRM
  • How each source holds its permissions, and whether they survive being copied into an index
  • Which questions are about documents, which are about numbers and which need both, because each is built differently
  • What a wrong answer costs, which decides how much the assistant may say without a source behind it

What we build

  • Document search on Databricks AI Search, formerly Vector Search: Delta Sync indexes that stay current with their source tables, and hybrid keyword and vector retrieval so part numbers and codes still match
  • Questions about numbers answered by Genie over governed tables, with the table and the query behind each answer on screen
  • Apps that use Databricks Apps user authorization, so the signed-in person's row filters and column masks decide what comes back
  • Answers that cite the passage or the table they came from, so checking one means reading the source
  • An evaluation set of real questions with known answers, rerun whenever the model, the prompt or the index changes
  • The assistant where people already work: a Databricks App, a web application, or inside a product you run

FAQ

AI assistants and enterprise search: common questions

What does an AI chatbot development company actually build?

The parts around the model. Retrieval that finds the right passage, permissions that decide what each person may see, citations so an answer can be checked, an evaluation set that shows when it gets worse, and the interface people use every day. The model is bought; the rest is engineering, and that's the part we do.

What is AI enterprise search?

Search across a company's documents and data that answers a question in a sentence, with its sources, instead of returning ten links. It combines keyword search, which finds exact terms like a part number, with vector search, which finds passages that say the same thing in different words. Databricks AI Search does both and merges the results.

How do you stop a chatbot showing documents someone shouldn't see?

Permissions are applied when content is retrieved, never filtered out of an answer afterwards. On Databricks, AI Search indexes are governed by Unity Catalog, and an app using user authorization queries as the signed-in person, so their row filters and column masks apply. Documents copied in from elsewhere carry their access lists as metadata, and every query filters on them.

Should we buy an enterprise search product instead?

Often, yes. If your documents live in a handful of SaaS tools and an off-the-shelf product connects to all of them, buying is faster and cheaper.

Building pays off when the answers depend on data in your lakehouse, ERP or CRM, when the permissions are unusual, or when the assistant has to sit inside a product you already run. We'll tell you which one you're looking at in the first conversation.

Can it answer questions about numbers, not just documents?

Yes, by a different route. Numbers come from Genie or a query over governed tables, with the query shown, rather than from a model summarising a PDF of last quarter's report. In the plant reporting build we've published, a Genie space answers plain-English questions about line downtime with the chart and the table behind it.

How do you know the assistant is any good?

A set of real questions with known answers, scored every time the model, the prompt or the index changes. Without it, quality is whoever spoke last in the review meeting, and nobody can safely move to a newer model.