How to stop clients installing random plugins that break your setup
A client finds a free plugin that promises to do something clever, installs it, and suddenly your carefully configured site has a conflict. Or they install a second SEO plugin. Or a security plugin that fights with yours.
ToggleWP’s Plugin Control module gives you tools to guide clients toward safe choices – and block the problematic ones entirely.
Block specific plugins by slug
If there are plugins you know cause problems – conflicting caching plugins, abandoned security tools, duplicate functionality – you can block them by WordPress.org slug. When a client searches for them, they simply don’t appear.
Replace the Featured tab
The default WordPress.org “Featured” plugins tab shows whatever WordPress decides to promote. You can replace it with your own curated plugin list – a set of approved suggestions you’ve vetted and trust.
Clients browsing for new plugins see your recommendations first, not a frequently changing selection from the repository.
Suggest plugins via a Curated Suggestions
For a more structured approach, Plugin Control includes a Curated Suggestions feature. Add plugins with names, descriptions, and installation links. Your recommendations appear as a dedicated tab in the plugin installer.
Deactivation protection
For plugins you’ve already installed and want to keep, add Deactivation Protection to prevent clients from removing them. The deactivate button simply disappears for those plugins.
Email alerts on activation/deactivation
You can configure email alerts per plugin – if a plugin is activated or deactivated (by anyone) via the UI you get notified. Useful for keeping tabs on what’s changing without micromanaging. Global activation / deactivation notices are also available.
Push rules across all sites
Configure all your Plugin Control rules once on your Site Sync parent and push them to every client site on a schedule.
You can’t always stop clients from trying things, but you can make it much harder to accidentally install something that causes a problem.
Read the KB article: How to set up plugin protection and add notes