> 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/tutorial/add-assets.md).

# Add Assets

Add knowledge to an Aissist workspace - help center articles, Google Drive and OneDrive documents, and websites - keep it in sync, and test retrieval with the asset debugger.

*Last updated: November 8, 2026*

Assets are the knowledge your agent answers from. This page shows how to add each type of asset in the console, how assets stay current, and how to check what the agent retrieves from them. For how assets work and when to use them, see [Assets](https://doc.aissist.io/capabilities/assets.md).

### Asset types

| Type                             | Use it for                                                                                                                               | How it stays current                                 |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| **Help center**                  | Your help desk's articles or macros, such as a Zendesk, Intercom or Freshdesk help center                                                | Synced every 6 hours                                 |
| **Google Drive** or **OneDrive** | Policies, procedures and price lists your team edits: Docs, Sheets, Slides, PDF, Word, PowerPoint, Excel and images (up to 200 a folder) | Synced every day                                     |
| **Website**                      | A documentation site, or the parts of your site that matter (up to 3,000 pages)                                                          | Checked every day, synced in full every week         |
| **Website search**               | A site too large to sync, searched live when a question needs it                                                                         | Changes appear once search engines re-index the page |

### Add an asset by describing it

{% stepper %}
{% step %}

### Open Add an asset

Go to **Workspace → Assets** and click **Add Asset**. To add an asset for one sub-agent, open the sub-agent's **Assets** tab and click **Add Asset** there.
{% endstep %}

{% step %}

### Say what to add

Paste the link and say which sub-agents should use it. For example:

* `Add help.example.com for the Refunds and Shipping sub-agents`
* `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`

Click **Continue**.
{% endstep %}

{% step %}

### Confirm what to add

Aissist checks the link. When it could be added more than one way - the whole site, a single page or a Google file - it asks you to choose. When there is no link, it asks for one.
{% endstep %}

{% step %}

### Review and create

Review the draft: **Title**, **Description**, and the sub-agents that should use it (suggested ones are marked). Untick any you do not want. Nothing is created until you click **Create asset**. If the link is already an asset, click **Use the existing one** to attach it to the sub-agents instead.
{% endstep %}
{% endstepper %}

Prefer a form? Click **Or add it yourself in the classic editor** and choose the type. The sections below show each one.

### Help center

Read your help desk's articles or macros through its connector. Connect the help desk under **Connectors** first and allow it for **knowledge**.

1. Choose **Help center**, then the connector and **Articles** or **Macros**.
2. Choose how to add them:
   * **Everything that matches**: every article that passes your filters, such as brand, section and language. New articles are added, deleted or unpublished ones removed.
   * **Only the ones I pick**: just the articles you tick. Edits are read, deleted or unpublished ones removed, and new ones are never added.
3. Check the **Title**, which is filled in from the help desk, and click **Create**.

### Google Drive or OneDrive

Read documents through a Drive connector. Go to **Connectors**, add **Google Drive** or **Microsoft OneDrive** (OneDrive also covers SharePoint document libraries), sign in, and allow it for **knowledge**.

1. Choose **Google Drive** or **OneDrive**, then the connector.
2. Choose how to add documents:
   * **Add a folder: include all its documents**. Browse to the folder and click **Add this folder**. Choose whether to **Include subfolders**, and leave out files or folders you don't want. Documents added to the folder later are read too.
   * **Add a list of documents**. Tick the documents you want, from any folder. New documents are never added.
3. Check the **Title**, which is filled in from the folder or connector, and click **Create**.

Aissist reads the drive as the account that signed in to the connector. A document that account can't open can't be added. To fix it, share the document or folder with that account, with at least view access. Files in a shared drive work the same way, as long as that account is a member.

### Website

Read your site's pages directly and keep them in sync.

1. Choose **Website**, enter an address such as `https://help.example.com/` or `https://example.com/help`, and click **Look up**. Aissist finds the pages under it, which takes up to a minute.
2. Choose how to add pages:
   * **Include all the pages under the address** (the default). New pages are added, changed ones updated, and gone ones removed. Leave out pages you don't want, and the pages under them go too. You can also keep only some languages.
   * **Select from the list**. Tick the pages you want from the pages found. New pages are never added.
3. Check the **Title**, which is filled in from the site, and click **Create**.

A website asset holds up to 3,000 pages. For a larger site, enter a subdomain or folder instead, or use **Website search**. If your site blocks bots, allow **AissistBot**: the lookup shows the robots.txt lines to add.

### Website search

Use a website search asset for a site too large to sync. The AI searches the domain when a question needs it, with no page limit.

* Enter the domain **without** `https://`, such as `example.com` or `help.example.com`.
* A subdomain covers only that subdomain. Add subdomains one by one when you do not want the agent to use everything under the main domain.
* Pages are found by web search, so a change appears once search engines re-index the page. This can take minutes or several days. To speed it up, request a re-crawl with [Bing Webmaster Tools](https://www.bing.com/webmasters/url-submission-api) or the [Google URL Inspection Tool](https://search.google.com/search-console/welcome?action=inspect).

<details>

<summary>Single web page and Google Article assets (deprecated)</summary>

These older types are deprecated: they can no longer be added, but existing ones keep working for now. A **Single web page** is read again about once a day. A **Google Article** is read only while the file is shared with **<support@aissistant.io>** or set to **Anyone with the link**.

Use a [Website](#website) asset with **Select from the list** instead of single web pages, and a [Google Drive](#google-drive-or-onedrive) asset with **Add a list of documents** instead of Google Doc links. One asset can hold all the pages or documents. See [the FAQ](https://doc.aissist.io/faq.md#assets-and-sync) for why, and how to move an existing asset.

</details>

### Keep assets up to date

Each asset type syncs on its schedule, shown in the table above. To sync an asset now, open it and click **Sync now**. Saving a change also syncs it. A large website or folder can take several minutes.

Aissist answers from what the asset read at its last sync. A deleted article goes at the next sync. A website page or Drive document that has gone goes after two syncs in a row can't find it. To stop something 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) for more.

### Format your documents

{% tabs %}
{% tab title="Google Doc" %}
Use **headings** to split the document into focused sections, one topic each. This helps the agent retrieve the right part. Use normal text, lists or tables within a section.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FebD7mV79rXwrdd6iA5Wt%2Fgoogle_doc_example.png?alt=media&amp;token=65302ee2-100e-47d0-9143-06bc66e51363" alt=""><figcaption><p>Example Google Doc format</p></figcaption></figure>
{% endtab %}

{% tab title="Google Sheet" %}
Keep sheets simple: narrow, focused tables, one table per tab, with a short description above each table.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FVswPY1jSuSDTZoagZ20i%2Fgoogle_spreadsheet_example.png?alt=media&amp;token=0c663d5d-90b5-4e19-9cf4-e9c268b0916b" alt=""><figcaption><p>Example Google Sheet format</p></figcaption></figure>
{% endtab %}
{% endtabs %}

### Check an asset

Open an asset from the list to see its details:

* **Help center, Drive and Website assets** show their **Synced** or **Selected** badge, what they hold, when they last synced, and every item with how often answers used it. Items that couldn't be read are listed with the reason, and **Not accessible** lists selected items that have gone. Click **Sync now** after fixing a problem.
* **Website search, Single web page and Google Article assets** show three checks under **State**: **Accessible**, **Supported** and **Valid URL**. After fixing a problem, click **Check again**.

The **Assets** list also shows each asset's sub-agents, and lets you enable or disable an asset without deleting it.

### Test with the asset debugger

The asset debugger shows what the agent retrieves for a question, before any reply is written.

1. Go to **Workspace → Assets** and click **Debug**.
2. Type a real customer question or a keyword, such as "how long do refunds take", and click **Search**.
3. Read each result: the passage, where it came from, and its relevance, marked **High**, **Medium** or **Low**. Use **Filter results...** to narrow a long list.

<details>

<summary>Fix common issues</summary>

**The right content does not appear**

* Check the asset is accessible: the page is public, or the document is shared with the connector's account.
* Check the item is in the asset: under its address or folder, not left out, and matching its filters.
* If you added or changed it recently, click **Sync now** on the asset.
* For a website search asset, check the page has been indexed by search engines.
* Add the missing page or document.

**The wrong content appears**

* Remove outdated or conflicting content at the source, then click **Sync now** on the asset.
* Split unrelated content into separate assets.
* Link workflow-specific assets to the matching sub-agents.

**The content is unclear**

* Rewrite the source so policies and steps are explicit.
* Remove duplicated content.

</details>

### Do it with Ask Engine

**Add an asset** is Ask Engine: one sentence is enough, and Ask Engine checks the link, asks you to confirm what to add, and suggests the sub-agents that need it. You review the draft before anything is created.

> Add help.example.com for the Refunds and Shipping sub-agents

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

In **Ask**, you can also check what your knowledge says before a customer asks:

> What do our assets say about the return window for sale items?

Ask Engine searches your workspace's assets and quotes what it found. See [Ask Engine](https://doc.aissist.io/capabilities/ask.md).

### Best practice

* Start with your highest-value sources: help center, policy pages and operational documents.
* Prefer a help center or website asset that syncs over website search. It reads your pages directly and stays current.
* Link workflow-specific assets to their sub-agents, so unrelated content does not crowd a reply.
* Check retrieval in the debugger before you tune instructions. If the knowledge is incomplete or inconsistent, fix that first.

### Related

* [Assets](https://doc.aissist.io/capabilities/assets.md)
* [Add Sub Agents](https://doc.aissist.io/tutorial/add-sub-agents.md)
* [Try](https://doc.aissist.io/tutorial/try.md)
