Multi-Accounting in Online Education: Tutors, Courses, LMS

GetAntik editorial team · October 12, 2026 · 11 min read

How tutoring agencies, course creators and L&D vendors run dozens of accounts across Preply, Kajabi and corporate LMS without bans.

An online school, a tutoring agency, or a corporate training vendor eventually hits the same wall: there are more students, teachers, curators and client LMS tenants than one browser with one Chrome profile can handle. Someone logs into a tutor's account to check the schedule, someone else opens a test student profile in the same window where an admin just logged into the course dashboard — and a week later the account gets suspended for "suspicious activity," or reviews from different students get mixed up.

This isn't about dodging platform rules. Services like Preply, iTalki, Kajabi, Udemy Business or Coursera for Business explicitly allow agencies and schools to manage multiple accounts — tutors, curators, test students. What's forbidden is different: padding reviews with fake students, using the same person to repeatedly claim free trial lessons, or faking activity to game the algorithm. Separating roles and access is exactly what multi-accounting tools are built for, and that's what we'll walk through.

Who actually runs into this

Tutoring agencies. A company manages 30–80 teachers on Preply or iTalki: each has their own profile with a schedule, reviews, and student messages. The agency's manager needs to log into these accounts for moderation, but credentials can't be shared in a group chat — that's a direct path to losing access when someone leaves.

Course authors and sellers. A school on Kajabi or Teachable sells several products under different brands, each with its own dashboard for mailings, webinars, and pricing tiers. On top of that, they need test student accounts — to check how the member area looks, whether the automated funnel works, whether emails arrive.

L&D vendors and corporate training providers. A contractor serves 10–20 clients, each with its own tenant in Coursera for Business, Docebo, or Udemy Business. Access is separate, client-side admins require a distinct login per company — mixing up progress reports between organizations is not an option.

QA staff and instructional designers. They need to view a course simultaneously as a student, a teacher, and an administrator — three different roles, three different permission sets, and confusing them in one browser is both inconvenient and risky: a draft lesson could accidentally get published under a real teacher's name.

Why one browser for everyone breaks faster than you'd think

The core problem isn't the number of passwords — it's the browser fingerprint. When an agency manager logs into five different tutor accounts from the same Chrome instance, anti-fraud systems at Preply or iTalki see the same canvas, the same font set, the same WebGL rendering, the same IP. From the platform's point of view, that looks like one person operating under five identities — exactly what these platforms try to catch while fighting fake reviews and inflated lesson counts.

The second problem is cookies and sessions bleeding into each other. One tutor sees another's messages, a test student account unexpectedly gets curator rights because a neighboring tab still has an active admin session. In practice this seems minor — until the school mass-emails the wrong group of students under the wrong teacher's name.

The third is access handoff during staff turnover. Tutors at language agencies rotate faster than managers at a typical office. If passwords sit in a shared file instead of a proper role system, every such transition risks leaking access to dozens of student accounts.

Where education platforms specifically trip people up

Language platforms have a quirk most other services don't: the tutor needs the browser's timezone and locale to match the location declared in their profile — otherwise the schedule of available slots shifts, and support starts asking questions about geolocation. This is a case where fingerprint consistency isn't abstract hygiene — it directly determines whether students see the right time slots in their own timezone.

Structuring a profile pool for an education project

The practical approach: one profile per entity — one tutor, one course brand, one client tenant, one test role. In GetAntik, each such profile runs on an isolated browser engine with a managed fingerprint — OS, browser version, screen, fonts, WebRTC, timezone and language are all pulled from the proxy's exit IP, so a tutor profile based in Barcelona actually looks like a device in Barcelona, not the same machine running the manager's profile for a tutor in Kyiv.

The pool structure usually looks like this:

1. Group by product or brand. If a school sells three courses under different brands, each brand gets its own profile group: sales account, support account, test student.
2. Group by role. Inside a tutoring agency — separate profiles for teacher accounts and separate service profiles for managers who log in for moderation or to handle complaints.
3. Test profiles for QA. A separate "test student," "test curator," "test admin" group — so instructional designers and developers don't touch the live accounts of real people. A similar role-based breakdown is covered in detail in testing a product across different environments, which also explains why mixing test and production sessions in one browser is a bad idea well beyond education platforms.

For an agency with fifty tutors plus a dozen test and service profiles, the Team plan with 300 profiles, role limits, and per-member permissions covers this with room to spare; a small school with one brand and a couple of curators fits comfortably into the Base plan at 100 profiles.

Proxies, timezones and language — the fine print for language and global platforms

On platforms where a teacher declares a country of residence (Preply, iTalki, Cambly), a mismatch between the proxy's geolocation and the declared address is a common cause of a "false profile information" suspension. So each tutor account needs not just a working proxy, but one with an exit IP in the same city or at least the same country listed in the teacher's profile, with the browser's timezone and language pulled from that same IP.

Corporate LMS situations are different: the client sets the access geography requirements themselves, sometimes through a VPN or a whitelisted IP on their end, and the contractor's job is not to confuse which proxy logs into client A's tenant versus client B's. A built-in proxy manager with checks and per-profile binding removes this risk — it's easier to pick a proxy once when creating a profile than to later explain to a client why an administrator logged into their LMS from an IP that had shown up for three other organizations. More on choosing the right proxy type for the task, and when residential proxies matter more than datacenter ones, is in the article on proxy types for multi-accounting.

Team roles, profile handoff, and 2FA

In a tutoring agency or an L&D vendor, there's almost always a role split: someone handles sales and client relationships, someone moderates content, someone owns billing. Giving everyone identical access to every account is an unnecessary risk, especially with corporate clients who demand an audit trail of who accessed their data and when.

A role model with owner, admin, member and finance permissions, plus per-member profile limits, solves this: a sales manager sees only their clients' profiles, a finance person sees only billing dashboards, a curator sees only the profiles of students in their group. When a tutor or manager changes, the profile gets handed off to a new employee without passing a password through a chat app — ownership simply changes inside the system. How that handoff works, and the common mistakes teams make during staff changes, is covered in the article on roles and profile handoff.

A separate pain point for education platforms is two-factor authentication. A Preply tutor typically has a phone number or authenticator app tied to their account, and if that key lives only on the tutor's personal device, the agency loses access the moment there's a conflict or a resignation. Storing the 2FA key attached to the profile rather than to a specific person's personal phone removes that dependency — the key stays with the company even after the tutor leaves.

Common mistakes

One browser for all tutors "to save time." Saving five minutes on spinning up a new profile ends up getting half the accounts banned at once, because anti-fraud systems see the same fingerprint across dozens of different teachers.

A proxy that ignores the profile's geolocation. Assigning a cheap datacenter proxy from a neighboring country to a tutor who listed a specific city in their profile is a reliable way to get a support request asking to verify identity.

Mixing test and live accounts. An instructional designer opens a test student in the same window where they just checked a mailing from a real curator account — and an automated email goes to the wrong audience. Separating these into distinct profile groups from the start solves the problem completely.

A shared password for a client's LMS across the whole team. When the employee who knew the client tenant password leaves, the team either has to reset the password for everyone or hope the former colleague doesn't use it. Role-based access and activity logs close this risk immediately — you can see exactly who logged in and when, with no passwords floating around in group chats.

Skipping warm-up for new tutor accounts. A fresh teacher profile that sets up ten slots, messages five students, and updates its description within the first hour looks suspicious for a brand-new account. Methodically warming up activity over the first few days cuts the suspension rate for new tutors far more than it seems like it should.

What it costs and when it pays off

If an agency runs 25 tutors plus 5 service profiles, the Starter plan at 20 profiles is already too small, while Base at 100 profiles for $44/month comfortably covers growth up to a hundred teachers without an immediate jump to Team. A school with several course brands and separate test accounts usually needs 30–50 profiles, which also fits inside Base.

What's worth comparing isn't the plan price in isolation, but the cost of one suspended tutor account: an account with a review history and rating takes weeks to recover, and sometimes doesn't recover at all — you start rebuilding reputation from zero. The methodology for calculating this kind of economics, with concrete numbers, is in the article on multi-accounting unit economics and team budgets — it applies to education projects just as well, you just substitute teacher and curator accounts for ad accounts.

For companies that have already grown past a hundred profiles and are losing track of groups, courses, and roles, it's worth planning pool structure early — how to name groups, who owns what, and how to find the right profile in ten seconds instead of ten minutes. A detailed approach to organizing large profile volumes without chaos is in the article on organizing hundreds of profiles.

You can start with the free plan at 3 profiles to see how isolated profiles behave on a specific platform — Preply, Kajabi, or a corporate LMS — before migrating the entire tutor pool over. The feature list and how profile management and team access work are on the site, and plan details are on the pricing page.

FAQ

Can a tutoring agency legally run dozens of accounts on one platform? Yes, as long as each account belongs to a real teacher or a real test role, not something created to inflate reviews or bypass trial lesson limits. Most tutoring platforms explicitly allow an agency model of operation — what's banned is faking activity and fake identities.

Does every tutor profile need its own proxy? Yes, especially if the platform relies on tutor geolocation. A proxy with an exit IP in the declared city or country reduces the number of support requests asking to verify identity and location.

How do you quickly check that a new tutor profile doesn't look suspicious to the platform? Build up activity gradually over the first few days — fill out the profile, add schedule slots in small batches, avoid sending bulk messages within the first hour. A sharp spike in activity on a fresh account is a common trigger for manual moderation review.

What should you do with test student accounts when a course gets updated? Keep them in a separate profile group that doesn't overlap with live teacher and curator accounts, and don't log into them in the same window where an admin panel was just open — otherwise sessions can get mixed up and a test notification can end up going to real students.

How do you hand off access to a client's LMS when a curator leaves the company? By transferring profile ownership inside the role system, without forwarding the password to a new employee through a chat message. This preserves the activity history and doesn't require the client to reset their password on their end.

online educationmulti-accountingtutoring agencieslmsantidetect browser