Plugins
Overview
Practically every functional area of this system is a plugin — quotes, invoices, projects, warehousing, time tracking. This page manages them: install, enable, disable, uninstall.
This is not a side surface but the main switch for what the system can do. What is disabled here does not exist for anyone: no menu entries, no API endpoints, no background runs, no reporting. A disabled module is genuinely off, not merely hidden.
Core tasks
Survey what exists. The list shows each plugin's icon, name, trust level and status. The levels are First-party (from the vendor), Verified partner and Community — they tell you how far a package can be trusted before you install it.
Enable and disable. The change takes effect immediately and for every user.
Install from the marketplace. Marketplace opens the catalogue. Paid extensions not yet purchased lead to the vendor's checkout; purchased ones can be installed directly. If no marketplace is configured, the page says so and offers the upload instead.
Upload your own package. Upload plugin accepts a .zip package. Important: an uploaded plugin is installed disabled. You then enable it deliberately. Installation runs in the background; with larger packages the result only appears after refreshing the list.
Uninstall with a choice. When uninstalling you decide whether the plugin's data is kept or removed with it. Kept data is picked up again by a later reinstall. That choice is why uninstalling is not a one-way street — but also the point at which a slip becomes final.
Fields in detail
This page has no input mask — it shows modules and offers actions. What a module configures lives on its own settings page.
| Element | From | What it means |
|---|---|---|
| Module | installed modules | Name, icon and short description. |
| Version | module | Which state is installed. |
| State | module switch | On or off. |
| Action | What it does |
|---|---|
| Enable | Makes the module fully available: menu entries, permissions, background processing, API. |
| Disable | Hides it completely — pages, API and background processing. The data is untouched and returns on enabling. That is the difference from uninstalling. |
| Uninstall | Removes the module. You are asked whether the data should be kept or deleted. Kept means a later reinstall picks it up again. Deleted is deleted. |
A disabled module is really off. There is no half-open door: the API stops answering too, and an automation aimed at the module runs into nothing instead of quietly carrying on.
Settings & permissions
- Permission
platform.plugin.manage. Without it the manager, marketplace and detail page are
unreachable.
- Plugin modules do not appear among the feature flags. They are switched on and off here, not
under System & feature flags.
- Every plugin brings its own permissions. After enabling, they appear under
Roles & permissions — not granted to begin with.
- Disabling is fail-closed. In case of doubt a surface stays hidden rather than appearing and
then failing.
FAQ & troubleshooting
An uploaded plugin does not show up. Installation runs in the background. Refresh the list; if it still does not appear, the installation failed and the message names the reason.
After enabling, the new menu entries are missing. Check your permissions: a new plugin grants nobody authority automatically. The permissions have to be assigned to a role.
The marketplace is empty. Then it is not configured. The package upload route remains available.
We uninstalled with data deletion by mistake. The plugin's data is then gone. The recycle bin does not cover this — only a backup helps. Which is why the choice during uninstall deserves deliberate attention.