Trust tiers
OpsRabbit-owned and reviewed customer-owned plugins can be trusted differently from third-party or unknown code.
Enterprise
Plugins
Plugins add packaged tools, widgets, channel integrations, scheduled work, and customer-owned context collection. Plugin code is deployed by the host operator; the Admin UI is used for status, settings, enablement, runtime review, and trust-tier visibility.
What this page covers
Classify plugins as OpsRabbit-owned, customer-owned, third-party, or blocked before enabling runtime use.
Mount plugin code read-only, declare capabilities accurately, and review source, dependencies, and execution mode.
Use runner execution for third-party code when available and keep unreviewed capabilities blocked.
Operational detail
How OpsRabbit supports Plugins
Plugins add packaged tools, widgets, channel integrations, scheduled work, and customer-owned context collection. Plugin code is deployed by the host operator; the Admin UI is used for status, settings, enablement, runtime review, and trust-tier visibility.
Operational evidence
Plugins that prefetch evidence should show completed, partial, failed, or queued status clearly in widgets and run summaries.
Tenant behavior
Plugin installation is deployment-wide, but runtime calls run inside the active tenant and should store tenant-owned records by tenant id.
Related pages