---
title: "Enterprise knowledge assistants for employees | YPAI"
url: https://ypai.ai/enterprise-knowledge-assistants/
description: "An internal assistant that answers employees from the governing source, cites the passage, applies their access rights and flags conflicting or silent sources."
source: "src/copy/routes (route /enterprise-knowledge-assistants/)"
---

# Internal knowledge assistants cited to the source that governs.

> An internal assistant that answers employees from the governing source, cites the passage, applies their access rights and flags conflicting or silent sources.

YPAI designs and builds internal knowledge assistants around the sources, the access rules and the questions your employees actually ask. Each answer shows the passage it came from, applies the access model chosen for the project, and makes a stale, conflicting or missing source visible in the answer itself.

From an employee question to the source that governs

Start with one employee group, one knowledge domain and a bounded source set. YPAI maps who owns each source, builds the employee experience, tests it on real questions and records what is ready for release.

## Search finds a document. The employee needs the governing answer.

- An employee finds several plausible documents across a policy library, shared drive, wiki, intranet or service desk. They still need to know which one governs, which version applies, whether they may use it and who owns the conflict.
- The person accountable for employee knowledge is managing more than search. Source authority, ownership, permissions and freshness decide which answer an employee can act on.
- A citation links the answer to the passage and can show the source, owner, version and effective date where the customer system provides them.

A freshly retrieved document and a current policy are two different things. The assistant tells them apart.

### Choose the first knowledge job

- Start where repeated questions and unclear authority create real work. The first domain needs named sources, named owners, a known user group and the questions that decide acceptance.
- One routine question is enough to begin: "Which policy applies to this request, and is it current?" Other domains follow when their content and ownership are ready.

## Define the answer before choosing the interface

- An answer contract defines what the assistant must establish before it responds. The retrieval design applies your chosen access model to the retrieved passages, the answer and the citation alike.
- Identity, groups, role, project membership, document permissions and explicit exclusions can all enter the project design. The source map separates authoritative, supporting, historical, restricted and excluded material.

## Evaluate the questions that change an employee decision

- The answer draws on the approved sources, and only those.
- Access applies to the answer and to the citation.
- When evidence is missing or in conflict, the assistant shows that and routes to the owner.

The evaluation set combines routine questions with ambiguous requests, restricted material, expired sources, document conflicts, missing evidence and unsupported conclusions. Measures are chosen for the questions and the risk, and acceptance thresholds are set per question set.

## Share the foundation, keep the access rules apart

### Company-wide

A company-wide assistant and a finance assistant draw on different sources. Teams share the infrastructure while each keeps its own permissions, answer rules and test questions.

### Next step

An employee may need a cited answer, a link to a form, a service ticket or a handoff to a person. The answer rules agreed for the project state where the assistant stops and what the employee sees next.