> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mantle.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace knowledge

> Give AI shared instructions, files, and canvases for your team’s work.

**Workspace Context** is the shared knowledge base for a workspace. It gives AI background that should be useful across
that workspace and can include instructions, reference files, and selected canvases.

To manage it, open **Settings**, choose the workspace under **Workspaces**, then open **Workspace context**. Workspace
owners and admins can change the context. Other workspace members benefit from it when they use AI in that workspace.

## How it works

When you ask AI a question in the workspace, Mantle can combine several kinds of context:

1. the messages and attachments in the current conversation;
2. the workspace instructions;
3. relevant parts of ready workspace files and selected canvases;
4. an agent's own instructions, knowledge, and tools when you are using an agent.

Instructions are considered in every AI conversation in the workspace. Files and canvases work differently: Mantle looks
for the parts that are relevant to the current request. It does not send every file in full every time. This keeps
answers more focused and avoids using context that is unrelated to the question.

Workspace Context does not make every answer correct. AI can misunderstand a source or miss an important section. For
important decisions, ask it to name the source and then open that source to check the exact wording.

## Add instructions

Instructions tell AI how to work in the workspace. They are considered in every AI conversation there.

Good instructions are short, specific, and stable. For example:

> Write for business users in plain English. Use our product name, Mantle Chat, in full on first mention. If a source
> does not answer the question, say what is missing instead of guessing.

Do not paste a whole handbook into the instructions box. Put long reference material in a file or canvas instead.

## Add reference files

Upload material that AI may need to answer questions, such as policies, product notes, research, spreadsheets, or FAQs.
Mantle supports common documents, plain text, structured data files, spreadsheets, and images. The upload screen shows
the file types and size limit available on your plan.

After upload, wait until the file shows as ready. Mantle can then use relevant parts when they help with a request.

An attachment in one chat is available to that conversation. A file in Workspace Context can help AI across the whole
workspace. Use Workspace Context only for material that should be reusable.

## Add selected canvases

Canvases must be added to workspace context before AI uses them as shared knowledge. This gives you control over which
living documents influence answers.

Open **Workspace context**, find **Canvases**, and choose the canvases to include. An ordinary workspace canvas remains
a collaborative document but is not automatically shared with AI as reusable knowledge.

Remove a canvas or file when it is obsolete. When facts change, update the source instead of adding a second document
that conflicts with it.

## Ask questions that use knowledge well

Name the source or kind of information you expect. For example:

* `According to our support policy, when can a customer receive a refund?`
* `Compare this proposal with the product principles in our workspace context.`
* `Find the SBI codes in the uploaded company document and quote the surrounding section.`

Ask the model to say when the answer is not in the provided material. For important work, open the source and check the
exact wording.

## Workspace knowledge or agent knowledge?

| Use...                | When the source should...                                            |
| --------------------- | -------------------------------------------------------------------- |
| **Workspace Context** | help many chats, channels, and agents in one workspace               |
| **Agent knowledge**   | help one reusable role, such as a sales assistant or policy reviewer |
| **Chat attachment**   | help only with the current conversation                              |

An agent can use both Workspace Context and its own focused knowledge.

## Keep the knowledge useful

* Prefer a small set of current, trusted sources over many overlapping files.
* Remove old versions instead of leaving conflicting copies.
* Use clear file and canvas names so people can check the source.
* Separate sensitive teams or clients into different workspaces when they should not share context.
* Check the limits shown on the Workspace Context screen. Knowledge and raw file storage use shared organization
  allowances; paid member seats add capacity to those pools.

<Warning>
  Add only material that workspace members are allowed to use. Anyone with access to the workspace may be able to ask AI
  about its shared knowledge. Do not use Workspace Context as a substitute for separating confidential access.
</Warning>