How to Set Teacher Access in an Online Language School

When an online language school starts to grow and you hire the second or third teacher, a problem appears that nobody talks about: everyone logs into the same system with the same access level. A new teacher can view all students' financial records, edit schedules that aren't theirs, and access enrollment data that has nothing to do with the class they're about to teach. It's not malicious - it's a configuration oversight. And any accidental update quickly becomes a headache.

Defining teacher access in a language school is one of the most overlooked parts of online school management, and also one of the most problematic when it hasn't been set up from the start.

Why this matters more than it seems

When the school's system has no role-based access control, you're left with two options - and neither is good.

The first is to give everyone full access. The teacher logs in, sees everything, and you hope nobody touches the wrong thing. It works while the team is small and trust is high, but the margin for error is enormous. An accidental edit on another teacher's schedule, a payment marked as received when it wasn't, a student deleted by mistake.

The second option is to create manual access profiles outside the system - a spreadsheet laying out who can do what - and trust that teachers will follow the rules. That doesn't scale. There's no way to verify that the rules are being respected, and you have no real control inside the system itself.

The real problem isn't trust. It's that a system without role-based permissions places operational responsibility on teachers who should be focused on teaching.

How most schools handle this today

The most common solution is to use separate tools for each function. Teachers only have access to Google Meet and the WhatsApp group. Finances live in a spreadsheet that only the owner accesses. Scheduling happens in Google Calendar with edit access open to everyone. Course materials sit in a Google Drive folder with a public link.

The result is that operations work - but in silos. Teachers can't see their own students' schedules without opening the right calendar. The owner can't tell whether a teacher updated the materials or not. Every tool has its own login, its own logic, its own access policy.

When the school grows to five or ten teachers, that model collapses. You start spending time managing access across four different systems, fixing what one teacher accidentally changed in another's calendar, with no way to audit what happened.

Some schools migrate to generic school management systems that include permission modules - but weren't designed for an online language school's operation. The access control is there, but the rest of the system doesn't fit: no integrated live classroom, no AI-powered lesson review, no per-student class credit tracking.

What actually makes a difference in real access control

For an online language school to run smoothly, access control needs to solve a few specific things.

First, teachers need to see their own students and schedules without seeing everyone else's. Access has to be granular by module - not a single global on/off switch.

Second, finances need to be restricted to the owner or administrative staff. Teachers have no reason to know how much a colleague bills, which students are behind on payments school-wide, or what the institution's sales history looks like.

Third, it needs to be possible to create more than one permission level. A pedagogical coordinator has different responsibilities than a freelance teacher. A senior teacher who supervises others may need broader access than someone who joined two weeks ago.

And fourth, access management has to live inside the same system the school already uses. If access control is in a separate tool, it won't be updated when a teacher leaves or when someone's role changes.

How Noladi organizes role-based access

In Noladi, each teacher's access is controlled by roles with configurable permissions. The school owner creates a role, selects which modules that role can access, and assigns users to that role.

Permissions are grouped by module: scheduling, students, finances, classrooms, reports, team, and others. This means you can create a teacher role with access to the live classroom and scheduling, but no visibility into the sales or financial reports module. And you can create a coordinator role that sees all students and the full team's schedules, but has no access to the school's settings.

When a teacher joins the team, you invite them by email, assign their role at the time of the invite, and they log in with the right access level right away - no extra configuration needed. If their role changes, you edit the role or reassign the user from a single screen.

You can also activate and deactivate users without deleting their history. If a teacher temporarily leaves the school, you disable their access without losing the records of the classes they've already taught.

Each team member's access lives inside the same system where classes happen, where schedules are managed, and where finances are tracked - no need to manage permissions across four different tools.

Get to know Noladi

If you manage an online language school with more than one teacher and still don't have role-based access control inside the system your team uses every day, Noladi was built to solve exactly that. Visit noladi.app/teacher and see how it works.