> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textmine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge Bases overview

> Collect source material, ask grounded questions, generate artifacts, and manage shared knowledge libraries in TextMine.

Knowledge Bases give teams a shared place to collect source material, ask questions over that material, and turn curated evidence into reusable outputs.

Use a Knowledge Base when the source set is broader than a single Vault folder or when the same collection of materials should support repeated questions, reports, artifacts, or review work.

## When to use a Knowledge Base

| Use Knowledge Bases for                                                                        | Use another TextMine area when                                         |
| ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Shared libraries of policies, documents, templates, records, or reference material.            | A document only needs standard Vault processing and validation.        |
| Asking questions across curated sources with source references.                                | The work is a one-off exploration in Workbench.                        |
| Creating reusable artifacts, reports, presentations, or review materials from a stable corpus. | The output should run automatically from a trigger; use a Workflow.    |
| Turning a drafted review artifact into reusable playbook logic.                                | The review rules are already known; create or run a Playbook directly. |

## Sources and organization

A Knowledge Base can include uploaded files, Vault documents, Legislate documents, and business records. Teams can organize sources into folders, move documents between folders, and arrange the library with an instruction when a large source set needs structure.

Knowledge Base sources keep their own display names, summaries, document type labels, topics, status, and source metadata. Where source files came from Vault, Legislate, or Records, the Knowledge Base keeps enough source information to let users trace the material back to its origin.

## Source profiles, tags, and feedback

Each source can be profiled before it is used for questions or deliverables. Profiles can include summaries, topics, starter questions, extracted text, tables, entities, and source metadata.

Teams can also add reusable tags to Knowledge Base sources. A tag is a question or extraction target that can be run against a source, stored, and reused for later review. Feedback fields let teams capture structured source-level review data such as status, priority, owner, date, or notes.

Use this when a Knowledge Base needs both searchable context and lightweight review tracking.

## Ask a Knowledge Base

Users can ask a Knowledge Base questions across all ready sources or a selected source subset. Answers are grounded in the hub's source material and can include source references and evidence snippets where available.

Ask is useful for questions such as:

* What does this policy library say about a control or obligation?
* Which documents mention a topic, exception, or risk?
* How do several source documents compare?
* Which source should be used when drafting a report, playbook, or presentation?

## Artifacts and reports

Knowledge Bases can generate artifacts and reports from selected sources. Outputs can include document, presentation, PDF, and report-style deliverables. Reports can include chart data where the source material supports it.

Generated outputs can be refreshed, revised with instructions, versioned, and exported to Word, PowerPoint, or PDF. This makes Knowledge Bases useful for recurring evidence packs, policy summaries, client-ready explainers, internal briefing notes, and draft review assets.

When a Knowledge Base artifact captures review rules or repeatable guidance, it can be promoted into a Playbook so the same logic can be applied consistently to future documents.

## Access and visibility

Knowledge Bases support team and private visibility. Members can be added to a hub, and administrators can manage access for that hub. Use private visibility for work-in-progress or restricted source collections, and team visibility when the hub should become a shared knowledge library.

## Agent guidance

Agents should use a Knowledge Base when the user asks to collect, curate, ask over, or generate from a named source library. Include the Knowledge Base ID, source IDs, report or artifact IDs, and any exported file links in the final answer.

Before making broad changes, confirm the hub, source scope, visibility, and whether generated outputs should stay as drafts, be exported, or be promoted into playbook logic.