BuddyPress Private Community Pro: A Hands-On Review
Our review of BuddyPress Private Community Pro 3.2.1: visitor locks, per-role group, friend and message limits, profile controls, gaps and pricing.

BuddyPress Private Community Pro is a plugin that turns an open BuddyPress site into a members-only community. It locks BuddyPress components, WordPress pages and custom post types for logged-out visitors, and it sets per-role rules for logged-in members: who can open which directories, how many groups they can join or create, how many friends they can add and how many private messages they can send. For a simple “logged-in only” site, BuddyPress 12 and later can already do that on its own; Pro earns its price when you need the per-role limits and the profile controls.
One disclosure before anything else: our team at Wbcom Designs makes this plugin. For this review we read the code and documentation of version 3.2.1, released on 18 November 2026, and checked every claim below on 21 November 2026. Where the plugin falls short, we say so. We already compared its profile visibility option with BuddyDev’s plugin in our BuddyPress Profile Visibility Manager review, so this post covers the rest of the plugin and does not repeat that comparison.
What does BuddyPress Private Community Pro do?
The plugin works on two layers, and it helps to keep them apart in your head because they are configured in different tabs and they protect against different things.
- Visitor layer. Rules for people who are not logged in. You pick BuddyPress components, individual pages and custom post types, and visitors get a login form, a message or a redirect instead of the content.
- Member layer. Rules for logged-in members, set separately for each WordPress role. Block directories and other members’ profiles, switch off Friends or Messages, cap group joins and creation, limit friend counts and set hourly, daily, monthly or yearly message caps.
On top of those two layers sit three member-facing extras: a profile visibility choice each member controls, a profile completion indicator with optional forced completion, and editable notice text for every restriction. In version 3.2.1 the settings live under WB Plugins > Community Pro in a card-based screen with eight tabs: Welcome, Visitor Restrictions, Profile Visibility, Profile Progress, Membership Restrictions, Notice Messages, FAQ and License.
Do you need it, or is BuddyPress’s own Members Only setting enough?
Start here, because many sites do not need a plugin at all. Since version 12.0, BuddyPress has a Community Visibility setting under Settings > BuddyPress > Options with two choices, Anyone or Members Only. Members Only hides the BuddyPress area from logged-out visitors and shows a “Members-only area” notice. It is one switch for the whole community, and it only appears when BuddyPress uses its default URL parser (it is missing if you run BP Classic). We walk through the core setting, and per-field profile privacy, in our guide to BuddyPress privacy features.
Here is how the options line up, checked on 21 November 2026:
Need | BuddyPress core (14.5.6) | Private Community for BuddyPress (free) | Private Community Pro 3.2.1 |
|---|---|---|---|
Hide the whole community from visitors | Yes, one global switch | Yes | Yes |
Lock some components and leave others open | Not in the settings screen | Yes | Yes |
Lock WordPress pages and custom post types | No | Yes | Yes, plus the Posts page and a latest-posts homepage |
Members choose who sees their profile | Per field only | No | Yes, whole profile |
Force profile completion | No | No | Yes |
Per-role limits on groups, friends, messages | No | No | Yes |
Price | Free | Free | From $49 a year or $149 lifetime |
If your answer to every row past the first is “no”, use the core setting or the free Private Community for BuddyPress plugin (version 2.4.0, updated 19 November 2026, 300+ active installs, 25 ratings averaging 98% on WordPress.org on 21 November 2026). Pay for Pro when you need the member layer.
How do you lock BuddyPress pages and custom post types for visitors?
Open the Visitor Restrictions tab and turn on the lock types you need. Everything on this tab applies to logged-out visitors only; members never see these locks.
Lock BuddyPress components
There are four choices, and their exact scope matters:
- Members directory locks the directory only. Individual profiles stay open unless you also tick the next item.
- Member pages (profile and every tab) locks each member’s whole page, including Friends, Groups and tabs added by other plugins. Member activity RSS feeds close too.
- Activity locks the site feed and every member’s Activity tab.
- Groups locks the directory, single group pages and members’ Groups tab.
A detail many lock plugins miss: the plugin also closes the BuddyPress REST API to visitors for every component you lock, so a locked members list cannot be read through /wp-json/buddypress/v2/members. Locked post types are removed from front-end search results for visitors as well.
Lock WordPress pages and custom post types
Pick individual pages from a list. Version 3.2.1 fixed two gaps that site owners kept hitting: the page set as the Posts page under Settings > Reading now locks the blog index and every paged view of it, and sites whose front page shows “Your latest posts” get a Homepage (latest posts) choice. Custom post types such as courses, listings or downloads can be locked as whole types, archive and single views together.
What visitors see instead
- Built-in form (the default): your message, written in a rich-text editor, followed by a login form with a Forgot password link and a Register button that points at BuddyPress sign-up when registration is open.
- Another plugin’s login form: paste its shortcode and the plugin renders it in place of its own.
- Redirect to a page: visitors, and members who log out, go to a page you choose.
Locked pages are sent with noindex and no-cache headers, so search engines skip them and page caches do not store a copy. They answer with HTTP 200 by default so uptime monitors do not raise alarms; the blpro_locked_page_status filter switches that to 401 or 403 if you prefer. The form can also be placed anywhere with the [blpro_login_form] shortcode.
What it does not lock out of the box
Two gaps are worth knowing before you buy. Both come from how the post type list is built in the 3.2.1 code: it offers public, non-built-in post types that are not excluded from search.
- Single blog posts. The built-in Post type is not in the list. You can lock the blog index, but a visitor who follows a direct link to one post can read it.
- bbPress forums. bbPress registers forums, topics and replies with
exclude_from_searchset to true, so they do not appear either. A WordPress.org reviewer of the free plugin raised the same gap in May 2025.
The list passes through the blpro_restrictable_post_types filter, so a developer can add both. We read this against the 3.2.1 source on 21 November 2026; it passed php -l on PHP 8.5 but we have not run it on a live site, so test it on staging first.
<?php
// Offer blog posts and bbPress post types on the Visitor Restrictions tab.
// Checked against BuddyPress Private Community Pro 3.2.1 source, 21 November 2026.
add_filter( 'blpro_restrictable_post_types', function ( $types ) {
foreach ( array( 'post', 'forum', 'topic', 'reply' ) as $name ) {
$object = get_post_type_object( $name );
if ( $object ) {
$types[ $name ] = $object;
}
}
return $types;
} );
Put it in a small custom plugin or your child theme’s functions.php, then tick the new entries under Lock custom post types and save. The lock check compares each post’s type against your saved list, so the filter only needs to make the types selectable.
Can members hide their own profile?
Yes. On the Profile Visibility tab, turn on Let members control profile visibility. Each member then picks one of the visibility levels BuddyPress has registered: Public, All Members, My Friends or Only Me. Administrators and the profile owner can always see the profile.
When a viewer is not allowed in, the plugin replaces the profile with your private message (use %user-name% to insert the member’s name). Since 3.2.1 the header is stripped too: the viewer sees only the name, avatar and action buttons, with friend count, member types, last active, the @handle and other plugins’ header details hidden. If the level is My Friends, an Add Friend button appears beside the message. Hidden profiles are also kept out of link previews and SEO meta descriptions, a leak several lock plugins still have.
One edge case is handled sensibly. If the site turns off the Friends component after a member chose My Friends, that choice behaves like All Members rather than locking everyone out. Two crash bugs around this case were fixed in 3.2.1, so update before you rely on it.
How does forced profile completion work?
The Profile Progress tab does two jobs. First, it can show a completion indicator on member headers, now a small chip with a progress ring. You choose what counts: specific profile field groups, a profile photo and a cover photo. The indicator respects profile visibility, so it is hidden from viewers who cannot see the profile.
Second, it can force completion. Turn on any of Require all mandatory fields, Require a profile photo or Require a cover image, and a member who has not met the requirement is sent to the matching edit screen with a reminder. Super admins are never forced, AJAX requests are skipped, and the member’s own profile edit screens stay reachable so there is no redirect loop. Developers can skip the check for a request with the bp_force_profile_completion_skip_check filter.
A note from experience: forced completion is a blunt tool. If you require a cover image, every existing member without one is redirected on their next visit. Turn it on for required fields first, announce it, and add the photo rules later.
What can you limit for each member role?
This tab is the real reason to buy Pro. Pick a role from Configure access for role, then set its rules. Administrators are not in the list and are never restricted, and a member with several roles is blocked if any one of them blocks the action.
Area | What you can set |
|---|---|
Pages | Block the activity feed, groups directory, members directory, other members’ profiles or single group pages, and choose where blocked members are sent |
Features | Turn off Friends or Messages for the role entirely, or hide the activity post form while keeping the feed readable |
Groups | Limit how many public, private or hidden groups they can join, block leaving, block creating (all or by privacy), cap how many they create, cap the size of group they can join |
Friends | Block sending, accepting or removing friend requests, and cap total friends |
Messages | Block new conversations, replies, messages to several people or deleting conversations; friends-only messaging; caps on recipients, total messages and messages per hour, day, month or year (UTC) |
Watch the zeros. For Most they can join, 0 means the role cannot join any group of that type. For every other limit on the tab, 0 means no limit. Mixing those up is the most common setup error we see in support, and the Membership Restrictions documentation calls it out for the same reason.
What about MemberPress, Paid Memberships Pro and other membership plugins?
In 3.2.1 the Membership Restrictions screen is organised by WordPress role. The code includes detectors for LearnDash, LifterLMS, MemberPress, Paid Memberships Pro, Restrict Content Pro, s2Member, WooCommerce Memberships and GamiPress, but the screen you configure picks a role, and our own troubleshooting docs ask you to confirm level targeting appears in your version before you depend on it. The practical setup that works today: have your membership plugin assign a WordPress role per level (most can), then set the rules on that role. Our roundup of membership plugins notes which ones handle roles cleanly.
What do members see when a rule stops them?
The Notice Messages tab holds the text for every group, friend and message restriction, from “Creating a group (limit reached)” to “Most messages per hour”. Since 3.2.1 each empty field shows its default in grey and uses a translated default, and the release added German, French, Spanish, Brazilian Portuguese and Italian translations. In group messages, %s is replaced by the group type.
Notices now appear as a dismissible notice in your theme’s own style, announced to screen readers, instead of the full-screen popup earlier versions used. Keep the text short and tell the member what to do next: “Upgrade to Gold to join more than three groups” works better than “Action not allowed”.
What changed in version 3.2.1?
The 18 November 2026 release was mostly about making locks hold. The items that matter most to site owners, from the release notes:
- Locked pages and hidden profiles no longer leak names, images or page text through browser titles, link previews, Yoast SEO or Rank Math meta, or RSS feed links.
- The Posts page and a latest-posts homepage can now be locked, every paged view included.
- Fatal errors fixed: viewing a Friends-only profile or messaging under the Friends-only rule when Friends is off, and the activity feed on BuddyBoss.
- Group creation limits count only finished groups, and turning off public group creation no longer blocks private and hidden groups.
- Icons switched to Dashicons, so the plugin no longer loads Font Awesome from an external CDN.
If you run 3.2.0 or older, this is a worthwhile update on its own. Read our guide to redirecting members after login if you also want to control where people land once the lock screen lets them in.
How much does it cost, and what does it need?
Prices from the product page on 21 November 2026, in US dollars:
License | Sites | Annual | Lifetime |
|---|---|---|---|
Personal | 1 | $49 | $149 |
5-Site | 5 | $99 | $299 |
Developer | Unlimited | $129 | $349 |
Every paid plan has a 30-day money-back guarantee. Without renewal the plugin keeps working, but updates and support stop.
Requirements in 3.2.1 are stricter than older posts (including the earlier version of this one) said: WordPress 6.5 or later, PHP 8.1 or later and BuddyPress 12.0 or later, active on the same site. The code checks only for BuddyPress, so Pro runs on its own. It detects the BP Nouveau and BP Legacy template packs, the BuddyBoss theme and Platform, and Youzify, where it adds a Profile Visibility tab.
One security note that has nothing to do with this plugin but everything to do with private communities. BuddyPress 14.5.6 (17 November 2026) is the current release. As of 21 November 2026, Patchstack lists CVE-2026-1360, a PHP object injection in BuddyPress XProfile that needs only a Subscriber account (CVSS 8.8, published 3 August 2026), as affecting versions up to and including 14.5.6 with no official patch. The CVE.org record lists versions up to 14.5.0. A members-only site with open registration still hands Subscriber accounts to strangers, so keep BuddyPress updated, watch for a fix, and consider manual approval of new members until one ships.
Common mistakes people report
These come up again and again in WordPress.org threads for the free version, which shares the visitor layer with Pro, and in our own support queue. Checked on 21 November 2026.
- Locking the blog page and assuming posts are hidden. Users of the free plugin on BuddyX reported in July 2023 and again in September 2025 that footer widgets still linked to readable posts. Lock the Posts page, and use the filter above if single posts must be private.
- Expecting bbPress forums to lock with the components. They are a separate plugin with their own post types; see the filter above, or use bbPress’s own private forum setting.
- Page builders and caching. A thread on Elementor reported page locks not applying. Some builders and custom templates bypass the standard template hooks, and a full-page cache can serve a copy saved before the lock. 3.2.1 sends no-cache headers on locked pages, but clear your cache after changing locks and test logged out in a private window.
- Breaking registration. One site saw its register page replaced by the lock screen. Never lock the BuddyPress Register or Activate pages; the built-in form already links to sign-up.
- Testing as an admin. Administrators are exempt from every member rule, so limits look broken when you test them on your own account. Create a test user with the role you configured.
Most of these are configuration problems rather than bugs, which is why we suggest a one-hour staging run before you switch locks on for real members. Our post on who holds your community’s member data covers the wider privacy picture beyond page locks.
Pros and cons
What we think it does well
- The per-role member layer: group, friend and message limits that no free plugin and no core setting offers.
- Locks that hold beyond the page itself: REST API, search results, link previews, SEO meta and feeds are all covered in 3.2.1.
- Member-controlled profile visibility that reuses the BuddyPress levels members already know.
- Sensible defaults: locked pages return 200 with noindex and no-cache, with a filter for 401 or 403.
- A lifetime license option, which suits communities that do not want another subscription.
Where it falls short
- Rules are set per WordPress role. There is no screen for choosing a membership level directly, so you map levels to roles first.
- Single blog posts and bbPress forums need a code filter to lock.
- Forced profile completion applies to existing members immediately, which can surprise a large community.
- No REST routes of its own, so you cannot manage its settings from an external app.
- It is a BuddyPress add-on. We maintain it for compatibility and fixes, and we do not promise new features for it.
Who should use it, and who should skip it?
Use it if you run an existing BuddyPress community that needs tiers: a paid network where free members can join two groups and paid members can join any, a school where students can message only classmates they have friended, or an association where new members must complete their profile before they see the directory.
Skip it if you only need the whole community hidden from visitors; the core Members Only setting or the free plugin does that. Skip it too if you are planning a new community from scratch rather than adding privacy to a running BuddyPress site. For new builds our team now starts with BuddyNext, our newer community stack, where privacy and access are part of the platform instead of an add-on.
Frequently asked questions
Does BuddyPress Private Community Pro work with BuddyBoss?
It detects the BuddyBoss theme and BuddyBoss Platform and adjusts its profile templates and progress indicator for them, and 3.2.1 fixed an activity feed crash on BuddyBoss. Test on a staging copy first, because BuddyBoss has its own privacy settings that can overlap.
Will locked pages still show up in Google?
Locked pages are sent with a noindex robots tag and no-cache headers, and with Rank Math active the plugin marks them noindex there too. Pages Google indexed before you locked them drop out as Google recrawls them.
Can I lock only some components and leave others public?
Yes. Each of the four components is a separate checkbox. A common setup keeps the members directory public for discovery and locks member pages, activity and groups.
Do I need the free plugin installed as well?
In the 3.2.1 code, the only hard dependency is BuddyPress. Pro includes the visitor-layer locking itself.
What happens if my license expires?
The plugin keeps working with your current settings. You stop receiving updates and support until you renew, which matters for a plugin that guards member data, so we recommend keeping it current.
Our verdict
BuddyPress Private Community Pro is the right tool when “members only” is not enough and you need different rules for different kinds of members. Version 3.2.1 closed most of the leaks that used to undermine page locks, and the per-role limits are thorough. The role-only targeting and the post and forum gaps are real, so plan for them before you buy.
Get it from the BuddyPress Private Community Pro page, read the documentation first if you want to check a specific rule, or talk to our team if you need help mapping membership levels to roles on your site.


