> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/teams/create-a-team.md).
# Create a team
Set up team members, booking hours, and routing readiness.
A workspace contains your organization's people and scheduling configuration. Teams group the people who can receive particular meetings.
Invite people through **Invite members** or manage membership in **Settings → Members**. Give each person the access they need. Ask new members to connect their calendar and check their availability before adding them to live routing.
Open **Teams** to compare members, timezone, availability, and the rules or routers using each team. Select a team to review its configuration.
## Create a team
Open **Teams → New Team**. Enter the **Team name**, select the **Booking timezone**, and choose the **Reps** who should receive meetings. Set the days and hours in **When can prospects book?**, then click **Create team**.
For example, keep an enterprise sales team separate from a customer success team when they handle different conversations. You can add people later, but a team needs eligible hosts before it can receive meetings.
To update an existing team, select its name, review the same settings, then click **Save team**.
## Before using a team in routing
Check membership, calendars, working hours, and the event type's availability source. If the event type uses team hours, changing only a person's weekly schedule may not give the result you expect.
Then select the team in the router's distribution or fallback configuration. Test the saved router draft and activate it when ready.
Being a team member and being allowed to start an outbound handoff are separate settings. For an Outbound Router, review **Access and allowed bookers** as well as the people eligible to host.
When someone leaves or changes roles, review their routing participation, group booking links, and any reusable outbound links they own.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.distro.so/teams/create-a-team.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
