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

# Brain

> Give Quivly reusable company and customer knowledge, and inspect the sources behind it.

Brain holds the context your team wants Quivly to reuse: what your company does, who you serve, product terminology, account background, and reference documents. Open **Configuration → Brain**.

Use connected integrations for live CRM, revenue, support, and usage records. Use Brain for the explanations and documents that help Quivly interpret those records. A [Skill](/product/skills.md) defines a repeatable task; Brain supplies knowledge that can be useful across tasks.

## Start with your company context

The organization context section has six subjects: **Who we are**, **Users**, **Buyers**, **Problem we solve**, **Ideal customer profile**, and **Market priorities**. Choose **Add** or **Edit** beside a subject and save guidance in plain language.

Include conditions and exceptions. For example:

> Our users are customer success managers at subscription software companies. Treat a customer opening a new region as a potential expansion signal, but do not assume that hiring alone means they need more licenses.

This context also helps Quivly assess the relevance of [market signals](/market-signals/configuration.md). Saving context does not turn on monitoring; configure that separately under [Notifications](/settings/notifications.md).

## Add knowledge or a document

**1. Choose where it applies**

Select company knowledge or a specific customer. Keep company-wide guidance separate from account-specific facts.

**2. Add a source**

Select **+ Knowledge**. Enter text or Markdown in **Guidance**, or choose a file to upload. Check **Applies to** before saving. Each source uses either guidance or a file.

**3. Save and check processing**

Select **Save guidance** or **Upload file**. Open **Sources** to check processing. Uploaded documents become available after processing; authored guidance can be used directly while its extracted knowledge is being prepared.

Supported uploads are text, Markdown, and PDF files up to **25 MB**. PDFs must contain readable text and have no more than **200 pages**. Split large documents into smaller sources if processing reports a limit.

### Save selected Slack content

Where your workspace's Slack app exposes **Send to Quivly**, use it from a message's shortcuts menu to deliberately capture that message and supported attachments or linked documents. A mapped customer channel supplies the customer destination; otherwise, choose company knowledge or a customer when prompted.

The receipt links to each source's processing status. Receipt of a source does not mean its document has finished processing. If a linked resource needs access or uses an unsupported format, check the relevant connection or upload a readable copy. This shortcut does not turn your entire Slack history into shared Brain knowledge.

## Find knowledge and verify its evidence

* **Knowledge** shows supported facts. Search for a fact or source title, then open a result to inspect the original excerpt.
* **Sources** shows the underlying guidance and documents, including their processing status. Search here by source title.
* Use the company/customer filters to keep the account context clear.

Open a source to read its **Content**, **Details**, and **Versions**. Facts can link to source passages or PDF pages. The source map helps you explore the evidence within that source; it is not a map of every relationship in your organization.

Ask Quivly from the Brain page when you want help exploring the available knowledge. Brain context can also inform [Ask Quivly](/product/ask-quivly.md), [notebooks](/product/notebooks.md), [Plays](/product/plays.md), and other AI features within their permitted company or customer scope. Adding a source does not guarantee it will be relevant to every answer.

## Keep sources current

Edit guidance when your business or account context changes. In **Versions**, inspect saved versions, select two to compare, or **Restore** an eligible version. Restoring creates a new revision; it does not erase later history. Original files can be opened or downloaded when available and permitted.

If processing fails, follow the source's guidance: **Retry processing** is available for retryable failures; an unreadable, unsupported, or incomplete upload needs a replacement. A link captured through another member's connection may need that member to retry or restore it.

If someone else changed the source while you were editing, preserve your draft and reload the saved version before resolving the conflict. Do not assume an unconfirmed save failed; use **Retry save** to check it.

## Access and removal

Sources are shared within your Quivly organization, not published to customers. Members can add knowledge and edit active guidance; admins can remove sources. Reprocessing captured links can require the original capture actor. Available controls reflect your permissions.

An admin can choose **Remove source** to stop its content being used in future answers. Removal retains source history; it is not a permanent data-erasure request and does not retract content already copied or delivered. Contact [support@quivly.ai](mailto:support@quivly.ai) for data-erasure requirements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.