Role-Based Access Control for School Staff

In a school, "who can see what" is not an IT preference — it is a student data question. Lekktura enforces access by role: principals see the full school, administrators support them, teachers see only the classes they teach, and parents see one child.

Four roles, four levels of access
Teachers scoped to their classes
Enforced by the platform

Start 30-Day Free Pilot See the full platform

No credit card required · Set up in days, not months

Role-Based Access Control for School Staff in Lekktura — school dashboard preview

Why "everything for everyone" goes wrong

Small schools often start with shared access because it is simpler. It works until the first accidental edit to another class’s records, or the first awkward question about who was able to read a particular student’s file.

Scoped access solves both at once. It reduces mistakes because there is less on screen to click by accident, and it narrows student data exposure to the staff who actually need it.

The roles

Roles map to how schools are actually staffed rather than to a generic permissions matrix that has to be configured before anyone can start.

What each role can see and do
Role	Can see	Can manage	Billing
Principal	The whole school	Staff, classes, students, parent access	Yes
School administrator	The whole school	Classes, students, parent access	No
Teacher	Only their assigned classes	Their own classes, students in them, grades, attendance, behavior	No
Parent	One child, read-only	Nothing	No

Joining a school

A principal invites a teacher by email. The teacher accepts and lands directly in the classes they have been assigned. There is no shared password and no generic staff login, which means access can be traced to a person rather than to a credential the whole staffroom knows.

When staff change mid-year

Staffing changes during a school year are normal, and they are where access control usually breaks. A subject can be reassigned from one teacher to another, and a teacher can be removed from a class without deleting anything they recorded.

The records stay with the school. A departing teacher loses access; the grades, attendance, and behavior they entered remain part of the class history for whoever picks the class up.

Why this matters for compliance

Limiting access to those with a legitimate educational interest is a foundational expectation under FERPA. Role-based access is how that principle is implemented in practice rather than promised in a policy document.

It also makes the answer to a parent question — who at this school can see my child’s record — short, specific, and true.

Which schools this fits

Role-based access control matters most where staff wear several hats and informal access creeps in — which describes most small schools rather than large districts with an IT department.

It is also what makes a short, honest answer possible when a parent asks who can see their child's record.

Private schools and independent schools with shared office staff

Charter schools onboarding teachers mid-year

Small districts without an IT team to manage user permissions

Schools with student data protection obligations under FERPA

Schools that currently use a shared or generic staff login

Schools where subject teachers should not see the whole year group

What to check when comparing access controls

Permissions are rarely on a buying checklist and are frequently the thing a school regrets. Worth checking:

1
Whether teacher access is scoped automatically or has to be configured per person
2
Whether a teacher can reach classes they do not teach
3
Whether there is any shared or generic staff login
4
How quickly access ends when someone leaves
5
Whether removing a teacher also removes the data they entered
6
Whether an administrator can be given operational access without billing control

Questions before you start

Short answers to what schools ask most.

What roles exist in a school account?

Principal, school administrator, teacher, and parent. Principals see the whole school and manage the subscription. Administrators support daily operations. Teachers see only their assigned classes and subjects. Parents see a single child through a private link.

Can a teacher see classes they do not teach?

No. A teacher’s visibility is limited to the classes and subjects they are assigned to. This is enforced by the platform on every request rather than relying on staff avoiding screens they should not open, which is where convention-based systems tend to fail.

How do teachers join the school?

The principal sends an email invitation. The teacher accepts and is placed directly into the classes they have been assigned, with no shared password. Access belongs to a named person, which is what makes it possible to remove it cleanly later.

What is the difference between a principal and an administrator?

Both see the whole school. The principal additionally manages the subscription and plan. An administrator can run day-to-day operations — classes, students, staff, parent reports — without being able to change billing, which is usually exactly the split a school wants.

What happens when a teacher leaves?

Their access is removed and their subjects can be reassigned to another teacher. Everything they recorded stays with the school, so the class history is intact for whoever takes over. Access ends; data does not leave.

Does this help with FERPA?

It supports it. FERPA expects access to be limited to those with a legitimate educational interest, and role-based scoping is the practical mechanism for that. It is not a substitute for your own policies, but it makes them enforceable rather than aspirational.

What is role-based access control in school software?

Role-based access control means what a person can see is determined by their role, not configured individually. In a school that maps to principals, administrators, teachers, and parents — each with a different and automatically applied level of access to student data.

Can office staff get access without seeing everything?

Yes. The school administrator role covers day-to-day operations across the school — classes, students, staff, parent access — without control of the subscription. That is usually the split schools want for office staff.

More for schools

Other parts of the platform your school will use every day.

See everything Lekktura does for schools

Run your whole school on one platform

Create your school, invite teachers by email, and start recording real grades and attendance during the pilot. No installation, no IT project.

Start 30-Day Free Pilot Talk to us first

30-day free pilot · No credit card required