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

# Squads Fundamentals

> What a Squad is, how members coordinate, and when to use one on the Mesh Canvas

## Overview

A **Squad** is how you group Digital Employees around one initiative on the **Mesh Canvas**. Squads appear as their own nodes — open one to see members, shared files, and run controls in the **Squad panel**.

In Cowork you always work with **Squads**, not a separate “Project Rooms” screen. Behind the scenes, each Squad uses a shared container for membership and files; you do not manage that container directly.

## What a Squad includes

* **Name and color** — identify the squad on the canvas
* **Up to 8 members** — Digital Employees only; each employee can belong to one active squad at a time
* **Optional lead** — one member you mark as lead when someone should own the final output
* **Shared working document** — created automatically; the squad’s living deliverable
* **Execution mode** — how members coordinate when the squad runs (see below)

## Execution modes

| Mode               | Best for                                             |
| ------------------ | ---------------------------------------------------- |
| **Individual**     | Members work independently on their own slice        |
| **Parallel**       | Members work at the same time against shared context |
| **Linear handoff** | Pipeline: each member builds on the previous one     |
| **Review board**   | Members critique a shared draft                      |
| **Debate**         | Members argue positions, then converge               |
| **Standup**        | Status-style updates across members                  |
| **Brainstorm**     | Open ideation round                                  |
| **War room**       | Focused, high-intensity problem solving              |

**Output format** tells the squad where results go:

* Update the **shared working document**
* Create a **new document** on the mesh
* **Review only** — feedback without changing the working document

<Tip>
  There is no fixed “Orchestrator / Specialist / Validator” role set. Every member participates the same way unless you designate a **lead**.
</Tip>

## Common use cases

* **Research + synthesis** — several employees gather input; the lead (or last handoff) produces the report in the working document
* **Review board** — a draft passes through multiple reviewers
* **Recurring rituals** — standup or war-room modes on a schedule via [Squad runs](/en/cowork/squads/squad-runs)

## Tips

* Start with **2–3 members** before scaling toward the 8-member cap
* Use a **lead** when one employee should own the final deliverable
* Keep the **working document** as the single source of truth for the squad’s output

## Next steps

* [Create a Squad](/en/cowork/squads/squad-creation)
* [Squad runs](/en/cowork/squads/squad-runs)
* [Documents on the mesh](/en/cowork/artifacts/artifacts-overview)

## Other languages

* [Português (BR)](/pt/cowork/squads/squads-fundamentais)
* [Español](/es/cowork/squads/squads-fundamentales)