Activate, deactivate, and manage plugins across every site in your network from one screen.

Managing plugins on a multisite network is messy. Deactivating a plugin at the network level can leave it quietly running on individual sites — but how would you know? Finding out means clicking through site after site, and fixing it means holding your breath while a bulk action either works or takes the network down.

Beardo Multisite Activation Console was built for one purpose: to save you that time. Every plugin, every site, one grid — with every change made carefully, recorded, and impossible to lock yourself out with.

Activation Grid

See the whole network at a glance: which plugins are network-active, which are switched on for individual sites, and which are off everywhere. Sort, search, and filter the way you already do in the WordPress admin — no spreadsheets, no site-hopping.

Quick Change

Change the status of any plugin on any site right from the grid. The console never fires off a giant batch and hopes for the best: each change runs on its own, with a health check first. If a plugin would break one subsite, that site is flagged and the rest of your network carries on untouched.

Clear Stale

Networks that have been around a while collect clutter — plugins marked active on a site and network-active at the same time. The console spots the redundant entries and clears them without deactivating anything that’s genuinely in use.

Dead References

Deleted a plugin from the server but WordPress still thinks it’s active somewhere? Those leftover entries hang around in your database for years. The console finds them and removes them.

Logs

Every change is written to a network-wide audit log: who did it, on which site, what they changed, and whether it worked. Filter by person, site, or plugin. When a client asks “who turned that off?”, you’ll have the answer in seconds.

Need the log outside WordPress? Export it as a CSV or Excel (.xlsx) file straight from the Audit tab — either the filtered view you’re looking at or the whole log — ready for a client report, a compliance review, or a spreadsheet.

Guardrails

A built-in protected list means the console will never deactivate itself, a drop-in, or anything else that would lock a super admin out mid-change. Developers can extend that list with a single filter.

Feels like part of WordPress

Built on the same DataViews interface WordPress itself uses, so there’s nothing new to learn. It follows your admin color scheme, works in right-to-left languages, and looks like it belongs.

Free, and nothing leaves your server

No paid tier, no external services, no tracking, no phoning home. The plugin reads and writes only your own network’s plugin state and its own audit log.

Who it’s for

Agencies and hosts managing client sites on one network
Universities, franchises, and publishers with dozens or hundreds of subsites
Anyone who has ever bulk-activated a plugin and immediately regretted it

Requires a multisite network. Only super admins can use the console, and every request is protected by WordPress nonces and capability checks.

Support & Documentation

Learn more: beardo.tools/multisite-activation-console
Get help: help.beardo.tools

External Services

This plugin makes no external HTTP requests. It reads and writes only local
WordPress data: the network’s plugin activation state, the sites in the
network, and its own audit log table. No data is sent to any third-party
service, and no tracking, telemetry, or analytics of any kind is collected.

Third-Party Libraries

The admin interface is a React application built from the plugin’s own source
in src/ using @wordpress/scripts. The shipped build/index.js is compiled
output — not obfuscated code — and contains only the plugin’s source plus the
standard WordPress packages it imports (@wordpress/components,
@wordpress/dataviews, @wordpress/element, @wordpress/api-fetch,
@wordpress/i18n, @wordpress/icons), all GPL-compatible.

The full, unminified source is available in the plugin’s public repository.