Retrieval, permissions and maintenance for a company knowledge base

A general model knows common sense, not your policies, permissions or which version is current. A company knowledge base has to solve retrieval, access control and maintenance.

Knowledge managementKnowledge base

Company sources and model knowledge

An employee asking who can approve a contract needs the policy for their department, transaction value and region. A model may know general contract practices, but it still needs the company’s current policy to answer this question.

Uploading a file can serve a single inquiry. Ongoing use by a team also requires updates, version handling, access controls and a way to investigate wrong answers. Those tasks need defined processes and owners.

Choosing context for each request

A question may require only a few paragraphs of a policy. Sending the full archive increases processing costs and includes outdated or irrelevant material. Old information accumulated in a long conversation can also affect the current answer.

We organize sources for retrieval and select passages according to the question, user permissions and task. Scope, effective version and document structure guide that selection. If the active version cannot be established, the system should explain the gap and ask the source owner to resolve it.

Preparing documents for retrieval

Retrieval-augmented generation, or RAG, finds source material before generating an answer. Preparation includes reading scans, preserving table relationships and separating versions. Splitting a long document also requires retaining the context needed to understand its clauses.

Retrieved passages need to be checked for coverage and conflicting rules. The workflow may retrieve more material or ask the user for missing details. Conclusions without sufficient support should go to a responsible reviewer. Users should be able to open the sources used in the answer.

Citations that support review

A citation should identify the passage and effective version supporting a specific statement. A link to a lengthy policy manual leaves the reader to find the relevant clause.

For policy, expense and access questions, retain the sources and processing records. Reviewers can then distinguish an outdated source from a retrieval or generation error. The answer should identify details the available material does not establish.

Retrieval with employee permissions

Identify the user, organization and role before retrieving authorized material. Cross-department sharing needs a defined scope and effective date. Departures, permission changes and withdrawn documents must be reflected in the knowledge base.

Logs require separate access controls so troubleshooting does not expose unnecessary sensitive information. Private deployment controls the infrastructure and data environment; application permissions, auditing and sensitive-data handling still need to be designed.

When to hand a request to a person

Equipment requests, routine account procedures and documented troubleshooting are frequent questions with established sources. Identity exceptions, elevated privileges, individual disputes and policy conflicts require an authorized person.

A handoff should include the facts established, sources found and steps already tried. This lets support continue the investigation without asking the user to repeat it. Acceptance testing should check handoff conditions and whether the ticket contains enough information.

Testing the first version

Use historical questions with agreed answers and sources to check accuracy, citations, permission boundaries and handoffs. Include ambiguous questions, outdated documents and requests for which no answer is available.

In Cyano’s IT knowledge assistant project, AI handled 80% of routine inquiries with an average response below three seconds. Each new project needs criteria based on its own source quality and workload; these figures are not a forecast for other implementations.

Start with one team

Choose one team, a relatively stable set of sources and recurring questions. Assign owners for source updates, sensitive-answer review and unresolved requests. Business owners, source maintainers and engineers all need to participate. During assessment, we examine source quality, permissions and the existing process to decide whether a pilot can begin or whether the sources need preparation first.

Discuss a similar project

Bring your current process and a work sample to discuss scope, costs and implementation requirements.

Discuss your project
80%Routine tickets handled
Enterprise ServicesPilot + ongoing service4-week pilot · 8-week rollout

AI handles 80% of routine inquiries, averaging under 3 seconds

Waiting in the queue< 3 s
Knowledge & Internal Assistants

Find internal information with source citations

Connect your wiki, SOPs and ticketing system to answer routine questions with sources and route complex requests to the support team.

CONTACT US

Tell us about your workflow

Book a 30–45 minute call to discuss your process, source material and project goals.

  • Reply within 1 business day
  • A 30–45 minute call
  • NDA available