> 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 - website domains, single web pages, and Google Docs, Sheets and PDFs - then test retrieval with the asset debugger.

*Last updated: October 25, 2026*

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

### Asset types

| Type                             | Use it for                                                                          | How it stays current                                                           |
| -------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **Website** (domain)             | A whole help center, documentation site or company site, such as `help.example.com` | Found by web search, so updates appear once search engines re-index the page   |
| **Web page**                     | One public page, such as a return policy or status page                             | Read directly and refreshed every 24 hours, or when you update the asset       |
| **Google file** (Google Article) | Google Docs, Google Sheets and PDFs in Google Drive                                 | Read through Google and refreshed every 24 hours, or when you update the asset |

### 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**, choose **Domain**, **Single Web Page** or **Google Article**, enter the URL, and click **Next**. Aissist analyzes the URL before you finish.

### Website domain

Use a domain asset to search across a whole site.

* Enter the domain **without** `https://`, such as `example.com` or `help.example.com`.
* `example.com` covers everything hosted under that domain. A subdomain such as `help.example.com` covers only that subdomain. Add subdomains one by one when you do not want the agent to use everything under the main domain.
* A public help center, such as one hosted on Intercom or Zendesk, can be added by its domain too.

<details>

<summary>When website changes appear</summary>

Website assets are found by web search. When you update your site, the agent sees the change after 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>

### Web page

Use a web page asset when only one page matters, such as a status page, a return policy or one FAQ.

* Enter the full URL, starting with `https://` or `http://`.
* The page is read directly and refreshed every 24 hours. Updating the asset in the console refreshes it too.
* For a whole site, use a domain asset instead.

### Google Docs, Sheets and PDFs

Use Google files for knowledge your team edits often, such as policies, procedures, price lists and product details.

* The URL must start with `https://docs.google.com` or `https://drive.google.com`.
* A Google file keeps its own name from Google Drive.

#### Share the file with Aissist

Aissist can read the file only when it is shared. Either:

* share it with **<support@aissistant.io>**, or
* set it to **Anyone with the link** can view.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2F7DA3XwccCOnmUufHYtku%2Fgoogledoc-share-2.png?alt=media&amp;token=e6688993-d53f-40b7-998e-f337d5528a44" alt=""><figcaption></figcaption></figure>

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FOCtHgKuYmTCVwHgZuOuy%2Fgoogledoc-share-1.png?alt=media&amp;token=54530b08-af72-4315-b90c-64e274e789c7" alt=""><figcaption></figcaption></figure>

If a file is not shared, the asset shows as not accessible, and the **Assets** page shows a warning until you fix it.

#### Other documents

For Word, Excel or text files, upload them to Google Drive, save them as Google Docs or Sheets, share them as above, and add the link.

#### Format your content

{% 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. **State** shows three checks: **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 Google file is shared.
* For a website, 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.
* 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](/capabilities/ask.md).

### Best practice

* Start with your highest-value sources: help center, policy pages and operational documents.
* Use a domain for broad coverage and single pages for focused, high-value content.
* 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](/capabilities/assets.md)
* [Add Sub Agents](/tutorial/add-sub-agents.md)
* [Try](/tutorial/try.md)