# How to organize the Knowledge Base by topic (/docs/portal/knowledge-base/organize-by-topic)





A well-organized Knowledge Base is easier to keep current and helps the AI find the right
content during conversations. Use the **Table of Contents** sidebar as your map, and group
related facts into the same section.

<img alt="The Table of Contents beside the entry list" src="__img0" />

One subject per entry [#one-subject-per-entry]

Each entry has a **Descriptor** and a body of content. The AI retrieves by subject, so an entry
that covers one subject cleanly is matched more reliably than a long one covering several.

| Instead of                                                      | Prefer                                         |
| --------------------------------------------------------------- | ---------------------------------------------- |
| One *General Info* entry holding history, financing and service | *About the Dealership*, *Financing*, *Service* |
| *Service and Parts*                                             | *Service*, *Parts*                             |
| A *Misc* entry that collects whatever didn't fit                | An entry per subject, named for the subject    |

There is no limit on the number of entries, and no approval step — press **Add Data** and the new
entry is yours to name.

Name the descriptor for the subject [#name-the-descriptor-for-the-subject]

The **Descriptor** is what the **Table of Contents** lists, so it's how you and your colleagues
find things later. Name it after the subject, the way a customer would think of it: *Trade-In
Process*, *Loaner Policy*, *Directions and Parking*.

Descriptors have to be unique within the store, compared without regard to case — *Financing* and
*financing* count as the same name, and **Save** is refused until one of them changes.

Reorder the list [#reorder-the-list]

The arrows beside each **Descriptor** move an entry up or down. Order affects nothing but the
Table of Contents, so arrange it however makes the list quickest to scan — most-edited entries at
the top, or related subjects next to each other.

To move *content* from one entry to another, cut it from the first entry's editor and paste it
into the second, then **Save** once. Both edits are part of the same save; there's no need to save
in between.

Avoid duplicates [#avoid-duplicates]

If two entries state the same policy, the AI has two sources that can drift apart. Keep one
canonical entry per fact and delete the other — the bin icon beside the descriptor removes an
entry, and it disappears once only one entry is left, since a store always keeps at least one.

<Callout type="info">
  Treat the Knowledge Base like a help center for your AI. The same principles that make a
  human-facing FAQ effective — clear topics, short answers, no duplicates — apply here.
</Callout>

Periodic review [#periodic-review]

A 30-minute review each quarter keeps the Knowledge Base trustworthy:

<Steps>
  <Step>
    Walk down the 

    **Table of Contents**

    , entry by entry.
  </Step>

  <Step>
    Delete entries that are no longer accurate.
  </Step>

  <Step>
    Update prices, names, and dates that have changed.
  </Step>

  <Step>
    Split any entry that has grown to cover more than one subject.
  </Step>

  <Step>
    **Save**

    , then 

    **Train AI**

     once at the end of the review.
  </Step>
</Steps>
