# 4. Communication Settings

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

---

## 4. Communication Settings

### 4.1 Collaboration Notifications
**What it does:** The Super Admin manages the collaboration notifications so parents and students are notified of the collaboration events.

**Sub-features:**
- Notification types: the types of collaboration notifications
- Notification triggers: the triggers for the notifications
- Notification channels: the channels for the notifications
- Notification preferences: the preferences per user
- Notification log: the log of the sent notifications
- Available on web
- Event logging (action performed)
- Audit logging of collaboration notifications

**Super Admin User Journey:**
1. As a Super Admin, open the collaboration notifications.
2. Configure the notification types and triggers.
3. Set the channels and preferences.
4. Review the notification log.

**Rules & Edge Cases:**
- A notification type is a goal update, celebration, or challenge.
- A notification trigger is the event that sends the notification.
- A notification channel is the delivery method (in-app, email).
- A notification preference is the user's choice of notifications.
- A notification log records the sent notifications.
- A notification without a channel is not sent.
- Notification actions are audit-logged with the actor and timestamp.

### 4.2 Communication Channels
**What it does:** The Super Admin manages the communication channels so the family can communicate through the supported channels.

**Sub-features:**
- Channel definition: the definition of a communication channel
- Channel enablement: the channel toggled active or inactive
- Channel permissions: the permissions per channel
- Channel routing: the routing of the messages
- Channel status: the status of the channel
- Available on web
- Event logging (action performed)
- Audit logging of communication channels

**Super Admin User Journey:**
1. As a Super Admin, open the communication channels.
2. Define a channel and set the permissions.
3. Enable the channel and set the routing.
4. Review the channel status.

**Rules & Edge Cases:**
- A channel definition names the communication channel.
- A channel enablement controls whether the channel is active.
- A channel permission controls who can use the channel.
- A channel routing directs the messages to the recipients.
- A channel status reflects the state (active, inactive).
- A message on an inactive channel is not delivered.
- Channel actions are audit-logged with the actor and timestamp.

### 4.3 Privacy and Consent
**What it does:** The Super Admin manages the privacy and consent so the family's data is protected and consent is tracked.

**Sub-features:**
- Consent definition: the definition of a consent
- Consent collection: the collection of the consent
- Consent status: the status of the consent (granted, revoked)
- Data visibility: the visibility of the data per user
- Consent log: the log of the consents
- Available on web
- Event logging (action performed)
- Audit logging of privacy and consent

**Super Admin User Journey:**
1. As a Super Admin, open the privacy and consent.
2. Define a consent and set the data visibility.
3. Collect the consent from the family.
4. Review the consent status and log.

**Rules & Edge Cases:**
- A consent definition names the consent.
- A consent collection records the family's consent.
- A consent status reflects the state (granted, revoked).
- A data visibility controls who can see the data.
- A consent log records the past consents.
- Data is not visible without a granted consent.
- Consent actions are audit-logged with the actor and timestamp.

### 4.4 Communication Audit
**What it does:** The Super Admin reviews the communication audit so the family communications are monitored for compliance.

**Sub-features:**
- Audit scope: the scope of the communication audit
- Audit events: the events in the audit
- Audit filters: the filters for the audit
- Audit export: the export of the audit
- Audit retention: the retention of the audit records
- Available on web
- Event logging (action performed)
- Audit logging of communication audit

**Super Admin User Journey:**
1. As a Super Admin, open the communication audit.
2. Set the audit scope and filters.
3. Review the audit events.
4. Export the audit.

**Rules & Edge Cases:**
- An audit scope defines the range of the audit.
- An audit event is a communication action.
- An audit filter narrows the audit results.
- An audit export produces the audit report.
- An audit retention defines how long the records are kept.
- An audit with no events shows an empty state.
- Audit actions are audit-logged with the actor and timestamp.