Plugin activation
Every pluggable component in LEMA Chat — widgets, integrations, connection providers, model catalogues — follows one standard plugin architecture (ADR-0011). A single registry, one credential story, and consistent activation semantics govern them all.
Hierarchical activation
Plugins are activated hierarchically:
- Platform — a SuperAdmin activates (or deactivates) a component plugin for the whole deployment.
- Workspace — within what the platform allows, a workspace can enable the plugins it wants.
If a plugin is disabled at the platform level, it isn't available to any workspace; the disabled state is surfaced through the access-control and dispatch layers so a disabled component simply doesn't resolve.
The versions table
The Settings page shows the platform's registered plugins and component versions, so you can see exactly what's installed and active.
Coming-soon plugins
Some catalogue tiles are registered placeholders with no working adapter yet — notably the hosting providers (Railway, Fly.io, Vercel, Netlify, Cloudflare Pages, Render) and several voice providers beyond Retell and VAPI. They appear so the catalogue is complete, but activating one does nothing until its adapter ships. See Integrations & plugins for the current status table.
Why one architecture
Before ADR-0011, each component kind was on track to grow its own registry, its own credential handling, and its own on/off semantics. Consolidating them means an operator learns activation once and it works the same for every present and future component kind.