# 7.2 HR System Sync

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

---

## 7.2 HR System Sync

### 7.2.1 HRIS Connector
**What it does:** Connects the platform to the organization's HRIS (e.g., Workday, BambooHR, SAP SuccessFactors) so the employee roster is maintained automatically.

**Sub-features:**
- Connector setup per HRIS
- Field mapping (name, email, department, role)
- Connection test and health monitor
- Sync direction (HRIS is source of truth)
- Available on web and mobile
- Event logging (viewed)
- Audit logging of the HRIS connector

**Corporate User Journey:**
1. The admin opens Integrations → HR System → Connector.
2. The admin selects the HRIS and configures credentials.
3. The admin maps the fields.
4. The connection test passes.
5. The HRIS becomes the source of truth for the roster.
6. The admin opens Profile → "Activity" and confirms the events are recorded.

**Rules & Edge Cases:**
- While the connector is active, manual roster edits are overridden by the next sync.
- Events (viewed) are logged with the account and the timestamp.
- The HRIS connector is audit-logged with the account and the timestamp.

### 7.2.2 Employee Sync
**What it does:** Syncs the employee roster from the HRIS: new joiners are enrolled, department and role changes propagate, and the seat pool is reconciled.

**Sub-features:**
- New joiner auto-enrollment
- Department and role propagation
- Seat pool reconciliation
- Sync report (added, updated, unchanged)
- Available on web and mobile
- Event logging (viewed)
- Audit logging of the employee sync

**Corporate User Journey:**
1. The HRIS records a new joiner.
2. The next sync enrolls the joiner and assigns a seat.
3. A department change propagates to the platform.
4. The seat pool is reconciled.
5. The sync report lists added, updated, and unchanged rows.
6. The admin opens Profile → "Activity" and confirms the events are recorded.

**Rules & Edge Cases:**
- Auto-enrollment is skipped when no seat is available; the joiner is queued.
- Events (viewed) are logged with the account and the timestamp.
- The employee sync is audit-logged with the account and the timestamp.

### 7.2.3 Offboarding Sync
**What it does:** Detects leavers in the HRIS and deactivates their access, revokes the seat, and preserves their records for reporting.

**Sub-features:**
- Leaver detection from the HRIS
- Automatic access deactivation
- Seat revocation on offboarding
- Record preservation
- Available on web and mobile
- Event logging (viewed)
- Audit logging of the offboarding sync

**Corporate User Journey:**
1. The HRIS marks an employee as departed.
2. The next sync deactivates the employee's access.
3. The seat is revoked and returned to the pool.
4. The employee's records are preserved.
5. The admin opens Profile → "Activity" and confirms the events are recorded.

**Rules & Edge Cases:**
- Deactivation happens within one sync cycle.
- Preserved records remain visible in reports but not in the active directory.
- Events (viewed) are logged with the account and the timestamp.
- The offboarding sync is audit-logged with the account and the timestamp.