Extensions
Site-wide components that extend SharePoint beyond individual web parts.
What are Extensions?
Extensions are SPFx Application Customizers that run site-wide, outside of individual pages. Unlike web parts that you add to specific page sections, extensions inject content into SharePoint's header or footer placeholders on every page of your site.
Extensions vs Web Parts
Web Parts
- Added to individual pages
- Configured per-instance
- Visible on specific pages only
- Placed in page sections/columns
Extensions
- Run on every page site-wide
- Configured once, applies everywhere
- Always visible across the site
- Placed in header/footer placeholders
How Extensions Work
Extensions use SharePoint's placeholder system to inject content into designated areas of the page chrome:
- Top Placeholder: Above the page content, typically used for navigation, banners, or alerts
- Bottom Placeholder: Below the page content, typically used for footers
Once activated on a site, an extension runs automatically on every page load. Configuration is typically stored in extension properties or a SharePoint list.
Activation Scope
Extensions are activated per site collection. Once enabled, they apply to all pages within that site collection, including subsites.
Bonzai 2 Extensions
Bonzai 2 includes multiple extensions. More may be added in future releases.
Mega Menu
3-level hierarchical navigation with desktop mega menu panels and mobile drawer.
Application CustomizerFooter
List-driven site footer with navigation, feedback, and branding.
Application CustomizerDeploying Extensions
Extensions are included in the Bonzai 2 SPFx package. Deployment is a two-step process:
- Step 1: Upload to App Catalog — Upload the Bonzai 2 .sppkg file to your tenant App Catalog and approve the API permissions
- Step 2: Add to Site — Go to Site Contents → New → App on each site where you want to use extensions, and add the Bonzai 2 app
Important: Step 2 is often missed. The Mega Menu will not appear until you add the Bonzai app to your specific site, even if the package is already in the App Catalog.
See individual extension documentation for detailed setup steps.