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

# Projects

> Organize chats, standing instructions, and context documents into durable workspaces

Projects are personal workspaces that group related chats together with standing instructions and context documents. Every chat in a project inherits the project's instructions and can read the documents you attach, so you don't have to repeat the same context in every conversation.

<Note>
  Projects are personal to your Omni account. They are not shared with other users, and they never grant access to documents you can't already see.
</Note>

## Why Use Projects

* **Keep related chats together** — a project collects every conversation about the same topic, launch, customer, or initiative.
* **Set standing instructions once** — guidance you'd otherwise paste into every chat is applied automatically to each chat in the project.
* **Attach reference material** — keep key indexed documents available as context across all of the project's chats.
* **Scope your chat history** — browse and search only the conversations that belong to a project.

## Creating a Project

1. Open **Projects** in the sidebar.
2. Click **New Project** (or **Create your first project** on the empty state).
3. Fill in:
   * **Name** — required, and unique among your live projects (case-insensitive).
   * **Description** — optional summary shown on the project card.
   * **Instructions** — optional standing instructions applied to every chat in the project.
4. Click **Create project**.

## Project Instructions

Instructions are included automatically in the system prompt of every chat in the project, alongside Omni's normal guidance. Use them for context and preferences that should always apply, for example:

```text theme={null}
This project is about the Q3 launch. Prefer German responses and reference the roadmap.
```

You can edit instructions any time from the project detail page and save them with **Save instructions**.

## Context Documents

The project detail page has a **Context documents** card. Search for an indexed document and attach it to make it available as standing context in every chat in the project.

Attached documents are provided to the model as pointers rather than pasted into every prompt — the assistant reads the full content on demand with `read_document` when it's relevant. Detach a document at any time with the remove control next to it.

Only documents you already have permission to read can be attached, and project membership never changes a document's permissions.

## Chats in a Project

### Starting a chat

Open a project and click **New chat** to start a conversation inside it. The chat inherits the project's instructions and context documents.

### Moving an existing chat

From an open chat, use the project menu in the chat header to move it into a project, switch it to a different project, or **Remove from project**.

### Deleting a project

Deleting a project is permanent, but it does **not** delete its chats. The chats are kept and move back to **unorganized** so you don't lose their history.

## Archiving a Project

Archiving hides a project from the main list without deleting anything. Toggle **Show archived** on the Projects page to see archived projects, and use **Unarchive** to bring one back. Archived projects are read-only: you can't start new chats or edit instructions and attachments until you unarchive them.

## Permissions

Projects are owned by a single user and are never shared. All project access is mediated by ownership, and projects do not widen source permissions:

* Instructions only affect the model's behavior; they cannot change what the assistant is allowed to read.
* Context documents must be documents you can already access.
* The assistant's document search inside a project is still filtered to your permissions.

This keeps project instructions and attachments safe to use without worrying that they grant access beyond what you already have.

## What's Next

<CardGroup cols={3}>
  <Card title="AI Assistant" icon="robot" href="/user-guide/ai-assistant">
    Learn how to work with the assistant
  </Card>

  <Card title="Search" icon="magnifying-glass" href="/user-guide/search">
    Search across your connected sources
  </Card>

  <Card title="Access Control" icon="shield" href="/user-guide/access-control">
    Understand document permissions
  </Card>
</CardGroup>