# 3. Parental Approval for Purchases

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

---

## 3. Parental Approval for Purchases

### 3.1 Approve a Child's Purchase Request
**What it does:** Lets the Parent approve or deny a purchase request made by the child: an add-on subject, a premium resource, or an extra feature. The child submits the request, the Parent reviews it, and the Parent approves or denies it. If approved, the purchase is completed. This gives the Parent control over the child's spending.

**Sub-features:**
- Child submits a purchase request
- Parent reviews the request
- Parent approves or denies the request
- Approved purchase completed
- Denial reason to the child
- Request history
- Approval available on web and mobile
- Approval event logging (requested, approved, denied)
- Audit logging of the approve a child's purchase request

**Parent User Journey:**
1. The child submits a purchase request (premium resource).
2. The Parent reviews the request.
3. The Parent approves the request.
4. The purchase is completed.
5. The child is notified of the approval.
6. The request appears in the request history.
7. Parent opens Profile → "Activity" and confirms the approval events are recorded.

**Rules & Edge Cases:**
- The request is submitted by the child.
- The Parent approves or denies the request.
- An approved purchase is completed.
- Approval events (requested, approved, denied) are logged with the account and the timestamp.
- The approve a child's purchase request is audit-logged with the account and the timestamp.

### 3.2 Spending Limits for the Child
**What it does:** Lets the Parent set spending limits for the child's purchases: a maximum amount the child can spend per month without approval. Purchases within the limit are auto-approved, and purchases above the limit require the Parent's approval. This gives the Parent a balance of autonomy and control.

**Sub-features:**
- Set a monthly spending limit for the child
- Purchases within the limit auto-approved
- Purchases above the limit require approval
- Spending limit status
- Limit change confirmation
- Limits available on web and mobile
- Limit event logging (set, changed)
- Audit logging of the spending limits for the child

**Parent User Journey:**
1. Parent opens the child's spending limits.
2. Parent sets a monthly spending limit.
3. A purchase within the limit is auto-approved.
4. A purchase above the limit requires the Parent's approval.
5. The spending limit status is shown.
6. A limit change confirmation is shown.
7. Parent opens Profile → "Activity" and confirms the limit events are recorded.

**Rules & Edge Cases:**
- The limit is a monthly maximum.
- Purchases within the limit are auto-approved.
- Purchases above the limit require approval.
- Limit events (set, changed) are logged with the account and the timestamp.
- The spending limits for the child is audit-logged with the account and the timestamp.

### 3.3 Purchase Approval Notifications
**What it does:** Notifies the Parent when the child submits a purchase request that requires approval. The Parent is notified in-app and, where enabled, by email or push. The notification links to the request for review. This ensures the Parent is aware of pending purchase decisions.

**Sub-features:**
- Notification on a child purchase request
- In-app, email, and push channels
- Notification links to the request
- Pending request count
- Notification preferences for purchase requests
- Notification event logging (sent, opened)
- Audit logging of the purchase approval notifications

**Parent User Journey:**
1. The child submits a purchase request; the Parent is notified.
2. The notification is in-app, email, and push.
3. Parent taps the notification; the request opens.
4. The pending request count is shown.
5. Parent sets the notification preferences for purchase requests.
6. The notification events are recorded.
7. Parent opens Profile → "Activity" and confirms the notification events are recorded.

**Rules & Edge Cases:**
- Notifications are sent on child purchase requests.
- The notification channels are in-app, email, and push.
- A notification links to the request.
- Notification events (sent, opened) are logged with the account and the timestamp.
- The purchase approval notifications is audit-logged with the account and the timestamp.