Each Subject Group carries its own set of notification templates and triggers, so a senior program and an underclass day at the same school can send different reminders. This page covers how notifications are configured at the group level and how to see what was sent.
When you create a group, the Notifications Enabled toggle turns on the group's non-booking notifications. Booking confirmations, reminders, and other booking-driven messages remain off until you review them and enable them individually, so nothing is sent to families before you intend it.
New Subjects Receive Welcome Email controls whether each newly added subject and contact receives your Account Created notification. Turn this off while loading data ahead of a launch.
Rather than editing each template from the studio default, select an existing group in Copy Notifications From when creating a new group. Its templates are copied to the new group.
For groups that already exist, select them on the Subject Groups list and choose Actions → Sync Notifications. Pick the source organization or group and either Sync All Notification Templates or select specific templates. The selected groups' templates are replaced with the source versions. Templates changed this way are marked Template was updated by a sync so the change is visible.
Open the group's Notifications settings to edit subject lines, message bodies, timing, and channels (email and SMS). Templates support variables such as the subject's name, session time, and the group's deadline dates. For the full list of triggers and variables see Notifications.
The Notifications tab on the group is a delivery log. Each row shows the notification type, recipient, send time, and whether it was opened and how many links were clicked. Undeliverable messages are flagged. Use it to answer "did this family get the reminder?" before resending.
<aside> 💡
Before enabling booking notifications, send yourself a test from one template. Deadline variables read from the group's Dates settings, so confirm those are filled in first.
</aside>