EdminBoost works on WordPress multisite, but settings are stored per site (per blog)—not one network-wide control panel for all sites.
How settings are stored
Each site in the network has its own copy of:
- edminboost_settings
- edminboost_version
Activating EdminBoost on the whole network still means each subsite has its own layout, theme, and features unless you configure each one or copy settings yourself.
Network Admin vs site admin
- EdminBoost screens appear under each site’s wp-admin (Site → Dashboard, etc.), not as a dedicated “Network → EdminBoost” global panel in the core plugin.
- Configure EdminBoost separately on each subsite where you want it, or use export/import on each site.
Typical workflows
Single network, different clients per subsite
Set up EdminBoost on subsite A for client A, subsite B for client B. Export JSON from one site and import on another if you want to clone a layout (see migrating settings guide).
Same layout on many subsites
Build once → Export settings → on each subsite, activate EdminBoost (if needed) → Import settings → adjust URLs or menu items that differ per site.
Main site only
Activate and configure only on the main blog; subsites stay untouched.
“Agency 10-site license” vs WordPress multisite
The Billing page describes a commercial license for up to ten production sites. That is a licensing product term—not the same as “one WordPress multisite network.” A network with twenty subsites still needs per-site configuration; a ten-site license refers to how many separate installs you may license under Asphalt Themes’ terms, not WordPress’s multisite feature count.
Uninstall on multisite
Deleting EdminBoost from a site removes that site’s EdminBoost options. Other subsites in the network are unaffected unless you delete the plugin network-wide (behavior depends on how your host handles network plugin removal).
Super admin tips
- Document which subsites use EdminBoost.
- Keep a JSON export per “template” client.
- After cloning a subsite, re-check Top Bar and Menu Studio—plugin slugs and menus may differ from the source site.