# 2. Content Access Restrictions

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

---

## 2. Content Access Restrictions

### 2.1 Content Access by Category
**What it does:** Lets the Parent restrict the child's access to content by category. The Parent can allow or block access to specific content types (e.g., social features, entertainment content) while keeping the core learning content available. This helps the Parent control what the child can access on the platform.

**Sub-features:**
- Allow or block content by category
- Core learning content always available
- Restricted category list
- Restriction applied in real time
- Restriction status shown to the child
- Restrictions available on web and mobile
- Restriction event logging (set, applied)
- Audit logging of the content access by category

**Parent User Journey:**
1. Parent opens the child's content access restrictions.
2. Parent blocks a content category (social features).
3. The core learning content remains available.
4. The restricted category is listed.
5. The restriction is applied in real time.
6. The restriction status is shown to the child.
7. Parent opens Profile → "Activity" and confirms the restriction events are recorded.

**Rules & Edge Cases:**
- The restrictions are by content category.
- The core learning content is always available.
- The restriction is applied in real time.
- Restriction events (set, applied) are logged with the account and the timestamp.
- The content access by category is audit-logged with the account and the timestamp.

### 2.2 Age-Appropriate Content Filter
**What it does:** Applies an age-appropriate content filter for the child based on their grade level. The Parent can enable the filter, which restricts content that is not suitable for the child's age group. The filter is aligned with the child's grade. This ensures the child sees content appropriate for their level.

**Sub-features:**
- Enable the age-appropriate content filter
- Filter aligned with the child's grade
- Unsuitable content restricted
- Filter status shown to the Parent
- Filter override by the Parent (with reason)
- Filter available on web and mobile
- Filter event logging (enabled, overridden)
- Audit logging of the age-appropriate content filter

**Parent User Journey:**
1. Parent opens the child's content filter.
2. Parent enables the age-appropriate filter.
3. The filter is aligned with the child's grade.
4. Unsuitable content is restricted.
5. The filter status is shown to the Parent.
6. Parent overrides the filter for a specific item with a reason.
7. Parent opens Profile → "Activity" and confirms the filter events are recorded.

**Rules & Edge Cases:**
- The filter is aligned with the child's grade.
- Unsuitable content is restricted.
- An override requires a reason.
- Filter events (enabled, overridden) are logged with the account and the timestamp.
- The age-appropriate content filter is audit-logged with the account and the timestamp.

### 2.3 Restricted Content Requests
**What it does:** Lets the child request access to restricted content, which the Parent can approve or deny. The child submits a request with a reason, and the Parent reviews it. If approved, the child gains access for a defined period. This gives the child a voice while keeping the Parent in control.

**Sub-features:**
- Child requests access to restricted content
- Request with a reason
- Parent approves or denies the request
- Approved access for a defined period
- Request history
- Requests available on web and mobile
- Request event logging (submitted, approved, denied)
- Audit logging of the restricted content requests

**Parent User Journey:**
1. The child requests access to a restricted item.
2. The request includes a reason.
3. The Parent reviews the request.
4. The Parent approves the request.
5. The child gains access for the defined period.
6. The request appears in the request history.
7. Parent opens Profile → "Activity" and confirms the request events are recorded.

**Rules & Edge Cases:**
- The request includes a reason.
- The Parent approves or denies the request.
- Approved access is for a defined period.
- Request events (submitted, approved, denied) are logged with the account and the timestamp.
- The restricted content requests is audit-logged with the account and the timestamp.