Answers built for real CTBA workflows

You land on a dashboard built for your role: menus only show modules you are allowed to use, and lists are scoped to your association, club, team, or personal record as appropriate. You can complete profile setup (identity, safety, and compliance fields), switch active role when you have more than one assignment, receive in-app notifications, and deep-link to sections such as transfers, finance, or match detail. The goal is one front door for every CTBA workflow instead of spreadsheets and scattered email threads.

The hierarchy is association → clubs → teams → players (and officials attached where relevant). Permissions follow that chain: association roles see cross-club operations; club roles see one club; team roles see one squad; players and parents see personal and household data. Competitions, fixtures, venues, and finance records attach at the right level so reporting and public pages stay consistent.

Your account can hold one or more role assignments (for example club admin and team manager). Each role opens a different sidebar: association treasurer sees finance queues; club admin sees people, registrations, logistics, and club announcements; team manager sees attendance and fees for their team; player sees their own fixtures and transfer status. You pick the role that matches the task so API calls carry the correct scope headers and you never accidentally edit another club’s data.

Association administrators maintain the master record: associations and settings, clubs and teams, player and coach or staff profiles, referees, competitions, fixture generation and edits, venue directory and association venue calendar, documents, announcements, social links, newsletter and subscribers, cross-club transfers at the admin stage, finance and payment-proof visibility, player ratings, user administration where permitted, and reports. Super administrators and exco-style roles extend that to multiple associations or high-level configuration. Vice presidents typically share the same operational modules as administrators for sections they are assigned.

Beyond the same broad association menus many presidents have, the product gives dedicated inboxes: public FAQ questions submitted from this help page, and general messages from the Contact page. The president can answer and optionally publish FAQ replies without showing the submitter’s name. On transfers, the president may approve or reject at the executive step when policy requires it, after club and administrative steps.

Treasurers work in a finance-focused dashboard: finance overview, invoices, payments, proof-of-payment (POP) review, club and team finance lenses, finance reports, transactions, audit trail read access, and finance settings. They approve or reject POP with reasons, which feeds eligibility and accountability elsewhere in the association.

Club admins are the bridge between the association and the squads: transfers visibility and club-side actions, club announcements, association leadership contacts, people operations (players, parents, guardians, coaches, staff, referees linked to the club), club operations (roster, availability, attendance, training, match-day tooling), competition entries and logistics, analytics, reports, activity log, club profile and teams, users and role assignments for the club, and integrations surfaced in the UI. Their data never crosses into another club’s private records.

Team managers handle day-to-day squad logistics: my team, players, attendance, training, schedule and matches, documents, messages, payments and fees, reports, tasks, announcements, and settings for their team. Head coaches and coaches use a coach workspace focused on players, training, matches, tactics, analysis, fitness, attendance, calendar, messages, video or document storage, and settings. Team administrators maintain roster, staff, documents, attendance, and match-day readiness for a single team. All of these stay inside the assigned team or club boundary.