notifications #13

Open
opened 2026-03-27 13:08:16 +00:00 by jkeffects · 1 comment
Owner

FF Admin Server Notification Issue

  • Notifications are saved with recipient
  • Store with timestamp, origin/module, event type, title and content, read status (e.g., readAt), delivery channels used (in-app, email, push)
  • Event-based notifications for defined events related to modules. e.g.: Entry created, Entry deleted, Entry completed, Entry due date/reminder
  • Sending of notifications depending on user settings (permissions)
  • Delivery channels: in-app (notification center), email, push notification

  • Real-time delivery of in-app notifications with existing WebSocket connection, otherwise only displayed in notification list. No resending
  • Trigger for toast notifications when app session is active

  • Management of notification settings: Activation/deactivation per event type, configuration per delivery channel (in-app, email, push)
  • Optional weekly sending of reminder emails: Email contains all unread notifications for a user

  • Push notification session management: Unique identification of sessions (e.g., via UAParser), Assignment of push subscriptions to sessions, Invalidation of push session upon logout, No delivery to logged-out sessions
  • on Distance Deactivation of push notifications via a session if not logged out but device is away...
[FF Admin Server Notification Issue](https://code.jk-effects.cloud/FF-Admin/ff-admin-server/issues/65) - [x] Notifications are saved with recipient - [x] Store with timestamp, origin/module, event type, title and content, read status (e.g., readAt), delivery channels used (in-app, email, push) - [x] Event-based notifications for defined events related to modules. e.g.: Entry created, Entry deleted, Entry completed, Entry due date/reminder - [x] Sending of notifications depending on user settings (permissions) - [x] Delivery channels: in-app (notification center), email, push notification ------- - [x] Real-time delivery of in-app notifications with existing WebSocket connection, otherwise only displayed in notification list. No resending - [x] Trigger for toast notifications when app session is active ------- - [x] Management of notification settings: Activation/deactivation per event type, configuration per delivery channel (in-app, email, push) - [ ] Optional weekly sending of reminder emails: Email contains all unread notifications for a user ------- - [ ] Push notification session management: Unique identification of sessions (e.g., via UAParser), Assignment of push subscriptions to sessions, Invalidation of push session upon logout, No delivery to logged-out sessions - [ ] on Distance Deactivation of push notifications via a session if not logged out but device is away...
Author
Owner

webpush handling:

Action / State system behaviour
login set existing device notify registration active (if registrated by login user)
logout set notify registration inactive
session refresh set notify registration expiry like refresh expiry
notify send check notify registration active state and expiry date
webpush handling: | Action / State | system behaviour | |-----------|-----------| | login | set existing device notify registration active (if registrated by login user) | | logout | set notify registration inactive | | session refresh | set notify registration expiry like refresh expiry | | notify send | check notify registration active state and expiry date |
Sign in to join this conversation.
No labels
bug
feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
FF-Admin/ff-admin-core-server#13
No description provided.