Adding the Ebbot Widget to a SharePoint Environment

Follow the steps below to add the Ebbot widget to your SharePoint environment.

  1. Download the app package Download the Ebbot widget apparrow-up-right. Make sure the file Ebbot.sppkg is saved locally.

  2. Upload the app to the SharePoint App Catalog

    1. Go to your SharePoint App Catalog. The URL is usually: https://[domain].sharepoint.com/sites/appcatalog/AppCatalog/Forms/AllItems.aspx

    2. Click New.

    3. Select Browse, then upload the downloaded Ebbot.sppkg file.

    4. Complete the upload and approve the app if prompted.

  3. Add the widget to a SharePoint page

    1. Navigate to the SharePoint page where you want to add the widget.

    2. Click Edit to edit the page.

    3. Click the plus (+) icon to add a new web part.

    4. Select EbbotWidget from the list of available elements.

    5. In the widget configuration:

    6. Select the appropriate hosting environment

    7. Enter your Bot ID

  4. Publish the page

    1. Save the page.

    2. Publish the page.

    3. Refresh the page to verify that the Ebbot widget is visible and working.

Configure Trusted Script Sources (CSP)

With Microsoft’s Content Security Policy (CSP) enforcement for SharePoint Online, external scripts and connections are blocked by default unless explicitly allowed.

To ensure the Ebbot widget loads correctly, communicates with our APIs, and supports real-time chat, you must add Ebbot domains to your SharePoint Trusted Script Sources.

Identify Required Domains

Depending on your Ebbot environment, you need to allowlist three types of domains:

  • Asset Domain (scripts and styles)

  • API Domain

  • WebSocket Domain (real-time communication)

Note: You can verify the correct domains in the CSP section inside the Ebbot platform.


Add Domains in SharePoint

Method A: SharePoint Admin Center (Recommended)

  1. Log in to the SharePoint Admin Center

  2. Go to Advanced → Script sources

  3. Click + Add source

  4. Add your Asset Domain and save

  5. Repeat for:

    • API Domain

    • WebSocket Domain

Important Notes

  • All three domains must be added for the widget to function properly

  • Missing domains may result in:

    • Widget not loading

    • Failed API calls

    • Broken real-time chat

  • Changes may take a few minutes to propagate

Last updated

Was this helpful?