Uninstall a ServiceNow pluginIssue Occasionally it may happen that you want to remove a plugin from your instance. A common question asked is if it's possible to uninstall a plugin that is activated on the instance?ReleaseAllCauseFor reference, there are 3 different types of Plugins usually referred: Base plugins (global scope only) have IDs starting with 'com.glide' and are part of the platform.Scoped plugins (global or app scope) have IDs starting with 'sn_' and are also part of the base platform.Scoped applications (global or app scope) have IDs starting with 'x_' and are installed from a private (git) repository or the ServiceNow app store, with a prefix indicating the customer company or vendor name. This article primarily covers base plugins (#1), with some aspects applicable to scoped plugins (#2).Follow the related article on uninstalling scoped applications (#3) in the product documentation: Uninstall an applicationResolutionTo uninstall a base plugin: According to ServiceNow Plugins: Note: After a plugin is activated, you cannot disable or deactivate it. If needed, you can hide the functionality. You should thoroughly test, in a non-production instance, the specific features and functionalities that are installed when you activate the plugin before using them in a production instance. When a plugin is activated, the installation process performs table schema changes and loads XML files (data, configurations, etc.). Deactivating the plugin does not roll back or disable these changes. Manually removing records by deletion can cause unexpected behavior. If the new functionalities are impacting users, it's recommended to either disable* or update the new functionalities and/or restrict access to them through the use of roles and ACLs. *There is also the option to hide the Application Menu from the Filtered Navigation. You can hide it by doing the following: Go to System Definition > Application Menus.Under title, search for the plugin.Open the entry and uncheck the "Active" box.Save and re-login. If a plugin was recently installed, a rollback context might be available to revert changes, but this may not undo all schema changes to prevent potential data loss. For sub-production instances, clone or restore the configuration from production to remove unwanted plugin installations, ensuring configuration consistency and avoiding unexpected differences during development cycles.Related LinksPlugin rollback and delete recovery Restrict access to an application Use the Rollback Contexts module to rollback a patch upgrade or plugin activation