Notifications and alerts
How Klubb signals members about games, role changes, and team-wide announcements.
Klubb has two ways of pushing information at you: notifications (system-generated, per-user) and alerts (admin-authored, team-wide and role-targeted).
Notifications
Notifications are emitted automatically by the app when something happens. Each one belongs to a single user on a single team.
| Type | Triggered when |
|---|---|
game_created | An admin schedules a new game |
game_updated | A field on a scheduled game changes |
game_cancelled | A game's status flips to cancelled |
game_reminder | A scheduled game is approaching |
team_joined | You join a team (or a new member joins one of your teams) |
role_changed | An admin changes your roles on a team |
chat_message | A new message lands in a channel you're in |
Each notification has a read flag so the unread badge on the bell icon stays accurate as you catch up.
Alerts
Alerts are different — they're authored by an admin and broadcast to the whole team, optionally filtered by role.
When creating an alert, the admin picks which roles should see it:
- All four roles (admin, player, trainer, guardian) → everyone
- A subset → only members holding at least one of the picked roles
This is the right tool for messages like "training cancelled tonight, players and trainers only" or "season fees due, guardians only" — anything that's a one-off announcement rather than something the system can detect on its own.
If you find yourself sending the same alert every week, that's a sign the underlying flow should be automated. Open an issue and we'll look at it.
Read state
Both notifications and alerts track per-user read state, so the badge clears as you open them and stays per-device-consistent.
Last updated today
Built with Documentation.AI