# 6. Content Moderation

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

---

## 6. Content Moderation

### 6.1 Content Moderation for Community-Created Content (Flashcards, Forums, Q&A)
**What it does:** Moderates the community-created content: the flashcards, the forum posts, and the Q&A submissions that the learners and teachers create, so the community content is accurate and appropriate. The Super Administrator oversees the moderation (the queue, the review, the action) so the community contribution is a feature with quality control, not a free-for-all.

**Sub-features:**
- Community content: the flashcards, the forum posts, and the Q&A submissions
- Moderation queue: the community content queued for review
- Moderation review: the content reviewed (the accuracy, the appropriateness)
- Moderation action: the action per the review (approve, reject, remove)
- Moderation scope: the moderation per the content type (the flashcards, the forums, the Q&A)
- Moderation record: the moderation recorded (the content, the action, the time)
- Audit logging of the moderation

**Super Administrator User Journey:**
1. A learner/teacher creates community content (a flashcard deck, a forum post, a Q&A submission); it enters the moderation queue.
2. Super Admin (or the designated moderator) reviews the queue: the community content, the type (the flashcards, the forums, the Q&A), and the context.
3. Reviews the content for accuracy (the facts, the answers) and appropriateness (the suitability); the review is the quality gate.
4. For content that passes, approves it (it is live in the community space); the action is recorded.
5. For content that fails (inaccurate, inappropriate), rejects or removes it (with the reason); the action is recorded.
6. For a high-volume community space (the forums), Super Admin sets the moderation scope (the types moderated, the frequency) so the load is managed.
7. Reviews the moderation record: the actions taken (the content, the action, the time), so the moderation is auditable.
8. The moderation is audit-logged with the content, the action, and the timestamp.

**Rules & Edge Cases:**
- The community content is the flashcards, the forum posts, and the Q&A submissions; it is moderated, not auto-published.
- The moderation queue is the entry point; the content is reviewed before it is live.
- The moderation review checks the accuracy and the appropriateness; the quality gate is the review.
- A moderation action is recorded (the content, the action, the time); it is auditable.
- The moderation scope is per the content type (the flashcards, the forums, the Q&A); the load is managed.
- Moderation is audit-logged with the content, action, and timestamp.

### 6.2 Reporting System for Inappropriate Content
**What it does:** Provides the reporting system for inappropriate content: the learners (and the teachers) can report content (the community content, or the platform content) as inappropriate, so the issue is surfaced to the moderators. The Super Administrator manages the reports (the queue, the review, the action) so a reported issue is handled, not ignored.

**Sub-features:**
- Content reporting: the content reported (the issue surfaced)
- Report submission: a learner/teacher submits a report (the content, the reason)
- Report queue: the reports queued for review
- Report review: the report reviewed (the content, the reason, the validity)
- Report action: the action per the review (the takedown, the correction, the dismissal)
- Report resolution: the report resolved (the issue addressed, the report closed)
- Audit logging of the reports

**Super Administrator User Journey:**
1. A learner/teacher reports content as inappropriate (the content, the reason); the report enters the queue.
2. Super Admin (or the designated moderator) reviews the report: the content, the reason, and the validity (is the report justified?).
3. For a valid report, takes the action (the takedown, the correction) per the issue; the content is handled.
4. For an invalid report (the content is fine, the report is a mistake), dismisses it (the reason noted); the content is not affected.
5. Resolves the report: the issue addressed, the report closed; the resolution is recorded.
6. Reviews the report queue: the open reports (the unresolved issues), so the reported content is worked down (not left reported).
7. For a pattern of reports (a content item reported repeatedly), Super Admin reviews the root cause (the content issue, the reporting confusion) and addresses it.
8. The reports are audit-logged with the content, the report, the action, and the timestamp.

**Rules & Edge Cases:**
- A report is the issue surfaced (the content, the reason); it is not an accusation, it is a signal.
- The report queue is the entry point; the report is reviewed before the action.
- A valid report triggers the action (the takedown, the correction); the content is handled.
- An invalid report is dismissed (the reason noted); the content is not affected by a bad report.
- A report is resolved (the issue addressed, the report closed); it is not left open indefinitely.
- Reports are audit-logged with the content, report, action, and timestamp.

### 6.3 Age-Appropriate Content Filtering
**What it does:** Filters the content for age-appropriateness: the Super Administrator configures the age-appropriate filtering so the content shown to a learner is appropriate for their age group. The filtering ensures a younger learner is not shown content meant for an older one (the advanced material, the mature themes), and the age gate is enforced.

**Sub-features:**
- Age-appropriate filtering: the content filtered by the age group
- Age group: the learner's age group (the grade, the age band)
- Content age rating: the content rated for the age group (the appropriate, the advanced)
- Age gate: the age gate enforced (the learner sees the appropriate content)
- Filtering configuration: the filtering set (the age groups, the content ratings)
- Filtering review: the filtering reviewed (the content in the right age group)
- Audit logging of the filtering configuration

**Super Administrator User Journey:**
1. Super Admin configures the age-appropriate filtering: the age groups (the grade, the age band) and the content ratings (the appropriate, the advanced).
2. Sets the age gate: the learner sees the content appropriate for their age group (the younger learner not shown the advanced material).
3. Rates the content for the age group (the appropriate, the advanced); the rating is the filter key.
4. Saves; the filtering is live, and the learners see the age-appropriate content.
5. For a content item that is mis-rated (the advanced content shown to the younger learner), Super Admin corrects the rating; the change is recorded.
6. Reviews the filtering: the content in the right age group (the appropriate content for the younger learner, the advanced for the older), so the filtering is correct.
7. For a new age group (a grade added), Super Admin extends the filtering (the age group, the content ratings) so the new group is covered.
8. The filtering configuration is audit-logged with the age groups, the content ratings, and the timestamp.

**Rules & Edge Cases:**
- The age-appropriate filtering is by the age group (the grade, the age band); the content is filtered for the learner's age.
- The age gate is enforced (the learner sees the appropriate content); the gate is not bypassed.
- The content age rating is the filter key (the appropriate, the advanced); the rating is specific.
- A mis-rated content item is corrected (the rating fixed); the change is recorded.
- A new age group extends the filtering (the age group, the content ratings); the new group is covered.
- Filtering configuration is audit-logged with the age groups, content ratings, and timestamp.