A school's records include children's names and photographs, guardians' phone numbers, medical notes, fee history and staff salaries. You do not need to be a technical expert to protect them. Most problems come from small habits: a shared password, a backup nobody has tested, a former teacher whose login still works. This is a practical checklist of those habits. It is general guidance, not legal advice, so check any specific obligations with a qualified adviser.
1. Know what you hold and who needs it
Begin with a simple list on one page:
- Student data: profile, photos, documents, marks, attendance, fees, health and conduct records.
- Staff data: contact details, qualifications, salary, leave and bank details.
- Financial data: receipts, dues, bills and payroll.
- Parent data: mobile numbers and e-mail addresses.
Mark the most sensitive items: medical details, counselling notes, salaries and identity documents. These deserve tighter access than a class list.
2. Give each role only what it needs
The principle is "least access". The receptionist does not need payroll. The librarian does not need fee dues. A teacher needs her own classes, not the whole school.
- List your roles: principal, vice principal, accountant, receptionist, teacher, librarian and so on.
- For each, write down which screens they need.
- Give each person their own login at the matching role.
- Review the list every term.
Avoid giving "admin" to someone because it is easier. Keep full administrator access to one or two trusted people. In My KalviKoodam, access follows twelve roles, and the reports a person sees follow the screens their role can open. You can see how two typical roles look on the principal and accountant pages.
3. Passwords that people will actually use
Rules that are too strict get written on sticky notes. Aim for sensible ones:
- One login per person. Never share a login, even for the "front desk".
- A long phrase is better than a short complicated one. Three or four unrelated words work well.
- A different password for school software than for personal e-mail or social media.
- Change a password immediately if someone saw it typed or if a phone was lost.
- Ask new users, including parents, to change the first password on first sign-in.
Remind staff never to say a password over the phone or in a WhatsApp message, and that nobody from the school office will ask for it.
4. Backups: three rules
A backup is a copy you can restore, held somewhere that will not fail with the original. Three rules cover most schools.
- Frequent. Daily for the database during the school year, and an extra copy before big events such as year-end promotion or result publication.
- Separate. Keep a copy away from the server that holds the live data, such as in a different account, drive or location. If the same hosting account holds both, one failure loses both.
- Tested. At least once a term, restore a backup to a test place and check that students, fees and marks are all there. An untested backup is a hope, not a backup.
Also back up uploaded files such as photos and documents, not only the database. Write down who is responsible, where the copies live and how to restore. If that person leaves, someone else should be able to follow the page.
5. If the data is on your own server
Hosting your own data gives the school control, but it also gives the school a few jobs. The honest list:
- Pay hosting on time, and keep the renewal date on a calendar.
- Keep the hosting panel login with two trusted people, not in a single phone.
- Switch on automatic backups in the hosting panel, and download a copy regularly.
- Keep the software and PHP version updated as the vendor advises.
- Use HTTPS on the school's address so logins are not sent in plain text.
A good vendor will help with the first setup. See cloud or your own hosting for a comparison of the two approaches. My KalviKoodam is installed on the school's own hosting, so records are not stored on our servers.
6. When people leave
This is the most commonly missed item. On the last working day of a staff member:
- Switch off their login. Do not delete it, so history stays correct.
- Hand over their duties, such as class teacher and timetable periods.
- Change any shared passwords they knew, such as a shared mailbox or messaging account.
- Collect school devices, keys and ID cards.
When a pupil leaves, their parent and student logins should also stop working. In My KalviKoodam, a pupil who leaves and a staff member made inactive lose their logins straight away, and the HR module lets you hand over a departing teacher's periods in one step. Put a leaver checklist on the office wall.
Vendors and other outsiders
Anyone outside your staff who touches the data is part of your security. That includes the software vendor, the hosting company, an SMS provider, a part-time computer technician and the person who built your website. For each one, ask three questions: what can they see, how do you remove their access when the work ends, and where is it written down? Give outsiders the narrowest access that lets them do the job, and ask the vendor to confirm in writing how your records are handled.
7. Everyday habits at the office
- Lock the screen when you step away from the computer. Use short auto-lock times.
- Do not leave printed class lists or fee dues on counters.
- Print only what you need, and shred old printouts of sensitive details.
- Be careful about sending data by WhatsApp or e-mail. A forwarded file can never be recalled.
- Keep browsers and phones updated, and use a reputable antivirus where staff share computers.
- Do not let visitors or parents use office computers.
Photographs deserve special care. Use them for the school's purposes, such as ID cards, and get consent before putting a child's picture on a public page.
8. Phones and public Wi-Fi
Teachers will use their own phones. Ask them to lock their phone with a PIN, to log out on shared devices and to avoid public Wi-Fi for logging in. If a phone is lost, the first step is to change the password and tell the office the same day.
9. Decide what you will do if something goes wrong
Write a half-page plan before you need it:
- Who is told first, and who decides?
- How do we stop the problem: change passwords, switch off accounts, take the site offline?
- How do we restore from backup, and how long will it take?
- Who informs parents and staff, and what do we say?
- What did we learn, and what do we change?
Practise by asking "what if the fee clerk's laptop is stolen tonight?" and see whether the answer is obvious.
A short monthly routine
- Review who has access and remove what is not needed.
- Check that the latest backup exists and has a sensible size.
- Look at the message and receipt logs for anything odd.
- Confirm that every leaver's login is off.
Bringing it together
Good security is mostly habit and a few controls that stay out of the way. If you want to see how roles, logins and exports work in practice, book a demo and ask for a walk-through of role access, or read the FAQ. Our school management software page describes the modules, and the students module explains how portal logins are created and removed.