PBX — Multi-Tenant Management
Tenant Architecture
The SipLive PBX is a true multi-tenant system. Each tenant is a logically isolated customer with their own extensions, DIDs, voicemail, call routing, and feature modules. Tenants share the underlying Asterisk engine and database but cannot access each other's data or calls.
Creating a Tenant
- Go to Tenants → Create Tenant.
- Enter the Company Name, Tenant Code (short unique ID, e.g.,
acme), and optional domain. - Select a Package (defines extension limits and feature set).
- Set a Theme Color for the branded portal.
- Save — the tenant record and default dialplan context are created automatically.
Tenant Code
The tenant code prefixes all PJSIP objects (acme-1001), dialplan contexts (acme-internal), and database rows. It cannot be changed after creation without a database migration. Choose carefully — lowercase, alphanumeric, 3–12 characters.
Module Permissions
- Voicemail — Voicemail-to-email, visual voicemail
- SMS / Messaging — Two-way SMS via DIDs
- Contact Center — Agent presence, queue management
- Call Recording — On-demand or automatic recording
- CDR / Reports — Call detail record access
- Softphone — WebRTC browser calling
- Mobile Push — iOS/Android push for inbound calls
Tenant Branding
Each tenant can have a custom logo and color theme on their portal login page. Upload logos under Tenants → [Tenant] → Branding. PNG or SVG, max 500 KB.
Tenant Portal Users (Roles)
- Tenant Admin — Manages extensions, DIDs, and routing for their tenant.
- Agent — Views CDRs, manages own extension, uses softphone.
- User — Read-only access to own extension and voicemail.
Provisioning via API
Tenants can be provisioned programmatically via POST /api/v1/tenants. The order fulfillment workflow creates the tenant, assigns the package, and generates the installer ZIP when an order is pushed from the admin portal.