Most programs are not “one flat list of 600 people.” They are squads, sections, houses, age bands, instrument sections, or project teams. Groups and teams in Talentelly are how you tell the product which subset of your population a given event, match, or report is about—so you never again export “everyone” and filter by hand in Excel. Admins work from Groups and Teams; open a specific roster from the list when you need to edit membership or metadata.
When to create a group
Create a group when:
- The same set of people meets repeatedly (a season, a semester, a batch).
- You need a roster for matches, performances, or attendance-style workflows.
- You want reports or certificates scoped correctly—“only Grade 10 science fair entrants,” not the whole school—see reports and printing.
Example: Westlake High runs House Carnivals. They create groups Aravali, Nilgiri, Shivalik, Udayagiri. Every inter-house match attaches to those groups so scores roll up to house totals automatically.
Example: A community choir has Sopranos, Altos, Tenors, Basses. Section leaders get reports filtered to their section for sectional rehearsals—without seeing other sections’ internal notes if your permissions are set that way.
A practical setup path
- Open Groups or Teams in admin (wording may match your org type).
- Name the container the way participants say it out loud: “U-14 Girls A” beats “Cohort_7”.
- Add members from your user directory, invites, or post-upload assignment.
- When you create events or matches, link the relevant group so registration and results stay scoped.
Example: Kickstart Football Club creates “2012 Boys — Coach Ravi” for the year. Every league match for that side references the group; end-of-season certificates use the same membership list—no manual “who played?” spreadsheet merge.
Teams vs groups: stop overthinking the label
In many deployments the underlying idea is identical: a bounded membership list you reuse. Your cricket club might say “team”; your school might say “section.” Pick what your staff already says in meetings.
Example: A robotics lab uses groups named after project teams (“Drone Rescue — Team Orion”). They are not sports teams, but the product behavior—roster + activities + outcomes—is the same.
Patterns that work in the real world
One group per “edition”
“Fall 2026 Beginners” next to “Spring 2027 Beginners” keeps history clean when alumni come back asking for proof of participation.
Stable groups + dated events
Keep “Senior Orchestra” stable all year; let individual concerts be events with dates. You do not need a new group for every concert unless membership actually changes.
Avoid duplicate near-copies
“U-12 A” and “Under 12 A” and “U12-A” will confuse coaches during a rainy Saturday. Pick a naming standard and stick to it in your ops doc.
Before the big day: roster hygiene
Example: Before a state tournament, the admin exports or prints the group roster from the product, asks each coach to initial a paper copy, then fixes any mismatches in Users / Groups before opening ceremony. Catching “we have two jersey #7” in admin beats chaos at check-in.
Tips
- End-of-season: Rename or internally tag groups with the year so next season’s admins are not editing last year’s roster by mistake.
- Large orgs: Prefer fewer, clearer groups over dozens of micro-groups nobody maintains.
- Communication: When you message parents, reference the same group name as in Talentelly—it reduces “which WhatsApp group is this?” confusion.
Related: Events and matches · User management · Hub discovery