# 3. Accountability Partners

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

---

## 3. Accountability Partners

### 3.1 Partner Matching
**What it does:** The Super Admin manages the partner matching so learners are matched with study buddies who have similar goals.

**Sub-features:**
- Match criteria: the criteria for the partner matching
- Match creation: the creation of a partner match
- Match status: the status of the match (pending, active)
- Match listing: the listing of all matches
- Match history: the history of the matches
- Available on web
- Event logging (action performed)
- Audit logging of partner matching

**Super Admin User Journey:**
1. As a Super Admin, open the partner matching.
2. Set the match criteria.
3. Create a partner match.
4. Review the match status and listing.

**Rules & Edge Cases:**
- A match criterion is a goal, subject, or schedule.
- A match creation links two learners as partners.
- A match status reflects the state (pending, active).
- A match listing shows all matches.
- A match history stores the past matches.
- A match without two learners cannot be created.
- Match actions are audit-logged with the actor and timestamp.

### 3.2 Goal Alignment
**What it does:** The Super Admin manages the goal alignment so the partners' goals are aligned for the study sessions.

**Sub-features:**
- Goal link: the link of the partners' goals
- Goal comparison: the comparison of the goals
- Goal sync: the synchronization of the goals
- Goal status: the status of the goal alignment
- Goal log: the log of the goal alignment
- Available on web
- Event logging (action performed)
- Audit logging of goal alignment

**Super Admin User Journey:**
1. As a Super Admin, open the goal alignment.
2. Link the partners' goals.
3. Compare and sync the goals.
4. Review the goal status and log.

**Rules & Edge Cases:**
- A goal link connects the partners' goals.
- A goal comparison shows the differences between the goals.
- A goal sync aligns the goals.
- A goal status reflects the state (aligned, misaligned).
- A goal log records the goal alignment events.
- A goal without a partner cannot be aligned.
- Goal actions are audit-logged with the actor and timestamp.

### 3.3 Progress Check-ins
**What it does:** The Super Admin manages the progress check-ins so the partners check in on each other's progress.

**Sub-features:**
- Check-in creation: the creation of a progress check-in
- Check-in frequency: the frequency of the check-ins
- Check-in status: the status of the check-in (done, pending)
- Check-in log: the log of the check-ins
- Check-in history: the history of the check-ins
- Available on web
- Event logging (action performed)
- Audit logging of progress check-ins

**Super Admin User Journey:**
1. As a Super Admin, open the progress check-ins.
2. Create a progress check-in.
3. Set the check-in frequency.
4. Review the check-in status and log.

**Rules & Edge Cases:**
- A check-in creation records a progress check-in.
- A check-in frequency is the interval of the check-ins.
- A check-in status reflects the state (done, pending).
- A check-in log records the check-ins.
- A check-in history stores the past check-ins.
- A check-in without a partner cannot be created.
- Check-in actions are audit-logged with the actor and timestamp.

### 3.4 Friendly Competition
**What it does:** The Super Admin manages the friendly competition so the partners can compete in a supportive way.

**Sub-features:**
- Competition creation: the creation of a friendly competition
- Competition rules: the rules of the competition
- Competition leaderboard: the leaderboard of the competition
- Competition status: the status of the competition (active, ended)
- Competition log: the log of the competitions
- Available on web
- Event logging (action performed)
- Audit logging of friendly competition

**Super Admin User Journey:**
1. As a Super Admin, open the friendly competition.
2. Create a competition with rules.
3. Review the competition leaderboard.
4. Check the competition status and log.

**Rules & Edge Cases:**
- A competition creation links the partners in a competition.
- A competition rule defines the scoring of the competition.
- A competition leaderboard ranks the partners.
- A competition status reflects the state (active, ended).
- A competition log records the competitions.
- A competition without partners cannot be created.
- Competition actions are audit-logged with the actor and timestamp.

### 3.5 Support Sessions
**What it does:** The Super Admin manages the support sessions so the partners can support each other during tough topics.

**Sub-features:**
- Support session creation: the creation of a support session
- Support topic: the topic of the support session
- Support status: the status of the support session (scheduled, completed)
- Support log: the log of the support sessions
- Support history: the history of the support sessions
- Available on web
- Event logging (action performed)
- Audit logging of support sessions

**Super Admin User Journey:**
1. As a Super Admin, open the support sessions.
2. Create a support session with a topic.
3. Schedule the support session.
4. Review the support status and log.

**Rules & Edge Cases:**
- A support session creation links the partners in a support session.
- A support topic is the tough topic to discuss.
- A support status reflects the state (scheduled, completed).
- A support log records the support sessions.
- A support history stores the past support sessions.
- A support session without partners cannot be created.
- Support actions are audit-logged with the actor and timestamp.
