Skip to main content
Projects serve as the primary organizational mechanism in Orion. Each project brings together your Chat Conversations and Analyses, along with all the context that supports them — Knowledge Base pages, data sources, uploaded files, memories, and other project-specific details.

​
Personal vs Shared Projects

When you create a new project in Orion, it is automatically private by default until you share it with other team members.
  • Personal (Private) Projects: Any anlsyses, insights, or conversations within the project are only accessible by you (aside from admins).
  • Shared Projects: Projects shared with 1 or more team members. Only those with access to the project can view the contents.

​
Creating a Project

Create new project dialog in Orion

​
Project Name

Give your project a descriptive name that reflects its purpose (e.g., “Marketing Strategy”, “Q4 Sales Analysis”, “Customer Churn Research”).

​
Project Description

The project description helps you and your team quickly understand what the project is about. This short (250 character description) appears in the project list and is intended for human readers—it’s different from Project Instructions, which provide rich context for Orion.

​
Next Steps After Creating a Project

Once you have created a new project, it will appear in the left-hand navigation menu and on the main projects page. Click into your new project to complete the setup. A dialog will appear prompting you to select a data source for the project. A project must always be connected to at least one data source to work.
Get started with new project dialog showing data source selection

​
Selecting a Data Source

The next modal displays a list of available data sources that have been connected by your Admin. Select one by enabling the toggle switch.
Select data source modal with available data sources

​
Accessing Project Settings

The Project Settings modal is always accessible by:
  • Clicking the Settings button in the top right corner of your screen, or
  • Clicking the three dots on the project item in the left-hand navigation menu and selecting Project Settings
From Project Settings, you can:
  • Update the project name, description, and instructions
  • Change the selected data source at any time

​
Memory Isolation

Memory isolation is enabled by default for all new projects.
When memory isolation is enabled, any memories formed by Orion within this project remain contained to the project itself. These memories will not be accessible in other chat conversations or analyses outside the project. Disabling memory isolation allows memories formed within this project to be accessible across other projects. This is useful when you want Orion to recall memories from one project in order to inform work in another.

​
Project Instructions

Project Instructions are best used for project-specific details and preferences, rather than broad company context. With the Knowledge Base available, you can now organize company-wide context into granular, reusable pages and enable only what’s relevant for each project.

​
What to Include in Project Instructions

Reserve Project Instructions for information specific to this project:

Project Scope

What this specific project is analyzing and its goals

Project-Specific Preferences

How Orion should approach analysis for this particular project

Analysis Constraints

Specific rules or limitations for this project

Project Stakeholders

Who cares about this project and any specific preferences

​
Using Knowledge Base Pages Instead

For company-wide context like metrics, definitions, processes, and methodologies, enable relevant Knowledge Base pages instead of duplicating content in Project Instructions. This approach:
  • Keeps context organized - Structured in your Knowledge Base with a clear folder hierarchy
  • Enables reuse - Use the same pages across multiple projects without duplication
  • Simplifies updates - Update context once in the Knowledge Base, not in every project
  • Improves focus - Enable only 8-10 pages per project to keep Orion focused
Example:
  • ❌ Don’t put a dense list of metrics definitions in Project Instructions
  • ✅ Instead, create a “Key Metrics” page in your Knowledge Base and enable it for this project

​
Example Project Instructions

Here’s a concise example showing how Project Instructions should look after moving company context to the Knowledge Base: 
# Q4 Sales Analysis - Project Instructions

## Project Scope
We're analyzing Q4 sales performance to identify top-performing regions,
product categories, and customer segments.

## Goals for This Analysis
- Identify regional performance trends
- Analyze product mix shifts
- Understand customer acquisition costs by channel

## Analysis Approach
- Focus on year-over-year comparisons (Q4 2023 vs Q4 2024)
- Segment analysis by: geography, product tier, customer cohort
- Highlight anomalies and recommend actions

## Project-Specific Constraints
- Only include data from our North American operations
- Exclude test/demo transactions
- Report findings in executive summary format (max 2 pages)

## Context from Knowledge Base
This project has Knowledge Base pages enabled for:
- Sales Metrics & KPIs
- Revenue Recognition Policies
- Regional Structure & Territories
Notice this is much shorter and focused on project-specific guidance. Company-wide context lives in Knowledge Base pages, reducing duplication and maintenance burden.

​
When Project Instructions Are Still Useful

Keep Project Instructions lean and focused on these project-specific details:
  • Unique project goals - What makes this project different
  • Analysis preferences - How Orion should approach this specific analysis
  • Reporting format - Style preferences for this project’s outputs
  • Data constraints - What data should/shouldn’t be included
  • Stakeholder context - Who’s involved and what they care about

​
Enabling Knowledge Base Pages

The Knowledge Base is the recommended way to provide your project with structured, organized context. By enabling Knowledge Base pages for your project, Orion gains access to your organization’s centralized documentation. From the Project Settings modal, click on the Knowledge Base tab to enable pages for this project.
Knowledge Base tab in project settings modal

​
How to Enable Pages

  1. Browse or search for Knowledge Base pages in the catalog
  2. Enable the pages you want Orion to have access to for this project
  3. Save your changes
By default, Orion has no access to any Knowledge Base pages until you explicitly enable them.

​
Best Practices for Knowledge Base in Projects

  • Keep it focused - Enable 8-10 pages maximum per project to keep Orion focused on relevant context
  • Enable strategically - Only enable pages that are directly relevant to this project’s analysis
  • Stay organized - Use your Knowledge Base folder structure to find related pages
When you enable Knowledge Base pages, Orion will:
  • Include them throughout its analysis workflow
  • Cite them with inline references in your reports, dashboards, and other deliverables
  • Reference them throughout your chat conversations
  • Use them to inform analytical decisions and methodology
Knowledge Base pages provide the foundation of structured context that Orion uses across chat and analysis. Combine them with file uploads for comprehensive context coverage.

​
Uploading Files to a Project

In addition to Knowledge Base pages, you can upload files to provide Orion with detailed reference materials and long-form documentation. From the Project Settings modal, click on the File Uploads tab.
File uploads tab in project settings modal

​
When to Use File Uploads

Project file uploads are ideal for long-form, unstructured documents, especially:
  • Dense PDFs - Research reports, whitepapers, or detailed analyses
  • Documents with images and charts - Anything with visual content or complex formatting
  • Transcripts and notes - Meeting recordings, interview transcripts, or detailed notes
  • Complex layouts - Documents that are difficult to structure into Knowledge Base pages
File uploads are primarily used within chat conversations for specific reference and research, rather than being integrated throughout your analysis workflow like Knowledge Base pages.

​
Supported File Types

Orion currently supports the following file formats for project document uploads:
  • Markdown (.md, .markdown)
  • PDF (.pdf)
  • Word Documents (.docx)
  • Plain Text (.txt)
Excel spreadsheets are not currently supported for file uploads, but we’re actively working on adding Excel support in an upcoming release. For spreadsheet data, consider uploading to the Knowledge Base as structured pages instead.

​
Common Examples of Project Files:

  • Research reports and whitepapers
  • PDF analyses and detailed documentation
  • Meeting transcripts and interview recordings
  • Competitor analysis documents with images
  • Industry reports and market research
Use file uploads for dense, reference-heavy documents. Use Knowledge Base pages for structured, reusable context that Orion should consistently apply to your project.

​
Comparing Knowledge Base Pages and File Uploads

Both provide context to Orion, but serve different purposes:

Knowledge Base Pages

Structured context (metrics, definitions, procedures) used throughout chat and analysis workflow

File Uploads

Long-form documents (PDFs, transcripts, historical reports) used for specific reference in chat

​
Cloning Projects

Within shared projects, you have the ability to clone projects. This is useful when you want to reuse the same project settings, data sources, and file uploads from an existing project. For example, if you’re using a project for customer-facing analytics reporting and want to use the same project configuration for a new use case, you can simply clone everything from the original project.
Clone project option in project dropdown menu
Memories from an isolated project will not automatically copy into a cloned project. Each cloned project starts with its own isolated memory.

​
Sharing Projects

You can share projects with individuals who have Orion accounts. To share a project, click the share button in the upper right-hand corner of the project interface.
Share button in upper right corner of project interface
Shared projects enable collaboration and allow you to work together with your team members on analyses.

​
Project Permissions

Orion supports three different user roles with varying levels of access and permissions:

Admin

Can control who has access to projects. Admins can assign users to projects from the Manage Users tab and have full control over project access.

Analyst

Can do just about anything within a project, including chatting with the project and sharing projects. The only limitation is that analysts cannot add existing users to other projects.

Viewer

Can view projects that have been approved and view insights that have been approved. Viewers have read-only access to approved content.