> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/capabilities/assets.md).

# Assets

Assets are the help centers, websites and Drive documents Aissist's AI answers from.

*Last updated: November 8, 2026*

Assets are the knowledge your AI agent answers from: your help center, your website, and documents in Google Drive or OneDrive. This page explains the asset types, how the AI finds the right passage, and how to keep assets accurate. For the steps, see [Add Assets](https://doc.aissist.io/tutorial/add-assets.md).

### Asset types

| Type                                    | What it holds                                                                                                                                                                                      | How it stays current                                 |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| **Help center**                         | Articles or macros from your help desk, read through its [connector](https://doc.aissist.io/capabilities/connectors.md)                                                                            | Synced every 6 hours                                 |
| **Google Drive** or **OneDrive**        | Documents in a folder, or ones you pick, read through your Drive connector (up to 200)                                                                                                             | Synced every day                                     |
| **Website**                             | The pages under an address, or ones you pick, read directly from your site (up to 3,000)                                                                                                           | Checked every day, synced in full every week         |
| **Website search**                      | A whole domain, searched live when a question needs it                                                                                                                                             | Changes appear once search engines re-index the page |
| **Single web page**, **Google Article** | One page or one Google file. Deprecated: they can't be added any more; use a **Website** or **Google Drive** asset instead ([why, and how to move](https://doc.aissist.io/faq.md#assets-and-sync)) | Read again about once a day                          |

Use a **Help center** asset for your help desk's articles: it reads them exactly as written, with nothing to block or render. Use a **Website** asset for a documentation site or the parts of your site that matter, such as `help.example.com` or `example.com/help`. Use **Google Drive** or **OneDrive** for policies and procedures your team edits often. Use **Website search** for a site too large to sync, such as a big product catalog.

Help center, Drive and Website assets are either **Synced** or **Selected**:

* **Synced** includes everything in a place you choose: every article matching your filters, every document in a folder, or every page under an address. New items are added, and removed ones go.
* **Selected** holds only the items you pick. Edits to them are read, but nothing new is added.

The badge on the asset's page and in the **Assets** list shows which one an asset is. You find assets under **Workspace → Assets**. The list warns you when an asset is not accessible.

### How assets stay current

Aissist answers from what an asset read at its last sync, not from your help desk, drive or site live. So an article you delete or edit is used as it was until the next sync. To sync an asset now, open it and click **Sync now**. Saving a change to an asset syncs it too.

A website page or Drive document that has gone is removed after two syncs in a row can't find it, so a short outage on your site or drive never empties an asset. To stop an item being used at once, leave it out, remove it from a Selected list, or turn the asset off. See [Assets and sync](https://doc.aissist.io/faq.md#assets-and-sync) in the FAQ for the schedules and the common questions.

### How retrieval works

The AI does not read all your assets for every reply. For each customer message:

1. Aissist works out the question being asked, in the context of the conversation.
2. It searches the assets available to this conversation and keeps the passages that match.
3. The reply is written from those passages, with your instructions deciding how to use them.

Which assets are available depends on [sub agents](https://doc.aissist.io/capabilities/sub-agents.md). An asset linked to a sub agent is searched only while that sub agent is active. An asset linked to none is available everywhere. This is the main lever against noise: an order tracking conversation should not pull in passages from your refund policy.

To see what a reply used, open the conversation under **Deploy → Sessions** and check the **Sources** of each AI reply.

### Test and refine

Use the asset debugger to check what the AI can find. On **Workspace → Assets**, click **Debug**, then enter a realistic question, such as "can I return a used item?". You see the passages that come back and where each came from.

* **Nothing relevant comes back:** check the asset is accessible, add the missing source, or add the missing detail to an existing one.
* **The wrong content comes back:** remove conflicting or outdated text, split unrelated topics into separate assets, or link the asset to the sub agent that needs it.
* **The content is vague:** rewrite the source with explicit steps, links and exceptions.

Fix the source, not the reply. If customers ask how to order a replacement part and the answer is vague, add the exact ordering steps and link to the document they belong in. That works better than a broad instruction.

### With Ask Engine

Click **Add Asset** and say what to add and which sub agents should use it:

```
Add the page https://example.com/returns-policy for the Returns sub-agent
```

```
Add our shipping rates sheet https://docs.google.com/spreadsheets/d/... for the Shipping sub-agent
```

Ask Engine checks the link, asks you to confirm what to add (the whole site, a single page, or a Google file), then drafts a title, a one-line description and the sub agents to link. You review and create it. You can also ask in **Ask**: "What do our assets say about international shipping?" It searches your assets and answers with the passages it found.

### Best practice

* **Start with your highest-value sources:** your help center site, policy pages, shipping and returns pages.
* **Link workflow-specific assets to their sub agents.** Keep only universal content unlinked.
* **Use headings** in documents, one topic per section, so each passage stands on its own.
* **Put facts in assets, not instructions.** Instructions say how to use the facts.
* **Debug before you tune instructions.** If the knowledge is missing or contradictory, fix that first.
* **Remove duplicates.** When one website asset is already covered by another, the list flags it; delete one of them.

### Insight Assets are separate

Documents you want used only to check answers, such as QA guidelines or internal procedures, belong in [Insight Assets](https://doc.aissist.io/capabilities/insight-assets.md) (**Insight → Insight Assets**), not here. They belong to the project, are used by Agent Insight, Evaluation, Session Insight and Analyze commands, and are never used to answer customers.

### Related

* [Add Assets](https://doc.aissist.io/tutorial/add-assets.md)
* [Insight Assets](https://doc.aissist.io/capabilities/insight-assets.md)
* [Instructions and Information](https://doc.aissist.io/capabilities/instructions-and-information.md)
* [Continuous Improvement](https://doc.aissist.io/capabilities/continuous-improvement.md)
