SIGNALS Docs

Plugins

Install, enable, disable, update, configure, and inspect plugins from the Plugin Manager.

Overview

The Plugin Manager is the operator surface for installed and discovered plugins. It installs uploaded or discovered packages, enables and disables them, applies an available update, removes them, and exposes their operational details.

Where it lives

Route: /plugins (plugins.index; admin/settings/plugins redirects here)

Open Extensions → Plugins, search Plugins in the command palette, or go directly to /plugins. Requires owner access or an administrator with plugins.manage.

Manage plugin lifecycle

Action Behaviour
Install Install a discovered plugin package.
Upload Add a plugin from a .zip archive, then install it from the discovered list.
Enable / disable Turn an installed plugin's integrations on or off. The manager shows the resulting status.
Update Apply a discovered newer version when the card shows Update available.
Uninstall Remove the plugin after confirmation; the confirmation warns that plugin tables and settings will be removed.
Reload Plugins Refresh discovery so newly available packages and versions appear.

On Signals Cloud, archive upload is unavailable; separately deployed plugin packages can still be installed or enabled from the Plugin Manager. Enabled state and runtime registration are isolated per tenant.

Settings, permissions, and health

Expand Details to inspect the plugin overview and recorded activity. The available tabs reflect what the plugin declares: permissions, data access, hooks, UI slots, settings and tables. Open Settings opens the settings form when the plugin publishes settings.

An enabled plugin is marked Healthy when it has neither a recorded hook failure nor a startup failure. A registration or boot failure shows Didn't start, with its stage and diagnostic details; the stored enabled state can remain unchanged while its runtime registrations are rolled back. Use php artisan signals:plugin check vendor/name --wire --json to investigate registration, and review the logs for boot() failures. Runtime failures still use the shared consecutive-failure counter and auto-disable threshold. See Troubleshooting.

Plugin management requires owner access or an administrator with plugins.manage. Uploading and installing requires owner access or an administrator with plugins.install. Self-hosted administrators may upload unsigned ZIP archives; Signals Cloud refuses ZIP uploads. Operations Manager has neither permission. Treat permission and data-access declarations as part of the review before enabling or updating a plugin.

The SDK guide owns package structure, manifests and development tooling; those topics are intentionally not repeated here.