Notifications
What Connected Performance notifies people about, how in-app, push and email delivery work, how admins configure who is notified per activity type, and how users turn browser push on.
Overview
Connected Performance records activity in your organization and turns some of it into notifications. Every notification lands in the in-app list under the bell icon. Depending on your organization's settings it can also go out as a push notification to the web app or the mobile app, and as an email.
Admins decide, per activity type, who is notified and by which channel under My App > Settings > Notifications. Chat messages are the exception: they always notify and cannot be switched off in these settings.
Separate from these notifications, the platform sends transactional emails for bookings, payments, memberships, waivers and account setup. Those are listed at the end of this article and are not affected by notification settings.
How To
Know what triggers a notification
An event is attributed to the person who did it, the actor. Recipients are picked by the actor's role and the event category, and the actor never receives their own notification.
| Who acted | Who is notified |
|---|---|
| Athlete or parent | The athlete's assigned coaches and all org admins |
| Coach | All org admins |
| System (payments) | All org admins |
| Admin | Nobody automatically |
Events that notify this way:
| Activity type | When it fires |
|---|---|
| Workout Completed | An athlete logs a completed workout |
| Assessment Completed | An athlete submits an assessment |
| File Upload | A file is uploaded to an athlete's file room |
| Booking Created | A session is booked |
| Booking Cancelled | A booking is cancelled |
| Assessment Graded | A coach grades an assessment response |
| Assessment Created | A coach creates an assessment |
| Workout Created, Updated | A coach creates or edits a workout |
| Workout Assigned | A workout is assigned to an athlete |
| Exercise Created, Updated | An exercise is created or edited |
| User Created, Deleted | A user account is created or removed |
| Schedule Updated | Staff notify an athlete from the schedule editor, an athlete shifts their own schedule, or an automation sends a notification |
| Progression Applied | A smart progression rule changes an athlete's schedule (sent to the rule's author) |
| Message Sent | A chat message is sent (sent to everyone else in the chat) |
| Settings Changed, Automation Created | Recorded in the activity feed only; no one is notified automatically |
Configure who gets notified (admins)
- Go to My App > Settings and open Notifications under Communication.
- Activity types are grouped under Coach Actions, Athlete Actions, Admin Actions and System Events. For each one:
- Tick Coaches, Athletes and/or Admins next to Notify: to allow that role to receive it.
- Switch Push on to send a push notification.
- Switch Email on to also send an email.
- Optionally type a Custom message and insert variables with + Variable.
- Click Save changes.
How the role checkboxes work: a user is notified only if at least one of the roles that selected them is ticked. An admin who also coaches an athlete counts as both, so ticking either Coaches or Admins reaches them. Parents have no checkbox and are never suppressed by these settings.
Custom messages replace the default description. Available variables: Organization Name, Date, Time, Actor Name, and depending on the event Athlete Name, Workout Name, Assessment Name, Grade, Uploader Name, File Name, User Name, User Role. Messages longer than 65 characters are saved but may be truncated on phones; the counter turns orange past that point.
An activity type that has never been saved on this page has no settings row, and in that state nobody is notified for it and no push or email goes out, apart from parents and chat messages. Open the page, set each activity type you care about, and save once. The checkboxes reflect what is saved, so an all-blank card means that type is currently silent.
Receive push notifications in the browser
The web app uses Firebase Cloud Messaging. The first time you click anywhere after signing in, the browser asks for notification permission. Allow it and your browser is registered; a notification then shows even when the tab is in the background.
To check or change this:
- Open your profile from the avatar menu (Profile).
- In the Notifications card, click Enable Notifications to prompt again. The browser prompt only appears while permission is still undecided.
If you blocked notifications earlier, the card shows "Notifications are blocked. Please enable them in your browser settings." The app cannot prompt again; allow notifications for the site in the browser and reload. Disable Notifications only changes the card's label; to stop browser push, block notifications for the site in your browser settings.
Push in the browser requires service worker support. On iOS Safari it only works when the app is installed to the home screen.
Receive push notifications on the mobile app
The mobile app registers its own device token when you sign in. Push arrives on every device you are signed in on, with an unread badge count. Signing in as a different user on the same device moves that device to the new user. A device that no longer accepts push is dropped automatically.
Read, open and clear notifications
Click the bell in the header. The badge shows how many are unread. Opening the drawer marks them read, so the badge goes to zero. In the drawer:
- Unread rows (including any that arrive while the drawer is open) have a coloured left edge.
- Each row is actor · verb, then the object, then a relative time such as "2 hours ago".
- Click a notification title to go to the linked page, for example the chat or the athlete's schedule.
- Click Mark all read to clear unread styling on anything that arrived while the drawer was open.
- Click the X on a notification to delete it.
- Click Clear All to delete every notification in the list.
The list shows your newest 200 notifications, newest first. New ones appear live at the top while you are signed in; you do not need to refresh. Each notification belongs to one user and nobody else can read or delete it. Logins are not written to the activity feed.
Notify athletes from the schedule editor (staff)
Coaches and admins can send a notification to an athlete directly from the schedule editor when changing their schedule. It is recorded as Schedule Updated and follows that activity type's push and email settings. The recipient has to be in your organization.
Understand transactional emails
These emails are sent regardless of notification settings, when the event happens:
| Sent to | Trigger | |
|---|---|---|
| Welcome email | New user | Account created (editable under Settings > Welcome Email) |
| Registration link, payment link | Prospective user or payer | Staff send a registration or payment link |
| Booking confirmed | Athlete | A booking is made |
| New booking | Coach | A booking is made on their session |
| Booking cancelled | Athlete and coach | A booking is cancelled |
| Schedule change | Booked athletes | A session's time changes |
| Coach reassignment | Booked athletes | A session's coach changes |
| Payment notice | Athlete | About 24 hours before a paid, still unpaid session |
| Booking past due | Athlete | A booking payment is still outstanding, repeated every 7 days by default |
| Payment receipt, payment failed, refund confirmation | Payer | A charge succeeds, fails or is refunded |
| Invoice created | Athlete or parent | An invoice is issued |
| Update your payment information | Athlete or parent | Staff request a new card on file |
| Membership renewal reminder | Member | Daily check for upcoming renewals |
| Membership payment failed, still outstanding, canceled | Member; admins get a billing alert | Membership dunning steps |
| Athlete info request | Parent or athlete | Staff send an information request |
| Waiver | Athlete | Staff send a waiver |
| Automation email | Athlete | An automation with a send-email action runs |
Tips
- Turn Email on only for the few activity types people need in their inbox. Email uses the same title and text as the in-app notification, so a chatty event becomes a chatty inbox.
- Admins are the fallback recipient for most events. If an admin is getting too much, untick Admins on the noisy activity types rather than disabling push.
- Chat notifications ignore these settings. There is no organization-level switch for them.
- Custom messages are the only way to change notification wording. Keep them under 65 characters so they are not cut off on phones.
Troubleshooting
I never get browser notifications. Check the Notifications card on your profile. If it says notifications are blocked, allow them in the browser's site settings. If the button says Enable Notifications, click it and accept the prompt. Push also requires the activity type to have Push switched on in Settings.
A coach is not notified when their athlete completes a workout. The coach has to be assigned to that athlete, and Coaches has to be ticked on Workout Completed in Settings > Notifications and saved. An activity type that was never saved notifies nobody. The athlete's own actions never notify the athlete.
Admins get nothing when another admin changes settings. By design. Admin actions are recorded in the activity feed but do not notify other admins.
The notification text is not what I typed as the custom message. Variables are only filled when the event provides them. An unused variable is replaced with nothing. Save the settings page after editing; the orange "You have unsaved changes" banner means it has not been saved.
"You cannot notify this user." The schedule editor notification was aimed at a user outside your organization.
Push arrives but the email does not. Email is a separate toggle per activity type, and the user needs an email address on their account.
Related
- Chat
- Customizing The Welcome Email
- Setting Up Automations
- Organization Settings
- Your Account & Profile
Referenced by
- 'Chat'communication
- 'Organization Settings'getting started
- 'Your Account & Profile'getting started