Skip to main content

Installing Sprocket on Individual Site

For larger organisations, specifically when their IT is managed internationally or by a third party, you may not be allowed to install Sprocket globally to the whole tenant.

The solution for this is to install it at the site collection level instead of the entire tenant. In other words, installling at the Tenant App Catalog rather than the Site Collection App Catalog.


Note: A better way to install Sprocket at the individual site level is to deploy to the global App Catalog and dont tick 'deploy to all sites'. Then you just add the app to each site you required. This makes upgrading much more straight forward. See Installing Sprocket

Create a Site Collection App Catalog

Sprocket does not need to be installed at the tenant app catalog but instead can be installed at a specific site collection app catalog. This does not exist by default and requires a powershell to create.

Step 1: PowerShell

View detailed instructions here.

Run the following command:

Connect-SPOService -URL "" Add-SPOSiteCollectionAppCatalog -Site ""​​​​​​


In order to run the PowerShell, you must have the following roles:

  • SharePoint Admin role or Global Administrator role
  • Site Collection Administrator of the tenant App Catalog
  • Site Collection Administrator of the site collection of the site specified in the -Site parameter

Step 2: Install Sprocket

Now that you have run the PowerShell and your App Catalog has been created, you can now install Sprocket.

You will find the App Catalog via one of the following ways:

  • In the Site Contents of the site collection (it will be called 'Apps for SharePoint')
  • Direct URL i.e. /sites/FinanceTeamsite/AppCatalog

Upload the sprocket-365.sppkg file to the local site collection app catalog and ensure you select 'Make this solution available to all sites in the organisation' for Sprocket-365.


Note: This needs to be done at each site collection you require Sprocket, not just the Hub site.