[Web - Global] Notifications system

[iarandrd]

As a content creator, I want to be able to see notifications of recent activities happening on my profile

• Define notification logic (can schedule with the PO to brainstorm)
• This notification should be on the header as a global item, which means that should work and every page on the system

[MBryder]

Acceptance Criteria for Notifications of Recent Activities:

1. Global Notification Icon:

Given that the user is logged into the system, When the user navigates to any page within the system, Then a notification icon should always be present in the header as a global item, visible across all pages, allowing the user to access notifications from any part of the platform.

2. Notification Badge for Unread Activities:

Given that the user has unread notifications (e.g., recent activities, comments, reviews, or approvals related to their content), When there are new activities, Then the notification icon should display a badge indicating the number of unread notifications (e.g., a red circle with a number).

3. Viewing Notifications:

Given that the user clicks on the notification icon, When the notification dropdown or panel appears, Then the system should display a list of recent activities such as:

• New comments or feedback on the user's content.
• Approvals or rejections of submitted content.
• Updates on courses, lectures, or profile views.
• System updates or announcements relevant to the user.

4. Mark as Read Logic:

Given that the user has viewed the list of notifications, When the user clicks on an individual notification or opens the notification panel, Then the notification should be marked as "read," removing it from the unread badge count on the notification icon.

5. Notification Scheduling and Frequency:

Given that different activities can generate notifications at varying intervals, When a specific event occurs (e.g., a comment, course approval, or system announcement), Then the system should notify the user immediately or at scheduled times based on the priority of the event (to be defined and brainstormed with the Product Owner).

6. Error Handling for Notifications:

Given that there is a system error or issue retrieving notifications, When the user clicks on the notification icon, Then the system should display an error message (e.g., "Unable to load notifications. Please try again later.").

7. Notification Storage and History:

Given that the user has received multiple notifications over time, When the user wants to view older notifications, Then the system should provide a way to view notification history, allowing access to all past notifications (possibly through a "View All" link or a separate notifications page).

8.Notification Customization:

Given that different users may want to customize which notifications they receive, When the user navigates to their profile or settings, Then the system should provide an option for the user to manage their notification preferences (e.g., enable/disable certain types of notifications, set frequency, etc.).