Skip to main content

Notifications

Keep your community in the loop. Zander delivers in-app notifications for events like punishment updates, ticket replies, and event announcements — and supports browser push notifications so players can be notified even when they're not actively browsing the site.

note

📸 Screenshot: The /notifications page showing a list of unread notifications with timestamps and a mark-all-read button

For Players​

Viewing Notifications​

All your notifications are listed at /notifications. The page shows each notification with a timestamp and a link to the relevant page. Clicking a notification marks it as read and takes you to the source.

A summary of up to 10 recent notifications (with unread count) is also available at /notifications/summary — this is used by the notification badge in the site header.

Browser Push Notifications​

You can opt in to browser push notifications to receive alerts even when the site is not open:

  1. Log in to your account.
  2. Go to your profile settings.
  3. Allow notifications when your browser prompts you.

Once subscribed, Zander will deliver push notifications directly to your browser for relevant activity on your account.

tip

Push notifications require a modern browser with the Web Push API supported (Chrome, Firefox, Edge, Safari 16+). They also require VAPID_SUBJECT, VAPID_PUBLIC_KEY, and VAPID_PRIVATE_KEY to be configured in .env.

Managing Notifications​

From /notifications you can:

  • Click any notification to mark it as read and navigate to the source
  • Use Mark All as Read to clear the unread badge
  • Dismiss individual notifications to remove them permanently

For Staff​

Configuration​

Browser push notifications require VAPID keys in .env:

VariableDescription
VAPID_SUBJECTContact email or URL (e.g. mailto:admin@example.com)
VAPID_PUBLIC_KEYVAPID public key — shared with browsers
VAPID_PRIVATE_KEYVAPID private key — kept secret on the server

Generate a key pair using:

npx web-push generate-vapid-keys

Copy the output values into your .env file. VAPID keys are stable — you only need to generate them once per deployment.

warning

Changing your VAPID keys invalidates all existing push subscriptions. Players will need to re-subscribe in their profile settings.