Tenant Management
Tenants are organizations using the platform. Create tenants, configure settings, enable/disable, and view stats. Tenants provide data isolation.
Tenant Management
Tenants are organizations that use the CrystalQore platform. Each tenant represents a distinct business, department, or customer with its own users, data, and configuration. Tenants provide complete data isolation—users only see and access data within their tenant.
Overview
In CrystalQore's multi-tenant architecture:
- One tenant = One organization (e.g., a company, agency, or department)
- Users belong to exactly one tenant
- Data (chat messages, contacts, files, call records, etc.) is scoped to the tenant
- PBX assignment — Each tenant is linked to a specific FusionPBX instance for calls and extensions
Tenant isolation ensures that users in Tenant A cannot see or access data from Tenant B. This is critical for hosted deployments serving multiple organizations.
Creating a Tenant
Navigate to Admin → Tenants — Open the tenant management page in the Superadmin panel.
Click Create Tenant — Start the tenant creation workflow.
Enter tenant name — Provide a descriptive name (e.g., "Acme Corp", "Sales Department").
Set domain — Specify the tenant's domain identifier used for routing and login.
Assign to PBX instance — Select the FusionPBX instance this tenant will use for calls and extensions.
Save — Create the tenant. You can configure additional settings after creation.
Required Fields
| Field | Description |
|---|---|
| Name | Display name for the tenant |
| Domain | Unique domain identifier |
| PBX Instance | The FusionPBX instance to connect |
Editing Tenant Settings
After creating a tenant, you can modify its configuration from the tenant detail or edit screen.
Session Settings
| Setting | Description | Default |
|---|---|---|
| Session timeout | How long users remain logged in before session expires (minutes) | Varies by deployment |
| Max users | Maximum number of user accounts allowed for this tenant | Unlimited (or tier-limited) |
General Settings
- Tenant name — Update the display name
- Domain — Change the domain identifier (may affect login URLs)
- PBX instance — Reassign to a different FusionPBX instance if needed
Changing the PBX instance may affect existing extensions and call routing. Ensure users are re-synced if you switch PBX instances.
Enabling and Disabling Tenants
You can disable a tenant without deleting it:
- Disabled tenants — Users cannot log in; existing data is preserved
- Enable — Restore access when ready
Use this when:
- Temporarily suspending an organization
- Migrating to a new tenant
- Handling billing or compliance issues
Viewing Tenant Statistics
The tenant management interface shows key metrics:
| Stat | Description |
|---|---|
| User count | Number of active user accounts in the tenant |
| Files | Total files stored (if applicable) |
| Last activity | Most recent user activity timestamp |
These stats help you monitor usage and plan capacity.
Tenant Isolation
Each tenant operates in complete isolation:
- Chat — Messages are visible only to users in the same tenant
- Contacts — Contact lists are tenant-scoped
- Call records — CDR data is filtered by tenant
- Files — File storage is tenant-scoped
- SMS — Numbers and conversations are tenant-assigned
Users in different tenants cannot see each other's presence, messages, or data unless explicitly shared through cross-tenant features (if enabled).
Best Practices
- Name tenants clearly — Use names that identify the organization or department
- Set appropriate session timeouts — Balance security with convenience (e.g., 30–60 minutes for standard use, shorter for high-security environments)
- Monitor user counts — Stay within your tier limits
- Disable before deleting — If removing a tenant, disable first to verify no active users, then proceed with data migration or deletion
Related Documentation
| Page | Description |
|---|---|
| User Management | Create users within tenants |
| PBX Instances | Configure FusionPBX connections |
| Role Permissions | Set up roles for tenant users |