Skip to content
Launch offer: 20% off all webpartsView launch offer
SPFxStore

B2B store: sales exclusively to businesses, public-law entities and special funds under public law. Prices are net plus applicable taxes.

Guide · App catalog

From download to a finished page

This is how you make a purchased webpart available to your organization. No developer skills required — just the .sppkg file and SharePoint administrator rights. Typical duration: under 10 minutes.

What you need

  • The .sppkg file from your purchase (download link in your order confirmation)
  • The "SharePoint Administrator" role (or Global Admin) in Microsoft 365
  • An app catalog in your tenant — if none exists yet, step 2 creates it
  1. 01

    Download the .sppkg file

    After your purchase you receive a download link by email. Save the file locally — it is your installation package and your licensed copy for any future re-deployment.

  2. 02

    Open (or create) the app catalog

    Open the SharePoint admin center and go to "More features" → "Apps" → "App Catalog". If no catalog exists yet, SharePoint offers to create one here — provisioning takes a few minutes, once.

    https://<your-tenant>-admin.sharepoint.com

  3. 03

    Upload and deploy the package

    In the app catalog, choose "Apps for SharePoint" and upload the .sppkg file. In the deployment dialog, check "Enable this app and add it to all sites" — the webpart becomes available tenant-wide immediately, with no per-site installation.

  4. 04

    Approve API permissions (if requested)

    If the webpart reads data via Microsoft Graph (e.g. profiles for an org chart), a pending permission request appears after the upload. Approve it in the admin center under "Advanced" → "API access". Each product page lists exactly which permissions a product needs.

  5. 05

    Add the webpart to a page

    Open any modern page, click "Edit", then the plus button in a section. Search for the webpart by name, place it, and configure it in the property pane on the right. Republish — done.

  6. 06

    Install updates

    New releases ship as an updated .sppkg file. Simply upload it to the app catalog again (step 3) — SharePoint detects the higher version number and updates every instance tenant-wide. Settings and placed webparts remain untouched.

If something doesn't work

The webpart doesn't appear in the page toolbox

Check that tenant-wide deployment was enabled during upload, and hard-refresh the page (Ctrl+F5). After the first deployment it can occasionally take up to 15 minutes until all sites offer the webpart.

The permission request doesn't show up under "API access"

Requests only appear after the package is deployed in the app catalog and can take a few minutes. Also verify you are signed in with the SharePoint Administrator role.

Does this work on classic SharePoint pages?

No — SPFx webparts are designed for modern pages. Classic pages (web part pages) are no longer developed by Microsoft and are not supported by our products.

This guide is also included with every purchase as an illustrated PDF — tailored to the specific webpart and its permissions.

Browse the webparts