Grounded enterprise knowledge assistants: retrieval, citations and permissions

The enterprise knowledge assistant is the most requested AI application and one of the most often abandoned. The pilot answers questions impressively. Then someone notices it confidently quoted a superseded policy, or showed a document the user shouldn't have seen, and trust evaporates.

Those failures aren't model problems. They are application problems, and they have application solutions.

What a grounded assistant needs

The knowledge and assistants family in the Atlas is built around five requirements.

1. Approved sources only. The assistant answers from a curated set of repositories (policies, procedures, product documentation, knowledge articles), each with an owner. Content has a lifecycle: draft, approved, superseded. Superseded content is excluded.

2. Retrieval with citations. Every answer links to the passages it relies on. If the sources don't support an answer, the assistant says so rather than improvising.

3. Permission-aware retrieval. Users only retrieve content they are allowed to see. Permissions come from the source systems and the identity provider, not from a separate copy that drifts.

4. Evaluation before and after launch. A test set of real questions with expected answers and sources, run on every change to prompts, models or content. We describe the approach in evaluation and guardrails.

5. Feedback and content ownership. Users flag wrong or missing answers. Flags become tasks for content owners, so the knowledge base improves instead of the prompt getting longer.

Beyond Q&A

Once retrieval is trustworthy, the same foundation supports more useful workflows:

• Drafting: first drafts of customer replies, reports or procedures, grounded in approved content
• Policy lookup inside other applications: the case worker or operator sees relevant policy passages in context
• Onboarding: role-specific guided learning over the procedures a new joiner needs
• Change impact: when a policy changes, find the procedures and articles that reference it

Controls designed in

• Answers restricted to what the user may access
• Logging of questions, retrieved sources and answers for audit, with retention rules
• No training on customer data by default, and a documented choice of model provider and hosting
• Sensitive-content filters configured per deployment

Integrations

Document management and intranets, knowledge bases, ticketing systems (resolved tickets are valuable knowledge), the identity provider and directory groups, and the chat or collaboration tools where people already work.

Who uses it

Everyone, which is why it needs owners: the business owner of each knowledge domain, the AI platform team, and IT for integration and access.

First scope

One domain with an owner and a clear audience, such as HR policies, IT support or a product line's procedures. Measure answer accuracy on the test set and the rate of cited answers. Scope it in a Solution Definition Sprint.

Explore the Atlas, or bring us your knowledge domain.