Module dependency reference

The technical view: which module depends on which. Install bottom-up; bridges and analytics activate once their dependencies are present.

Layer	Modules	Depends on
Foundation	`ep_core` (SIS)	—
Academic	`ep_academic`	`ep_core`
Finance	`ep_fees`	`ep_core`, `ep_academic`
Services	`ep_library`, `ep_transport`, `ep_hostel`, `ep_meals`	`ep_core` (+ `ep_academic` for hostel)
Admissions / people	`ep_admissions_crm`, `ep_hr_payroll`, `ep_alumni_giving`	`ep_core`
Welfare	`ep_health_clinic`, `ep_counseling`, `ep_special_needs`, `ep_discipline`	`ep_core`
Exams / curricula	`ep_assessment_engine`, `ep_ib_dp/myp/pyp`, `ep_cbet`	`ep_core`, `ep_academic`
Bridges	`ep_fees_*_bridge`, `ep_academic_library_bridge`, `ep_assessment_gradebook_bridge`	both sides they connect
Analytics	`ep_ai_insights` (Bria)	`ep_core`, `ep_academic`, `ep_fees`

Soft dependencies — Apps also guard optional links with 'model.name' in self.env, so a module installs and runs even when a sibling is absent. Bridges turn the link on when both are present.

Was this page helpful?