Module: Core_Architecture

Platform Overview

Understanding the architectural components, multi-tenant isolation, and data flow of the EduFlow ecosystem.

EduFlow is not a single application, but a distributed ecosystem designed to handle the complex operational requirements of modern educational institutions. This document provides a high-level overview of our technical architecture.

Multi-Tenant Architecture

Every institution operates within a strictly isolated "Tenant". This guarantees absolute data privacy and security. The tenant identifier is often the subdomain (e.g., https://lincoln.eduflow.ng).

Row-Level Security

Database queries are automatically restricted at the Postgres level ensuring cross-tenant data leakage is cryptographically impossible.

Edge Delivery

Assets and static pages are served from edge nodes closest to the user via AWS Amplify, reducing latency to <50ms.

Real-time Sync

WebSockets power instant chat, live attendance tracking, and immediate payment confirmations without page refreshes.

Role-Based Access Control (RBAC)

The platform morphs its interface based on the authenticated user's role. A Bursar sees a vastly different application compared to a Teacher or a Parent.

  • Administrators & Owners: Have global access to system configurations, financial audits, and security settings.
  • Bursars: Restricted to the Financial Suite, managing ledgers, payroll, and debt networks.
  • Teachers: Focused on academic delivery, lesson planning, and student behavioral tracking.
  • Parents & Students: Provided with read-only views of results, attendance, and interactive portals for fee payment.