# Teams

A **team** is a named pool of users that powers [round-robin event types](/help/event-types/round-robin):
the team's members are the hosts, and 42min distributes bookings among them. Teams are
managed at [**Teams**](/360/teams), and each one also has its own public page at
`42min.us/team/<team-slug>`. (A team is *not* the same as a
[group](/help/team-and-admin/groups-and-permissions) — groups organize people and
delegate invitations; teams are host pools.)

## What it has

- **Members** — the users who can be assigned bookings from this team's round-robin
  event types.
- **A slug** — used in the team's URL and its event-type links.
- **Reschedule host policy** — when an invitee reschedules a round-robin booking, either
  **keep** the original host or **re-roll** (pick a host fresh for the new time).
- **Slot availability mode** — **maximize** (offer a slot if *any* member is free — the
  widest availability) or **balance** (lean toward spreading bookings more evenly).
- Optionally an **avatar** for the team's public page.

<Screenshot
  src="/help/screenshots/team-and-admin/team-settings.png"
  alt="The Teams page in the 42min dashboard with a team expanded, showing its members and the TEAM SETTINGS section: Slot availability (Maximize available slots / Balance team workload) and Round-robin reschedule (Keep the same host / Re-assign through round-robin)"
  caption="Click a team to expand it. TEAM SETTINGS holds the round-robin behavior: Slot availability (maximize vs balance) and Round-robin reschedule (keep the same host vs re-assign)."
/>

## How to do it

1. Open [**Teams**](/360/teams) (admin) and create a team: name it, add members, set
   the slug.
2. Choose the **reschedule host policy** (keep vs re-roll) and **slot availability
   mode** (maximize vs balance).
3. Create a [round-robin event type](/help/event-types/round-robin) and point it at
   this team.
4. Share `42min.us/team/<team-slug>` or the round-robin event's direct link.

## Common pitfalls

- **A member's calendar isn't connected.** They'll look the most available and grab a
  disproportionate share — every host should
  [connect their calendar](/help/integrations/google-calendar) and set their schedule.
- **Reschedule keeps the "wrong" host.** That's the team's reschedule host policy — set
  it on the team, not the event type.
- **Created the team but no round-robin event.** A team on its own does nothing; you
  need a round-robin event type pointed at it.