Ten portals, so nobody wades through somebody else's screen
A parent should not see an admin dashboard, and a driver should not need one. Each role gets its own surface, and the roles who spend their day moving get a native Android app as well.
Owner & Principal
Everything — setup, oversight, approvals, consolidated reporting
Teacher
Today board, attendance, marks, quizzes, tasks, lesson plans, check-in, search and QR scanner
Parent
Attendance, results, fees and payment, leave, complaints, bus tracking, chat, search
Student
Timetable, results, quizzes, assignments, class feedback, leave, complaints, library, admit card, search
Accountant
Collections, challans, day-book, expenses, bank import
Receptionist
Inquiries, visitors, gate, phone log
Driver
Trip board, pick/drop custody, live GPS, SOS
Warden
Roll call, out-passes, leave, mess, night rounds
Librarian
Circulation, catalogue, fines
Ilmora Connect
The staff workspace — channels, DMs, module feeds, actions
Permissions and campus access are two different things
What kind of thing you may do, and whose data you may do it to, are separate axes. A campus-1 accountant with full fee rights still cannot see campus-2 challans — enforced in the database, not only in the interface.
- Roles are yours to build and rename per institute
- Screens, actions, exports and every report follow permissions automatically
- Campus grants are independent of role
- Past academic sessions are read-only, and need their own permission
- Portals are strict — an admin cannot open the teacher or student portal
- Two-factor login available, and changing a password revokes every other device
See Ilmora on your own data
A 30-minute demo with someone who knows the product. We will set up your institute properly afterwards — nobody self-serves their way into a broken configuration.