Stephanie Leary

<ul>
<li>Optionally adds private pages to <code>wp_list_pages()</code>, <code>wp_page_menu()</code>, and the Pages widget</li>
<li>Provides a separate <code>wp_list_private_pages()</code> tag (a clone of <code>wp_list_pages()</code> that accepts all the same arguments)</li>
<li>Specifies private categories, in which all posts will automatically be set to private</li>
<li>Lets you change the “Private:” prefix on private post/page titles</li>
<li>Lets you change the “Protected:” prefix on password-protected post/page titles</li>
<li>Lets you choose which user roles can read private pages and posts</li>
</ul>
<p>Now on <a href="https://github.com/sillybean/private-suite" rel="nofollow ugc">GitHub</a>.</p>
<h4>Translations</h4>
<ul>
<li>French (fr_FR) by Regis Lemaire</li>
<li>Bulgarian (bg_BG) by <a href="http://www.siteground.com/" rel="nofollow ugc">SiteGround</a></li>
<li>Turkish (tr_TR) by <a href="http://bijoubijouterie.com" rel="nofollow ugc">Ömer Faruk Karabulut</a></li>
</ul>
<h3>Notes</h3>
<h3>Reading Settings</h3>
<p>You must have at least one public page. Otherwise, as of 3.1, the front page settings (where you can choose a static page as your home page) will not appear on the settings page at all. As long as you have one public page, all the private pages will appear as options in the dropdown menu.</p>
<h3>Page Lists and Widgets</h3>
<p>Adding private pages to <code>wp_list_pages()</code>, <code>wp_page_menu()</code>, and the Pages widget does not always work as it should. The private pages will be out of order, and they might appear as children of the wrong parent page. If this occurs, try using the <code>wp_list_private_pages()</code> template tag instead. It’s a clone of <code>wp_list_pages()</code> and should accept all the same arguments. This plugin includes an extra Pages widget that includes private pages.</p>
<h3>Private Categories</h3>
<p>When you mark a category as private, all the posts in that category will have their visibility set to private when they are published, even if you don’t change the visibility setting on the edit screen. Only published posts are affected; your draft, pending, and scheduled posts will work as usual, except that scheduled posts will be set to private when they become active.</p>
<h3>Acknowledgments</h3>
<p>Huge thanks to <a href="https://profiles.wordpress.org/mtekk" rel="nofollow ugc">mtekk</a> for providing the <a href="https://core.trac.wordpress.org/ticket/8592" rel="nofollow ugc">patch</a> that makes the page list features possible. The alternative method of listing pages was adapted from <a href="http://activecodeline.com/create-a-menu-for-private-pages-and-posts-in-wordpress" rel="nofollow ugc">Branko Ajzele</a>.</p>
<h3>Translations</h3>
<p>If you would like to send me a translation, please write to me through <a href="http://sillybean.net/about/contact/" rel="nofollow ugc">my contact page</a>. Let me know which plugin you’ve translated and how you would like to be credited. I will write you back so you can attach the files in your reply.</p>


Private Suite

Allows you to choose who can read private content and offers better control of privacy features.

Syed Balkhi

Jared Atchison

Slava Abakumov

Nathan Singh

Chris Kelley

LionSher Technologies

<p>WordPress is one of the most popular platforms for building corporate intranets and private company websites. The problem is that WordPress was designed for public-facing sites. Making it work as a private intranet typically requires installing multiple plugins, configuring each one separately, and hoping they all play nicely together.</p>
<p>All-In-One Intranet solves this by giving you everything you need in a single plugin to turn your WordPress site into a fully private intranet. Enable privacy with one checkbox, set up auto-logout to protect sensitive information, configure where users land after login, and manage multisite access controls – all from one settings page.</p>
<p>Whether you are building a corporate intranet, a private knowledge base, a restricted client portal, or an internal communications hub, this plugin handles the foundational privacy and access control so you can focus on your content.</p>
<h4>What is an Intranet?</h4>
<p>An intranet is a private website or network used internally by an organization. Unlike a public website, an intranet is only accessible to authorized users – typically employees, contractors, or specific team members.</p>
<p>Common uses for a WordPress intranet include:</p>
<ul>
<li>Internal company communications and announcements</li>
<li>Employee handbooks, policies, and procedures</li>
<li>Knowledge bases and documentation wikis</li>
<li>Project collaboration and team coordination</li>
<li>HR portals for onboarding and training materials</li>
<li>Client portals with restricted access to project files</li>
</ul>
<p>WordPress is well suited for all of these because of its familiar editing interface, extensive plugin ecosystem, and flexible user role system. All-In-One Intranet provides the access control layer that makes it all work.</p>
<h4>Features</h4>
<p>All-In-One Intranet includes five core features designed to cover the most common intranet requirements:</p>
<h4>One-Click Private Site</h4>
<p>Enable the “Force site to be entirely private” checkbox, and your entire WordPress site becomes restricted to logged-in users only. Anyone who is not logged in gets redirected to the WordPress login page automatically.</p>
<p>This single setting handles multiple layers of privacy at once:</p>
<ul>
<li><strong>Page and post access</strong> – all frontend content requires authentication</li>
<li><strong>REST API protection</strong> – unauthenticated REST API requests are blocked with a 401 error, preventing data leaks through the API</li>
<li><strong>XML-RPC blocking</strong> – XML-RPC is disabled entirely when privacy is active, closing another potential access vector</li>
<li><strong>Search engine blocking</strong> – the robots.txt file is automatically updated to disallow all crawling, keeping your private content out of search indexes</li>
<li><strong>Pingback suppression</strong> – outgoing pingbacks and trackbacks are disabled so your private site does not announce itself to external services</li>
<li><strong>Feed protection</strong> – RSS, Atom, and comment feeds require authentication, so protected posts and comments cannot be read through <code>/feed/</code> or crafted feed URLs</li>
<li><strong>Comment and trackback blocking</strong> – unauthenticated visitors cannot post comments or trackbacks to protected content through <code>wp-comments-post.php</code> or <code>wp-trackback.php</code></li>
<li><strong>Admin endpoint gating</strong> – the <code>admin-ajax.php</code> and <code>admin-post.php</code> handlers require a valid login, so public “nopriv” actions registered by your theme or other plugins do not run for logged-out visitors</li>
<li><strong>Entry-point coverage</strong> – WordPress files that load the site outside the normal page render, such as <code>wp-links-opml.php</code> (the blogroll and OPML export) and <code>wp-activate.php</code>, are sealed so they cannot leak post content, feeds, your site title, or the WordPress version number</li>
<li><strong>Slug enumeration prevention</strong> – WordPress’s canonical redirect no longer reveals the slugs of private posts to unauthenticated visitors on pretty permalinks</li>
<li><strong>Role and membership enforcement</strong> – the REST API and comment gates apply the same role and sub-site membership checks as the rest of the site, so a logged-in user with no role, or who is not a member of the current sub-site, cannot read API content or post comments they would otherwise be blocked from</li>
</ul>
<p>The plugin also monitors your WordPress registration settings. If “Anyone can register” is enabled on a single site, or if open registration is allowed on a multisite network, the plugin displays a warning on the settings page so you can fix it before it becomes a problem.</p>
<h4>Auto-Logout for Inactive Users</h4>
<p>Shared workstations and forgotten browser tabs are a real security risk for intranets. The auto-logout feature lets you set a maximum idle time – in minutes, hours, or days – after which users are automatically logged out.</p>
<p>The plugin tracks each user’s last activity timestamp. On every page load, it checks whether the configured idle time has been exceeded. If a user has been inactive for too long, they are logged out immediately and redirected back to the page they were viewing, which triggers the login wall if the site is private.</p>
<p>This protects sensitive company information without requiring users to remember to log out manually. Set it to 30 minutes for high-security environments, a few hours for typical office use, or leave it blank to disable the feature entirely.</p>
<h4>Custom Login Redirect</h4>
<p>By default, WordPress sends users to the dashboard after they log in. For an intranet, this is not useful – your team is logging in to read content, not to manage the site.</p>
<p>The login redirect feature lets you set any URL on your site as the post-login landing page. Point it to your company homepage, a news feed, or a team dashboard so users see relevant content right away.</p>
<p>This redirect only applies when users log in directly through the standard WordPress login page. If a user tries to access a specific page and gets redirected to log in first, they will be sent back to that page after authentication – not to the custom redirect URL. This keeps the user experience smooth.</p>
<h4>Multisite Sub-site Privacy</h4>
<p>If you run a WordPress multisite network, you can require logged-in users to be members of a specific sub-site before they can view it. This is useful for organizations with multiple departments, teams, or client areas – each with their own sub-site that should only be visible to relevant people.</p>
<p>When a user who is logged in but not a member of the current sub-site tries to access it, they see a message listing all the sub-sites they do have access to, with clickable links to navigate there. Access to the Network Admin area is never restricted by this setting.</p>
<p>This option works in combination with the main privacy setting. Enable private site first, then enable sub-site membership requirements for granular access control across your network.</p>
<h4>Multisite Default Role Assignment</h4>
<p>Managing user access across multiple sub-sites in a WordPress network can be tedious. Every time you add a new user or create a new sub-site, you would need to manually assign roles across all the relevant sites.</p>
<p>The default role assignment feature automates this. Choose a role (Subscriber, Editor, Administrator, or any custom role), and the plugin handles the rest:</p>
<ul>
<li>When a <strong>new user</strong> is created, they are automatically added to every active sub-site in the network with the selected role</li>
<li>When a <strong>new sub-site</strong> is created, all existing users are automatically added to it with the selected role</li>
</ul>
<p>This saves significant administration time, especially for growing organizations where new employees and new sites are added regularly.</p>
<h4>How to Make Your WordPress Site Private</h4>
<p>Setting up a private WordPress site with All-In-One Intranet takes about one minute:</p>
<ol>
<li>Install and activate the plugin from the WordPress plugin directory</li>
<li>Go to <strong>Settings > All-In-One Intranet</strong> in your WordPress admin (or <strong>Network Admin > Settings > All-In-One Intranet</strong> for multisite)</li>
<li>Check the box labeled <strong>“Force site to be entirely private”</strong></li>
<li>Click <strong>Save Changes</strong></li>
</ol>
<p>That is all it takes. Your site is now private. Any visitor who is not logged in will be redirected to the WordPress login page. The REST API, XML-RPC, and search engine indexing are all locked down automatically.</p>
<p>If you see a warning about registration settings after enabling privacy, follow the link in the warning to disable open registration and close the gap.</p>
<h4>How to Set Up Auto-Logout for Inactive Users</h4>
<p>The auto-logout feature protects your intranet from unattended browser sessions:</p>
<ol>
<li>Go to <strong>Settings > All-In-One Intranet</strong></li>
<li>Find the <strong>Auto Logout</strong> section</li>
<li>Enter a number in the time field (e.g., 30)</li>
<li>Select the time unit from the dropdown: <strong>Minutes</strong>, <strong>Hours</strong>, or <strong>Days</strong></li>
<li>Click <strong>Save Changes</strong></li>
</ol>
<p>Users who are inactive for longer than the configured period will be logged out on their next page interaction. Their activity timer resets on every page load, so active users are never interrupted.</p>
<p>To disable auto-logout, clear the time field and save.</p>
<h4>How to Configure Login Redirect</h4>
<p>To send users to a specific page after they log in:</p>
<ol>
<li>Go to <strong>Settings > All-In-One Intranet</strong></li>
<li>Find the <strong>Login Redirect</strong> section</li>
<li>Enter the full URL of your desired landing page (e.g., <code>https://example.com/welcome</code>)</li>
<li>Click <strong>Save Changes</strong></li>
</ol>
<p>Users who log in via <code>/wp-login.php</code> will now land on that page instead of the WordPress dashboard. Users who were redirected to the login page from a specific URL will still return to that URL after logging in.</p>
<h4>How to Set Up a WordPress Multisite Intranet</h4>
<p>For organizations running a WordPress multisite network:</p>
<ol>
<li>Go to <strong>Network Admin > Settings > All-In-One Intranet</strong></li>
<li>Enable <strong>“Force site to be entirely private”</strong> to restrict the entire network to logged-in users</li>
<li>Optionally enable <strong>“Require logged-in users to be members of a sub-site to view it”</strong> for per-site access control</li>
<li>Under <strong>Sub-site Membership</strong>, select a default role to automatically assign users to sub-sites</li>
<li>Click <strong>Save Changes</strong></li>
</ol>
<p>The privacy and membership settings apply network-wide. The default role assignment runs automatically when new users or new sub-sites are created. Existing sub-sites and users are not affected retroactively when you change the role setting.</p>
<h4>Security Features</h4>
<p>All-In-One Intranet takes a layered approach to access control:</p>
<ul>
<li><strong>Authentication enforcement</strong> – uses WordPress’s built-in <code>auth_redirect()</code> function for reliable login redirection</li>
<li><strong>REST API lockdown</strong> – blocks unauthenticated API requests, preventing data access through endpoints like <code>/wp-json/wp/v2/posts</code></li>
<li><strong>XML-RPC disabling</strong> – completely disables XML-RPC when privacy is active</li>
<li><strong>No-role user handling</strong> – on single-site installations, users who are logged in but have no assigned role are logged out and shown an error message, preventing access by deactivated accounts</li>
<li><strong>Registration monitoring</strong> – displays admin warnings if WordPress is configured to allow open registration, which would undermine your private site setup</li>
<li><strong>Nonce verification</strong> – all settings forms use WordPress nonce validation to prevent cross-site request forgery</li>
<li><strong>Capability checks</strong> – settings pages require <code>manage_options</code> (single site) or <code>manage_network_options</code> (multisite) capabilities</li>
</ul>
<p>Note that media uploads (images, PDFs, etc.) remain accessible to anyone who knows their direct URL. This is a limitation of how WordPress stores media files and is common to most privacy plugins. If you need to protect individual file downloads, consider a dedicated file protection plugin alongside All-In-One Intranet.</p>
<h4>For Developers</h4>
<p>All-In-One Intranet provides the <code>aioi_allow_public_access</code> filter for developers who need to make specific pages or endpoints accessible without authentication.</p>
<p>This filter runs during both the template redirect check and the REST API dispatch check. Return <code>true</code> to allow public access for the current request:</p>
<pre><code>add_filter( 'aioi_allow_public_access', function( $allow ) {
    // Allow public access to a specific page
    if ( is_page( 'public-landing' ) ) {
        return true;
    }
    return $allow;
} );
</code></pre>
<p>This is useful for exposing specific landing pages, webhook endpoints, or custom API routes while keeping the rest of the site private.</p>
<h4>Google Workspace Integration</h4>
<p>If your organization uses Google Workspace (formerly Google Apps), two companion plugins extend your intranet:</p>
<ul>
<li>
<p><strong><a href="https://wp-glogin.com/glogin/?utm_source=wprepo&utm_medium=link&utm_campaign=AllInOneIntranet" rel="nofollow ugc">Google Apps Login</a></strong> – lets employees sign in to WordPress using their Google Workspace accounts. Domain admins can manage WordPress access entirely from the Google Admin Console, and only authorized employees can access the intranet.</p>
</li>
<li>
<p><strong><a href="https://wp-glogin.com/drive/?utm_source=wprepo&utm_medium=link&utm_campaign=AllInOneIntranet" rel="nofollow ugc">Google Drive Embedder</a></strong> – allows authors to embed Google Docs, Sheets, Slides, and other Drive files directly into pages and posts. Useful for intranets where documentation lives in Google Drive.</p>
</li>
</ul>
<p>Visit <a href="https://wp-glogin.com/?utm_source=wprepo&utm_medium=link&utm_campaign=AllInOneIntranet" rel="nofollow ugc">wp-glogin.com</a> for more information about these and other plugins.</p>


Intranet & Private Site – All-In-One Intranet

Turn WordPress into a private intranet in one click. Restrict access to logged-in members, with auto-logout and login redirect.

Private Suite vs Intranet & Private Site – All-In-One Intranet