---
title: Teams
description: Team handles, roles, and how member contributions are counted.
---

On team-mode events, everything competitive (solves, points, attempts, hints, instances) belongs to the **team**, not the individual. (Certificates are the exception: they're issued to each player individually.) This page is the reference for how teams work; the walkthrough for creating or joining one is in [Create or join a team](/players/how-to/create-or-join-a-team).

If your event doesn't use teams, none of this applies: there is no Team page, and solo players compete individually.

## Identity: name and handle

A team has two names with different jobs. The **team name** (2–32 characters) is display-only: it's what shows on the scoreboard, and it can be renamed by the leader until the event starts (after that, the same button sends a rename request to the organizers instead). The **team handle** (3–20 letters, numbers, or dashes, chosen at creation and stored uppercase) is the team's permanent public identity; it can never be changed, and it's what teammates use to join.

## Credentials: handle and join password

Joining takes the handle plus one real secret:

| | Team handle | Join password |
|---|---|---|
| Shape | 3–20 characters, made of letters, numbers, and dashes; chosen when the team is created (handles starting with `solo-` are reserved: *"Team handles starting with 'solo-' are reserved."*) | 12 characters, mixed case |
| Case | Doesn't matter when joining | Must match exactly |
| Where you see it | Public, and always visible on the team page (**@MY-TEAM**) | Shown **once** in the creation dialog, and emailed to the leader |
| Lifetime | Permanent | Valid until the leader regenerates it |

Joining requires both. The password is **reusable**; it isn't consumed by a join, so anyone holding the pair can join until the leader regenerates the password. Regenerating invalidates the old one immediately (*"The previous join password no longer works."*) and emails the new one to the leader.

## Roles: leader and member

The player who creates the team is its **leader** (crown badge in the members list); everyone who joins is a **Member**. Four things are leader-only:

- **Regenerate join password**: *"Only the team leader can regenerate the join password."*
- **Rename team**: before the event starts; afterwards the button becomes **Request name change** and files a request with the organizers.
- **Remove**: the leader can remove any member from the members list.
- **Disband team**: only when the leader is the last member left.

Everything else (solving, submitting flags, unlocking hints, managing instances, submitting the team writeup) is open to every member equally. Leadership transfers automatically: if the leader leaves the team, the longest-standing member becomes the new leader.

## Leaving, removals, and disbanding

Membership can change during the event, but score history never moves with a player. Solves and points always stay with the team they were earned on:

- **Leave team**: any member can leave from the team page and then join or create another team. The last remaining member can't leave; they disband instead.
- **Remove**: the leader can remove any member. Removed players keep their accounts and can join another team.
- **Disband team**: permanently deletes the team along with its solves, points, and scoreboard entry; only possible once the leader is the sole member and no challenge instances are running (*"Stop your running challenge instances before disbanding the team."*).

Trying to join a second team while you're still on one fails with *"Leave your current team before joining another."*

The team page doesn't display a member cap, but if your event sets a maximum team size, it's enforced when you join: trying to join a team that's already at the limit fails with *"This team is full."* Nobody already on the team is removed; a full team just can't take new members. If your event has no team-size limit, teams can grow without one.

## The team page

The **Team** page (avatar menu → Team) shows the shared picture:

- Team name, **team handle** (shown as **@HANDLE**), total **points**, and current **rank** (shown as **Unranked** until the team is ranked).
- **Members**: each player's display name and handle, with their Leader/Member badge.
- **Recent solves**: the team's last ten solves, each tagged with the teammate who scored it and the points earned.

Certificates aren't here; they're issued per player and appear on your own profile page after the freeze. See [After the freeze](/players/how-to/after-the-freeze).

Your team also has a **public team page** at `/team/<HANDLE>`, linked from the scoreboard and from **View public team page** on your own team page. It shows the team's rank, points, solve count, and member count, the full roster (each member linking to their profile), a score-progression chart, a **Member Contribution** chart, and a solve timeline with blood badges. Teams hidden from the scoreboard don't have one.

After the freeze it carries a notice: *"The scoreboard is frozen. Solves and contributions recorded after the freeze are hidden."* That's generic wording rather than a hint that something is being withheld; submissions close at the freeze, so there are no later solves to hide.

## Member contributions

**View member contributions** on the team page opens the per-member breakdown, covering the event since it started:

- **Net contribution by member**: a bar per teammate, split into **Positive** and **Negative**.
- A cumulative chart per member, showing each teammate's running net contribution over time.
- **Reason breakdown**: totals per reason. Four reasons can appear, and only the ones with activity are listed:
  - **Solve**: positive; the points a solve earned, credited to the teammate who submitted the flag.
  - **Hint Penalty**: negative; charged to the teammate who unlocked the hint, even though the hint becomes visible to the whole team. See [Use hints and files](/players/how-to/use-hints-and-files).
  - **Admin Adjustment**: a manual point change (positive or negative) an organizer applied. It appears here when they targeted a specific member; a team-wide adjustment still moves the score but doesn't show in this per-member breakdown.
  - **Member Removal**: recorded when an organizer **deletes a player's account**. That player's own solve points and hint penalties are reversed off the team's total. This is the one case where points move: a teammate simply leaving or being removed from the roster never changes the team's score.

The team's total is simply the sum of these events across all members; there is no separate team bonus on top.
