Enterprise

Multi-tenancy

Multi-tenancy keeps customer environments, source history, chats, agents, scheduled jobs, groups, service principals, runtime configuration, and resource grants isolated by active tenant. Deployment admins can switch tenants; tenant admins see only tenants where they have admin access.

What it covers

Three things it does for your team.

01

Separate tenant-scoped resources from deployment-scoped configuration and plugin installation.

02

Keep inbounds, source event history, chats, agents, scheduled jobs, groups, and service principals scoped to the active tenant.

03

Use tenant-local grants so one customer tenant cannot reveal another tenant's chats, agents, jobs, or source events.

Operational detail

How OpsRabbit supports Multi-tenancy

Multi-tenancy keeps customer environments, source history, chats, agents, scheduled jobs, groups, service principals, runtime configuration, and resource grants isolated by active tenant. Deployment admins can switch tenants; tenant admins see only tenants where they have admin access.

01

Active context

The selected tenant controls what users can see, configure, search, share, and run.

02

Admin boundaries

Deployment admins can switch broadly; tenant admins see non-default tenants where they hold tenant admin access.

03

Runtime safety

Inbounds, service principals, scheduled jobs, and workflow settings resolve inside the active tenant.

Get started

Your next incident is already on its way.

Bring one service and we’ll show you its root cause, in your environment, with your data, read‑only.

Pilot live in under 2 weeksROI within 30 daysDedicated support