# 4. Notification History & Management

User Type: **Affiliate**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 4. Notification History & Management

### 4.1 Notification History
**What it does:** Shows the Affiliate their full notification history: all past notifications with their type, message, and timestamp. The Affiliate can browse, filter by category, and search the history. This gives the Affiliate a record of everything they were notified about.

**Sub-features:**
- Full notification history
- Notifications with type, message, and timestamp
- Filter by category
- Search the history
- History paginated
- History available on web and mobile
- History event logging (viewed)
- Audit logging of the notification history

**Affiliate User Journey:**
1. Affiliate opens the notification history.
2. The full notification history is shown.
3. The notifications show type, message, and timestamp.
4. Affiliate filters by category.
5. Affiliate searches the history.
6. The history is paginated.
7. Affiliate opens Profile → "Activity" and confirms the history events are recorded.

**Rules & Edge Cases:**
- The history shows all past notifications.
- The history is filterable by category and searchable.
- History events (viewed) are logged with the account and the timestamp.
- The notification history is audit-logged with the account and the timestamp.

### 4.2 Mark as Read & Clear
**What it does:** Lets the Affiliate manage their notification state: mark a notification as read, mark all as read, and clear the notification list. The Affiliate's unread count updates accordingly. This keeps the notification area tidy.

**Sub-features:**
- Mark a notification as read
- Mark all as read
- Clear the notification list
- Unread count updates
- Read state persists across devices
- Management available on web and mobile
- Management event logging (marked read, cleared)
- Audit logging of the mark as read and clear

**Affiliate User Journey:**
1. Affiliate opens the notifications.
2. Affiliate marks a notification as read.
3. Affiliate marks all as read.
4. Affiliate clears the notification list.
5. The unread count updates.
6. The read state persists across devices.
7. Affiliate opens Profile → "Activity" and confirms the management events are recorded.

**Rules & Edge Cases:**
- The unread count updates on mark-as-read and clear.
- The read state persists across devices.
- Management events (marked read, cleared) are logged with the account and the timestamp.
- The mark as read and clear is audit-logged with the account and the timestamp.

### 4.3 Critical System Notifications
**What it does:** Delivers critical system notifications to the Affiliate: account security alerts, program policy changes that affect earnings, and payout issues. These cannot be muted or batched and are always delivered in real time on all enabled channels. This ensures the Affiliate never misses something important.

**Sub-features:**
- Critical system notifications delivered
- Account security alerts
- Program policy change alerts
- Payout issue alerts
- Cannot be muted or batched
- Always real-time on all enabled channels
- Notifications event logging (sent, viewed)
- Audit logging of the critical system notifications

**Affiliate User Journey:**
1. Affiliate receives a critical system notification.
2. The account security alerts are delivered.
3. The program policy change alerts are delivered.
4. The payout issue alerts are delivered.
5. The notification cannot be muted or batched.
6. The notification is always real-time on all enabled channels.
7. Affiliate opens Profile → "Activity" and confirms the notifications events are recorded.

**Rules & Edge Cases:**
- The critical notifications cannot be muted or batched.
- The critical notifications are always real-time on all enabled channels.
- Notifications events (sent, viewed) are logged with the account and the timestamp.
- The critical system notifications is audit-logged with the account and the timestamp.