Skip to main content

Hosting Integrations


Sapling provides a number of integrations, including for browsers—such as Chrome and Edge—as well as for Microsoft Word and Outlook.

When a client hosts Sapling's backend, the integrations must be updated so that they know to query the client's backend instead of the default Sapling backend. End users should then install the custom client integrations instead of the default Sapling integrations.

Here we briefly describe options for hosting these custom integrations.

Browser Integrations

For browser integrations such as Chrome and Edge, team managers have a few options

  1. Have Sapling submit a custom, unlisted extension to the Chrome/Edge/Mozilla app store. We strongly recommend this option, as the app store has a process for vetting extensions, and Sapling can provide updates as needed.
  2. Submit the custom extension to the app store themselves—this usually results in more work when updating extensions.
  3. Install the extension as a package outside of the app stores. Example instructions for Edge and for Chrome.

Microsoft Add-Ins

Custom office add-ins can also be built and centrally managed. Here is a list of prerequisites and an overview of how to deploy from the admin center. The centralized deployment service again allows deployment of add-ins from the store or non-store applications through a manifest.xml file. The Sapling team can provide this.