Extensions
Extensions add widgets, bot modules, automation nodes, themes and integrations to your channel. You find them in the Extension Store (Dashboard > Store) and manage the ones you installed under Store > Installed. The store is part of the Extensions feature of your plan.
Installing from the store
Open an extension in the store and choose Install. Before anything is installed, the install dialog lists the data the extension receives from your channel, what it can do for you and the servers it can send data to. When the extension declares any of those, the button reads Allow and install. A store install always receives the latest published version.
Installing needs the extension-store:install permission in the channel. Paid extensions go through checkout first; see Billing.
Managing installed extensions
Store > Installed lists every extension installed in the channel, with a category filter when there are more than two categories. Each row shows the developer (or Built-in by Lumio for Lumio's own extensions), the category and the installed version.
- Auto-update (needs
extension-store:configure): when on, the extension moves to each new published version automatically. - Uninstall (needs
extension-store:uninstall): removes the extension from the channel. You choose whether its stored data is kept for 30 days or deleted at once. Built-in extensions cannot be uninstalled.
If the list cannot be loaded, the page says so and offers Try again instead of showing an empty list.
Testing a version you were invited to
A developer can invite you to test a version of their extension before it is published. Your invitations appear at the top of Store > Installed under Test invitations, newest first. The section is shown only when you have at least one invitation. Each invitation names the extension, the test version and when you were invited.
Choose Install test version to install that exact version in the channel you are working in. You need the extension-store:install permission in that channel, and you must be signed in to Lumio yourself: API keys and tokens cannot install test versions.
A test version behaves differently from a store install:
- It carries a Test version x.y.z badge in the installed list and on the extension's store page.
- It stays on that version. It has no auto-update switch and never moves to a newer test version or to the published version on its own. To test a newer version, install it from its own invitation.
- It is removed automatically when the testing phase ends for you: when the developer removes you as a tester, requests publication of the version or abandons it, or deletes the extension. The removal works like a normal uninstall, so the extension's data in your channel is kept for 30 days.
- Installing it never charges you and never creates a purchase. A paid extension still needs a plan that includes paid extensions.
An invitation cannot be installed in these cases, and the row tells you why:
| Row shows | Why |
|---|---|
| Installed | This test version is already installed in the channel. |
| Already installed in this account | The channel already has the extension (the store version or another test version). Uninstall it first, then install the test version. |
| No longer in the testing phase | The developer requested publication or abandoned the version. |
If the invitations cannot be loaded, the section shows an error with Try again.
Running a testing phase (developers)
As a developer you manage the testing phase on your extension's Testing page (Dashboard > Extensions > your extension > Testing). Pick the test version from the Test version list; it lists the versions that are in testing or waiting for the final review (pending_publish), and shows the status next to it. While the version is in testing you can invite testers by their user ID, see who you invited and choose Request Publish. Requesting publication removes the testers' test installs, because a test version can be installed only while it is in testing.
Abandon test version ends the testing phase of the selected version for good. A confirmation dialog lists what happens: testers' test installs of this version are removed, the feedback they left is kept, and the version cannot be resumed. To test again, submit a new version. Abandoned versions show the Abandoned status in your submissions.
Details for developers: Testing phase.