--- sourceDocument: Australia ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-administration Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Plugin installation support # Individual plugin installation from Product Hub {#ariaid-title1} Release version: Australia Updated August 27, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Individual plugin installation from Product Hub Individual plugin installation from Product Hub allows ServiceNow administrators to discover, review, and install standalone plugins directly without needing to install entire product bundles. This capability supports flexible and incremental deployment, early validation of plugin functionality, and granular control over instance capabilities. The installation experience aligns with the existing guided framework used for bundled product installs, ensuring familiarity and consistency. Show full answer Show less ## Key Features * **Flexible deployment:** Activate only the necessary plugins to reduce unnecessary components and instance bloat. * **Early adoption and validation:** Business units can pilot plugins in controlled environments before wider deployment. * **Incremental rollout:** Phase plugin installations over time to match business priorities and readiness. * **Streamlined installation process:** Includes entitlement validation, dependency checking, installation progress tracking, and dynamic display of items to be installed. * **Clear dependency management:** All required dependencies are displayed and must be installed along with the plugin. * **Independent licensing evaluation:** Licensing constraints are checked at the plugin level, enabling selective installation based on available licenses. * **Synchronization with App Manager:** Plugin installation status in Product Hub reflects the actual state managed by App Manager. ## Practical Use Cases * **Selective capability adoption:** Install only specific plugins needed without extra apps from full bundles. * **Pilot deployments:** Test plugins in sandbox or development environments before production rollout. * **Phased rollout:** Different teams can adopt plugins according to their schedules without waiting for bundled releases. * **Licensing optimization:** Install licensed plugins immediately and defer others until licensing is obtained. * **Feature experimentation:** Evaluate plugins for business fit before committing to broad adoption. ## Considerations for ServiceNow Customers * **Mandatory dependencies:** All required dependencies for a plugin must be installed together; skipping dependencies is not allowed. * **Entitlement enforcement:** Installation is blocked if appropriate licensing is not active for the plugin or its dependencies. * **Plugin registration:** Only plugins registered by their owning business units appear in Product Hub for individual installation. Contact your implementation team if a needed plugin is not visible. * **Limited customization:** Individual plugin installs follow a streamlined path without optional component customization. For detailed control over optional apps, use the bundled product installation flow. * **Status synchronization:** Plugin status in Product Hub updates to reflect changes made directly via App Manager. ## Using Individual Plugin Installation Administrators can use Product Hub to search for, review details, and install standalone plugins without committing to full product bundles. This enables targeted capability activation aligned with organizational needs and licensing availability, simplifying management and accelerating value delivery. Individual plugin installation enables you to discover, review, and install standalone plugins directly from Product Hub without requiring a bundled apps package. This capability supports flexible deployment scenarios, early adoption, and validation of plugins before committing to full product bundles. Product Hub traditionally expose product bundles, providing guided installations of complete product packages with mandatory and optional apps. Individual plugin installation extends this capability by allowing admins to install specific standalone plugins without committing to an entire bundle. This approach enables business units (BUs) such as ITAM to adopt plugins incrementally, validate functionality before broader deployment, and maintain granular control over their instance's capabilities. Individual plugins are surfaced alongside bundled products in Product Hub. Each plugin displays its name, description, current status, and required dependencies. The installation process leverages the same guided framework used for bundled installs, including entitlement validation, dependency checking, installation progress tracking, and dynamic item count display. Individual plugin installation workflows mirror the product bundle installation experience, ensuring consistency across product bundle installation scenarios. ## Key benefits {#ia-plugin-install__section_benefits} Individual plugin installation provides the following benefits: * Flexible deployment: Admins can activate only the capabilities they need, avoiding unnecessary components and reducing instance bloat from unwanted functionality. * Early adoption: Business units can validate new plugins in controlled environments before deciding on broader deployment or full product adoption. * Incremental rollout: Organizations can phase plugin adoption over time, aligning deployments with business priorities and readiness schedules rather than bundled all-or-nothing approaches. * Faster time to value: Admins bypass the overhead of evaluating and installing entire product bundles when they only need specific capabilities. * Simplified licensing: Plugin-level licensing constraints are evaluated independently, allowing admins to proceed with available plugins and defer others pending license acquisition. * Clear dependency visibility: The install flow displays all required dependencies, helping admins understand what will be activated alongside their selected plugin. {#ia-plugin-install__ul_ajd_1qr_jkc} ## Use cases {#ia-plugin-install__section_use_cases} Individual plugin installation is useful in the following scenarios: * Selective capability adoption: An organization needs a specific plugin's functionality but does not want the additional apps that would come with a full product bundle. Individual plugin installation lets them activate exactly what they need. * Pilot deployments: A business unit tests a plugin in a sandbox or development instance before deciding whether to roll it out to production. If validation is successful, they proceed with installation in production; if not, they can defer or abandon the plugin without affecting other deployments. * Phased rollout: A large enterprise rolls out multiple plugins over time according to organizational readiness. Using individual plugin installation, different teams can adopt plugins on their own schedule without waiting for bundled product releases. * Licensing optimization: An organization has licenses for some plugins but not others. They install available plugins immediately and defer others until additional licensing is procured, avoiding all-or-nothing delays. * Feature experimentation: IT teams evaluate whether a plugin's capabilities align with business requirements before committing to broader rollout, minimizing waste and maximizing ROI on technology investments. {#ia-plugin-install__ul_cjd_1qr_jkc} ## Considerations {#ia-plugin-install__section_considerations} Consider the following when using individual plugin installation: * Dependencies are mandatory: When a plugin has required dependencies, all of them must be installed as part of the transaction. You can't selectively skip dependencies even if you don't intend to use them. Dependencies are identified during installation planning and validated before execution begins. * Entitlements are authoritative: Plugin availability is controlled by active licensing and can't be overridden within Product Hub. If a plugin or dependency lacks appropriate licensing, installation is blocked until licensing is obtained. * Plugins are registered by business units: Not all plugins are automatically eligible for individual installation through Product Hub. Plugins must be explicitly registered in the Product Hub registry by their owning business unit. Contact your implementation team if a plugin you need is not visible in the hub. * Individual plugin installs don't include bundle customization: Individual plugin installation follows a streamlined path with pre-defined mandatory apps and dependencies. If you need fine-grained control over optional components, consider the bundled product installation flow instead. * Installation status reflects App Manager state: The plugin's installation status in Product Hub is synchronized with App Manager. If a plugin is set to inactive or is uninstalled outside of Product Hub (for example, via direct App Manager operations), the status in Product Hub updates to reflect the current state. {#ia-plugin-install__ul_djd_1qr_jkc} * **[Install an individual plugin from Product Hub](https://www.servicenow.com/docs/RTHdllAAwWY_NzyiGQsnqA)** Use Product Hub to discover, review, and install an individual standalone plugin without requiring a full product bundle installation.