Purpose and location
Create isolated tenants with plans, domains, limits and custom reporting fields.
Open Platform → Platform Tenants. The available controls depend on the active edition, module entitlement, role and tenant scope.
Before you start
Platform changes can affect every tenant. Confirm a recent verified backup, an audit owner and a maintenance window whenever the operation can restart services or change entitlement.
Capture the current value or export the affected records before a bulk or routing change. This gives the operator a precise comparison point and makes a supported transaction undo easier to assess.
Step-by-step workflow
Complete the steps in order. Do not combine an initial configuration with unrelated cleanup; small, attributable changes are easier to test and reverse.
- Choose the service plan and unique SIP domain.
- Set timezone, limits and tenant administrator.
- Add customer identification fields.
- Run isolation and first-call checks.
Field reference
Use the reference below while completing the form. Fields hidden by edition, module entitlement or role are intentionally unavailable to the signed-in user.
- Domain
- Unique SIP realm and tenant routing identity.
- Service plan
- Commercial and technical entitlement baseline.
- Limits
- Extensions, concurrent calls, storage and enabled modules.
- Custom fields
- Customer-defined metadata available to reports and integrations.
- Tenant administrator
- Initial delegated management identity.
Acceptance checks
A saved record is only the beginning of validation. Run every relevant check below and retain the call-session ID, time and result when telephony is involved.
- Open the new tenant through its hostname and confirm the organization domain is prefilled but editable on sign-in.
- Verify a tenant administrator cannot enumerate another tenant through the UI or API.
- Register two test extensions and complete a two-way internal call before handoff.
Common mistakes and safe recovery
If a check fails, stop adding changes. Restore the previous value or use a supported transaction undo, regenerate PBX configuration, then repeat the smallest failing test.
- Only multi-tenant editions can create additional tenant realms.
- A hostname must resolve to the PBX and have a trusted certificate before it is given to users.
What to include in a support case
Provide the tenant, module and object name, local time with timezone, expected result, observed result and the most recent successful state. For a call problem, include the logical call-session ID and the redacted SIP/SDP text diagnostic before requesting PCAP.
Never paste passwords, private keys, raw license payloads or unredacted customer media into a ticket. Use the one-time diagnostic grant and attachment controls when support requests additional evidence.