Active context
The selected tenant controls what users can see, configure, search, share, and run.
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 this page covers
Separate tenant-scoped resources from deployment-scoped configuration and plugin installation.
Keep inbounds, source event history, chats, agents, scheduled jobs, groups, and service principals scoped to the active tenant.
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.
Admin boundaries
Deployment admins can switch broadly; tenant admins see non-default tenants where they hold tenant admin access.
Runtime safety
Inbounds, service principals, scheduled jobs, and workflow settings resolve inside the active tenant.
Related pages