Case Study 04: EduPath Learning Solutions — Presentation Notes
AI-Generated Content — Use for Reference Only
This content is AI-generated and has only been validated by AI review processes. It has NOT been reviewed or validated by certified Salesforce CTAs or human subject matter experts. Do not rely on this content as authoritative or completely accurate. Use it solely as a reference point for your own study and preparation. Always verify architectural recommendations against official Salesforce documentation.
Presentation Format
Total time: 30 minutes presentation + 30 minutes Q&A Strategy: Cover all 9 artifacts; go deeper on LMS integration, multi-portal design, and FERPA compliance
Opening (2 min)
“EduPath Learning Solutions needs to transform from disconnected systems into a unified platform serving three distinct audiences: B2B corporate sales, learner support, and content creators. The critical architectural challenge is integrating a custom AWS-based LMS that must remain the system of record while making its data actionable in Salesforce for sales, support, and self-service portals — all under three different privacy regimes with a hard FERPA deadline at month 6.”
Show System Landscape. Frame scale: 800 employees, 250K learners, 15K corporate accounts, 85 courses, 42M progress events in LMS. State single-org decision and multi-portal approach.
Deep Dive 1: LMS Integration Pattern (6 min)
“42 million progress events live in the LMS. The question is: what data does Salesforce actually need?”
Salesforce needs summarized data — enrollments, completion percentages, certifications, assessment scores. Not raw lesson-by-lesson progress. LMS publishes webhook events (enrollment, completion, certification, assessment score) to MuleSoft. MuleSoft transforms and upserts to Salesforce. For the reverse direction: portal enrollment requests flow through Platform Events to MuleSoft to LMS API.
Daily batch reconciliation compares enrollment counts as a safety net. External IDs (LMS_Enrollment_Id__c, LMS_Course_Id__c) ensure idempotent upserts.
Trade-off: Corporate dashboards show completion percentages and milestones, not granular lesson progress. Sufficient for renewal conversations and training manager needs. If granular progress is ever needed, it is available via API call to LMS — not stored in Salesforce.
Deep Dive 2: Multi-Portal Architecture (5 min)
“Three user populations, but only two need Salesforce portals.”
Corporate Portal (Customer Community Plus): ~2,000 corporate admins manage enrollments, view dashboards, download reports. Instructor Portal (Partner Community): 45 content creators view course metrics and revenue share.
Critical decision: individual learners (250K) do NOT get a Salesforce portal. They use the LMS directly. This avoids a 250K-user licensing problem and keeps the learner experience on the purpose-built LMS.
Sharing sets scope corporate admins to their own Account’s data. Instructors see only their assigned courses and aggregated metrics.
Deep Dive 3: FERPA Compliance (4 min)
“K-12 partnerships launch at month 6. FERPA is a hard constraint — without it, those partnerships cannot proceed.”
Architecture: K-12 flag on Account, FERPA flag on learner Contact, Restriction Rules limiting access to K12 Data Access permission set holders. Shield encryption on PII fields. Consent object with parental consent workflow. Shield Event Monitoring for audit trail.
Phase 1 prioritizes FERPA framework alongside Sales Cloud and LMS integration — the three are inseparable because K-12 accounts need Sales Cloud to manage and LMS integration to track learner progress.
Supporting Artifacts (9 min)
Data Model (1.5 min): Enrollment bridges Contact and Course. Certification is separate (multiple enrollments can contribute). License Allocation tracks seats per corporate account. Consent Record is jurisdiction-aware (FERPA/GDPR/Privacy Act).
Sharing Model (1.5 min): Account OWD Private with Territory Management (US/UK/AU). Enrollment inherits from Contact via Account. Course is Public Read Only. Consent Records are Private with permission-set-only access. Portal sharing sets scope corporate admins to their account.
Identity (1.5 min): Three IdPs: Google Workspace SAML for employees, Auth0 OIDC for portal users (fallback), corporate SAML federation for enterprise clients. Instructors use Google Workspace into Partner Community. MFA enforced across all paths.
Data Migration (1.5 min): HubSpot accounts/contacts and LMS learner data in Phase 1. Zendesk tickets as read-only cases in Phase 2. Stripe syncs going forward only — no bulk historical migration. 42M progress events stay in LMS.
Governance + Environments (1.5 min): ARB bi-weekly with VP Engineering as chair. 3-person CoE for knowledge transfer from SI partner. Full Copy sandbox for UAT, Partial Copy connected to LMS staging for integration testing. CI/CD via Salesforce CLI + GitHub Actions.
Roadmap (1 min): 18 months in three phases. Phase 1 driven by FERPA deadline. Phase 2 delivers portals and service. Phase 3 adds analytics and optimization. LMS integration runs continuously across all phases.
Transitions
- Opening to LMS Integration: “The first decision that affects everything else is how we integrate with the LMS.”
- LMS to Portals: “Once learner data flows into Salesforce, the next question is how we expose it to the right audiences.”
- Portals to FERPA: “One of those audiences — K-12 school districts — introduces a hard compliance constraint.”
- FERPA to Supporting: “With the three key decisions covered, let me walk through the supporting artifacts.”
- Supporting to Close: “Let me close with the top risks and mitigations.”
Closing (2 min)
Three risks and mitigation:
- LMS integration reliability: Event-driven with daily batch reconciliation as safety net; external ID-based upserts ensure idempotency
- FERPA month-6 deadline: Phase 1 prioritizes FERPA framework in parallel with Sales Cloud — not sequentially after it
- Small team (12 internal): SI partner handles build; 3-person CoE ensures knowledge transfer; governance prevents scope creep
“EduPath’s architecture balances platform unification with system-of-record clarity — the LMS owns learning, Salesforce owns relationships, MuleSoft bridges them, and privacy controls span both.”
Timing Checkpoints
| Segment | Duration | Cumulative |
|---|---|---|
| Opening | 2 min | 2 min |
| LMS Integration Deep Dive | 6 min | 8 min |
| Portal Architecture Deep Dive | 5 min | 13 min |
| FERPA Deep Dive | 4 min | 17 min |
| Supporting Artifacts | 9 min | 26 min |
| Closing | 2 min | 28 min |
| Buffer | 2 min | 30 min |