Browse all docs

Plugin market and install confirmation

Buy or claim plugins in the console: feature modules activate on payment; the administrator confirms themes, rule packs and page plugins and picks tenants.

What it solves

To add a capability to your control plane you do not have to wait for a release or build it yourself: the official publisher and third-party developers list plugins on the plugin market, and the control plane administrator buys, installs, upgrades and removes them in the console. Each purchase is bound to one control plane and delivered through an officially signed per-installation catalogue.

Plugin kindAfter paying or claimingWho confirms
Feature modules (official)Active straight away, menus appearNobody
Themes, rule packsWaiting for confirmation, installed on this control planeControl plane administrator
Page plugins, external servicesWaiting for confirmation, the administrator picks tenantsControl plane administrator
DNS, SMS, email, ICP, payment providersWaiting for confirmation, enabled after the contract test passesControl plane administrator

Tenants neither need to nor can confirm installs: once the administrator installs a plugin for a tenant it simply appears under that tenant's My plugins.

Turning it on

  1. Open Plugin market → Plugin store, search under Browse and open Details to check publisher, version, permissions (especially high-risk ones), price and the pages it adds.
  2. Click Get for free plugins; for paid ones choose a price and pay from your market balance or by QR code. Zero-amount orders (free, promotional, trial) complete inside the dialog.
  3. Under My plugins, click Install on anything "bought, waiting for you" and check the permissions. For page plugins and external services pick the tenants, or "All tenants (including future ones)".
  4. Enable it on its page (themes, rule packs, provider plugins…) and try it once with a real user's account.

Step-by-step help is in plugins.

Main settings

WhereWhat you can do
BrowseSearch, check details and permissions, get or buy
PurchasedLicences, expiry, auto-renewal; cancel subscriptions here
My pluginsConfirm installs, pick tenants, upgrade, disable, uninstall
Security noticesPlugin security notices to act on; mark them handled afterwards

Typical uses

  • A page plugin for every customer: choose "All tenants" when confirming, and tenants created later get it too.
  • VIP customers only: tick just those tenants, and change the selection at any time.
  • Moving servers: a plugin purchase can be rebound to the new control plane (by default once per rolling 30 days).

Limits and notes

  • Plugins never run in the control plane or node request path; rule packs are data interpreted by the core engine.
  • Uninstalling is not cancelling or a refund; orders and renewals are handled under Purchased.
  • The community edition registers a free installation identity before it can reach the plugin market; official items are not free for it and are sold at community prices.
  • Official modules, datasets and engine modules are published by the official publisher only.
  • The current community release does not yet include the "administrator confirms and picks tenants" flow.