Choose a plugin's activation scope according to its documented Multisite support and the sites that need it. Network activation loads the plugin across the network, while site activation limits it to selected subsites when the plugin supports that mode.
IN THIS ARTICLE
01 Check the plugin's intended scope
Review its official documentation for Multisite compatibility, network-only requirements, licence limits and where settings are stored. A plugin may support Multisite but still require separate configuration on each site. A network-wide activation does not automatically create one shared set of products, forms or content.
02 Test and activate
- Back up the network and test the plugin on an isolated copy or an appropriate test subsite.
- Install the approved plugin through Network Admin.
- If every site needs it and the developer supports network activation, activate it from the network plugin list.
- If only selected sites need it, make the site plugin menu available where appropriate and activate it on those sites.
- Configure its settings at the documented network or site scope and verify the actual feature on each affected site.
Can a subsite administrator deactivate a network plugin?
Normally a network-active plugin is controlled by the network administrator. This is useful for required network services, but it also means a faulty network plugin can affect many sites. Have a documented recovery method and avoid deploying untested code to the whole network.
Are must-use plugins the same as network-active plugins?
No. Must-use plugins are loaded through the installation's must-use plugin mechanism and have a different management and update workflow. Their presence may not appear as an ordinary site-level activation choice. Identify who maintains them before attempting to disable related functionality.
03 Review shared risks
Check scheduled tasks, mail delivery, external API connections and database changes before expanding activation. A plugin may create tables or recurring jobs for each site, so resource use can grow with the network. Deactivation also does not necessarily remove stored data or scheduled integration state.
04 Confirm the result
Test an affected site and an unaffected site, including administration and public pages. Record the activation scope and configuration owner. If a problem begins, revert the reviewed activation change and consult the plugin's supported recovery procedure rather than deleting its database tables or network configuration blindly.