> ## 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, to Looker and dbt for existing business logic, and to a small set of external-context sources, and it lets teams ask questions in natural language to get shared analyses, dashboards, reports, and slide decks. The Connecting Data Sources page is the authoritative list of supported sources. 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.

# Structured Context

> Shared tables that people and Orion both read and write

Structured Context is a kind of Context page that holds tables as well as text. A page has a Markdown introduction, typed tables of records, and saved queries that show up as cards. Use it for trackers, decision logs, plans, and inventories that change over time and that both people and Orion need to see.

A plain [Context page](https://docs.runorion.com/core-concepts/knowledge-base.md) holds guidance Orion reads. A Structured Context page holds records Orion can read and also update, with every change recorded.

> [!NOTE]
>
> Structured Context is available on select workspaces. Ask your Gravity contact to enable it. Where it is not enabled, a page of this type shows "State pages are not enabled." The screens still say "state page" in places.

## Creating a Page

Go to **Context** in the left-hand navigation menu and select **+** in the page tree header. The menu offers **New folder**, then a **New state page** group with one entry per template:

| Template | What it starts with |
| - | - |
| **Blank** | No tables. You define your own |
| **Mission** | Objectives, milestones, and decisions with owners and status |
| **Orchestrator** | Workstreams linked to pages, artifacts, and workflows, plus contacts |

Enter a page title and pick a **Project**, then select **Create**. Orion uses the page in chats of the project you pick. With **No project (Orion cannot use it yet)**, the page is not enabled on any project, so Orion does not use it in chats.

## Reading a Page

A Structured Context page has four tabs:

| Tab | What it shows |
| - | - |
| **Data** | The rows of each table. Add a row, edit a cell, or delete a row |
| **Tables** | The structure: tables and columns, which you can add to |
| **Explore data** | A box for a read-only query, with **Run** and **Save as view**. Saved views are listed beside it, and a view can be pinned |
| **History** | The latest 50 writes to the page, with each status and who made it |

&#x20;**Download data** saves the page as a `.sqlite` file, and  **Refresh** reloads it. Orion writes appear in **History** with an **Orion** badge beside the name.

## Controlling Who Can Change It

Two controls at the top of the page set the rules. Only the page owner or an admin can change them.

**Structure** is either open or locked. When it is open, anyone who can edit the page can change tables and columns. When it is locked, others can propose table changes and the owner or an admin approves them in **History**.

**Data: Open**, or another mode from the **Who can change rows** menu, sets who can change rows:

| Setting | Who can change rows |
| - | - |
| **Open** | Anyone who can edit the page, and Orion |
| **Append only** | Others can add rows. Only the owner can change or delete them |
| **Humans only** | People can change rows. Orion can read but not write |
| **Locked** | Only the owner or an admin |

## Reviewing and Undoing Changes

**History** lists each write with its status: **applied**, **queued**, **rejected**, or **needs approval**. A change that needs approval waits there. An owner or admin selects **Approve** to apply it.

An applied write that can be undone has a **Revert** button. When the revert would change table structure and the structure is locked, the button reads **Request revert** and the request goes to the owner.

An owner or admin can also restore the whole page to an earlier version. Enter a version number under **History** and select **Rewind**, or use the restore button on a row. The restore is recorded as a new version, so it can be undone.

## Using a Page's Rows in an Analysis

Ask Orion in chat to analyze a table, a saved view, or a query from a page the project uses. Orion loads those rows into the analysis notebook. One load is capped at 100,000 rows, so narrow a larger table with a saved view or a query first.

Rows pulled into a notebook are a snapshot by default. A scheduled report then keeps the rows of the day it was built. Ask Orion to make the source follow the page instead, and every run re-reads the page's current rows. Keep the snapshot where the numbers have to stay as they were reported. Follow the page where the report answers where something stands now, and expect each run to differ.

A followed source reads the page as the run-as user, so page access is checked on every run. That person needs access to the page in this project, and so do you when you save the source.

To tell which one a scheduled analysis got, open its notebook step in the workflow builder and read the step's source list. A followed source is listed as **State page** and says it reads the page's current rows on every run. See [Workflows](https://docs.runorion.com/core-concepts/workflows.md) to put the analysis on a schedule.

## Using It From an Assistant

An MCP assistant can find, read, and write these pages with the [Structured Context tools](https://docs.runorion.com/mcp/tools.md#create_state_page). A write is complete only when its status is `applied`. See [Reading the write receipt](https://docs.runorion.com/mcp/tools.md#reading-the-write-receipt).


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