How to Build an Employee Intranet with BuddyPress: Forums, Media Library and Recognition System
Build a members-only employee intranet on WordPress with BuddyPress or BuddyNext: company SSO, department forums, media and recognition, checked November 2026.

Yes, you can build an employee intranet on WordPress with BuddyPress or BuddyNext: a members-only community where staff sign in with company SSO, talk in department forums, share photos and videos, and recognise each other with badges and kudos. It works well for companies of roughly 50 to a few thousand people who want to own their data and avoid per-seat pricing. It is a poor fit if you need document co-authoring, Microsoft 365 or Google Workspace-level compliance tooling, or you have nobody to run a WordPress site.
This guide shows the stack our team uses, what each piece does and costs, the setup order for a rollout, and the mistakes people report most often. Every plugin version, price and setting below was checked on 21 November 2026. Several of the tools are made by our team at Wbcom Designs (BuddyNext, Jetonomy, MediaVerse, WB Gamification, BuddyX and Reign); we say so where they appear and list their weak spots.
Can BuddyPress be used as a company intranet?
It can. BuddyPress gives you member profiles with custom fields, groups, activity streams, private messages and notifications, which covers the social half of an intranet. Since BuddyPress 12.0 there is also a built-in Community Visibility setting that restricts BuddyPress pages to logged-in members, as WP Tavern reported when it shipped. That one setting removed the need for a separate “private BuddyPress” plugin on many builds.
On 21 November 2026, BuddyPress was at version 14.5.6 (17 November 2026) with 90,000+ active installs. That is down from 200,000+ a few years ago, and you should factor the trend into a long-term decision. Security matters more on an intranet than on a public blog, because every employee has an account. Patchstack lists CVE-2026-1360, a PHP object injection that any logged-in Subscriber could trigger, rated CVSS 8.8 and published 3 August 2026, as affecting BuddyPress up to and including 14.5.6 with no official patch available when we checked; the CVE.org record lists versions up to 14.5.0. On an intranet where every employee is logged in, that is exactly the user level that matters. Keep BuddyPress on the latest release, watch the advisory, and put a web application firewall in front of the site.
BuddyPress or BuddyNext for a new intranet?
If you are starting from nothing, we now start intranets on BuddyNext, our team’s free community plugin. If you already run BuddyPress and your staff are used to it, stay on BuddyPress and add the pieces below. Here is why, using what each product’s own pages listed on 21 November 2026.
Need | BuddyPress | BuddyNext (free) |
|---|---|---|
Members-only site | Community Visibility setting (since 12.0) | Invite-only or admin-approved registration, guest settings, Private and Secret spaces |
Department areas | Groups (public, private, hidden) | Spaces (Open, Private, Secret) with owner, moderator and member roles |
Profile fields from HR data | xProfile fields | 13 field types with per-field privacy |
Moderation | Basic; add-ons for more | Reports, queue, warnings, strikes, suspensions, log |
Email digests | Needs an add-on | Daily or weekly digests built in |
Two-factor login | Needs a plugin | Built in (app, backup codes, email fallback) |
Enterprise SSO (SAML or OIDC) | Separate plugin | Separate plugin (not listed as built in) |
Add-on ecosystem | Large, many unmaintained | Smaller, newer |
The honest trade-off: BuddyNext is newer, so fewer third-party plugins support it, and BuddyPress add-ons do not run on it. BuddyPress has the bigger ecosystem but a shrinking install base and more of the intranet basics (digests, 2FA, moderation) arrive as separate plugins you have to maintain. BuddyNext Pro starts at $149 a year (checked 21 November 2026); most intranets can run on the free version.
What plugins do you need for an employee intranet?
A working intranet needs six jobs done. This is the stack we use, with alternatives where a non-Wbcom plugin is the better fit.
Job | Our default | Alternatives | Cost (checked 21 Nov 2026) |
|---|---|---|---|
Community core | BuddyNext | BuddyPress 14.5.6 | Free |
Theme | BuddyX | Reign | BuddyX free; Pro from $79 a year |
Department forums and Q&A | Jetonomy | bbPress 2.6.22 | Jetonomy free; Pro from $69 a year |
Photos, video, audio | MediaVerse | Core media library | Free; Pro from $69 a year |
Recognition | WB Gamification | GamiPress, myCred | Free |
Company SSO | OpenID Connect Generic Client | SAML Single Sign On (miniOrange) | Free plugins; paid tiers for some IdP features |
You do not need every row on day one. Most of our rollouts launch with the core, the theme, SSO and forums, then add recognition after the first month when people are actually posting.
How do you make department forums that people use?
Jetonomy is the forum and Q&A plugin we use for intranets. It runs standalone (BuddyPress is optional) and gives you four space types: Forum, Q&A, Ideas and Show & Tell. Spaces sit in categories, each with its own members and rules. The free version includes trust levels, voting, accepted answers, search, notifications, rule-based moderation and one-click importers from bbPress, wpForo and Asgaros. Pro adds polls, email digests, AI moderation, analytics, custom fields and private messaging, from $69 a year for one site or $199 lifetime.
The layout that works for staff is boring on purpose:
- One category per department, with a Q&A space for “how do I” questions and a Forum space for discussion.
- One company-wide Ideas space, where staff vote on suggestions and leadership marks status. This replaces the suggestion box nobody trusts.
- A Show & Tell space for wins, launches and photos from events.
- Gate department spaces by membership so finance threads stay in finance.
Q&A with accepted answers is the part that pays off. Six months in, the answer to “how do I book a meeting room” is one search away instead of a repeated message to HR. Trust levels reduce how much a moderator has to approve by hand as people prove themselves; our guide to self-moderating forums with trust levels covers the settings.
The weak spot: Jetonomy is a separate product from BuddyNext’s core, so forums are an extra plugin to install and update. If you are already on bbPress (version 2.6.22, 100,000+ installs), it still works; it is just simpler and has no Q&A or ideas mode.
How should an intranet handle files, photos and video?
Split this into two jobs, because one plugin rarely does both well.
Photos, video and audio. MediaVerse (formerly WPMediaVerse) lets members upload from the front end, sort uploads into albums and set privacy per item or album. It runs standalone or with BuddyPress, and with BuddyNext it plugs into the community screens. The free version includes uploads, albums, privacy levels, a moderation queue and direct messaging; Pro adds feed layouts, cloud storage and importers from rtMedia, MediaPress and BuddyBoss Media, from $69 a year. Event photos, training clips and team videos belong here. Our MediaVerse setup guide walks through it.
Policy documents and handbooks. MediaVerse’s product page does not describe document or PDF management, so we do not use it for that. For a handful of policies, a private WordPress page per policy with a “last reviewed” date is enough. For collaborative documents inside BuddyPress groups, BuddyPress Docs (version 2.2.8, 6,000+ installs, updated 18 November 2026) is the long-running option. If your company already keeps documents in SharePoint or Google Drive, link to them from the intranet instead of copying files into WordPress. Two copies of a policy is how people end up following the wrong one.
Large video files are the usual hosting surprise. Check your host’s upload limit and storage before you announce “upload your training videos here”.
How do you add employee recognition to WordPress?
WB Gamification is our free recognition plugin (version 1.6.8, updated 20 November 2026, according to its product page). It awards points for actions you choose, and adds badges, levels, leaderboards, streaks, community challenges and peer kudos with daily limits and moderation. Shared badges get an OpenBadges 3.0 credential page. It integrates with BuddyPress, bbPress, BuddyNext, Jetonomy and MediaVerse among others.
If you prefer a plugin from the WordPress.org directory, GamiPress (10,000+ installs, 4.9 out of 5) and myCred (10,000+ installs, 4.6 out of 5) are the established choices. Our gamification plugin comparison covers them in detail.
Recognition at work is different from gamification on a public forum. What we have learned on staff networks:
- Kudos first, leaderboards later or never. Peer thanks feels good. A public ranking of colleagues often does not, and some teams find it divisive.
- Tie badges to company values, not to post counts. A “Helped another team” badge says more than “100 posts”.
- Reward answers, not noise. Give points for accepted answers and for welcoming new starters, not for every activity update.
- Let managers see, not police. Recognition data is useful in one-to-ones; it should never be a performance metric on its own.
How do employees log in with company SSO?
Staff should sign in with the same account they use for email. WordPress does this through a plugin that talks to your identity provider.
- OpenID Connect: OpenID Connect Generic Client (version 3.11.5, 10,000+ installs, updated 20 November 2026) works with Microsoft Entra ID, Okta, Keycloak, Google and other OIDC providers. Its maintainers ask for issues on GitHub rather than the WordPress.org forum.
- SAML: SAML Single Sign On by miniOrange (version 6.2.2, 10,000+ installs, 4.9 out of 5 from 402 ratings) covers SAML providers including Entra ID, Okta and Google Workspace. Some features, such as attribute and role mapping beyond the basics, are in paid tiers.
BuddyNext’s built-in social login (Google, Facebook, GitHub, Discord) and two-factor authentication are useful for public communities, but for an intranet you still want a proper SSO plugin so that disabling someone in your directory locks them out of the intranet too.
Once SSO creates users, put every new account in your all-staff group automatically. This BuddyPress snippet does it on registration; change 12 to your group’s ID. Checked on 21 November 2026 with BuddyPress 14.5.6 and WordPress 7.1; add it as a small must-use plugin.
<?php
// Add every new user to the all-staff BuddyPress group.
add_action( 'user_register', function ( $user_id ) {
if ( function_exists( 'groups_join_group' ) ) {
groups_join_group( 12, $user_id ); // 12 = your all-staff group ID.
}
} );Common mistakes people report
These come up again and again in support threads for BuddyPress and the SSO plugins intranets depend on. Checked on 21 November 2026.
- Assuming “private” covers the REST API. A user of the OpenID Connect plugin found its “enforce privacy” option hid pages but did not block the WordPress REST API (thread). Test what a logged-out visitor can read at /wp-json/ before launch, and block it if needed (snippet below).
- Logging out of WordPress but not out of SSO. Several threads report that WordPress logout ends only the WordPress session while the identity provider session stays open (OIDC thread, SAML thread, May 2025). On shared office computers that matters. Configure single logout or a short IdP session.
- Sessions that expire too early or too late. Users of the OIDC plugin reported being logged out prematurely (2024 thread). Agree a session length with IT and test it, including on phones.
- Directory attributes that do not map cleanly. A SAML user found Active Directory attributes containing commas broke the mapping (January 2025 thread). Test department, title and manager fields with real HR data, not one tidy test account.
- Upgrading BuddyPress without testing add-ons. After BuddyPress 12.0 changed how URLs are built, sites running older add-ons found member pages empty (February 2024 thread). Keep a staging copy and upgrade there first.
Block the REST API for logged-out visitors (the standard pattern from the WordPress REST API FAQ, checked on 21 November 2026). Test your SSO login after adding it, since some plugins call the API before the user is logged in.
<?php
add_filter( 'rest_authentication_errors', function ( $result ) {
if ( true === $result || is_wp_error( $result ) ) {
return $result;
}
if ( ! is_user_logged_in() ) {
return new WP_Error( 'rest_not_logged_in', 'You are not logged in.', array( 'status' => 401 ) );
}
return $result;
} );What is the setup order for a 300-person rollout?
This is the order we follow. Each step is something you can check before moving on.
- Hosting and staging. A managed WordPress host with daily backups, a staging copy, PHP 8.1 or newer and object caching. Intranet traffic is spiky (Monday mornings, all-hands days), so do not size for the average.
- Core and theme. Install BuddyNext or BuddyPress, then BuddyX or Reign. Turn on members-only access straight away, before any real data goes in.
- SSO. Connect your identity provider, map name, email, department and job title, and test with five real accounts from different departments.
- Profile fields. Create fields that match HR data: department, location, title, manager, start date, skills. Decide which are visible to everyone.
- Groups or spaces. One all-staff space, one per department, one per office. Auto-join new users to all-staff.
- Forums. Install Jetonomy, create a Q&A and a Forum space per department, and seed each with five real questions and answers from HR and IT.
- Media. Add MediaVerse, set privacy defaults to staff-only, and agree a video size limit with your host.
- Notifications. Set sensible defaults (daily digest, mentions immediately) so the intranet does not become another inbox. Our notification systems comparison helps choose.
- Pilot. Two departments for two weeks. Fix what they report.
- Launch. Company-wide announcement from leadership, a short “how to post” video, and named champions in each team.
- Recognition. Add WB Gamification or GamiPress in month two, starting with kudos and a few value badges.
A detail that saves support tickets: decide where people land after login. The activity feed, the all-staff space or a news page are all reasonable, but pick one. Our guide to redirecting BuddyPress members after login shows how.
What should the intranet home page show?
The home page decides whether people come back. Ours usually has four blocks, in this order:
- Company news, two or three posts from internal comms, newest first. Pin anything people must read, and unpin it after a week.
- Unanswered questions from the Q&A spaces, so anyone with a spare minute can help a colleague.
- New starters and anniversaries, pulled from profile fields. This is the block people mention most in pilot feedback.
- Quick links to the tools people already use: payroll, leave requests, the IT help desk, the document store.
Keep the activity feed one click away rather than on the home page. A raw feed from 300 people moves too fast to read, and it buries the news you actually need everyone to see. Department spaces can show their own feed, where the volume is manageable.
Review the home page monthly with the comms owner. If a block gets no clicks for two months, replace it.
How much does a WordPress intranet cost compared with SharePoint?
The software in our default stack can be free: BuddyNext, BuddyX, Jetonomy, MediaVerse, WB Gamification and an OIDC plugin all have free versions. If you buy the Pro tiers we mention, the yearly list prices on 21 November 2026 were $149 (BuddyNext Pro), $79 (BuddyX Pro), $69 (Jetonomy Pro) and $69 (MediaVerse Pro) for one site, and none of them charge per employee.
The real costs are elsewhere:
- Hosting sized for your headcount, with backups and staging.
- Setup time: SSO, profile fields, spaces, content seeding and a pilot. Plan weeks, not days.
- Ongoing care: plugin updates, security monitoring, and someone in HR or internal comms who owns the content.
Microsoft 365 and Google Workspace intranets are licensed per user per month and bundle things WordPress does not do well: document co-authoring, retention policies, eDiscovery and deep Teams or Chat integration. If you already pay for those and mainly need document management, a SharePoint intranet may be the cheaper answer. A WordPress intranet wins when you want a social, branded space you fully control, with no per-seat cost as you grow.
When should you not build an intranet on WordPress?
- You need regulated records management. Legal holds, retention schedules and audit-grade document history are not BuddyPress or BuddyNext features.
- Nobody owns it. An intranet without an internal owner goes stale within a quarter, whatever software it runs on.
- Your company lives in Teams or Slack already and the real need is a searchable FAQ. A help centre or wiki may be enough.
- You cannot keep plugins updated. Every employee has a login, so an unpatched site is a bigger risk than a public blog.
Frequently asked questions
Is BuddyPress free for an intranet?
Yes. BuddyPress is free and open source under the GPL, with no per-user fees. You pay for hosting, any premium add-ons and the time to run it.
Can I make a BuddyPress site private to employees only?
Yes. Since BuddyPress 12.0, the Community Visibility setting restricts BuddyPress pages to logged-in members. Pair it with SSO, block the REST API for logged-out visitors, and check that regular WordPress pages you want private are private too.
Does BuddyNext replace BuddyPress?
For new sites, it can: it covers profiles, spaces, activity, moderation and digests in one plugin. It does not run BuddyPress add-ons, and its ecosystem is younger. Existing BuddyPress intranets do not have to move.
How many employees can a WordPress intranet handle?
We have seen BuddyPress communities run well into the thousands of members on good hosting with object caching. The limit is usually hosting and the number of plugins, not WordPress. Load-test the activity feed and search before launch.
Can the intranet work on phones?
Yes, through the mobile browser. BuddyX and Reign are responsive. Test SSO login on phones specifically, since that is where session and redirect problems show up first.
Can contractors or partners get access?
Yes, with care. Create them through the same SSO if your identity provider holds guest accounts, or invite them by email with admin approval. Put them only in the spaces they need, and give them a profile field or role that marks them as external so staff know who they are talking to. Remove access the day the contract ends.
How do we moderate an internal community?
Lightly. Set clear posting guidelines, give each department a moderator, and use reporting and a moderation queue for the rare problem. Our community moderation guide covers tools and team setups.
Where to start
Write down the three things your staff most need from an intranet this quarter: usually finding answers, hearing company news and knowing who does what. Build only for those, on BuddyNext or your existing BuddyPress, with SSO from day one. Add media and recognition once people are posting. If you want a second opinion on a specific rollout, BuddyNext is a free place to start a pilot this week.


