School app · for staff
Eleven people open the same app and get eleven different ones
The Edoovi school app puts the running of the school on staff phones — approvals, attendance, fee collection, circulars and gate passes. It is on Android and iOS, and what any one person sees is decided by their role, so a gatekeeper and a director open the same install and meet completely different screens.
- Android & iOS
- Eleven staff roles
- In every plan
Same install, different software
Change the person. Watch the app change.
There is no single “admin screen” that everybody learns and then ignores the irrelevant half of. What opens is decided by the role, so nobody is trained on work that is not theirs.
Waiting on you
- Leave requests 4
- Concerns from parents 2
- Circulars to approve 1
The queue of things only a principal can clear.
Your classes today
- VIII-B attendance Not marked
- Class test marks Pending
- Homework set Done
Only the classes and subjects that teacher is mapped to.
This month
- Fee collection Live
- Outstanding dues Live
- Attendance by section Live
The whole school, read-only, drawn from the same ledger.
At the desk
- New enquiries 6
- Fee collection Open
- Appointment requests 3
Enquiries, collection and the people asking to come in.
The gate
- Log a visitor Open
- Issue gate pass Open
- Still inside 7
The narrowest role in the system, deliberately.
Routes running
- Route 4 On the way
- Route 7 At school
- Unassigned students 2
Routes, stops and who is allocated to which bus.
Six of the eleven roles, with the shape of each home screen. The figures are an illustration, not a school’s real queue.
Who reaches what
The rules are the same on a phone as on a desktop
An app is not a lighter set of permissions. Four of the eleven roles, against the things a school worries about somebody being able to do.
| Can they | Principal | Class teacher | Front office | Gatekeeper |
|---|---|---|---|---|
| Approve leave | Yes | No | No | No |
| Mark a class register | Yes | Yes | No | No |
| Enter marks | Yes | Yes | No | No |
| Collect a fee | Yes | No | Yes | No |
| See dues and defaulters | Yes | No | Yes | No |
| Send a circular | Yes | No | Yes | No |
| Log a visitor | Yes | No | Yes | Yes |
| Whole-school reports | Yes | No | No | No |
Between two classes
The pile that used to wait on a desk
Leave requests, parent concerns and circulars waiting to go out all arrive in one queue. Clearing it is a thing done standing in a corridor, and each decision writes to the same records the register and the payroll read.
Go on — clear it.
An illustration of the queue. The requests are made up; no real staff member, student or family is shown.
- Staff leave Class teacher, VIII-B Half day, Thursday. Cover arranged.
- Student leave Roll 14, Class VI-A Two days. Raised by the parent in the app.
- Parent concern Class IX-C Asking about the transport route change.
- Circular Whole school Sports day moved to Saturday. Ready to send.
Cleared
Every decision has already written to the register, the payroll and the parent app. There is no desk to go back to.
The same job, twice
Four steps either way. Count the ones that need a desk.
One leave request, handled two ways. Nothing here is a saved-time claim — it is the same four steps, and where each of them has to happen.
Tied to a desk
4 of 4 need one
On the app
0 of 4 need one
See the request
Get what you need
Decide
Make it count
The narrowest role
A gatekeeper reaches the gate and nothing else
No fees, no marks, no staff records — logging a visitor in, issuing a gate pass, and knowing who is still on the campus. That is the entire role, and it is meant to be.
It is also the best test of role-based access: if the narrowest role can reach something it should not, the rules are not real.
An illustration of a school gate log with three entries: a parent and a vendor signed in with gate passes, and the parent signed out again.
Management
One number, before the meeting rather than after
A director does not want a report emailed on Monday. They want the figure now, and they want it to be the same figure the office would quote if somebody walked in and asked.
- Collection so far Against the same ledger the office receipts into.
- Dues and defaulters A live read, not a list compiled at month end.
- Attendance by section Where a section has dropped, before anyone reports it.
The obvious worry
Putting it on phones does not loosen anything
The reasonable question about a school app is whether the convenience quietly cost something. It did not, because the app is a view of the same system rather than a lighter version of it.
-
The role decides, not the device
A phone widens nobody's access. What a person reaches in the app is exactly what they reach in a browser.
-
OTP still stands in the way
The sensitive money actions — a fee discount, a cancelled receipt — stay behind OTP verification in the app too.
-
The data has not moved
The app reads the same records in the same Indian data centres. There is no second copy living on a handset.
Staff app questions
What a school checks before rolling it out
Which staff roles can use the school app?
Eleven, across the plans: admin, class teacher, principal, authority or director, academic coordinator, front office, library, transport, security or gatekeeper, driver or attendant, and the student and parent side. Each one is a different set of screens on the same install.
Can a teacher see another teacher's classes?
No. A class teacher reaches the classes and subjects they are mapped to and nothing further. Role-based access runs through the whole of Edoovi, so the app is not a lighter set of rules than the browser — it is the same rules on a smaller screen.
Can a principal approve leave without going back to the office?
Yes. Leave requests from staff and from parents arrive in a queue in the app and can be approved or turned down from wherever the principal is standing. The decision writes to the same records the register and the payroll read, so nothing has to be re-entered at a desk afterwards.
Do staff and parents install the same thing?
No. They are two separate downloads — the school app for staff and management, and the Parent and Student app for families. Both are on Android and iOS, and both are included rather than charged for on top.
What does a gatekeeper actually see?
The gate, and only the gate: logging a visitor in, issuing a gate pass, and who is still inside the campus. No fees, no marks, no staff records. It is the narrowest role in the system and it is meant to be.
Can management see fee collection from the phone?
Yes. Collection, dues and the defaulter list are readable on the app, drawn live from the same ledger the front office collects into — so the figure a director sees on the way to a meeting is the figure the office would quote if asked.
Included in every plan
Give the staff room its own screen
Roles are set up with you during onboarding, so nobody is handed an app full of work that is not theirs. Start with one class on the free trial.
Or just look at the app: Google Play · App Store