Configuration
Notification configuration controls which Kanera updates reach you and which channel they use.
There are two useful places to know:
- Profile settings -> Notifications: personal notification preferences.
- Organisation settings -> Org: organisation-level push and SMTP settings.
Personal notification settings
Open Profile settings -> Notifications to choose how Kanera sends card updates to you.
The page has three channel controls:
| Setting | What it does |
|---|---|
| Allow email notifications | Enables or disables email notifications for your account. |
| Allow push notifications | Enables or disables browser push notifications for your account and browser. |
| Play a sound for assignments and mentions | Plays an attention sound for assignment and mention notifications. |
Email is enabled by default. Push requires both organisation/system support and browser permission.
These master controls gate the whole channel for your account. For example, turning off Allow email notifications stops email delivery even if individual notification types are still enabled for email.
Notification types
Each notification type can be configured separately for email and push.
| Type | Use |
|---|---|
| Card assigned | Notify when you are assigned to a card. |
| Card comment added | Notify assignees when someone comments on their card. |
| Tagged in a comment | Notify when someone mentions you in a comment. |
| Card due date changed | Notify assignees when a card due date changes. |
| Card overdue | Notify when assigned cards or assigned checklist items become overdue. |
The master email and push toggles control whether those channels can send anything. If email notifications are off, individual email type toggles do not send. If push notifications are off, individual push type toggles do not send.
Use the per-type toggles to keep high-signal updates in faster channels. For example, many teams keep assignments, mentions, and overdue work enabled for push, while leaving lower-priority comment or due-date changes to email or the notification drawer.
Push notifications
Push notifications depend on three things:
- Kanera must be configured for push at the system level.
- The organisation must allow push notifications.
- Your browser must grant notification permission.
If push is unavailable, Kanera shows why in the notification settings page. Common reasons include push being turned off for the organisation, push not being configured for the deployment, browser support limitations, or browser permission being denied.
Push settings are browser-specific. Enabling push in one browser does not necessarily enable it in every browser or device you use.
If you use Kanera as an installed PWA, the push permission still belongs to the browser or operating system profile that installed it. Check the same browser/device if push appears enabled in Kanera but alerts do not arrive.
Organisation push setting
Organisation admins can control whether push is enabled for the organisation from Profile settings -> Org.
If organisation push is disabled, individual users cannot enable push notifications until an admin turns organisation push back on.
On self-hosted Kanera, enabling organisation push also prepares the shared web-push configuration that browsers need before users can subscribe.
Good configuration
Start with email enabled and push off unless your team wants browser-level alerts.
Turn on push for high-signal work such as assignments, mentions, and overdue cards. Keep lower-priority channels quieter if your team already uses the notification drawer throughout the day.