> 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/turn-assets-into-ai/google-drive.md).

# Google Drive

*Last updated: May 12, 2026*

Use Google Docs and Google Sheets for managed knowledge that changes often.

This works well for policies, procedures, product details, and other content your team updates often.

<figure><img src="/files/RC5HV2BeogoCfsrHvNiI" alt=""><figcaption></figcaption></figure>

### Add a Google Drive asset

Go to **Workspace → Assets** and add a Google Doc or Google Sheet.

Then connect the file you want Aissist to retrieve from.

### Share the file with Aissist

For Aissist to access the file, use one of these options:

* Share it directly with **<support@aissistant.io>**.
* Set it to **Anyone with the link can view**.

<figure><img src="/files/Org7bnZqP8QyDllqPvlw" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ogEdFmmd9zPHFxsxP8h4" alt=""><figcaption></figcaption></figure>

### Choose asset or workspace instruction

These serve different purposes.

* **Workspace Instructions** are global. Use them for rules that apply in every conversation.
* **Google Docs and Sheets** are contextual. Use them for detailed knowledge that should be retrieved only when needed.

Keep instructions short.

Put longer policies, procedures, and reference content into assets.

See [Instructions, Assets, and Sub Agents](/tutorial/instructions-assets-and-sub-agents.md).

### Format your content

{% tabs %}
{% tab title="Google Doc" %}
Use headings to separate topics clearly.

{% hint style="info" %}
Use **headings** to split the document into focused sections. This helps Aissist retrieve the right content.
{% endhint %}

Recommended format:

* use headings for each topic
* keep each section focused
* use normal text, lists, or tables as needed

{% hint style="danger" %}
Images inside Google Docs are not supported yet.
{% endhint %}

<figure><img src="/files/rEF3GJQ4Wf7IDU48bRjA" alt=""><figcaption><p>Example Google Doc format</p></figcaption></figure>
{% endtab %}

{% tab title="Google Sheet" %}
Keep Sheets simple and easy to interpret.

Recommended format:

* keep tables narrow and focused
* use one table per tab
* add a short description above each table

<figure><img src="/files/e9s0mKgY8kx5kfMsGf4c" alt=""><figcaption><p>Example Google Sheet format</p></figcaption></figure>
{% endtab %}
{% endtabs %}

### Best practice

Use Google Docs for narrative knowledge, such as policies and procedures.

Use Google Sheets for structured data, such as pricing, product details, or internal reference tables.