# 1. Notification Channels & Delivery

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

---

## 1. Notification Channels & Delivery

### 1.1 In-App Notifications
**What it does:** Delivers notifications to the Parent within the platform: an in-app notification center with the Parent's notifications, unread indicators, and deep links to the relevant content. The Parent sees the notifications when they open the platform. This is the primary channel for Parent notifications.

**Sub-features:**
- In-app notification center
- Unread notification indicator
- Deep link to the relevant content
- Notification categories
- Mark as read
- In-app notifications available on web and mobile
- Notification event logging (received, read)
- Audit logging of the in-app notifications

**Parent User Journey:**
1. The Parent receives an in-app notification.
2. The unread indicator is shown.
3. Parent opens the notification center.
4. Parent taps a notification; the relevant content opens.
5. Parent marks the notification as read.
6. The notification categories are shown.
7. Parent opens Profile → "Activity" and confirms the notification events are recorded.

**Rules & Edge Cases:**
- The notifications are in the in-app center.
- An unread indicator is shown.
- A deep link opens the relevant content.
- Notification events (received, read) are logged with the account and the timestamp.
- The in-app notifications is audit-logged with the account and the timestamp.

### 1.2 Email Notifications
**What it does:** Delivers notifications to the Parent by email: digests of the Parent's notifications, critical alerts, and reports. The Parent can enable or disable email notifications and choose the digest frequency. This gives the Parent an email channel for important updates.

**Sub-features:**
- Email notifications for the Parent
- Digest of notifications by email
- Critical alerts by email
- Reports by email
- Enable or disable email notifications
- Digest frequency selection
- Email event logging (sent, opened)
- Audit logging of the email notifications

**Parent User Journey:**
1. The Parent receives an email notification.
2. A digest of notifications is emailed.
3. A critical alert is emailed.
4. A report is emailed.
5. Parent enables or disables email notifications.
6. Parent selects the digest frequency.
7. Parent opens Profile → "Activity" and confirms the email events are recorded.

**Rules & Edge Cases:**
- The email notifications include digests, alerts, and reports.
- Email notifications can be enabled or disabled.
- The digest frequency is selectable.
- Email events (sent, opened) are logged with the account and the timestamp.
- The email notifications is audit-logged with the account and the timestamp.

### 1.3 Push and SMS Notifications
**What it does:** Delivers notifications to the Parent by push (mobile app) and SMS: time-sensitive alerts like a missed session or a critical performance alert. The Parent can enable or disable push and SMS and choose which alert types use each channel. This gives the Parent immediate, on-the-go awareness.

**Sub-features:**
- Push notifications on the mobile app
- SMS notifications
- Time-sensitive alerts via push and SMS
- Enable or disable push and SMS
- Per-alert-type channel selection
- Delivery confirmation
- Notification event logging (sent, delivered)
- Audit logging of the push and SMS notifications

**Parent User Journey:**
1. The Parent receives a push notification.
2. The Parent receives an SMS notification.
3. A time-sensitive alert is delivered via push and SMS.
4. Parent enables or disables push and SMS.
5. Parent selects the alert types for each channel.
6. A delivery confirmation is recorded.
7. Parent opens Profile → "Activity" and confirms the notification events are recorded.

**Rules & Edge Cases:**
- The push and SMS are for time-sensitive alerts.
- Push and SMS can be enabled or disabled.
- The alert types per channel are selectable.
- Notification events (sent, delivered) are logged with the account and the timestamp.
- The push and SMS notifications is audit-logged with the account and the timestamp.