How to upload knowledge in Assist

What you'll learn

The easiest way to give Assist long-term context is to drag a file straight into the chat and tell it what the file is. That single action — drop and describe — is enough for Assist to save the file as reusable knowledge. Once it's saved, Assist can pull it into any future chat automatically, or you can call it up yourself with an @ -mention.

What you'll learn

• How drag-and-drop upload works
• How describing the file turns it into saved knowledge (not just a one-off attachment)
• How Assist decides whether to save to project or workspace scope
• How tags get applied and why they matter
• How to find and reuse uploaded knowledge later

Quick recap: what "knowledge" means in Assist

Knowledge is persistent reference material — documents, guidelines, transcripts, URLs — that Assist can pull into any future chat. It lives at one of three tiers:

• Project — visible only within a specific project
• Workspace — available to everyone in the workspace, across all projects
• Organisation — available across every workspace in the org (managed by admins via the Library, not via the chat flow)

This is different from a one-off chat attachment. If you drop a file into a message without describing it, the file exists only in that conversation. Saving it as knowledge is what makes it reusable.

Before you start

• Make sure you're in the right workspace.
• If the knowledge belongs to a specific project, scope your chat to that project first. This tells Assist where to save it by default. (If you're not sure how to scope a chat to a project, check the "Manually selecting a project" article.)
• Have the file or URL ready to go.

How to upload knowledge — step by step

1. Open a chat in the workspace or project where you want the knowledge to live.
2. Drag your file into the chat composer. You can also paste a URL directly, or click the attach icon if you prefer to browse for the file. Supported formats include PDFs, documents, images, audio, video, spreadsheets, and more.
3. In the same message, describe what the file is and what it's for. For example: "This is our brand tone of voice guide — save this so we can reference it across all campaign work." The description is what tells Assist this file is worth keeping. Without it, Assist treats the file as a one-off attachment.
4. Send the message.
5. Assist will propose saving it to knowledge. It will show you a suggested scope (the project the chat is scoped to, or it will ask if the chat isn't scoped) and a set of suggested tags based on the file content and your description.
6. Review the suggested title, scope, and tags. Adjust anything that doesn't look right — you can accept the suggestions as-is, edit the tags, or change the scope (for example, switching from project to workspace if the material is relevant to the whole team).
7. Confirm. Assist saves the knowledge item. Done.

The knowledge now appears in the Library under the scope you chose, and Assist will automatically surface it in future chats when it's relevant.

Worked example

Imagine you're working on a Spring Campaign project. You have a PDF of your company's brand guidelines and you want the whole team to be able to use it — not just in this project, but across everything they work on.

Here's what you do:

1. Open a chat. It's currently scoped to the Spring Campaign project.
2. Drag brand-guidelines.pdf into the chat composer.
3. Type: "This is our brand tone of voice guide — save this so we can reference it across all campaign work."
4. Send.

Assist reads the message and detects that you want to save this for future use. Because the description signals that this material is relevant beyond a single project ("across all campaign work"), Assist proposes saving it at workspace scope rather than project scope — so it's available everywhere in the workspace, not just inside Spring Campaign.

Assist suggests tags: brand , tone-of-voice , guidelines .

You review the suggestions. The tags look right. You confirm.

The knowledge item is saved. It now appears in the Library under the workspace tier. Any teammate in the workspace can find it there, and Assist will automatically pull it into context whenever a chat touches brand or tone topics. You can also call it up directly in any chat by typing @brand-guidelines  (or whatever name it was saved under).

Tips & common pitfalls

"I uploaded a file but nothing got saved to knowledge."

You probably didn't describe what the file was. Assist needs context to know the file is worth saving — a bare attachment without explanation is treated as a one-off. Re-send the file with a sentence explaining what it is and what it's for.

"It saved to the wrong scope."

The default scope is the project the chat is scoped to. If you wanted workspace scope instead, tell Assist explicitly in your message ("save this to workspace knowledge") or move it later from the Library.

"My teammate can't see the knowledge I uploaded."

It's most likely saved at project scope and your teammate either doesn't have access to that project, or they're working in a different project. Open the Library, find the knowledge item, and check which scope it's saved under. If it needs to be wider, you can promote it from there.

"How do I edit the tags later?"

Go to the Library, find the knowledge item, and edit the tags there. Note that tags replace rather than append — so if you want to keep existing tags, include them alongside any new ones you're adding.

"Can I upload a URL the same way?"

Yes. Paste the URL into the chat composer, describe what the page is and why it's useful, and send. Assist will crawl the page and save the content as a knowledge item, just like a file upload.

"Do I need to upload the same file to every project separately?"

Not for shared material. Save it once at workspace scope and it's available across every project in that workspace. Only use project scope for material that's specific to one piece of work — briefs, transcripts, references that only make sense in that context.