Interactions Manager for Mediasite

Export and import interactions and chapters between Mediasite presentations. Unofficial, not affiliated with Mediasite.

Mediasite Interactions Manager (Unofficial) This is an independent, unofficial browser tool for people who manage Mediasite presentations. It is not affiliated with, endorsed by, or supported by Mediasite or Enghouse Video. "Mediasite" is used only to describe compatibility with that platform's REST API. What it does: Interactive elements (hotspots, buttons and text) and chapters don't carry over automatically when you replace content within a Mediasite presentation. This extension copies them for you: 1) Export interactions and chapters from a source presentation 2) Save a local backup (JSON) you can keep or re-import later 3) Import/restore that data onto a new or replacement presentation Works entirely against your own Mediasite server's REST API, using credentials you provide Two modes: > Lite: a simple export → save → import flow for one-off migrations > Advanced: per-type control over interactions and chapters, including a "Discover" tool that probes your server for the correct chapters endpoint name (this varies slightly between Mediasite versions) How your data is handled: > Your Mediasite root URL, API key, username, and password are entered by you in the Settings panel and stored only in your browser's local extension storage, on your own device. > Nothing is sent anywhere except the Mediasite server URL you configure. There is no external analytics, tracking, or third-party server involved. > Exported interaction/chapter data is cached locally so you can navigate away and import later without losing it. > Your credentials are never sold, shared, or used for anything other than authenticating your own requests to your own Mediasite server. Why it asks for broad site access: Mediasite is self-hosted software, deployed on whatever domain each institution or company chooses. Because that domain isn't known in advance, the extension requests general host access rather than a fixed one — it only ever contacts the single Mediasite root URL you configure in Settings. Requirements: > A Mediasite server you have API access to (root URL, API key, username, password) > Your Mediasite account has the relevant permissions to work with the API, Interactions and Chapters > HTTPS connection to that server