Build a WordPress Intranet and Staff Social Network

A member of staff signs in with their work account and lands on a home page of announcements. They have a profile with their role and team, a feed of posts from the spaces they follow and notifications when someone mentions them. Department spaces keep conversations where they belong, and project spaces keep cross-team chatter in one place.

Files and media go through MediaVerse, which has privacy levels so a file can be visible only to the people meant to see it. Messages run on WPMediaVerse. Jetonomy handles internal questions: how do I claim expenses, who approves leave. The accepted answer stays findable and the question stops circulating.

Because the whole site is members-only, the conversation is for employees. A staff directory that is a search away makes it easier for people in different offices to find each other.

Check the gate first. Open the site in a private window with no login and confirm nothing is visible. Then test sign-in with a real work account and a leaver account, and confirm that disabling the work account removes access.

Check privacy levels on files with a test group: upload a file, restrict it and confirm someone outside the group cannot open it. Then read your data protection obligations with whoever owns them in your company. MediaVerse free includes GDPR export and erasure, but your policies are your own to write.

Look at the intranet on a phone, since many staff read announcements there.

A calendar of company events is a natural next step: Eventonomy gives event pages, recurring events, RSVPs and attendee management. For recognition, WB Gamification adds points, badges and leaderboards earned from real activity, free of charge, which some companies use for onboarding milestones.

If you need broadcast email, push notifications or analytics, BuddyNext Pro adds them, and also paid plans and gated spaces, which you may not need. MediaVerse Pro adds documents and cloud storage. Jetonomy Pro adds polls, email digests and analytics.

The plugins page lists each one and what is free. All of them use the same accounts your staff already sign in with.

This build suits a company that wants a self-hosted staff network and does not want a licence that grows with each new hire. It also suits a charity, a school or an association whose members are effectively staff. The licence covers the site, so adding people does not change the theme cost.

If your community is open to the public, see the open community build. If it is invited customers or peers, the private community build is closer. If you already run BuddyPress or BuddyBoss internally, do not migrate: Reign styles those and the BuddyPress Community Bundle holds our Pro plugins for that stack. For very large networks, the scale page and hosting page show how big sites are run.

Appoint a small group to own the intranet: someone for announcements, someone to moderate and an IT contact for sign-in. Announcements work best weekly. A daily digest gets filtered out; a weekly one gets read.

Review spaces every few months. Close or merge spaces that nobody posts in, and pin the useful answers. An intranet that looks neglected stops being used.

Cost stays the same shape as the staff list grows: Reign is a flat theme licence with no per-member fee and no share of your sales. Hosting is the cost that follows use. The pricing page lists the plugin plans.

The first is launching without owners. An intranet needs a person for announcements, a person to moderate and a contact in IT. If those jobs belong to nobody, the site decays within a few months. Name them before launch and tell staff who they are.

The second is copying the org chart into spaces. A space for every team looks tidy and stays empty. Start with the spaces people actually need: a general one, an announcements one and a handful for the departments or projects that already talk to each other. Add more when someone asks.

The third is moving everything at once. If staff must use the intranet for leave requests, policies, files and chat from day one, they will resent it. Start with one thing that is easier on the intranet than anywhere else, such as finding a colleague or a policy, and let the rest follow. Staff also need a reason to visit that is not an announcement. A weekly question, a new starter introduction or an answered question in Jetonomy gives them one.

Finally, involve your data protection lead early. Decide what staff may post, how long files stay and who can see what, before the first file is uploaded. These decisions are easier to make at the start than to change afterwards.