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

# Moving to the new layout

> What changed for people who used Mission Controls: where each page went, what stays the same, and what to do differently.

Effective is moving everyone to a new layout. Mission Controls are now called **projects**, and the
left sidebar now covers your whole organization instead of one Mission Control. This page is for
people who used the old layout. For what projects are and how to use them, see
[Key concepts](https://docs.canary.effectiveai.app/concepts/key-concepts.md#projects).

## Where things moved

| Old layout | New layout |
| - | - |
| Mission Control | Project |
| Choosing or creating a Mission Control | The **Projects** page: a tile for each project with its description, assets, people, and recent activity. Create projects here. |
| Mission Control addresses (`/mc/<id>`) | Project addresses (`/projects/<id>`). Old links still open. |
| A sidebar for each Mission Control | One sidebar for your organization: Projects, Apps, Pinned, and Records, then the directory, data, and organization sections |
| **Overview** | The project's home page: a chat box, plus the project's chats, shown for the team or just yours |
| **Procedures**, **Apps**, **Skills**, **Assets** | The details panel on the project's home page, which also lists newsletters |
| **Records**, inside a Mission Control | **Records** in the left sidebar, for your whole organization: the types you've pinned or viewed recently, plus All records |
| Members and settings | The top of the project's home page |
| Mission Control Vault | Project vault |

## What stays the same

A project is the same thing a Mission Control was. Each one keeps its access boundaries, its members
and admins, the skills, apps, and procedures installed in it, its ContextBase, and its vault. Your
chats, outcomes, assets, and records keep the same access.

The API keeps the Mission Control name. Scopes stay `mc:<UUID>`, the
`X-Effective-Mission-Control-Id` header is unchanged, and filing responses still report a Source
Mission Control.

## What to do differently

* **Start with a chat.** For most work, just chat with the agent from the chat page; you don't need a
  project. Start a project when you want the agent to work with specific context or knowledge you
  share with your team.
* **Open a project from the sidebar.** Go to **Projects**, or pin the projects you use most from their
  tiles so they stay under **Pinned**.
* **Find a project's procedures, apps, skills, and assets on its home page**, in the details panel,
  instead of in the sidebar.
* **Find records under Records in the left sidebar**, not inside a project. Pin a record you use
  often to keep it under **Pinned**.
* **Pick the project when you start an outcome from the chat page.** Turn on **Outcome** in the chat
  box, then choose the project it belongs to. An outcome started from a project's home page goes in
  that project.


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