# 5. Child Safety

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

---

## 5. Child Safety

### 5.1 Age Verification
**What it does:** Verifies the age: the verification of the age (the verification, the user, the age, the date) is done, so the age is verified (the verification is the check). The Super Administrator verifies the age (the verification, the user, the age, the date) so the verification is structured and the check is explicit.

**Sub-features:**
- Verification: the verification (the verification, the user, the age, the date)
- User: the user (the user, the name, the verification)
- Age: the age (the age of the user, the number, the date)
- Verification method: the method (the method of the verification, e.g., the date of birth, the document)
- Verification status: the status (the verified, the unverified)
- Verification count: the count (the count of the verifications)
- Verification view: the view (the verifications, the users, the ages, the dates)
- Audit logging of the age verification

**Super Administrator User Journey:**
1. Super Admin verifies the age: the verification (the verification, the user, the age, the date), the user (the user, the name, the verification), and the age (the age of the user, the number, the date); the verification is explicit.
2. Selects the user: the user (the user, the name, the verification); the user is the subject.
3. Sets the age: the age (the age of the user, the number, the date); the age is the value.
4. Sets the verification method: the method (the method of the verification, e.g., the date of birth, the document); the method is the technique.
5. Views the verification status: the status (the verified, the unverified); the status is the state.
6. Views the verification count: the count (the count of the verifications); the count is the measure.
7. The age is verified: the verifications, the users, the ages, the dates, so the check is complete.
8. The age verification is audit-logged with the verification, the user, and the timestamp.

**Rules & Edge Cases:**
- The verification is the check (the verification, the user, the age, the date); the verification is the confirmation.
- The user is the subject (the user, the name, the verification); the user is the person.
- The age is the value (the age of the user, the number, the date); the age is the number.
- The verification status is the state (the verified, the unverified); the status is the control.
- The age is verified (the verifications, the users, the ages, the dates); the check is managed.
- Age verification is audit-logged with the verification, user, and timestamp.

### 5.2 Parental Consent for Minors
**What it does:** Obtains the parental consent for the minors: the consent of the parent (the consent, the parent, the minor, the date) is obtained for the minor, so the minor is protected (the consent is the permission). The Super Administrator obtains the parental consent for the minors (the consent, the parent, the minor, the date) so the consent is structured and the permission is explicit.

**Sub-features:**
- Consent: the consent (the consent, the parent, the minor, the date)
- Parent: the parent (the parent, the name, the consent)
- Minor: the minor (the minor, the age, the date)
- Consent method: the method (the method of the consent, e.g., the email, the document)
- Consent status: the status (the granted, the pending, the denied)
- Consent count: the count (the count of the consents)
- Consent view: the view (the consents, the parents, the minors, the dates)
- Audit logging of the parental consent

**Super Administrator User Journey:**
1. Super Admin obtains the parental consent for the minor: the consent (the consent, the parent, the minor, the date), the parent (the parent, the name, the consent), and the minor (the minor, the age, the date); the consent is explicit.
2. Selects the parent: the parent (the parent, the name, the consent); the parent is the guardian.
3. Selects the minor: the minor (the minor, the age, the date); the minor is the child.
4. Sets the consent method: the method (the method of the consent, e.g., the email, the document); the method is the technique.
5. Views the consent status: the status (the granted, the pending, the denied); the status is the state.
6. Views the consent count: the count (the count of the consents); the count is the measure.
7. The consent is obtained: the consents, the parents, the minors, the dates, so the permission is complete.
8. The parental consent is audit-logged with the consent, the parent, and the timestamp.

**Rules & Edge Cases:**
- The consent is the permission (the consent, the parent, the minor, the date); the consent is the agreement.
- The parent is the guardian (the parent, the name, the consent); the parent is the authority.
- The minor is the child (the minor, the age, the date); the minor is the protected user.
- The consent status is the state (the granted, the pending, the denied); the status is the control.
- The consent is obtained (the consents, the parents, the minors, the dates); the permission is managed.
- Parental consent is audit-logged with the consent, parent, and timestamp.

### 5.3 Monitored Communication Channels
**What it does:** Monitors the communication channels: the monitoring of the channels (the monitoring, the channel, the user, the date) is done, so the channels are monitored (the monitoring is the watch). The Super Administrator monitors the communication channels (the monitoring, the channel, the user, the date) so the monitoring is structured and the watch is explicit.

**Sub-features:**
- Monitoring: the monitoring (the monitoring, the channel, the user, the date)
- Channel: the channel (the channel, the type, the date)
- User: the user (the user, the name, the monitoring)
- Monitoring status: the status (the monitored, the not-monitored)
- Monitoring count: the count (the count of the monitorings)
- Monitoring view: the view (the monitorings, the channels, the users, the dates)
- Monitoring export: the export (the monitorings, the format, the channel)
- Audit logging of the channel monitoring

**Super Administrator User Journey:**
1. Super Admin monitors the communication channel: the monitoring (the monitoring, the channel, the user, the date), the channel (the channel, the type, the date), and the user (the user, the name, the monitoring); the monitoring is explicit.
2. Selects the channel: the channel (the channel, the type, the date); the channel is the medium.
3. Selects the user: the user (the user, the name, the monitoring); the user is the participant.
4. Views the monitoring status: the status (the monitored, the not-monitored); the status is the state.
5. Views the monitoring count: the count (the count of the monitorings); the count is the measure.
6. Exports the monitorings: the export (the monitorings, the format, the channel); the export is the record.
7. The channels are monitored: the monitorings, the channels, the users, the dates, so the watch is complete.
8. The channel monitoring is audit-logged with the monitoring, the channel, and the timestamp.

**Rules & Edge Cases:**
- The monitoring is the watch (the monitoring, the channel, the user, the date); the monitoring is the observation.
- The channel is the medium (the channel, the type, the date); the channel is the path.
- The user is the participant (the user, the name, the monitoring); the user is the actor.
- The monitoring status is the state (the monitored, the not-monitored); the status is the control.
- The channels are monitored (the monitorings, the channels, the users, the dates); the watch is managed.
- Channel monitoring is audit-logged with the monitoring, channel, and timestamp.

### 5.4 Content Moderation
**What it does:** Moderates the content: the moderation of the content (the moderation, the content, the user, the date) is done, so the content is moderated (the moderation is the review). The Super Administrator moderates the content (the moderation, the content, the user, the date) so the moderation is structured and the review is explicit.

**Sub-features:**
- Moderation: the moderation (the moderation, the content, the user, the date)
- Content: the content (the content, the type, the date)
- User: the user (the user, the name, the moderation)
- Moderation action: the action (the action of the moderation, e.g., the approve, the remove)
- Moderation status: the status (the moderated, the pending)
- Moderation count: the count (the count of the moderations)
- Moderation view: the view (the moderations, the content, the users, the dates)
- Audit logging of the content moderation

**Super Administrator User Journey:**
1. Super Admin moderates the content: the moderation (the moderation, the content, the user, the date), the content (the content, the type, the date), and the user (the user, the name, the moderation); the moderation is explicit.
2. Selects the content: the content (the content, the type, the date); the content is the subject.
3. Selects the user: the user (the user, the name, the moderation); the user is the author.
4. Sets the moderation action: the action (the action of the moderation, e.g., the approve, the remove); the action is the decision.
5. Views the moderation status: the status (the moderated, the pending); the status is the state.
6. Views the moderation count: the count (the count of the moderations); the count is the measure.
7. The content is moderated: the moderations, the content, the users, the dates, so the review is complete.
8. The content moderation is audit-logged with the moderation, the content, and the timestamp.

**Rules & Edge Cases:**
- The moderation is the review (the moderation, the content, the user, the date); the moderation is the check.
- The content is the subject (the content, the type, the date); the content is the asset.
- The user is the author (the user, the name, the moderation); the user is the creator.
- The moderation status is the state (the moderated, the pending); the status is the control.
- The content is moderated (the moderations, the content, the users, the dates); the review is managed.
- Content moderation is audit-logged with the moderation, content, and timestamp.

### 5.5 Reporting System for Inappropriate Content
**What it does:** Provides the reporting system for the inappropriate content: the report of the content (the report, the content, the user, the date) is provided, so the content is reported (the report is the flag). The Super Administrator provides the reporting system for the inappropriate content (the report, the content, the user, the date) so the report is structured and the flag is explicit.

**Sub-features:**
- Report: the report (the report, the content, the user, the date)
- Content: the content (the content, the type, the date)
- User: the user (the user, the name, the report)
- Report reason: the reason (the reason of the report, e.g., the inappropriate, the offensive)
- Report status: the status (the reported, the reviewed, the resolved)
- Report count: the count (the count of the reports)
- Report view: the view (the reports, the content, the users, the dates)
- Audit logging of the content reporting

**Super Administrator User Journey:**
1. Super Admin provides the report for the inappropriate content: the report (the report, the content, the user, the date), the content (the content, the type, the date), and the user (the user, the name, the report); the report is explicit.
2. Selects the content: the content (the content, the type, the date); the content is the subject.
3. Selects the user: the user (the user, the name, the report); the user is the reporter.
4. Sets the report reason: the reason (the reason of the report, e.g., the inappropriate, the offensive); the reason is the cause.
5. Views the report status: the status (the reported, the reviewed, the resolved); the status is the state.
6. Views the report count: the count (the count of the reports); the count is the measure.
7. The content is reported: the reports, the content, the users, the dates, so the flag is complete.
8. The content reporting is audit-logged with the report, the content, and the timestamp.

**Rules & Edge Cases:**
- The report is the flag (the report, the content, the user, the date); the report is the signal.
- The content is the subject (the content, the type, the date); the content is the asset.
- The user is the reporter (the user, the name, the report); the user is the actor.
- The report status is the state (the reported, the reviewed, the resolved); the status is the control.
- The content is reported (the reports, the content, the users, the dates); the flag is managed.
- Content reporting is audit-logged with the report, content, and timestamp.

### 5.6 Background Checks (Teacher Credentials, Content Creators, Regular Audits)
**What it does:** Performs the background checks: the check of the teachers (the check, the teacher, the credential, the date), the content creators (the check, the creator, the credential, the date), and the regular audits (the audit, the scope, the date) are performed, so the people are verified (the check is the verification). The Super Administrator performs the background checks (the check, the teacher, the creator, the audit) so the check is structured and the verification is explicit.

**Sub-features:**
- Check: the check (the check, the teacher, the credential, the date)
- Teacher: the teacher (the teacher, the name, the check)
- Credential: the credential (the credential of the teacher, the type, the date)
- Creator: the creator (the creator, the name, the check)
- Audit: the audit (the audit, the scope, the date)
- Check status: the status (the verified, the unverified)
- Check view: the view (the checks, the teachers, the creators, the audits, the dates)
- Audit logging of the background checks

**Super Administrator User Journey:**
1. Super Admin performs the background check: the check (the check, the teacher, the credential, the date), the teacher (the teacher, the name, the check), and the credential (the credential of the teacher, the type, the date); the check is explicit.
2. Selects the teacher: the teacher (the teacher, the name, the check); the teacher is the educator.
3. Verifies the credential: the credential (the credential of the teacher, the type, the date); the credential is the proof.
4. Selects the creator: the creator (the creator, the name, the check); the creator is the maker.
5. Performs the audit: the audit (the audit, the scope, the date); the audit is the review.
6. Views the check status: the status (the verified, the unverified); the status is the state.
7. The people are verified: the checks, the teachers, the creators, the audits, the dates, so the verification is complete.
8. The background checks are audit-logged with the check, the teacher, and the timestamp.

**Rules & Edge Cases:**
- The check is the verification (the check, the teacher, the credential, the date); the check is the confirmation.
- The teacher is the educator (the teacher, the name, the check); the teacher is the instructor.
- The credential is the proof (the credential of the teacher, the type, the date); the credential is the evidence.
- The audit is the review (the audit, the scope, the date); the audit is the inspection.
- The people are verified (the checks, the teachers, the creators, the audits, the dates); the verification is managed.
- Background checks are audit-logged with the check, teacher, and timestamp.