What this helps you do
Your registration and league-management systems keep registration, rosters, teams, fixtures, venues, official assignments, standings, scores, brackets, payments, waivers, eligibility and facility reservations. The Hub holds only the people you put in it, the audiences they are in, roles and grants, what was sent and the replies. There is no connector to a registration, scheduling, league-management or assigning platform, and nothing is synchronized: the Hub doesn't know a player's team, a game's time or who is affected by a change.
When to use it
Use a CSV at the start of a season, when registration has closed and teams are formed. Use the inbound webhook when a registration form should add a person the day they sign up. Use outbound events when your own records should hear about connections and replies.
How to do it
- Export a communication-only list from your registration system (email, name, household and an audiences column) and import it on Participants.
- Point your registration form at the inbound webhook on Integrations, or ask for the Zapier app.
- Add your HTTPS endpoint under events out if your league records should hear about connections and replies.
- Put your league's public calendar link in Settings to see upcoming items on Home with an Announce button.
Example
A league exports its opted-in registration contacts with the division and team audiences in one column. On Saturday morning a field is closed; the field coordinator sends the change to the division from Send. The schedule system still holds the fixture list, and the message links to it.
Good to know
- The calendar link shows up to twelve upcoming items from the next two weeks on Home. It notices no change, knows no team and sends nothing on its own.
- The Hub never reschedules a game, assigns an official, records a result or updates standings.
- A division or team column in your export only matters as an audiences column naming audiences you already created: the assignment is kept; the column itself is not.