The CreatorCon Call for Content is officially open! Get started here.

John_Yates
ServiceNow Employee
ServiceNow Employee

KH_MFA_UserReset_Banner_20250811.png

 

Now that you have tested your app and are ready for production, let's review the process to add a paid app to your contract. This article shows you how, as well as helps with some terminology for a smoother experience. 

 

To move a paid Store app into a production instance, you'll need a license. This step isn’t required when you want to try out an app in a development or testing instance, which makes it easier to explore new capabilities from the ServiceNow Store.  But, it can be overlooked when it's time to go live.

 

Check the additional resources at the end of this article for complete details.

 

Steps to get (procure) a paid app for your production instance

  1. Locate the app in the ServiceNow Store. Your paid app will have the blue Paid tag on the tile.
    John_Yates_0-1759529459619.png

     

  2. If you can’t find the app, it may be either:
  • A plugin. Plugins installation can be requested via ServiceNow Catalog on Now Support (Item name: Activate Plugin)
  • A dependency app that is hidden in the Store. These apps are installed automatically with the parent application installation. 
  1. On the app page, select Request license.
  2. The button changes to License requested.
  3. Work with your ServiceNow account manager to formally add the app to your contract.
  4. After the app is added to your contract, the button changes to Get so you can procure the application.
  5. Once the app is procured, the Get button changes to Ready to install.

 

Review this quick refresher on some store terminology

 

Paid
This tag means the application requires purchase and licensing before installation. It will always show the Paid tag even if you already purchased the app. The application page gives more details.

 

Procure, entitle 
Used interchangeably, these terms mean to get or acquire an app. This action establishes a back-end connection with your instance and the app. This step is necessary to avoid accidental app installation on a production instance without non-production testing. These terms do not imply the need for purchase. 

 

Eligible, not eligible
A product suite page has two tabs that list which apps within the suite are in your contract and mapped to your instance.

 

Instances
All customers have at least three instances: development, testing, and production. The first two are commonly referred to as non-production or sub-production.  

 

 Additional Resources

 

 

Version history
Last update:
26m ago
Updated by: