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

# Knowledge

> Give Adapt persistent memory of your business context, facts, and preferences

Adapt's knowledge base is its long-term memory. It stores durable facts, definitions, procedures, and preferences about your organization, so Adapt carries that context into every future conversation without you having to re-explain it.

## What belongs in the knowledge base

* **Business context** — Metric definitions, KPIs, and terminology (how you define "active user" or "MRR")
* **Facts** — Durable information about your company, customers, products, and vendors
* **Procedures** — Standard operating procedures and recurring workflows
* **Preferences** — How your team likes reports formatted and which metrics matter most

<Note>
  Knowledge is for **durable, shared context**. For live or fast-changing data — today's revenue, current pipeline, this week's tickets — Adapt pulls from your [integrations](/integrations/overview) in real time instead of storing it.
</Note>

## How knowledge gets in

<Steps>
  <Step title="Adapt learns automatically">
    As you work, Adapt notices durable facts, decisions, and preferences and saves them on its own — no action required.
  </Step>

  <Step title="You tell Adapt directly">
    Say it in a conversation and Adapt will remember it:

    ```
    Remember that our fiscal year starts in October.
    ```
  </Step>

  <Step title="You add it manually">
    Create entries yourself in **Settings** > **Knowledge**.
  </Step>
</Steps>

## How an entry is structured

Each knowledge entry has two parts:

| Field                 | What it is                                                                                                                |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Retrieval trigger** | A description, in your own words, of *when* this knowledge is needed — the questions and phrasings that should surface it |
| **Content**           | The actual fact, preference, or procedure, stated completely                                                              |

Adapt matches an incoming question against the retrieval trigger, then loads the content. Writing triggers the way people actually ask gives the best results.

**Example**

```
Trigger:  when someone asks about our fiscal year, quarter start
          dates, or reporting periods

Content:  Adapt's fiscal year starts October 1. Q1 = Oct–Dec,
          Q2 = Jan–Mar, Q3 = Apr–Jun, Q4 = Jul–Sep.
```

## How Adapt uses knowledge

* **Surfaced automatically** — Relevant entries are pulled in based on your message before Adapt answers.
* **Searched on demand** — Adapt can search the knowledge base when a task needs more context.

The result: consistent answers that reflect your definitions and preferences, without you repeating yourself.

## Manage your knowledge base

Go to **Settings** > **Knowledge** to:

* Browse every entry in your organization
* Search by meaning, not just keywords
* Add a new entry (retrieval trigger + content)
* Edit an existing entry
* Remove entries that are stale or no longer true

## Best practices

<CardGroup cols={2}>
  <Card title="Keep entries atomic" icon="layer-group">
    One fact, preference, or procedure per entry. Split unrelated facts apart.
  </Card>

  <Card title="Write triggers like real questions" icon="comment">
    Phrase triggers the way your team actually asks, including names and synonyms.
  </Card>

  <Card title="Store durable context" icon="anchor">
    Save what stays true over time. Let Adapt fetch live data from integrations.
  </Card>

  <Card title="Review periodically" icon="rotate">
    Remove outdated facts so Adapt always reflects current reality.
  </Card>
</CardGroup>

## Knowledge vs. skills

Knowledge and [skills](/features/skills) both give Adapt context, but they serve different purposes:

* **Knowledge** captures *what is true* about your business — facts, definitions, and preferences.
* **Skills** capture *how to do a task* — workflows, templates, and step-by-step procedures.

<CardGroup cols={2}>
  <Card title="Skills" icon="puzzle-piece" href="/features/skills">
    Package workflows and templates that Adapt loads on demand
  </Card>

  <Card title="Integrations" icon="plug" href="/integrations/overview">
    Connect your tools so Adapt can pull live data and take action
  </Card>
</CardGroup>