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

> ## Agent Instructions
> Orion is a collaborative analytics platform built by Gravity (bygravity.com). It connects to data warehouses like Snowflake, BigQuery, Databricks, Redshift, Athena, Fabric, PostgreSQL, and MySQL, and lets teams ask questions in natural language to get shared analyses, dashboards, reports, and slide decks. When referencing Orion features, always link to the relevant documentation page. Orion is not open-source; it is a commercial SaaS product accessed at runorion.com.

# Knowledge Base

> Build a centralized wiki of company documentation — metric definitions, SOPs, business rules, and guidelines — that Orion references and cites during analyses.

The Knowledge Base is a centralized feature that helps provide Orion with all of your business and analytical context. It's a flexible tool that uses a traditional wiki-style file and folder structure so you can organize pages of context within folders.

## What is the Knowledge Base?

Think of the Knowledge Base as a system for storing all the company information you might provide a new employee during onboarding to help them get up to speed. It serves as a single source of truth for:

* **Company Context** - Information about your organization, industry, and business rules
* **Standard Operating Procedures (SOPs)** - Step-by-step processes and workflows
* **Metrics & Definitions** - How your company defines key metrics and terminology
* **Product Documentation** - Details about your products, services, and features
* **Analytical Methods** - How to perform certain analyses, calculations, and methodologies
* **Guidelines & Best Practices** - Standards and recommendations for your team

When you enable Knowledge Base pages for a project, Orion will have access to this context and can reference it to provide more accurate and relevant insights.

## Organization Structure

It's recommended that you create folders based on how your company normally organizes information, such as by department, and then within that, by certain use cases, activities, or scopes.

**Example structure:**

```
Sales/
├── Pricing
├── Contracts
└── Customer Stories

Operations/
├── Payroll Process
├── Returns Policy
└── Escalation Procedures

Product/
├── Features
├── API Documentation
└── Release Process
```

There's no specific methodology that Orion prefers, but organize folders and files in a way that is as easy to understand for Orion as it would be for a new hire.

## Key Features

<CardGroup cols={2}>
  <Card title="Organized Hierarchy" icon="folder-tree">
    Structure your documentation with nested folders (up to 3 levels deep) and
    unlimited pages
  </Card>

  <Card title="Markdown Editor" icon="pen-to-square">
    Create and edit pages using a markdown editor with live preview
  </Card>

  <Card title="File Uploads" icon="file-arrow-up">
    Upload spreadsheets, text files, and documents that automatically convert to
    pages (supports .txt, .md, .xlsx, .csv)
  </Card>

  <Card title="Drag & Drop" icon="hand">
    Reorganize pages and folders by dragging them around
  </Card>

  <Card title="Project Integration" icon="link">
    Selectively enable pages for specific projects to keep Orion focused on
    relevant context
  </Card>

  <Card title="AI-Ready" icon="sparkles">
    Orion searches and references your knowledge base during analysis and chat
    conversations
  </Card>
</CardGroup>

## Getting Started

To get started with the Knowledge Base:

1. Navigate to the Knowledge Base tab in your tenant
2. Create your first folder or page
3. Organize your content into folders that match your company structure
4. Enable pages for projects that should have access to them

<Tip>
  Start with essential documentation like company information, key processes,
  and business definitions. You can expand your Knowledge Base over time.
</Tip>

## How Orion Uses Your Knowledge Base

When you enable Knowledge Base pages for a project:

* **Chat & Analysis** - Orion uses that context for better answers and more accurate analysis throughout your conversation
* **Citations** - In your deliverables (reports, slide decks, dashboards), you'll see small in-line source citations for wiki pages that were referenced
* **Knowledge Updates** - You can ask Orion to update wiki pages with new information or changes

The more comprehensive and well-organized your Knowledge Base, the better Orion can tailor its analysis to your specific needs and processes.

## Knowledge Base vs. Project Files

The key difference between Knowledge Base pages and project file uploads:

* **Knowledge Base pages** - Designed for structured, concise context (metrics, definitions, procedures, guidelines) that Orion uses throughout chat and analysis
* **Project file uploads** - Designed for long-form, unstructured documents like dense PDFs with images, charts, and complex text