Stop Account Sharing with LifterLMS Prevent Concurrent Logins

How the LifterLMS prevent concurrent logins setting works, who it should apply to, how to exempt specific users, and the other measures that make sharing one account less attractive than buying a seat.

  • Add as a preferred source on Google
Illustration for “Stop Account Sharing with LifterLMS Prevent Concurrent Logins”

One 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.

How LifterLMS prevent concurrent logins works

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:

  1. If the user has only one active session, nothing happens.
  2. If they have two or more, and their role is one of the roles you selected, LifterLMS keeps the newest login and destroys all the others.

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.

How to switch it on

  1. Go to LifterLMS > Settings > Accounts.
  2. In the Student Dashboard section, tick Prevent concurrent logins ("Only allow the most recent login for each user account").
  3. In the roles field that appears, choose which user roles the rule applies to. Student is selected by default.
  4. Save.

Which roles to include

  • Student: yes, this is the point.
  • Subscriber or Customer: include them if your learners have those roles, for example on sites that also run WooCommerce or another membership plugin. The rule matches any of the user's roles.
  • Instructor and Instructor's Assistant: usually no. Instructors often work from several devices, and they are not your sharing problem.
  • Administrator and LMS Manager: no. Getting logged out of the admin while editing on two screens is just friction.

What honest students will notice

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:

  • Say it in your terms and on the checkout page: "Your account can be used on one device at a time."
  • Add a line to the welcome email and the login page, so the first logout is not a surprise.
  • Brief your support team. "I keep getting logged out" is the most common ticket after switching this on, and sometimes it is the first sign an account is being shared.

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.

Exempting specific users (for developers)

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.

When you need more control: session limit plugins

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.

Other ways to discourage account sharing

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.

Give teams a legitimate way to buy

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.

Make the account personal

  • Certificates carry the student's name, so a shared account produces certificates for the wrong person. For credentialed training, require a graded final quiz.
  • The student dashboard shows orders, billing details and progress. People are less willing to share an account that exposes their address and purchase history.

Protect the content itself

  • Protect downloadable files so links to them cannot be passed around. See how to protect course files in LifterLMS.
  • Turn on Content Protection under LifterLMS > Settings > General to block casual copying of text and images.
  • Use your video host's domain restrictions so embeds only play on your site.

Watch for the signs

  • The Users screen has a Last Login column and the Students report has Last Seen. Accounts that log in many times a day from different places are worth a look, and many security plugins log login IP addresses.
  • A sudden run of "I keep getting logged out" from one account usually means two people are using it.
  • Completion patterns that do not make sense, like a whole course finished in an evening with perfect quiz scores, deserve a polite question.

Set the rules

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.

Common mistakes and troubleshooting

  • Applying it to administrators. You will log yourself out every time you switch devices.
  • Selecting no learner roles. If your students have the Subscriber role and only Student is selected, nothing happens. Check a test account's role.
  • Testing in two tabs of the same browser. Tabs share one session. Test with two different browsers or a private window.
  • Stacking session plugins. Choose one approach.
  • Not telling students. Surprise logouts read as a broken site. Explain the rule once, clearly.

Frequently asked questions

Does preventing concurrent logins stop all account sharing?

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.

Will students lose their progress when logged out?

No. Progress, quiz attempts and recorded lesson time are stored on the server and are there when they log back in.

Can I allow two devices instead of one?

Not with the LifterLMS setting, which keeps only the newest session. A session management plugin can set a higher limit.

Does it work with "Remember me" logins?

Yes. A remembered login is still a WordPress session, and the newest session wins as usual.

What to do next

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.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day