# 2. SIS Sync

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

---

## 2. SIS Sync

### 2.1 Automatic Enrollment
**What it does:** Automatically enrolls students into the platform from the Student Information System (SIS).
**Sub-features:**
- Enrollment trigger (new SIS record, scheduled batch, manual).
- Enrollment scope (institutions, grade bands, programs).
- Auto-enrollment into plans/courses (mapping rules).
- Enrollment confirmation and notification.
- available on web
- event logging (action performed)
- Audit logging of automatic enrollment
**Super Admin User Journey:**
1. Open Integrations & APIs → SIS Sync → Automatic Enrollment.
2. Set the enrollment trigger and scope.
3. Define the plan/course mapping rules.
4. Run a test enrollment and review the results.
5. Activate automatic enrollment.
**Rules & Edge Cases:**
- A student with no matching plan mapping is enrolled into the default plan or held.
- A duplicate enrollment (same student, same plan) is not created twice.
- An enrollment failure is logged and retried per the retry policy.
- A deactivated SIS record deactivates the platform enrollment.

### 2.2 Demographic Data Import
**What it does:** Imports student, parent, and guardian demographic data from the SIS.
**Sub-features:**
- Demographic fields imported (name, DOB, grade, contact, address).
- Field mapping (SIS field to platform field).
- Import scope (students, parents, guardians).
- Import log (records imported, updated, skipped).
- available on web
- event logging (action performed)
- Audit logging of demographic data import
**Super Admin User Journey:**
1. Open SIS Sync → Demographic Import.
2. Map the SIS fields to platform fields.
3. Set the import scope.
4. Run a test import and review the log.
5. Activate the import.
**Rules & Edge Cases:**
- A record with a missing required field is skipped and flagged.
- A field mapping conflict (two SIS fields to one platform field) is rejected.
- An import failure leaves existing data intact and is logged.
- A changed demographic updates the existing record (not a duplicate).

### 2.3 Schedule Integration
**What it does:** Integrates class periods and timetables from the SIS into the platform.
**Sub-features:**
- Schedule scope (class periods, timetables, exam schedules).
- Schedule mapping (SIS period to platform slot).
- Schedule sync frequency.
- Conflict detection (overlapping periods).
- available on web
- event logging (action performed)
- Audit logging of schedule integration
**Super Admin User Journey:**
1. Open SIS Sync → Schedule Integration.
2. Set the schedule scope and mapping.
3. Set the sync frequency.
4. Run a test sync and review conflicts.
5. Activate the integration.
**Rules & Edge Cases:**
- An overlapping period is flagged as a conflict, not silently merged.
- A schedule change updates the platform schedule and notifies affected users.
- A sync failure leaves the last good schedule intact.
- A period with no platform mapping is skipped and flagged.

### 2.4 Report Card Integration
**What it does:** Pulls and pushes report card data between the platform and the SIS.
**Sub-features:**
- Report card direction (SIS → platform, platform → SIS, both).
- Report card fields (grades, comments, attendance, GPA).
- Term/period mapping.
- Report card sync log.
- available on web
- event logging (action performed)
- Audit logging of report card integration
**Super Admin User Journey:**
1. Open SIS Sync → Report Card Integration.
2. Set the direction and fields.
3. Map the terms/periods.
4. Run a test sync and review the log.
5. Activate the integration.
**Rules & Edge Cases:**
- A report card for an unmapped term is not synced and is flagged.
- A grade conflict (platform vs SIS) is resolved by the configured source of truth.
- A sync failure is logged and retried.
- A finalized report card is not overwritten without an explicit re-open.

### 2.5 Sync Frequency, Field Mapping & Conflict Resolution
**What it does:** Configures the overall SIS sync cadence, field mappings, and how conflicts are resolved.
**Sub-features:**
- Global sync frequency (real-time, hourly, daily, manual).
- Central field mapping registry (SIS to platform).
- Conflict resolution policy (SIS wins, platform wins, manual review).
- Sync health summary (last run, success/failure counts).
- available on web
- event logging (action performed)
- Audit logging of sync frequency, field mapping & conflict resolution
**Super Admin User Journey:**
1. Open SIS Sync → Settings.
2. Set the global sync frequency.
3. Review and edit the field mapping registry.
4. Set the conflict resolution policy.
5. Review the sync health summary.
**Rules & Edge Cases:**
- A conflict with policy "manual review" is queued for review, not auto-resolved.
- A field mapping change takes effect on the next sync run.
- A sync frequency of real-time requires the SIS to support push events.
- A repeated sync failure raises an alert per the monitoring rules.