Installing the SPFx package in your tenant

A one-time admin task, upload the sppkg, approve API permissions, deploy. After this the product is available across the tenant.

SharePoint Forms365 is delivered as a SharePoint Framework (SPFx) package, a single

forms365.sppkg file you upload to your tenant's App Catalog. Once installed, the form customizer is available across every site collection in the tenant.

This is a one-time admin task. Once done, end users never see SPFx again, they just see SharePoint Forms365 forms render where the default ones used to.

Prerequisites

  • SharePoint admin role, required to upload to the App Catalog
  • A configured tenant App Catalog (created via SharePoint Admin Center → More features → Apps)
  • The forms365.sppkg file (downloaded from your SharePoint Forms365 account, or provided by your reseller)

Step 1, Upload to the App Catalog

  1. Open the SharePoint Admin Center → More features → Apps → App Catalog.
  2. Click Apps for SharePoint in the left rail.
  3. Drag forms365.sppkg onto the upload zone, or click Upload.
  4. In the resulting dialog, check Make this solution available to all sites in the organization and click Deploy.

Step 2, Approve API permissions

The first deploy triggers a permission-approval prompt for the Microsoft Graph scopes the runtime needs (user profile reads, group membership lookups, etc).

  1. Browse to SharePoint Admin Center → Advanced → API access.
  2. Look for pending requests under "Pending requests". You'll see one or more from forms365 for scopes like User.Read.All, GroupMember.Read.All.
  3. Approve each one. Without these, audience trimming and people-pickers fall back to a limited mode.

Step 3, Verify

  1. Visit any list in any site collection.
  2. Open List settings → Form settings. You should see SharePoint Forms365 as an available form option.

That's it. End users opening a list now see SharePoint's default form by default; once a SharePoint Forms365 form is published against the list, they see that instead.

Upgrading

Same process, upload the new .sppkg over the old one. SharePoint's CDN cache forces a brief delay before the new bundle reaches every user. Bumping the package version is what triggers the upgrade banner; if you're unsure whether an install took, check the version constant from the form's console:

[forms365] vX.Y.Z · {git-sha} · built {date}