Device limits for online courses: how many devices to allow
Two devices per student, one playing at a time, with a few controlled device changes, suits most coaching courses. Here's how to tune it by course type without locking out honest students.
On this page 8 sections
For most coaching courses, a sensible default is two devices per student, usually one phone and one laptop or tablet. Allow only one to play at a time, and a small number of device changes over the course. That matches how most students study, while stopping one login from serving a whole group. Tighten it for test series and short, high-value courses, loosen it for school students on family devices, and offer a quick way to replace a lost phone.
What a device limit does, and what it doesn't
A device limit caps how many phones, tablets and computers can be signed in to one account. It stops the crudest kind of sharing, where one login is handed to ten friends who all watch on their own phones.
It doesn't stop sharing within the allowed slots. A student with two slots can give one to a friend, sign a roommate in for an evening, or share their screen on a video call. Device limits are one control among several, and our guide to how to stop account sharing explains where each of the others falls short.
Three separate limits are often confused, and you need all three:
| Limit | What it controls | A sensible starting point |
|---|---|---|
| Registered devices | How many devices can be signed in to the account at all | Two |
| Simultaneous streams | How many of those can play at the same moment | One |
| Device changes | How often a device can be removed and replaced | A few over the course, then through support |
Treat these as defaults to adjust, not rules. The right numbers depend on your students and your course.
A "device" is an estimate
Modern phones don't let ordinary apps read a serial number, so platforms recognise a device from what the app or browser reports. Depending on how a platform does this, reinstalling the app, clearing browser data or a factory reset can make a familiar phone look new. Browsers are the weakest case, because each browser, and each private window, can look like a separate device.
So check how your platform counts. A student who reinstalls the app after a phone update shouldn't lose one of their device changes. A browser that clears its data every evening shouldn't fill the account with ghost devices.
Which devices do your students really use?
Before picking a number, think through an ordinary week for a typical student in your batch. For many Indian coaching students, it involves some of these:
- A budget Android phone for most lectures, often on mobile data.
- A family laptop or desktop for long sessions and mock tests, sometimes shared with a sibling.
- A tablet, for students who like to annotate notes alongside the lecture.
- A replacement phone after a drop, a theft or a festive-season upgrade.
- A library, hostel or cyber café computer, used now and then.
A one-device limit breaks that week, and a five-device limit lets a whole group in. Two registered devices with one stream at a time covers the honest pattern, and a fair change process handles the rest.
Match the limit to the course
Different courses carry different risks, so one rule for everything is rarely right. These are illustrative starting points, not industry figures:
| Course type | Suggested starting policy | Why |
|---|---|---|
| Long foundation batch, a year or more | Two devices, one stream, a few changes a year | Students will replace phones during the course |
| Short crash or revision course | Two devices, one stream, one or two changes | High value in a short window, with little reason for many changes |
| Online test series | One device per test attempt | Stops one paid attempt being taken on two devices at once |
| Offline downloads | Downloads on one device at a time | A download puts whole lectures on a phone you can't see |
| School and tuition courses | Two or three devices, one stream | Families often share a laptop or a parent's phone |
| Recorded courses with long validity | Two devices, with changes spread across the validity | Devices will be replaced over the years |
Live classes need a rule of their own: one device at a time during the class, whatever the registered limit. A shared login can't then fill a room, and a student who joins on a laptop after starting on a phone simply moves across. For test series, the attempt rules matter as much as the device rule. Our page on online test series software covers how tests are delivered and timed.
Device changes: where policies succeed or fail
Most complaints about device limits are really complaints about device changes. A student with a broken phone two weeks before an exam doesn't care about your piracy policy. They need to watch tonight.
A change policy that works usually has these parts:
- Self-service removal of an old device, confirmed with an OTP to the registered phone number.
- A cap on self-service changes, after which a request goes to support.
- A short waiting period after each change, so a slot can't be passed around daily.
- A support process that answers within a day, with a few standard questions.
- A log of every change, so staff can spot an account that changes device every week.
- Authority for support staff to make exceptions, and to sign an account out of every device.
The pattern of changes says more than the device count. An account that registers a new phone every few days is passing a slot around, whatever the limit says. A student who changes phone once in six months almost certainly isn't.
Plan the support load before you launch. As an illustration, if 500 students each change device once a year, that's about ten requests a week. Self-service handles most of them, and a written support script handles the rest, so the work stays manageable even in exam months.
Tell students the rule before they pay
A limit students discover only when they're blocked feels like a punishment. The same limit, explained at enrolment, feels like a rule. Put it in your terms of use and on the course page, and repeat it in the app.
- Show students their registered devices, and let them remove one themselves.
- When a limit is reached, say which devices are registered and exactly what to do next.
- Explain why: shared logins are how batches end up on Telegram, and that hurts the students who pay.
- Apply the rule consistently, including to the students who complain loudest.
Plain wording works better than legal language. An illustrative version for your terms and course page:
Your account is for your use only. You can watch on two devices, one at a time. You can replace a device yourself up to three times during the course; after that, contact support. Accounts used by more than one person may be blocked.
Signs your limit is set wrong
| Sign | What it suggests |
|---|---|
| Device-change tickets climb in exam months | The limit, or the change process, is too strict |
| Many accounts sit permanently at the device limit | The limit may be too loose, or slots are being shared |
| One account changes device every week | Sharing, whatever the limit |
| Enquiries mention watching "on a friend's account" | Limits exist on paper but aren't enforced |
| Refund requests mention being locked out | The appeal route is too slow |
Review the numbers after each batch and adjust. Device policies are easier to tune than to get right first time. For the wider set of controls, see how to prevent students sharing coaching accounts.
Upclass gives institutes branded apps in their own name on Android, iOS, Windows and Mac. Inside them, VidSafe brings account-sharing prevention alongside dynamic watermarking, screen- and camera-recording detection and VidSafe proprietary encryption. VidSafe adds visible and invisible watermarks that are extremely hard to remove, even after heavy re-encoding, so a leaked copy can be traced back to the account it came from. See Upclass pricing.
Frequently asked questions
How many devices should an online course allow?
Two registered devices with one playing at a time is a sensible default for most coaching courses. It covers a phone plus a laptop or tablet, which is how most students study. Adjust it for the course: stricter for test series and short high-value courses, a little looser for school students who share family devices.
Does a device limit stop account sharing?
Only partly. It stops one login being used on many phones. A student can still give one of their slots to a friend, or share their screen on a video call. Combine device limits with one stream at a time, controlled device changes, watermarks and checks for unusual account use.
What should happen when a student changes their phone?
They should be able to remove the old device themselves, confirming with an OTP to their registered number. They should then be watching on the new phone the same day. After a few self-service changes, further requests can go to support. Keep a log, so staff can see accounts that change device unusually often.
Should the app and website share one device limit?
Yes, count them together, so an account can't add browsers on top of its app devices. A simple rule is one phone and one computer, whether the computer uses an app or a browser. Browsers are easier to record, so steer paid video towards your apps where you can.
