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

# Projects and teams

> Organize issues and sessions by putting them in a project or on a team, from the issue, the session, or a right-click

A workspace organizes its work two ways. A **project** is a body of work with
an end, like "Web app" or "Q4 launch". A **team** is a group of people and
agents, like "Platform". Add either from the plus next to Projects or Teams in
the sidebar.

An issue can be in one project and on one team. So can a session.

## Issues

On an issue's page, the **Project** and **Team** rows in the side rail show
where it is. Click either to choose another, or pick **No project** or
**No team** to take it out. Press **M** on an issue for the project list.

In the Issues list, right-click a row and choose **Project…** or **Team…**.
When several rows are selected, the choice applies to all of them.

**New issue** on a project's page starts the issue in that project. On a
team's page it starts on that team.

A team's page lists the open issues on the team and the open issues assigned
to anyone on it.

## Sessions

A session's page has **Project** and **Team** rows in its side rail. In the
Sessions list, right-click a row and open **Project** or **Team**. The current
choice has a check mark.

A session you have not filed takes its issue's project, and the side rail
says "from its issue". It counts as on a team when someone on the team
started it or took part. Once you choose a project or a team for a session,
that choice wins. Choosing **No project** or **No team** goes back to reading
it from its issue and its people.

**Sessions** at the top of a project's or a team's page opens the Sessions
list filtered to it.

## Synced from Linear

Issues and projects synced from Linear can be filed the same way. Your
choices stay in Orchestra and are never written back to Linear, and the next
sync leaves them as you set them. See [Linear](https://docs.orchestrahq.ai/integrations-linear.md).

## Archiving and deleting

An archived project or team takes nothing new, so it is left out of these
lists until you unarchive it. Deleting a project or a team leaves its issues
and sessions in place, in no project or on no team.

## Who can see what

Anyone in the workspace can see and organize projects and teams. What is in
them is shown only to people who can see it: a restricted issue or session
does not appear in a project's or team's list, and it does not change a count,
for anyone who cannot open it.


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