> ## 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. # Warp Drive > Answers drawn only from content your team already approved Warp Drive is a project mode where Orion quickly returns governed answers from approved material like metrics, scheduled deliverables, and Knowledge Base pages. Ordinary chat can reach past those sources into your warehouse. Warp Drive does not. Turn it on for projects where business users ask well-understood questions and expect immediate responses. A finance project holding a handful of signed-off metrics is a good fit. An exploratory project where analysts are still shaping the data is not. ## What Orion Can Answer The name describes the speed, but Warp Drive is also a governance policy. The speed follows from the smaller boundary, because Orion retrieves from approved material instead of exploring your data sources. These sources sit inside the boundary: | Source | What it covers | | - | - | | **Knowledge Base** | Pages enabled for the project | | **Project documents** | Files uploaded to the project | | **Catalog metrics** | Metric definitions published to the Metrics Catalog | | **Project metrics** | Metrics saved on the project | | **Reports and dashboards** | Deliverables already built in the project, read from saved output | | **Workflow outputs** | Output from a completed run of a project workflow | | **Project memory** | What Orion has been asked to remember | | **Conversation history** | Earlier chats in the project | Orion can still run a query in this mode, as long as somebody defined it first. Executing a saved metric or a catalog metric is allowed, because its definition was already reviewed. Writing new queries is not. Everything else sits outside the boundary: warehouse queries, Looker Explores, notebooks and Python, and the creation of dashboards, reports, and slide decks. Warp Drive is read-only, so it cannot edit a Knowledge Base page, a metric, or a workflow either. ## Turning Warp Drive On Warp Drive has its own tab in [Project Settings](/core-concepts/projects#accessing-project-settings). An empty project cannot turn it on. Orion needs a foundation of approved content first. **Readiness checks** lists the three requirements. Each row shows how many sources the project has against how many it needs, under the line "Checked automatically from project content." Until all three pass, the tab shows **Locked** instead of the on and off control. Once the project is ready: 1. Switch **Warp Drive** on 2. Choose a **Full Analysis access** policy 3. Click **Save Changes** ## Full Analysis Access Full Analysis is the way out of the boundary. It reruns the question with the tools and the model ordinary chat uses, and it stays selected for the rest of the chat. **Full Analysis access** decides who is allowed to do that. The tab puts the choice as "Choose who can ask questions with Full Analysis when Warp Drive isn't enough." | Option | Who can run Full Analysis | | - | - | | **No one** | Nobody. Orion names a project owner instead | | **Project owners, analysts, and admins** | The project team. This is the default | | **Anyone with project access** | Everyone who can open the project | Choose according to how far you trust the approved content to cover what people will actually ask. ## What You See in Chat When Orion cannot answer from approved content, it replies with one of the following information cards: | Card | What happened | | - | - | | **Deeper analysis needed** | The request needs tools outside Warp Drive | | **Not enough approved information** | Orion checked the approved sources and could not support an answer | | **Answer requires deeper analysis** | Orion drafted an answer, but some claims in it need a deeper check | Where Orion read something before giving up, the card carries **Sources checked**, listing what it read. Named deliverables, metrics, and Knowledge Base pages link out so they can be inspected. Where a draft was written and then rejected, the card also shows the draft. Orion keeps it so you can see what it nearly said and which claims it wanted to test. It is not an approved answer, and Orion does not treat it as context in later chats. If your access policy allows it, the card offers **Run Full Analysis**. Where it does not, the card names the project owners, so you know who to ask for help. ## Who Can Change These Settings Changing the mode or the access policy needs one of the following: * A tenant admin or analyst with access to the project * A project owner * An admin of a group that has the project Roles are covered in full under [Groups](/configuration/groups#roles-at-a-glance). ## Next Steps Build the approved context Warp Drive reads from Define the numbers Orion is allowed to execute Where the Warp Drive tab lives Turn a recurring answer into a scheduled deliverable This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.