Skip to content

Team communication settings

Who this is for: team admin Applies to: all

What this page covers

How your team's communication is configured: how announcements are delivered by default, which channels are used for emergencies, who receives announcements, whether senders can customize channels, and when quiet hours start. After reading you'll be able to review and change these settings, and you'll know that every change is recorded and that only team admins can make them.

Before you start

  • You must be a team admin on the team (an owner has exactly the same powers).
  • These settings belong to one team, so first make sure you are looking at the team you want to configure (use the team picker to switch).
  • Open Team Settings and tap the Communication tab.

Step-by-step

  1. Open Team Settings and tap the Communication tab.
  2. Default Channels — tap the chips to set how a normal announcement reaches people by default: Push Notifications, Email, SMS, and In-App.
  3. Emergency Channels — choose the channels used for urgent communications that bypass quiet hours.
  4. Emergency Alert Settings — turn on Always include parents for athlete emergency alerts so parents receive emergency notifications even when they are not in the default audience.
  5. Default Audience — tick who receives team announcements by default: Coaches, Athletes, Parents, Emergency Contacts.
  6. Override Behavior — Allow channel override lets senders customize the channels when they compose an announcement.
  7. Quiet Hours — set the Start Time (HH:mm) and End Time (HH:mm), pick the Timezone these hours use, and choose whether to Allow emergencies during quiet hours. Quiet hours are described as the time period when non-emergency notifications are suppressed.
  8. Tap Save Changes. You can also tap Send Test Message to check delivery.

The Settings Preview card on the same screen shows how your choices will appear to athletes, parents, and coaches.

What you should see

  • The settings screen confirms your changes are saved, and a test message reports that it was sent.
  • Announcements and notifications follow the new defaults for the whole team.
  • Only team admins see the editing controls; everyone else sees these settings as read-only.
  • Every change is recorded — who made it and when — so there is a history of changes to the team's communication settings.

Notes and limits

  • If you have never changed these settings, the defaults are:
  • Channels: Push Notifications, Email, and In-App,
  • Emergency channels: Push Notifications, SMS, and Email,
  • Default audience: Coaches, Athletes, and Parents,
  • Channel override: allowed,
  • Parents always included on emergency alerts: on,
  • Quiet hours: 9:00 pm to 7:00 am in Mountain Time (MT), with emergencies allowed through.
  • Today, announcements actually go out in the app and as push notifications. Email and text-message delivery options are saved but are not yet used when an announcement is sent.
  • Settings are stored per team, not per account or per organization.
  • Quiet hours use a time zone you pick in these settings. The picker offers Eastern Time (ET), Central Time (CT), Mountain Time (MT), Arizona (no DST), Pacific Time (PT), Alaska Time (AKT), and Hawaii Time (HT); it starts as Mountain Time (MT). A team that trains in another time zone should pick its own zone here, or the quiet-hours window will open and close an hour or more off for those families.
  • Event times elsewhere in the app are shown in your team's own time zone, which also starts as Mountain Time (MT). Only the quiet-hours time zone can be picked in these settings; see the open question below.
  • Open question: the team's own time zone (the one used for event times) has no visible editor — the only time-zone picker in the app is the quiet-hours one in these settings. How a team outside Mountain Time gets its event times right is not documented yet; ask your team admin or contact support if event times look wrong.
  • Open question: the source documents what these settings are but not exactly what each one does from a member's point of view — for example, it does not say whether a routine message sent during quiet hours is delayed until morning or held back entirely.