Managing plugins

Enable, update and disable plugins for an organisation. For administrators; what a plugin is trusted with is in Plugins.

Before you start

Managing plugins requires the Admin or Owner role in the organisation (the settings:manage permission). Changes apply to every member of the organisation.

Open System settings > Plugins. Each plugin published on the platform is listed with its name, description and status:

Status	Meaning
Not enabled. Latest version x	Available, not running for this organisation.
Enabled, version x	Running for every member, at version x.
Enabled, version x - not loaded: built for another app version	Version x is not compatible with the current application, so it does not run. Update it, or disable it.
No version works with this app yet	No published version is compatible with the current application. It cannot be enabled.

When no plugin is published on the platform, the page says No plugins are available yet.

Enable a plugin

1. Find the plugin and choose Enable. The most recently published compatible version is enabled.
2. Choose Reload now in the notice at the top, or reload the application.

Other members get the plugin the next time they load the application. What the plugin adds, such as a main-menu destination, appears for everyone whose role allows it.

Update a plugin

When a compatible version is published after the enabled one, the plugin shows Update to with that version. Choose it, then reload.

Updating is always a deliberate choice. A new version never replaces the enabled one by itself.

Go back to an earlier version

Not possible from the settings. Enable and Update to always offer the most recently published compatible version, and no other version can be picked. If a new version misbehaves:

1. Choose Disable and reload, so the plugin stops running.
2. Ask the plugin's publisher for a fixed version. A publisher undoes a release by publishing the earlier code under a new version number, which then appears under Update to or Enable.

Disable a plugin

Choose Disable, then reload. What the plugin added disappears for every member on their next load. Disabling deletes nothing: anything the plugin stored stays where it is, and enabling it again picks it up.

When a plugin does not appear

1. Reload the application. Plugin changes take effect on the next load, for each user separately.
2. Check its status in System settings > Plugins. If it says not loaded: built for another app version, choose Update to, or disable it until a compatible version is published.
3. Check the role. A plugin may offer some of what it adds only to members with a given role or permission. Sign in as one to compare.
4. Read the reason in the browser. Open the browser's developer console, reload, and find the line that starts [plugins] followed by the plugin's id. It ends in loaded, or says skipped or failed and why. Send that line to the plugin's publisher, or, if it mentions an integrity digest, to the platform operator.

Related pages

• Plugins: how plugins are published, loaded and trusted.
• Plugin reference: what each [plugins] console message means.