ServiceNow plugins unlock platform functionality — from HR modules to advanced integrations. This guide walks you through the plugin activation process and helps you avoid the gotchas that can take down production features.
Why plugin activation matters for platform stability
Before ServiceNow's plugin architecture, platform updates meant all-or-nothing upgrades that affected every customer the same way. Now, most functionality ships as plugins that activate on demand. Platform architects and system admins control what gets enabled when, but activating the wrong plugin at the wrong time can disable critical features or cause unexpected downtime. Users don't see plugins directly — they just see features that work or don't work — but IT teams own the consequences of activation decisions.
How plugin activation actually works
Plugin activation happens in two phases: lightweight plugins activate immediately, while complex plugins queue for background installation that can take minutes or hours. The process loads new tables, business rules, UI components, and integrations. Some plugins have hard dependencies — activating one automatically pulls in others. The 'activate with demo data' option populates sample records, which is useful for testing but creates cleanup work later. Most admins start with sub-prod testing, then activate during maintenance windows on production.
Managing plugins in production environments
After basic activation works, the improvements that matter are: maintaining a plugin inventory across instances, testing plugin interactions before production deployment, and establishing rollback procedures for plugins that break existing functionality. Well-managed plugin governance includes change approval processes, dependency mapping, and scheduled activation windows. Some plugins can't be easily deactivated once enabled, so the activation decision is often permanent.
Before you start
- •admin role or plugin_admin role
- •System Administrator access to target instance
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to the plugins list
Go to System Definition > Plugins. This loads the master plugin catalog showing all available plugins, their current state, and dependencies. The State column shows 'Active' for enabled plugins and blank for available ones. Use the search box to find your specific plugin rather than scrolling — there are hundreds of plugins in a typical instance.
Filter by State = 'Available' to see only plugins you can activate.
Locate and select your plugin
Search for the plugin by name or ID — plugin IDs are usually more reliable than display names. Click the plugin name to open the plugin record. The Dependencies tab shows what other plugins will automatically activate with this one. The Description field explains what functionality you're enabling, but it's often vague.
Check plugin dependencies and impact
Review the Related Links section for dependency information and the Tables tab to see what database tables will be created. Large plugins that create many tables take longer to activate and have higher risk of conflicts. Note any warnings about production impact or required configuration steps post-activation.
Choose activation options
Click the 'Activate/Upgrade' button to open the activation dialog. Check 'Load demo data' only if you need sample records for testing — this creates cleanup work later. The dialog shows estimated activation time and any additional dependencies that will be pulled in. Most plugins should be activated without demo data in production.
Confirm and monitor activation
Click 'Activate' to start the process. Simple plugins activate immediately and redirect you back to the plugin list with State = 'Active'. Complex plugins show a 'Queued for installation' message and run in the background. Check System Logs > System Log > All for activation progress and any error messages.
Activation jobs appear in System Definition > Scheduled Jobs if you need to monitor progress or check for failures.
Verify activation completed successfully
Return to System Definition > Plugins and confirm your plugin shows State = 'Active'. Navigate to the feature or module the plugin enables and test basic functionality. Check that new menu items appear where expected and that any new tables were created properly. Some plugins require additional configuration before they're fully functional.
Best practices
Always test plugin activation on a sub-production instance first — some plugins cause unexpected feature conflicts that only surface under load.
Never activate plugins during business hours on production — even 'lightweight' plugins can cause brief service interruptions for related modules.
Document plugin dependencies before activation because deactivating a parent plugin can break child functionality that users rely on.
Avoid activating plugins with demo data in production — the sample records often contain inappropriate data and create security review headaches.
Create a plugin activation checklist that includes post-activation testing steps — some plugins activate successfully but require additional configuration to work properly.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue