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

# Knowledge Base

> Organize reference files and make them available as task context.

Knowledge Base gives related requirements, designs, procedures, and other reference material a shared home. Use a focused knowledge base when a task needs stable context that does not belong in the code repository itself.

## Find or create a knowledge base

1. Select **Knowledge Center** in the sidebar.
2. Open the **Knowledge Base** tab.
3. Search by name or use **All workspaces** to narrow the list. Switch between **Grid view** and **List view** if needed.
4. Open an existing knowledge base, or select **Create knowledge base**, enter a name, and choose its effective scope: **User** or **Workspace**.

Use one knowledge base for one product, project, or stable topic. Separating unrelated policies and designs makes the source list easier to maintain and the retrieved context easier to verify.

## Add and review files

1. Open the knowledge base.
2. Select **Add knowledge**, then choose the local files that belong to this knowledge base.
3. Use **Search files** to find a source. Sources are grouped in the file list, and selecting one opens its preview area.
4. When available for the selected source, switch between **Rendered Markdown** and **Markdown source**, copy the Markdown, or download the file.

The upload dialog supports PDF, Word, Excel, PowerPoint, Markdown, TXT, CSV, HTML, and common image formats. Each file can be up to 500 MB. After adding material, confirm that the expected files appear and can be opened. A source that cannot be previewed should be checked at its origin before it is relied on in a task.

## Use it from a task

Use the knowledge base from a task within its effective scope. In the instruction, name the knowledge base and describe the expected result—for example, “Use the onboarding knowledge base to check this implementation against the release checklist.”

For important work, ask a question whose answer is easy to locate in the source. This confirms that the intended material is available before you rely on it for a larger change.

## Maintain useful knowledge

- Use names that make the scope obvious to other users.
- Remove or replace outdated files instead of leaving unexplained conflicting versions.
- Keep an authoritative source for policies, interfaces, and operational procedures.
- Recheck task results against current code, configuration, and runtime behavior.

<Warning>Do not add production credentials, personal data, or information you are not authorized to share.</Warning>