How to invite a new teacher to your language school and define what they can access

When a language school grows and you need to bring on a new teacher, the onboarding process is rarely straightforward. You need them to have access to the scheduling system, the classrooms, maybe the student records - but you don't want them seeing the school's full financial picture, billing data, or general account settings. The problem is that most tools schools use today weren't built for that kind of granular control.

The result: the new teacher gets too much access and sees things they shouldn't, or gets too little access and has to ask for permission every time they need to do their job.

Why defining access permissions matters more than it seems

When the school has a single teacher - the owner - there's no conflict. You control everything and know exactly where each piece of information lives. But the moment you bring on a second teacher, the equation changes.

The hired teacher needs to access their students' schedules. They need to enter the live classroom, see the class history, perhaps check student profiles. But they don't need to see how much the school earns, which student payments are overdue, the financial reports, or other teachers' data. That distinction matters both for confidentiality and for simplicity: a teacher who sees less of what isn't relevant to their work stays less confused and performs better.

On top of that, in a school with three or four teachers, you need to know that configuration changes don't happen by accident - that nobody deletes a booking by mistake, and that financial data stays protected.

How most schools handle this today

The most common approach is to manage access outside the main system. The new teacher gets the Google Meet password, the link to the scheduling spreadsheet, access to the Drive folder with materials. Each tool has its own access management, and the school owner has to handle that across at least four or five different places.

When a teacher leaves the school, you have to revoke access in each tool individually. If you forget one, they can still access Drive, the calendar, or the financial spreadsheet.

Another path schools try is using a single tool with simple user profiles: "admin" and "user." The problem is that binary split doesn't match reality. A teacher who runs their own classes and manages their own schedule needs more than "user" but far less than "admin." There's no middle ground, so the school ends up giving admin access to everyone for the sake of convenience.

A third approach: keep everything separated by email. The teacher gets the school's WhatsApp number, a shared email for reminders, and nothing more formalized. It works while the school is small, but it doesn't scale and provides no real control.

What an invitation and permissions system needs to do

A well-built team management system for a language school needs to solve at least three things.

First, the invitation process needs to be simple and trackable. You type the teacher's email, define what role they'll have, and they receive a link to create their account - no passwords sent over WhatsApp, no shared generic accounts, no manual process.

Second, access roles need to be configurable by module. "Admin" and "teacher" aren't enough. You need to be able to say: "this teacher can access scheduling and the student area, but cannot access financials or settings." And if the policy changes tomorrow, you edit the role and the change applies automatically to everyone who holds that role.

Third, the system needs to make the status of each invitation clear: who accepted, who hasn't logged in yet, whose invitation is still pending. If a teacher takes a while to accept, you need to be able to resend the invitation without creating a new process from scratch.

Finally, when a teacher leaves, you need to be able to deactivate their access in one place, with immediate effect.

How Noladi handles team management at a language school

Noladi has a team and permissions module designed for exactly this kind of operation. The flow starts in Settings, where you invite a new user by their email and define the role they'll hold - teacher or manager.

The invited teacher receives an email with a link to create their account. In the invitations panel you can see which invitations are pending, which have been accepted, and which have expired. If a teacher hasn't logged in yet, you resend the invitation with one click.

When the teacher joins the system, they access exactly what their role allows. Roles are configurable by module: you define which permissions each role has, and a teacher can have access to scheduling and the student area without access to financial reports or account settings. If you need to adjust the permissions for a role, the change applies immediately to all teachers with that role.

If you need to deactivate a teacher, you do it from the users panel - no need to revoke access across multiple separate tools. Your entire team is visible in one place, with each member's status and role.

That means the new teacher can start working the day after the invitation, with the right access from day one, without you having to manage passwords, shared folders, or different logins across separate tools.

Getting to know Noladi

If you're building or expanding an online language school and need real control over what each teacher can access, Noladi has this module ready to go, integrated with scheduling, classrooms, and the student area. You can explore it for free at https://noladi.app/teacher.