← Knowledge library

IT & integrations

Understand backend plugins and frontend apps

Extend MANSOQ through the correct server or user-interface extension contract.

Current source · source reviewed · 7 min read

Before you begin

1. Choose the extension surface

Backend plugins are Django applications managed by the plugin configuration. Frontend apps use module federation and manifests for UI routes, components, tabs and devices.

2. Pin compatible versions

The backend guide recommends including plugins during image build. Pin the plugin version and review its models, routes, migrations and dependencies against the current core release.

3. Configure through protected deployment settings

Plugin-specific values follow the documented configuration precedence. Use secret references/environment controls for credentials rather than copying illustrative inline secret examples into production.

4. Verify UI discovery

The frontend PluginEngine merges configured plugins and exposes declared routes/components. Confirm the intended app is enabled and compatible before teaching its functions as universal core features.

5. Test and document the boundary

Exercise permissions, upgrade behavior and failure handling in a test deployment. Document which features belong to the installed extension and which are present in core.

Backend routing

The pluggable-app guide describes plugin URLs under /api/plugin-name/. A particular installed plugin may define additional routes and requires its own contract.

Availability varies

A default core image is not proof that a specific integration is installed. The knowledge article for an optional app should state its installation/entitlement prerequisites.

Troubleshooting

An extension menu or route is absent

Check enabled apps, manifest compatibility, deployment configuration and the plugin’s supported version before troubleshooting the clinical record.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.