OmniKlasa is a closed-access school application designed around specific classrooms, teachers, homeroom tutors, and students. Its core purpose is to bring order to assignment workflows: the teacher publishes an assignment with a deadline, the student submits their work as a file, the teacher provides comments and feedback, the student can submit a revision, and both parties maintain full visibility over task status and complete communication history.
The project is not an electronic gradebook (e-dziennik), an attendance tracker, a payment processor, or a social network. It is explicitly scoped to solve a narrower problem: fragmented communication scattered across messaging apps, emails, loose files, and missed revision deadlines.
What has been built
The application supports user roles, classrooms, subjects, teacher assignments, tasks, student file submissions, inline feedback, structured revisions, classroom affairs, parent/student acknowledgments, CSV data export, notifications, and deadline reminders. Student accounts are not publicly registerable — access is strictly governed by assigned role and class/subject enrollment.
What the project demonstrates
OmniKlasa demonstrates designing an educational application with well-defined user roles, granular permissions, restricted access models, demonstration environments with fictionalized test data, and a clear architectural boundary between the public landing pages and the protected school application.
What the project is not
- It is not an electronic gradebook, grading system, or attendance tracking platform.
- It is not a social network or tuition/payment processor.
- It does not allow public student account registration — all access is role- and roster-bound.