# Setting up teams Teams sit one level below activity groups. They're the actual rosters that play matches and attend sessions — *Under 15A*, *Open Firsts*, *Soprano Section*. Most activity groups have multiple teams; some run as one big group with no team structure (choirs, clubs). ## When you need teams Use teams when: - The activity is competitive and students need to be sorted into grades. - You run separate trainings or fixtures for different ability levels. - You report on participation per team rather than per activity group. Don't use teams when: - The whole activity group does the same thing together (large choir, social club, debating squad). In the latter case, tick **No teams** on the activity group (see [Setting up activity groups](/portalhq/articles/setting-activity-groups/)) and students are added directly to the group. ## Creating teams From the activity group page, choose **New team**. Fields: - **Name** — *Under 15A*, *Open B*, *Tenor Section*. Whatever your school's convention is. - **Activity group** — pre-filled to the group you're adding the team to. - **Sort order** — controls how teams appear on the activity group's team list. Lower numbers first. - **Year groups** — optional restriction on which year levels can be in this team. - **Coach** — assigned later (see [Assigning staff, coaches and students to groups](/portalhq/articles/assigning-staff-coaches-and-students-groups/)). - **Default venue** — the venue the team's home fixtures usually run at. Inherited as the default when creating sessions. Save. ## Adding students to a team Two patterns: 1. **From the signup list** — once parents/students have signed up to the activity group, the signup list shows everyone unallocated. Drag students into teams. 2. **Direct add** — from the team detail page, search for and add specific students. Bypasses the signup workflow (useful for late additions). See [Assigning staff, coaches and students to groups](/portalhq/articles/assigning-staff-coaches-and-students-groups/) for the full workflow. ## Moving students between teams To move a student up or down a grade mid-term: 1. Open the team they're currently in. 2. Find them in the roster. 3. Choose **Move to team** and pick the new team. The move is logged. Their attendance history stays with them — the move is forward-looking only. ## Removing students Removing a student from a team takes them out of the team but keeps them on the activity group (so they can be added to a different team). To remove them from the activity group entirely: 1. Open the activity group. 2. Find the student in the signup list. 3. Choose **Withdraw**. Withdrawals are logged for reporting and audit. ## Coaches and assistant coaches Each team can have one or more staff/coaches assigned. The first staff member with the *is_coach* flag is the lead coach for the team — they appear on roll-marking and incident forms as the responsible adult. See [Assigning staff, coaches and students to groups](/portalhq/articles/assigning-staff-coaches-and-students-groups/). ## Reporting Teams roll up into activity group reports — total students per team, attendance percentage per team, incident counts per team. The team is the most granular level for most reports. ## Tips - **Name consistently.** *Under 15A* sorts before *Under 15B*; *15A* sorts after *14B*. Pick a convention and stick to it across activities. - **Don't over-segment.** Two teams of 10 are easier to manage than ten teams of 2. Reserve fine-grained teams for activities that genuinely need them. - **Plan team count up front.** Adding a team mid-term is fine, but reorganising students across newly-added teams is more work than getting it right at signup.