L
Utilities Free WordPress.org

Loggedin – Limit Concurrent Sessions

4.9 (110 reviews)
· 8K+ active installs · By Joel James
Active Installs
8K+
Rating
4.9 / 5
Version
v3.0.2
Last Updated
Jul 2026
Share

Plugin Review

AI-Researched

What is Loggedin?

Loggedin – Limit Concurrent Sessions is a focused utility that caps how many devices a single user can be logged into at once on your WordPress site. Created by veteran developer Joel James, this plugin has been in active development for 10 years. It currently holds 8K+ active installs with a 4.9/5 rating from 110 reviews — 95% of which are five-star. The plugin hooks directly into WordPress’s native authentication system, using the WP_Session_Tokens API to track and limit active sessions without any third-party services or background polling.

When you want to limit concurrent logins WordPress accounts, Loggedin gives you three enforcement modes. You can log out the oldest device, log out every other device, or block the new login entirely. Version 3.0.2 was last updated on Jul 1, 2026, ensuring compatibility with the latest WordPress releases. The plugin is designed to be lightweight — no cron jobs, no bloat — and works with any hosting environment that supports standard WordPress session storage.

Key Features of Loggedin

  • Global concurrent-login limit — Set a per-user cap from 1 session upward, applied site-wide to every account.
  • Three built-in enforcement modes — Choose Logout Oldest, Logout All, or Block New to control what happens when the limit is reached.
  • Admin Force Logout panel — Clear all active sessions for any user by entering their ID, email, or username in one click.
  • Works with any session storage — Uses the standard WP_Session_Tokens API, supporting stock WordPress, Redis, and Memcached out of the box.
  • Zero third-party dependencies — No external services, no API keys, no background polling required for session enforcement.
  • Per-role limits with official add-on — The Limit Per Role add-on lets you assign different caps to administrators, editors, subscribers, and other roles.
  • Per-user overrides with official add-on — The Limit Per User add-on adds a profile field to override the global cap for specific accounts.
  • Native wp-login integration — Rejected logins display a clear error message on the standard WordPress login screen.

Who Should Use Loggedin?

This plugin is built for site owners running membership sites, online courses, subscription stores, or client portals. If you operate a LearnDash or LifterLMS installation and want to stop account sharing WordPress plugin abuse, Loggedin enforces one seat per paid user. The same applies to WooCommerce Memberships, Paid Memberships Pro, BuddyPress communities, and corporate intranets where audit policies require session caps. No coding skills are needed — anyone who can install a plugin can configure the limit in under two minutes.

The plugin is equally useful for compliance-driven sites in healthcare, finance, and education. With 8K+ active installs and a 1% one-star rating, the user base skews heavily toward satisfied administrators who need a simple, reliable solution. If you are researching how to limit concurrent logins in WordPress without complex server configurations, this is the most straightforward path. For sites that need to wordpress force logout users when they exceed a session cap, the Logout All mode handles this automatically on each new login attempt.

Installation & Setup

Install Loggedin from the WordPress.org plugin directory by searching “Loggedin” under Plugins → Add New, or upload the ZIP file manually. After activation, navigate to Users → Loggedin to set your concurrent-login limit and choose your enforcement mode. The interface is beginner-friendly — you pick a number and a rule, then save. No configuration files or code snippets are required.

Support & Community

The plugin’s support forum shows 1 open thread and 0 resolved threads over the past 2 months, resulting in a 0% resolution rate. This is a notable data point — while the plugin is mature and stable, users with active issues may experience slow response times. The 95% 1% one-star suggests most installations run without problems. For anyone evaluating the best concurrent login plugin WordPress options, the high rating indicates that when the plugin works as designed, it delivers exactly what it promises. The 10-year development history and recent 3.0.2 update suggest ongoing maintenance, even if forum activity is currently low.

Pros & Cons

What's Good
  • Rated 4.9/5 from 110 reviews with 95% five-star ratings, reflecting strong user satisfaction for a niche utility plugin.
  • Active installs exceed 8K, indicating reliable real-world use for controlling concurrent sessions on membership and LMS sites.
  • Uses WordPress's native WP_Session_Tokens API and hooks into the standard authentication pipeline, ensuring compatibility with any host, theme, or login plugin.
  • Provides three configurable actions when the session cap is reached (log out oldest, log out all others, or block new login), giving site owners flexible enforcement options.
  • Includes a one-click Force Logout panel that accepts user ID, email, or username, allowing admins to quickly resolve lockouts when a user cannot access their other devices.
Drawbacks
  • Support threads show 0 resolved out of 1 total (0% resolution rate), suggesting minimal or no developer support for troubleshooting.
  • Does not offer per-role or per-user session limits; the cap applies globally to all users, limiting granular control.
  • Lacks any built-in logging or audit trail of session limit events, making it difficult to track how often users are being blocked or displaced.
  • The plugin description warns that closing a browser tab does not end a session, which may confuse users expecting session timeouts tied to browser behavior.

Technical Details

Requires WordPress
6.0+
Requires PHP
7.4+
Tested up to WP
7.0.2
First Released
2016 (10+ years)
Support (last 2 months)
1 threads  —  0% resolved

Feature Tags

concurrent-login force-logout login-limit prevent-account-sharing user-sessions

Frequently Asked Questions