This article outlines paths, specific steps, and best practices for rolling out Elise Sidekick to your full organization.
Rollout Paths
Option 1: IT-Led Rollout (Recommended)
EliseAI recommends IT-Led Rollout for Elise Sidekick, especially for larger organizations.
When IT centrally deploys Sidekick through device management tools or policies, this allows for near-instant, uniform adoption across all user machines.
| PROS | CONS |
| Seamless deployment: no manual downloads needed by users | Requires IT involvement and setup time |
| Ensures 100% consistency | Dependent on existing IT infrastructure and permissions |
| Saves managers and trainers from chasing down individual users | May require coordination if mixed platforms and devices are involved |
| Better audit and tracking controls |
Top Platforms / Methods & Reference Guides
NOTE: All these methods support force-installing for both Chrome and Edge. These browsers share many policy infrastructure features.
A. Group Policy Objects (GPO) - Windows Active Directory
- How it works: Use Chrome and Edge ADMX templates to “force-install” the Sidekick extension across domain-joined machines.
- Reference: Deploying Chrome Extensions via GPO (Google Admin docs)
- This also works for Edge if you use Edge ADMX with a similar “Configure the list of force-installed apps and extensions” policy.
B. Microsoft Intune (Endpoint Manager)
- How it works: Create a Configuration Profile—either Admin Templates or Settings Catalog—to force-install the extension by specifying the extension ID and update URL (found below).
- Chrome Ref: Manage Browser Extensions via Intune
- Edge Ref: Silently Install Edge Extension via Intune (Microsoft Q&A)
C. Jamf Pro / Jamf School (macOS MDM)
- How it works: Deploy a configuration profile (plist) with ExtensionInstallForcelist key — containing Sidekick extension ID and update URL.
- Chrome Ref: Jamf School: Deploy Chrome Extensions to macOS
-
Edge on macOS: Use Edge Enterprise policy plist equivalently.
D. VMware Workspace ONE (AirWatch / UEM)
- How it works: Deploy the extension via Device Profiles or Baselines using custom scripts or registry modifications.
- Chrome Ref: Deploy Chrome Extension Using Workspace ONE (Torii)
- Edge Ref: Workspace ONE: Deploy Chrome Browser Cloud Management Tokens (Windows/macOS) — similar steps apply for Edge browser settings.
Chrome Web Store URL:
https://chromewebstore.google.com/detail/elise-sidekick/kpifjidocdfajhopejaimakelkknfhii
→ Extension ID = kpifjidocdfajhopejaimakelkknfhii
Edge Add-ons Store URL:
https://microsoftedge.microsoft.com/addons/detail/elise-sidekick/bbmdcceghmgjmgeedeflpokknmlibbil
→ Extension ID = bbmdcceghmgjmgeedeflpokknmlibbil
Option 2: Individual-Led Rollout (Fallback)
With individual-led rollout, users download and install Sidekick themselves through provided links for Chrome or Edge. This is manual but effective if IT installation is not feasible.
| PROS | CONS |
| No IT infrastructure needed | Time-consuming to ensure implementation |
| Faster to start in small or ad hoc setups | Higher risk of partial adoption or user confusion |
| Requires ongoing reminders and support |
Process
Follow these steps to complete individual-led rollout:
- Provide users with direct download links for:
- Chrome (Chrome Web Store link)
-
Edge (Microsoft Edge Add-ons link)
- During onboarding/training, instruct each user to:
- Click the link
- Add the Sidekick extension
- Sign in
-
Confirm functionality
- Follow up with users through:
- Training calls
- LMS tracking
- Manager check-ins
Recommended Training and Onboarding Procedure
A. Before Launch
-
Review Training Resources
- Set up all team members with a Training Role (or a role with additional permissions) in the EliseAI platform. This ensures seamless access to training and support resources.
- Complete an on-demand course and/or attend a live training webinar in the EliseAI Learning Center to learn how Sidekick enhances EliseAI workflows.
- Leverage all materials and assets (including on-demand courses, live webinar training, and Help Center resources) for internal team training and implementation.
-
Internal Kickoff Call (per Property or Team)
- Provide a live demo of Sidekick.
- Confirm install on-call (via IT or individual).
- Have onsite team download and install during the session.
- We recommend downloading the extension as soon as we provide your login credentials.
- We recommend downloading the extension as soon as we provide your login credentials.
-
Exec-Level Communication
-
Send an email announcing the launch: for instance, “We are implementing EliseAI + Sidekick — Sidekick is required on your work browser.”
-
-
Share Initialization Instructions with the Team
- Feel free to use and adapt the example copy below:
|
Once the Elise Sidekick extension has been installed in your browser, follow these steps to open and log in: Chrome
Edge
✨ Tip: After logging in, pin the Sidekick icon to your browser bar so you can open it with one click. |
B. Post Launch
-
Weekly Round-Tables / Check-Ins
- Gather feedback, answer questions, and iterate based on user experience.
- Gather feedback, answer questions, and iterate based on user experience.
-
Ongoing Support & Tracking
- Monitor LMS completion and usage metrics.
- Send reminders or escalations if installation or training remain incomplete.