The CX system is designed as a multi-tenant platform, enabling you to effortlessly create and oversee multiple isolated tenants. Now, let's delve into the specifics of tenant configuration and management.
This comprehensive guide will walk you through the process of learning and mastering tenant management.
Create Tenant
To create a new tenant, select the left menu “Tenant” and click “
“.
1.1 Tenant Information
When creating a tenant, you can specify the tenant profile details as follows.
Company Information: Input the company information, such as Company Name, Company/Organization Size, and Country/Region.
Admin Information: Input the admin information, such as Admin Username, Admin Password, First Name and Email Address. Set the Site time zone and System language for the tenant.
A tenant's profile can be modified after the Tenant Admin logging into the Tenant. You can find more details from 9.2.1 Company General Information.
1.2 Email Notification
When creating a tenant, you can choose to allow a tenant administrator to access the system by logging in with the login information provided from an email, or by clicking the activation link in an email.
1.3 Tenant Domain (Optional)
If the end-user wishes to log in using their personalized sub-domain and make customizations on their tenant, a Tenant Domain setup is recommended.
The prerequisite for utilizing the tenant rebranding feature is to have the tenant domain enabled and valid.
Subsequently, you must integrate the customer's sub-domain, already configured on your DNS Provider’s portal, into your service. This enables customers to access their accounts directly through their unique sub-domain. For example, if your system's domain is: https://cx.example.com, and you have a customer named Company A, you can allocate a sub-domain like https://companya.example.com exclusively for this customer.
By utilizing such a sub-domain, the customer can personalize their tenant's branding and eliminate the necessity to enter a company name during the login process.
If the domain is in a Non-Secure state, the sub-domain configured to the tenant will not be operational.
1.4 Permission Setting
Upon completing the preceding steps, the next task involves configuring the permissions for your tenant. While there exists a default setting for tenant feature permissions, you have the flexibility to customize it according to your requirements.
1.5 Capability Settings
Upon completing the preceding steps, you need to set usage quotas for certain features of your tenant. Some of these functions have default quotas, you have the flexibility to customize them according to your requirements.
Basic
Maximum Agents: The number of Agents in the tenant can be restricted. Please note that this limit will correspond to the number of Agents authorized by the system license.
Disk Quota: Tenants' storage capacity can be restricted, and upon reaching the limit, expansion can be facilitated by the system administrator.
Advanced
Maximum Widgets: The number of widgets in the tenant can be restricted.
Maximum Channel Accounts: The number of connected channel accounts in the tenant can be restricted.
Maximum Workflow: The number of created workflows in the tenant can be restricted.
Maximum Audio/Video: The number of concurrent audio or video sessions in the tenant can be restricted.
Maximum Canned Messages: The number of added canned messages (Public and Private) in the tenant can be restricted.
Maximum Al Agents: The number of added AI Agents in the tenant can be restricted. Please note that this limit will correspond to the number of AI Agents authorized by the system license. System license limit the number of the tenant can use the feature of AI Agent. When the tenant quota for using Al Agent has reached the upper limit, this input inbox can not be edited.
Dataset Resources - Maximum Files: The number of files that the tenant can synchronize when using the dataset of Al functions can be restricted.
Dataset Resources - Maximum URLs: The number of URLs that the tenant can synchronize when using the dataset of Al functions can be restricted.
Add-on
Extra Workflow Triggers: Each tenant has 1,000 free trigger quotas. The number of extra workflow triggers in the tenant can be restricted. Please note that this limit will correspond to the number of Workflow Triggers authorized by the system license.
Whether there are related function quota settings in Advanced and Add-on depends on whether you have enabled the corresponding function permissions in the Permission Settings.
After this step, there will have a page to show the tenant information and capability settings.
Click “Save” to finalize the creation of the tenant.
2. Tenant Log
After the tenant has been created, you can click the button to view the operation logs of this tenant and the usage of tenant-related quotas.
Operation Logs: You can select to view different types of operation logs with a certain time range. If you want to download the operation logs, you can click the Download button to download.
Usage: The Usage shows the usage of each enabled functions in the tenant.
3. Deactivate Tenant
After creating the tenant, you have the option to activate or deactivate the tenant using the "Enable" switch button available in the tenant management interface.
When the tenant is disabled, agents under this tenant will not be able to log in to the CX system again until the system administrator reactivates the tenant. However, the data under the tenant will be preserved.
3. Delete Tenant
After the tenant has been created, you can force delete the tenant by click the "" button.
Note: Please exercise caution when utilizing this operation, as it will result in the complete deletion of tenant data, which cannot be recovered!
4. Manage The Permissions
An administrator has the ability to restrict the permissions of a tenant post-creation. This can be achieved by, for instance, disabling the tenant's access to features such as Contact, Help Center, and other functions.
For further details, kindly click on the Permission button associated with tenant Management.
