> ## 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.

# Templates

> Reuse the layout and theming of a slide deck or dashboard

A template is a saved slide deck or dashboard design that Orion builds the next deliverable on. A deliverable carries the numbers from one analysis. A template keeps the layout, theming, and chart structure, and takes its numbers from whatever analysis uses it.

Use a template when the same deck or dashboard goes to the same audience again and again, so every version looks the same. Templates live in projects. A template you save is available in the project you save it in, and you can add it to other projects.

## Save a Slide Deck as a Template

1. Click the slide deck in chat to open it full screen
2. Click **Save as template** in the top bar
3. Enter a **Name**, and optionally a **Description** that says what the template is best used for
4. Click **Save template**

Orion stores a copy of the deck with all data values stripped out. The button then reads **Template saved**, and the template is ready to use in this project.

Interactive dashboards built in chat do not offer **Save as template**. To make a dashboard template, upload an HTML file.

## Upload an HTML Template

Upload a file when you already have a design, such as a deck your brand team built.

1. Click **+** in the chat input, then **Use Template**
2. In **Choose a template**, select the **Slides** or **Dashboards** tab
3. Click the **Upload HTML template** tile
4. Drop an `.html` or `.htm` file on the dialog, or click to browse. The file must be UTF-8 encoded and no larger than 5 MB
5. Check the **Name**, which starts as the file name, add an optional **Description**, and click **Upload template**

The **Saved templates** tab on the dashboard plan card has the same **Upload HTML template** tile.

> [!WARNING]
>
> An uploaded file is stored exactly as you upload it. Orion strips data values
> only from decks saved in chat, so remove real figures before you upload.
> Everyone in the template's projects can preview it.

## Use a Template

Every place you pick a template shows the same tiles. Hover a tile and click **Preview** to see it full size. Click the tile, or **Use this template** in the preview, to pick it.

Where you pick it decides what happens next:

* **+ menu**: **Use Template** inserts the template as a reference in the chat input. Ask for the deck in the same message. Typing `@` and opening **Templates** does the same: see [Basics & Navigation](https://docs.runorion.com/chat/basics-navigation.md)
* **Deliverable card**: after you pick **Slides** in **Choose an output format**, Orion asks how to build the deck. Click **Choose from a template** instead of **Generate from scratch**. This step appears for slides only
* **Dashboard plan card**: click **Browse styles and templates**, then open the **Saved templates** tab. The dashboard borrows the look of the template you pick. See [Dashboards](https://docs.runorion.com/dashboards/overview.md)
* **Workflows**: a **Slides** or **Web page** step can use a template on every run. Set it from **Design template** in the step's Report Configuration: a Slides step takes a slide template, and a Web page step takes a dashboard template. See [Workflow Outputs](https://docs.runorion.com/workflows/outputs.md)

## Rename, Share, or Delete a Template

Open **Choose a template** and click the **...** actions menu on a template's tile:

* **Rename**: change the name and description. The new name shows wherever the template is referenced
* **Add to projects**: check a project to add the template to it, or uncheck one to remove it, then click **Save changes**. The list shows projects you have access to, and **Linked** marks the ones that already have the template
* **Delete**: asks for confirmation, then removes the template from every project it is linked to. Deleting cannot be undone

Adding a template to a project does not copy it. Every linked project shares one template, so renaming or deleting it in one project changes it in all of them. Unchecking every project in **Add to projects** removes it only from the projects you can see, and does not delete it. To remove a template for good, use **Delete**.

If some project changes fail, the ones that succeeded stay. Open **Add to projects** again to retry the rest.

## Who Can Change Templates

Anyone with access to a project can preview and use its templates. Changing a template needs Analyst access or higher to the projects involved:

| Action | Access you need |
| - | - |
| Save or upload | Analyst or higher in the current project |
| Rename or delete | Analyst or higher in every project the template is linked to |
| Add to a project | Analyst or higher in the project you add it to |
| Remove from a project | Analyst or higher in that project |

A **Tenant Admin** can do all of these in any project. The **...** menu appears for everyone, so a Viewer who tries one of these actions gets an error instead.


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