> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usesyndicate.org/llms.txt
> Use this file to discover all available pages before exploring further.
# Create your first team
> Create a team, choose a working directory, and send Atlas a first task.
This guide gets you to a running team and shows the choices you make along the way. A team includes Atlas, the Manager, plus specialist agents that share one working directory.
Click **+** next to **Team Hub** in the sidebar (or press **Ctrl+K** and choose **Create New Team**). The wizard asks "How would you like to get started?" with three options: **Generate Team**, **Starter Templates**, and **Start from Scratch**.
Pick the path that matches how much control you want:
* **Starter Templates**: choose a pre-built roster such as **Application Developers** or **Research Analysts**. All six templates are described in the [template reference](/reference/team-templates).
* **Generate Team**: describe your project and let Atlas propose a roster. Choose a **Team model**, write the **Project Description**, then click **Generate Team**.
* **Start from Scratch**: start with only Atlas and add specialists yourself. The **Solo Agent** option in this path branches to [Create a solo agent](/guides/create-a-solo-agent).
Choose **Starter Templates** for your first team unless you already know the exact roles you need.
The **Your Team Roster** screen shows the Manager row (always included) and each proposed agent with a checkbox. Here you can:
* Edit the **Team Name**
* Toggle agents on or off
* Click **Edit** on any agent to change its name, specialization, or model
* Expand **Skills (N)** to see what each agent comes with
* **+ Add Agent** to bring in more specialists
Click **Create Team** when the roster looks right. At least one specialist must be selected. If a selected model is unavailable because its provider disconnected, Syndicate resolves it to the first available connected model.
Pick the local folder the team will work in: **Choose where your team's project files live.** An existing project folder or an empty one both work. Agents read, write, and run commands inside this folder.
If it is a real project, make sure it is a Git repository first, so every agent change is reviewable.
Use **Team Settings** to choose how often Atlas asks before delegating or opening new work. **Balanced** is the best starting point. Move toward **Minimal** once you trust the team, or toward **Hands-on** / **Manual** for risky work.
Open the **Chat** tab and give Atlas a clear, bounded goal:
> "Read this project and produce a prioritized improvement plan. Do not change any files yet. Flag anything you need from me."
Atlas plans, creates tasks, and delegates. Watch the Dashboard canvas light up as agents start working.
## Verify everything is working
* Agent tiles show green **Active** dots while working.
* **Agent Tasks** fills with tasks and owners.
* Questions for you appear in **User Tasks**.
* The **Files** and **Activity** trays show exactly what agents touched.
* Attached documents that live outside the working directory appear in **Uploads**.
## Creation paths in detail
| Path | Use it when | Notes |
| ---------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------- |
| **Starter Templates** | You want a known-good roster quickly | Templates load complete teams with roles, models, and skills already chosen |
| **Generate Team** | You can describe the project but do not know the right roles | Atlas proposes the roster from your description |
| **Start from Scratch** | You know the exact specialists you want | Starts with Atlas; add agents one by one |
Every agent needs a model from a connected provider. With no providers connected, the wizard asks you to connect a provider before generating or launching a team.
## Next steps
Briefs, slash commands, task assignment, and interruption levels.
Dashboard, tasks, Atlas, and team controls.