If you've ever run an online class, you know the ritual: copy the meeting link, paste it into an email or a message group, remind students not to share it publicly, and hope for the best. Meeting links were supposed to make online teaching simple. Instead, they became the weakest link in classroom security.
The problem isn't just opportunistic gatecrashers—though "Zoombombing" made global headlines in 2020. The deeper issue is architectural: when access to your classroom is controlled by a URL, anyone with that URL can get in. It can be screenshotted, forwarded, posted to social media, or leaked accidentally. You have no way to know who's passing it around, and no way to revoke it without starting over and resending a new link to everyone.
So we built Simpleclass differently. There are no meeting links. Students and teachers log in with an account, and access is granted by course enrolment. If you're not enrolled, you can't join—no matter how many links you collect.
How meeting links became a security problem
Meeting links were designed for the corporate world: ad-hoc video calls between colleagues who already trust each other. Drop a link in Slack, everyone joins, the call ends, and the link expires or gets forgotten. That works fine when your participants are known, employed adults within the same organisation.
But education is different. Classes run week after week with the same group. Students share devices, parents forward emails, siblings pass links to friends. A single leaked URL can let strangers into your classroom—and once they're in, they can disrupt the lesson, record without permission, or worse.
The response from most platforms was to bolt on waiting rooms, passcodes, and host-approval flows. These help, but they don't solve the root cause: the link itself is still a bearer token. Possessing it is enough to request entry, and every additional safeguard adds friction for legitimate participants.
Account and enrolment: access without links
Simpleclass takes a different approach. Every student and teacher has an individual account on your institution's custom subdomain. When a student is enrolled in a course, they see that course's upcoming sessions in their dashboard. When they click to join, the system checks their identity and enrolment in real time, mints a private, per-user token, and grants access to the session.
There is no URL to copy. There is no passcode to remember. There is nothing to leak. If a student tries to forward their dashboard link to a friend, that friend will hit a login screen—and even if they somehow obtained login credentials, they still wouldn't be enrolled in the course.
This model is sometimes called authenticated, enrolment-based access. It's how learning management systems have worked for years, and it's how most schools already think about their online classrooms: you're either in the class or you're not. Meeting links were always an awkward fit.
What you gain by removing the link
Switching from meeting links to account-based access delivers several immediate benefits:
- No more Zoombombing. Strangers can't join your session, because they don't have an account and aren't enrolled in your course.
- No more accidental leaks. There's no link to screenshot, forward, or post publicly. Each participant's access is personal and non-transferable.
- Simpler onboarding. Students log in once, see all their courses, and click to join. No hunting through emails for this week's link.
- Audit trail. Because every participant is authenticated, you know exactly who was in the session and for how long. Attendance is tracked automatically.
- Easier admin. Need to remove a student mid-term? Unenrol them from the course. Their access ends instantly, with no need to regenerate and redistribute links.
For tutoring centres and language schools running dozens or hundreds of sessions a week, these advantages add up quickly. You spend less time on access control and more time teaching.
How it works under the hood
When a student clicks to join a session in Simpleclass, the system performs several checks in sequence:
- Is the user logged in? (Authentication)
- Is the user enrolled in the course that owns this session? (Authorisation)
- Is the session scheduled and active?
If all checks pass, the backend mints a short-lived access token tied to that user and that session. The token is passed to the self-hosted media server, which allows the connection. The token cannot be reused by anyone else, and it expires when the session ends.
This is fundamentally different from a meeting link, which is a long-lived, shareable identifier. Meeting links were designed for convenience at the expense of control. Account and enrolment access inverts that trade-off: you keep full control, and participants still get a smooth, one-click join experience—once they're logged in.
What about guest access or trial lessons?
One common objection is that meeting links make it easy to invite a guest or run a trial lesson with someone who isn't yet a student. That's true—but there are better ways to handle it.
In Simpleclass, you can create a student account for a trial participant and enrol them in a trial course. It takes about thirty seconds, and you can remove them afterward if they don't continue. This approach still requires a login, but it gives you an audit trail and keeps your access model consistent.
For open webinars or large public events, meeting links may still make sense. But for ongoing classes—where you know your students, track their progress, and expect them back next week—account-based access is safer, simpler, and more professional.
The broader shift: platforms purpose-built for education
Removing meeting links is part of a wider trend: education is moving away from repurposed corporate video tools and toward platforms designed from the ground up for teaching.
Corporate meeting tools assume every participant is an equal, temporary attendee. Educational platforms recognise that teachers and students have different roles, different needs, and an ongoing relationship that spans weeks or months. That difference shows up everywhere—not just in access control, but in features like breakout room monitoring, attendance tracking, session recording with proper consent, and integration with course structures.
If you've been using Zoom, Google Meet, or Microsoft Teams for tutoring or language classes, you've probably felt the friction: breakout rooms that you can only visit one at a time, no way to require cameras on, no attendance log, and yes, those meeting links you have to copy-paste every week.
Simpleclass was built to eliminate that friction. No meeting links is just one example. We also host all video, recordings, and files in the EU, offer live monitoring across multiple breakout rooms at once, and bundle everything—video, whiteboard, chat, attendance—into a single platform with transparent per-teacher pricing. If you're curious how it compares in detail, our Simpleclass vs Zoom comparison covers the key differences.
Try it yourself
The best way to understand the difference is to experience it. Simpleclass offers a 7-day free trial with 1 teacher account and 50 student accounts—no credit card required. Set up a course, enrol a few students, and run a session. You'll see immediately how much simpler it is when there's no link to manage.
Meeting links were a compromise born of corporate video tools applied to education. It's time to move on. Access by account and enrolment is safer, simpler, and purpose-built for the way teaching actually works.