-
Notifications
You must be signed in to change notification settings - Fork 294
Open
Description
Currently, managing separate school branches or distinct schools under one organization within the Education Module requires implementing the Multi-Company feature and extensive User Permission adjustments. This setup is complex because key Education DocTypes, such as Student and Student Applicant, do not natively link to the Company Doctype (which is used to represent a Branch/School).
I propose adding native fields and logic to the Education Domain to simplify multi-school management, making it easier for large educational institutions to adopt ERPNext.
Proposed Changes/Behavior:
-
Introduce a "School/Branch" Field:
- Add a mandatory Link field for School/Branch (or similar Doctype) to all core Education DocTypes, including:
- Student
- Student Applicant
- Instructor
- Course Schedule
- Student Attendance
- Assessment
-
Permission Management:
- Implement User Permissions based on this new School/Branch field by default. This would allow an administrator or instructor from "Branch A" to only see the data linked to "Branch A," without manual, deep permission configuration.
-
Integration with Existing ERPNext Features:
- Ensure the new School/Branch Doctype can be linked to a Company Doctype. This maintains the critical financial separation and reporting (Fees, Expenses, Payroll) while simplifying the academic (Student, Course) separation.
-
Reporting:
- All standard Education Reports (e.g., Student Register, Fee Collection Report) should include the School/Branch as a primary filter option.
mohsinalimat
Metadata
Metadata
Assignees
Labels
No labels