/* Docs are the one layout with a fixed sidebar, and page level furniture such as the footer has to clear it. `pinned` already means "this is a docs page". */
365crafted your tenant. your tools. your data.

Installing a package

v1.0 · updated 3 august 2026

The same four steps install any tool on the shelf. Only the package name and the permission it asks for change.

plate 01upload the package

Upload the package

  1. 01Open the SharePoint admin centre and go to more features, then apps, then app catalogue.
  2. 02Drag the .sppkg file into the library. SharePoint reads the manifest and shows a trust dialog.
  3. 03Decide whether to make the solution available to all sites. Ticking this deploys it tenant wide, so editors do not have to add the app to each site first.
  4. 04Choose deploy.
plate 02approve the permission request

Approve the permission request

If the tool reads tenant data, uploading it queues a permission request. Nothing works until that request is approved.

  1. 01Open the SharePoint admin centre and go to advanced, then API access.
  2. 02Find the pending request naming the package.
  3. 03Read the scope it asks for and approve it.
plate 03add it to a page

Add it to a page

  1. 01Edit any modern page.
  2. 02Open the toolbox and pick the tool by name.
  3. 03Open the property pane and configure it. Each tool documents its own settings.
  4. 04Publish the page.
plate 04updating later

Updating later

Upload the newer .sppkg over the old one in the same app catalogue and deploy it again. Pages using the web part pick up the new version on their next load, and configuration is preserved.

checking the installed version
Get-SPOApp -Identity "Rollup" |
  Select-Object Title, AppVersion, IsEnabled