> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/brains/overview.md).

# Brains overview

A Brain brings directly uploaded source documents, a maintained Wiki, and contributed facts together around one subject. Use it for personal knowledge or a shared team's reference material, then connect a Q\&A agent when you want answers grounded in that Brain.

> **Availability:** Brain creation and Knowledge Engine features depend on your environment; Brain-backed querying and GitHub export have separate runtime gates. These guides describe current application behavior, not verified deployment availability. See [Feature availability](https://docs.katara.ai/about/reference/availability.md) if a feature is missing or unavailable.

## Understand the three layers

* **Sources** are accepted originals uploaded directly to this Brain. They are not documents attached from an existing collection or corpus.
* **Knowledge** contains committed Wiki pages. Generated narrative can be refreshed from sources; editing generated prose makes it authored and manually maintained.
* **Facts** are attributed contributions with their own active or historical status. A fact's withdrawal does not erase narrative that previously used it.

These layers have different completion checks. An upload accepted for processing is not proof of search readiness. A queued refresh is not a finished Wiki update. A saved export configuration is not a completed GitHub export.

## Choose who can use it

A **Personal** Brain has no Brain audience grants. A **Team** Brain can grant users or groups **Viewer** or **Editor** access. A Team Brain without audience grants is owner-only. Kind is chosen at creation and cannot be changed afterward.

Ownership, contribution and viewing are separate permissions. Organization administration does not automatically grant access to private Brain content. Use the role and actions shown for the selected Brain, rather than assuming your organization role permits every operation.

Original documents can also have additional viewers. That sharing does **not** grant access to the Brain, Wiki or facts. Conversely, removing an additional document grant may leave inherited Brain access intact. See [Sources](https://docs.katara.ai/about/brains/sources.md) and [Settings](https://docs.katara.ai/about/brains/settings.md).

## Follow the main workflow

1. Finish [workspace setup](https://docs.katara.ai/about/start-here/quickstart.md), select the intended organization, and open **Brains**.
2. [Create a Brain](https://docs.katara.ai/about/brains/create.md), choose its kind and audience, and wait for initialization to be ready.
3. [Upload sources](https://docs.katara.ai/about/brains/sources.md). Check accepted files separately from pending or failed uploads.
4. Use [Activity](https://docs.katara.ai/about/brains/activity.md) to request and inspect refreshes. Open [Knowledge](https://docs.katara.ai/about/brains/knowledge.md) to read the resulting pages.
5. If you need to correct knowledge, edit an existing page or [contribute a fact](https://docs.katara.ai/about/brains/facts.md). Those mutations require a validated, enabled Q\&A alias bound to this exact Brain; reading Wiki pages does not.
6. Configure a [Q\&A agent](https://docs.katara.ai/about/agents-and-answering/qna.md) to answer from the Brain. Its saved Brain target cannot later be switched to another Brain or collection.
7. If you need an external copy, review the full-history risks before enabling [GitHub export](https://docs.katara.ai/about/brains/github-export.md).

## Find an existing Brain

The Brains index shows your accessible entries. **Search loaded Brains…** searches the current loaded server page, not every Brain in the organization. Use **Previous** and **Next** when the Brain is not on that page.

Within a Brain, the primary tabs are **Knowledge**, **Sources**, **Activity** and **Settings**. GitHub export is configured inside Settings, not a separate primary tab.

If an entry or action is missing, first check the selected organization and current access. Unknown role or processing metadata means the value was not reported; it does not mean owner access, no work, or successful completion.
