SDKs & infrastructure
Multi-tenancy
Multi-tenancy lets multiple customer or organizational contexts share infrastructure while keeping their resources, access rules and data appropriately separated.
Also found under: Tenant isolation, Application isolation, Workspace
How it works
Isolation requires explicit boundaries in storage, routing and authorization. A channel name alone does not establish which tenant may use it. Applications must derive tenant membership from trusted identity and enforce it when users request access to a project's or organization's events.
In a Pubb integration
Pubb isolates channel names by application, while plan capacity is shared across applications in a workspace. If your product represents several tenants inside one Pubb application, enforce those tenants' channel permissions in your backend.
Understand channel accessA practical example
Two Pubb applications may each use a notifications channel without sharing their audiences. Within one application, private-tenant-42 still needs an explicit tenant-membership check.