Running an Institution

Roles and Permissions: Who Should See What in Your School's System

studive-official0 comments
Roles and Permissions: Who Should See What in Your School's System

The default in most schools is that everyone with a login can see everything. That is convenient, and it is the source of most of the awkward incidents that follow.

When a school first sets up a management system, permissions feel like an obstacle. Everyone needs to get things done, nobody is quite sure who will need what, and the fastest route is to give the whole staff broad access and move on.

It works until the day a teacher opens a colleague's salary, or a clerk edits last term's marks, or a parent asks who exactly was able to see their child's medical note.

The principle, stated plainly

People should see what they need for their own work, and not the rest. Not because staff are untrustworthy — almost all of them are — but because access that exists will eventually be used, and because the school cannot answer questions about who saw what if the answer is “everyone”.

Start from jobs, not from people

The common mistake is configuring permissions per person: Sir Ahmed gets these screens because he helps with admissions sometimes.

Six months later Sir Ahmed has moved on, somebody inherited his login, and nobody can reconstruct why it has the access it has.

Define roles by job instead — class teacher, head of department, admissions clerk, accountant, principal — and assign people to roles. When someone changes job, you change their role, not twenty individual switches.

Four categories worth separating

Student academic data. Marks, attendance, reports. Teachers need their own classes; heads of department need their subject; the principal needs everything. Few others need any of it.

Student personal data. Addresses, guardian details, medical notes, anything sensitive. A narrower group than academic data, and often the one schools are most casual about.

Money. Fees, concessions, salaries, expenses. Should be visible to the office and the principal, and essentially nobody else. Salary data in particular causes lasting damage when it circulates.

Configuration. Who can create users, change roles, alter the academic calendar, delete records. This is the smallest group of all — usually two people — because mistakes here are hard to undo.

Scope matters as much as permission

“Can view attendance” is not one permission. There is a large difference between viewing attendance for your own section, your campus, or the whole organisation.

A system that only offers permissions without scope forces you to choose between a class teacher seeing nothing and seeing everybody. Scope is what lets a campus administrator run their campus without seeing the other one.

The two rules that prevent most trouble

Nobody grants themselves anything. The person who can change permissions should not be the person whose work is constrained by them, and a system where an organisation can quietly expand its own access is not a permissions system at all.

Changes leave a trace. Who changed what, when. Not to catch people — almost every change is routine — but because the one time it matters, memory is not evidence.

Review it once a year

Permissions drift. Someone needs temporary access during admissions and keeps it for three years. A staff member leaves and their login stays active because nobody owns deactivation.

Once a year, list everyone with access and what they can reach, and ask whether it still matches their job. It takes an afternoon. Schools that do it are consistently surprised by at least three entries, and the most common is an account belonging to someone who left.

Comments

Leave a reply