The admin area is your control room for an entity. After you sign in, land on the admin dashboard—it is where you learn what changed overnight, who needs a response, and which module to open next without memorizing every URL. The admin root may redirect or complement that entry point depending on your setup.
What you will see
- A summary-style layout with shortcuts into the modules your organization actually uses: users, groups, teams, events, matches, tournaments, reports, and more.
- Navigation grouped by how work flows in the real world: you usually add people before you assign them to groups, and you run activities before you print certificates (reports and printing).
- Notifications for operational events: connection requests from another entity (entity management), bulk upload completion, or other changes that are easy to miss if you only stare at one screen all day.
Example: Greenfield International School’s sports coordinator opens the dashboard at 7:30 AM, sees a notification that a bulk upload finished with 3 row errors, fixes those three students in the upload detail view, then jumps to Events to confirm Saturday’s inter-house match is still published.
Typical day flows (with examples)
“Registration week”
- Land on Dashboard — scan for failed jobs or pending connections.
- Open Users and bulk upload to ingest new admissions or trialists (bulk operations).
- Create or update Groups or Teams (“Grade 9 A”, “House Blue”) and assign members (groups and teams).
- Publish or update Events for orientation / trials.
Example: A dance studio runs January intake. Admins upload 80 new students, split them into Beginner Batch A/B, and attach those groups to the first showcase event so attendance lists are pre-filtered.
“Match day”
- Check Notifications for last-minute roster or venue changes someone else saved.
- Open Matches (or Events, depending on your setup) and verify status, scores, or forfeit flags. For head-to-head analysis, match compare may be available.
- If you issue same-day certificates, open Reports or hub print flows after results are final.
Example: A cricket league admin marks Match 14 as completed, enters the score, then generates Player of the Match certificates from a template that pulls names from the match record—no retyping in Canva.
“End of season”
- Reports — participation summaries, awards lists, or export for the annual report PDF. Report templates keep layouts consistent.
- Entity profile — update “Programs offered” or hero copy for next season’s hub traffic.
- Archive mentally: rename groups internally (“2025–26”) so next year’s data does not collide in people’s heads even if the product allows overlapping names.
Account vs entity settings (common confusion)
Your personal admin area (admin account, account settings)—password, email, how you get notified—is not the same as the entity record (entity, settings, admins, connections, payments: public description, other admins, org-level connections).
Example: Coach Vikram changes his phone number under account settings; the school’s GST or billing contact still lives under entity or payments screens. Mixing the two is how finance gets the wrong email on an invoice.
Tips
- Pin admin dashboard in the browser your volunteers actually use—not only your personal laptop.
- Check notifications before deep work; many workflows surface there first (e.g. another school accepting your connection request).
- New admin onboarding: Spend 15 minutes clicking every sidebar item once; the order is intentional and maps to “people → structure → activities → outputs.” Stuck? Open admin help or the knowledge base.
Related: Getting started · User management