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

# Knowledge base

> Manage pages, folders, documents, links, and synced sources in the V3 Knowledge Base.

The Knowledge Base stores facts your agents can retrieve when they answer. Use it for policies, product details, listing details, FAQs, help articles, and imported source material.

Open **Knowledge** from the **Agents** group in the workspace sidebar.

<Info>
  Knowledge is for facts. Put tone in Persona, reusable process instructions in Skills, escalation boundaries in Behavior or Guardrails, and action instructions in Tools or Skills.
</Info>

## Knowledge Structure

V3 Knowledge is organized as a folder tree. You can create pages and folders, search, sort, move items, rename items, and delete items from the Knowledge sidebar.

| Item | Use it for |
| - | - |
| **Page** | Hand-written knowledge that your team owns and can edit directly. |
| **Folder** | Organizing pages and imported source files by topic, region, listing, product, or team. |
| **Source file** | Imported document, spreadsheet, text file, or link content. Source-backed files are usually read-only because they are managed by sync. |

## Composable Knowledge

Knowledge pages work best as focused, reusable building blocks. Instead of copying the same policy or detail into several places, create one source page and reference it from related pages or Skills.

Use references when:

* A page depends on another page for definitions, eligibility rules, pricing, or exceptions.
* A Skill needs factual context but should not duplicate the underlying policy.
* A scoped page extends a global page for one listing, customer group, product, or operational category.

For example, keep a global "Cancellation policy" page as the source of truth, then create listing-specific pages that reference it and only add the local exceptions. A refund Skill can then reference the cancellation policy page instead of repeating every cancellation rule.

## Structured Reference Data

Knowledge is not limited to policies and help articles. Any structured reference data an agent or Skill needs to look up can live in the Knowledge Base as a general-purpose data repository.

Common examples:

| Example | What it captures |
| - | - |
| Cleaning or maintenance schedule | Which unit gets cleaned or serviced, and when. |
| Cleaner or vendor assignment | Which cleaner or vendor is responsible for which properties or listings. |
| Vendor directory | Vendor names, services, and contact details for dispatch or escalation. |

These pages work the same way as any other Knowledge page. Skills reference them, they can link to and from other Knowledge pages, and they stay current either through direct edits or through sync from an external source.

## How Knowledge Reaches An Answer

When a contact sends a message, the AI engine:

1. Analyzes the question and identifies what information is needed.
2. Searches across connected context sources such as Knowledge, PMS data, CRM records, and imported documents.
3. Retrieves the most relevant information.
4. Uses that context to generate an accurate response.

The more complete and well-organized your Knowledge is, the more confidently the agent can respond without escalating to a human. For how the engine processes information, see [How Conduit Agents Work](/get-started/how-conduit-agents-work#what-happens-when-a-message-arrives).

## Where To Go Next

<CardGroup cols={2}>
  <Card title="Adding Knowledge" icon="plus" href="/build-your-agent/knowledge-base/adding-knowledge">
    Create pages and folders, upload documents, and import links.
  </Card>

  <Card title="Connected Sources" icon="plug" href="/build-your-agent/knowledge-base/connected-sources">
    Sync from Notion, Google Drive, Airtable, and business systems.
  </Card>

  <Card title="PMS Knowledge" icon="building" href="/build-your-agent/knowledge-base/pms-knowledge">
    Add and override listing content without losing edits.
  </Card>

  <Card title="Managing Knowledge" icon="sliders" href="/build-your-agent/knowledge-base/managing-knowledge">
    Scope, permissions, versions, and deletion behavior.
  </Card>
</CardGroup>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How do I decide between a Knowledge page and a Skill?">
    Knowledge holds facts the agent can look up. A Skill holds a reusable process the agent should follow. If the content answers "what is true", it belongs in Knowledge. If it answers "what should happen next", it belongs in a Skill.
  </Accordion>

  <Accordion title="How long should a Knowledge page be?">
    Short enough to cover one topic. A focused page retrieves more accurately than a long page mixing several policies, so split content that covers unrelated subjects.
  </Accordion>

  <Accordion title="Can Knowledge hold reference tables, not just policies?">
    Yes. Cleaning schedules, cleaner and vendor assignments, and vendor directories all work as Knowledge, and Skills reference them the same way they reference any other page.
  </Accordion>

  <Accordion title="The agent is not using a page I added. What should I check?">
    Confirm the source finished syncing, check the page is scoped to the right listing or entity, and make sure a competing page does not cover the same topic with different wording.
  </Accordion>
</AccordionGroup>

## Common Mistakes

* Do not put tone instructions in Knowledge. Put tone in the agent Persona or a Skill.
* Do not put tool invocation rules only in Knowledge. Put them in Skills or the relevant Tool description.
* Do not put escalation thresholds only in a factual page. Put hard boundaries in Guardrails or Behavior.
* Do not edit source-backed PMS content directly when the source will overwrite it on the next sync.
* Do not duplicate the same policy at global and scoped levels unless the scoped version intentionally overrides the global one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.