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

# Memory modes

> Choose whether and how a knowledge base remembers durable facts across conversations.

[Memory](/memory/overview) lets an assistant recall durable facts — preferences, decisions, and context — across separate conversations. Each knowledge base has a **memory mode** that decides whether it participates in memory, and how its memories are scoped.

## The three modes

<AccordionGroup>
  <Accordion title="Disabled" icon="ban">
    This knowledge base never stores or recalls durable memory. Every conversation starts fresh. Choose this when you want purely stateless answers.
  </Accordion>

  <Accordion title="Subject (default)" icon="user">
    Memory follows the tenant's memory setting and is scoped to the tenant — or to an individual end user when you provide an external subject id. This is the default and the right choice for most knowledge bases, including customer-facing ones where each of your users should have their own memory.
  </Accordion>

  <Accordion title="KB-restricted" icon="lock">
    Memory is kept in an isolated store just for this knowledge base and never mixes with the tenant-wide memory. Choose this when a knowledge base should build its own recall without sharing it with, or drawing from, the rest of the tenant.
  </Accordion>
</AccordionGroup>

## How modes relate to the tenant setting

A knowledge base's mode can only **further-restrict** what the tenant already allows — it always stays within the tenant's memory policy.

<Note>
  If a tenant has memory turned off, a knowledge base cannot turn it on. This keeps the tenant in control of whether any durable memory is stored at all. To enable memory for a knowledge base, make sure the tenant permits memory first — see [Memory](/memory/overview).
</Note>

| Tenant memory | Disabled              | Subject                            | KB-restricted              |
| ------------- | --------------------- | ---------------------------------- | -------------------------- |
| On            | No memory for this KB | Follows tenant, scoped per subject | Isolated to this KB        |
| Off           | No memory for this KB | No memory (follows tenant)         | No memory (follows tenant) |

## Managing KB-restricted memory

When a knowledge base uses **KB-restricted** mode, its memories live in their own store — and you can view and manage them right from the knowledge base:

<CardGroup cols={2}>
  <Card title="Review memories" icon="list">
    See the durable facts this knowledge base has kept, and remove any you no longer want recalled.
  </Card>

  <Card title="Explore the entity graph" icon="diagram-project">
    Inspect the entities and relationships this knowledge base has learned, isolated from the tenant-wide graph.
  </Card>
</CardGroup>

<Tip>
  Use **Subject** mode when you want a shared, tenant-wide sense of memory (or per-end-user memory in a customer-facing product). Use **KB-restricted** when a knowledge base should keep its own recall separate from everything else in the tenant.
</Tip>

## Next steps

<CardGroup cols={2}>
  <Card title="How memory works" icon="brain" href="/memory/overview">
    Understand durable memory across AutoSage.
  </Card>

  <Card title="Durable memory" icon="database" href="/memory/durable-memory">
    See what gets remembered and how it is recalled.
  </Card>
</CardGroup>