> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/knowledge/adding-sources.md).

# Adding sources

Attach files, add pages, or paste notes for the assistant to answer from.

**Knowledge** in the admin.

Supported formats: **PDF, Word, text, Markdown, CSV, and HTML**, plus links and pasted notes. Sources are indexed for retrieval, so the assistant quotes your documents instead of guessing. More formats can be added on request.

{% hint style="warning" %}
**Treat everything you add here as public.** The assistant answers shoppers from these sources, quotes them back in its own words, and on a claim that matters it shows the shopper the sentence it drew on. Add what you would be happy for a shopper to read, and keep anything confidential, internal, or personal out of it. See [Citations](/maker-greatstore/storefront/citations.md).
{% endhint %}

{% stepper %}
{% step %}

#### Add a source

Attach a file, add a page, or paste a note.
{% endstep %}

{% step %}

#### Give it time to process

A source has to be processed before the assistant can answer from it.
{% endstep %}

{% step %}

#### Test it

Use the chat on the same screen to ask a question the new source should answer. See [Testing answers](/maker-greatstore/knowledge/testing-answers.md).
{% endstep %}
{% endstepper %}

## Choosing what to add

Add what shoppers actually ask and your catalogue cannot answer, and only documents you are happy for shoppers to see:

* [x] Returns and exchanges
* [x] Shipping: destinations, timings, costs
* [x] Sizing and fit guidance
* [x] Care and materials
* [x] Warranty and repairs
* [x] Store locations: the assistant already knows roughly where the shopper is, so a plain list of your stores is enough for it to answer "find the nearest store to me"

{% hint style="warning" %}
An empty knowledge base is not a failure state; the assistant still answers from your catalogue and connectors. It simply cannot answer policy questions.
{% endhint %}

## Working with a source

Every source in the list has a menu on its row. What it offers depends on the kind of source.

| Action            | What it does                                                                     | Offered on                              |
| ----------------- | -------------------------------------------------------------------------------- | --------------------------------------- |
| **Rename**        | Changes the name the source is filed under. Give it one that says what's inside. | Every source                            |
| **Preview**       | Opens what the assistant actually reads, in a new tab.                           | Files and notes                         |
| **Open original** | Opens the page the source points at.                                             | Links                                   |
| **Download**      | Downloads a copy of the source's content.                                        | Files and notes                         |
| **Reindex**       | Processes the source again.                                                      | Any source that has finished processing |
| **Delete**        | Removes the source. It stops being searchable, and this can't be undone.         | Every source                            |

Tick several sources and the menu at the top of the list reindexes, downloads or deletes them together.

### Reindex a link whenever its page changes

A link is read when you add it and whenever you reindex it, and at no other time. If the page it points at changes (a new returns window, updated shipping rates, a rewritten size guide), the assistant keeps answering from the version it read until you reindex the source. Reindexing fetches the page as it stands today and replaces what the assistant knows, keeping the name you gave it.

Make it part of the routine: edit the page, then reindex the source that points at it.

For a file or a note, reindexing processes the same content again, which is worth a try if a source finished with problems. To change what a file or note says, delete it and add the new version.

{% hint style="info" %}
A source that failed to process shows its own retry button on the row, so you don't have to go looking in the menu for it.
{% endhint %}

## What the shopper sees

When a shopper asks something your catalogue cannot answer, the assistant answers from these sources instead of guessing or deflecting, and this is what powers policy answers on the product page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-greatstore/knowledge/adding-sources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.