Install Plugins
Plugins add reviewed third-party capabilities to a workspace, such as mail, chat, identity, or data tooling. The catalog is served by the Soln control plane; the installation record, the configuration values, and the running plugin container all belong to your tenant.
This page covers installation, configuration, enabling, disabling, and uninstalling plugins in general. Feature-specific instructions are grouped by plugin type in the sidebar; use the guide for the installed plugin rather than assuming every plugin provides directory mapping or message push.
The Plugins → Enterprise Identity Plugins section currently covers DingTalk, Feishu, and WeCom. Start with the usage guide, then the list and action reference or provider-specific setup. Other plugin types can have different menus, configuration fields, and permissions.
Find The Plugin Catalog
- Open Integration → Apps
- Click the puzzle-piece button in the top bar. The page title switches to Plugins and the area below lists every published plugin, two per row, each with its icon, name, and summary
- Search by plugin name, summary, or plugin ID to narrow the list. Click the apps button to switch back to the app list
Install A Plugin
- Click
+on the plugin row. The button is disabled when your role cannot manage installations - Review the dialog: version, publish and update dates, provider, the permissions the release declares (allowed outbound hosts and runtime scopes), and the configuration fields
- Fill in the configuration. Fields marked as secrets are encrypted and stored in your tenant database; they are never sent to Soln
- Tick the permission consent and click Install. Installation and activation run in one step
- The plugin then appears in the app list with the Plugin tag. Open its card to reach the detail page
Manage An Installed Plugin
Open the plugin card in Apps to reach its detail page.
| Action | Where | Notes |
|---|---|---|
| Edit configuration | Detail page → Edit app | Leave a secret field empty to keep the stored value |
| Disable or enable | Detail page | Disabling stops the plugin and keeps its configuration |
| Uninstall | Detail page → Uninstall | Removes the plugin container, the resources the plugin created, and the tenant installation record |
Permissions And Versions
- A release declares its own permissions; the tenant console cannot widen them
- Installing a version asks for permission consent again whenever the declared permissions change
- The container image is pulled by digest, so a running plugin always matches the reviewed release
- Reaching the catalog needs the Apps page permission; installing and uninstalling additionally need Manage App Installations
Troubleshooting
| Symptom | What to check |
|---|---|
| The Plugins list is empty | The runtime must reach the control plane catalog, and at least one release must be published there |
+ is disabled | Your role needs Manage App Installations on the Apps page |
| Installation fails | Check the configuration values, and that the runtime host can reach the outbound hosts the release declares |
| The dialog cannot load the release | The exact plugin ID and version must still be published and not revoked |