The LifterLMS Course Completion Page and What Happens at the End
What LifterLMS does when a student finishes a course, how to set a global or per-course completion page, what to put on it, and how to make the last…
Read articleOne person buys the course, five colleagues use the login. For a course business this is lost revenue, and for certified training it is worse: the certificate says someone completed a course they never took.
LifterLMS includes a setting to prevent concurrent logins, so each account can only be signed in on one device at a time. This guide explains how it works, how to set it up without annoying honest students, how developers can exempt particular users, and the other tactics that, together, make sharing more trouble than it is worth.
The behaviour below was checked against the LifterLMS 10.3 source code. The feature has been in the free core plugin since version 5.6.
WordPress keeps a list of active sessions for every user, one for each browser or device they have logged in on. With the LifterLMS setting switched on, every page load by a logged-in user is checked:
In practice: Alice logs in on her laptop. Bob logs in with Alice's details on his phone. The next time Alice's laptop loads a page, she is logged out. If she logs back in, Bob is logged out on his next click. Sharing still technically works, but only for one person at a time, and both get interrupted constantly.
The LifterLMS documentation describes it the same way: a new login logs out the older sessions.
The rule cannot tell a shared account from one person with a laptop and a phone. A student who starts a lesson on their desktop and continues on their phone will be logged out on the desktop. That is the trade-off, and it is acceptable for most course businesses if you are upfront about it:
Logging out does not lose progress. Completions, quiz attempts and time already recorded are stored on the server. If you use lesson time tracking, note that it also allows only one tracked lesson session per student at a time, which adds a second layer against two people studying on one account.
Some accounts legitimately need several sessions: a demo login used at trade shows, a support team account, or a kiosk in a training room. The llms_allow_user_concurrent_logins filter lets you exempt users. It receives false and the user ID; return true to allow concurrent sessions.
This example exempts any user with a custom user meta flag, which an administrator can set from a small admin tool or with WP-CLI (wp user meta update 42 llmsx_allow_multiple_sessions 1):
<?php
/**
* Plugin Name: LLMSX Concurrent Login Exemptions
*/
add_filter( 'llms_allow_user_concurrent_logins', 'llmsx_allow_flagged_users', 10, 2 );
function llmsx_allow_flagged_users( $allow, $user_id ) {
if ( get_user_meta( $user_id, 'llmsx_allow_multiple_sessions', true ) ) {
return true;
}
return $allow;
}
Keep exemptions rare and documented. Every exempt account is an account that can be shared freely.
The LifterLMS setting is strict: one session, newest wins. If you want to allow two devices, or block the new login instead of logging out the old one, use a dedicated session plugin instead. Loggedin on WordPress.org, for example, lets you set a maximum number of active logins per account and choose whether to log out the oldest session, log out all others, or block the new login.
Use one tool or the other, not both. Two plugins fighting over the same session list produce confusing logouts that are hard to debug.
Session limits stop simultaneous use. They do not stop people taking turns, or sharing a password with a friend in another time zone. Combine them with measures that make sharing less valuable and easier to spot.
A lot of sharing is a company buying one seat for a team because there was no team option. Sell seats properly with vouchers or the Groups add-on; see LifterLMS groups and team training. Price it so buying seats is easier than sharing.
Put a single-user licence in your terms of service, and state what happens when sharing is detected: a warning first, then suspension. Enforcement is easier when the rule was clear at purchase.
No. It stops two people using one account at the same moment. People can still take turns, which is why the other measures above matter.
No. Progress, quiz attempts and recorded lesson time are stored on the server and are there when they log back in.
Not with the LifterLMS setting, which keeps only the newest session. A session management plugin can set a higher limit.
Yes. A remembered login is still a WordPress session, and the newest session wins as usual.
Switch on Prevent concurrent logins for the Student role and whichever other roles your learners have, add one sentence about it to your checkout page and welcome email, and test with two browsers. Then look at why people share: if it is teams, give them a team product.
If sharing is costing you real money or undermining certificates, our LifterLMS consulting can review your offer and access setup, and our customization team can build detection and reporting around logins. Tell us what you are seeing and we will suggest the right mix.
What LifterLMS does when a student finishes a course, how to set a global or per-course completion page, what to put on it, and how to make the last…
Read article
How LifterLMS media protection keeps PDFs, images, audio and video files away from people who are not enrolled, how to protect a file, what signed…
Read article
How LifterLMS course tracks turn separate courses into a learning path: create a track, require it before an advanced course, award a certificate…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.