Multi-Tenant Django School Manager MVP

Django Multi-Tenant School Management MVP
Budget-12.5k INR Fixed
We need to build a small but properly structured multi-tenant School Management MVP using Django.
The goal of this phase is to create the core foundation with tenant isolation, school/user management, student/staff management, RBAC, audit logs, PWA setup, and background task setup.
Technology Stack
• Latest stable Python Django
• HTMX for CRUD operations
• PostgreSQL
• Celery, beat, Redis
• PWA setup

MVP Modules
1. Multi-Tenant Architecture
• Each school will be treated as a separate tenant
• data isolation between schools
• School-specific users, students, staff, and academic structure
• Tenant-aware permissions and queries
• Architecture must also support single-tenant deployment using the same codebase
2. Super Admin Panel
Use Django Admin for the platform-level Super Admin.
3. School Admin Panel
Custom Django + HTMX based panel.
(You can use tailwind or other for this to optimize frontend, you can use any mobile friendly theme for this)
School Admin should be able to manage:
• School profile
• School users with Roles and permissions
• Teachers & Staff
• Students
• Academic structure
School Admin must only access data belonging to their own school.
4. Flexible Academic Structure
Each school should be able to independently create its own:
• Academic Years
• Classes / Standards
• Sections / Divisions
• Streams where required
No class or standard names should be hard-coded globally.
Example:
• Nursery
• KG
• Standard 1
• Grade 5
• Class 10
• 11 Science
• 11 Commerce
• Any custom name
5. Student Management
Student management module

Excel Student Import
School Admin should be able to upload an Excel file and bulk-import students into their own school.
Import should include:
• Validation
• Error reporting
• Duplicate handling
• Class/section mapping
• Import summary
6. Staff & Teacher Management
Teachers will be treated as school users/staff with appropriate roles.
Required functionality:
• Activate/deactivate
• User account association

7. RBAC
Implement Role-Based Access Control.
Initial roles may include:
• Super Admin
• School Admin
• Teacher
• Staff
Requirements:
• Role-based menu/access control
• Backend permission validation
• Tenant-aware permissions
• Ability to add additional permissions later
8. Full Audit Logs
Important activities must be logged.
Examples:
• User created/updated
• Student created/updated
• Staff updated
• School settings modified
• Login-related activity where appropriate
• Record deletion/deactivation
• Role/permission changes
Audit records should contain useful information such as:
• User
• School
• Action
• Object/reference
• Date/time
• Relevant change information
9. PWA Setup
The School Admin interface should be configured as a proper responsive PWA.
10. Redis + Celery + Celery Beat
Complete setup required for:
At least one working background/scheduled task should be implemented to verify the setup.
Code Quality
The project should include:
• Clean Django enterprise project level structure
• Modular Django apps
• Proper database relationships and indexes
• Reusable HTMX components
• Proper migrations
• Basic validation and error handling
• Production-ready configuration structure
Final MVP Deliverables
• Multi-tenant Django application
• Django Super Admin panel
• School Admin panel
• School management
• School user management
• Student management
• Teacher/staff management
• Flexible academic structure
The focus of this MVP is to build a small, clean and scalable foundation without unnecessary modules or complexity.