Tenants
SYSTEM ADMIN
This view allows you to manage RTC Launcher tenants,
Add Tenant
SYSTEM ADMIN
To add a tenant click the 'Add Tenant' button and fill the fields of the opened 'Create Tenant' pop-up.
Fill the settings according to the table below.
Details
Field Name | Description |
---|---|
Name | Any unique within RTC Launcher tenant name. |
Company Name | Any company name. |
Base APIInternal URL | URL(s) of the APIused by the tenant.
|
Base APIExternal URL | URL of the API used by the tenant.
|
Header Key | Can be used to create a custom HTTP header for all the HTTP requests made by RTC Launcher Client. |
Header Value | The value of the 'Header Key' for custom header for all the HTTP requests made by RTC Launcher Client. The filed becomes enabled and mandatory only if 'Header Key' is set. |
Show Conversation Participants | Display the avatars and names of the conversation participants. |
Send Chat History | Enables or disable the possibility to send chat history to the additionally added participants of the conversation. |
Disable CORS | Disables CORS (Cross-Origin Resource Sharing) checking for APIrequests |
Enable auto-sync contacts on adding | Enables or disables auto-synchronization of added contact information with Active Directory. |
VCard Information enabled | Enables vCard (Virtual Contact File) for the contact belonging to a particular tenant, which can be viewed or downloaded. |
Disable RTC Launcher |
When checked, then shows the information for TENANT ADMINSITE ADMIN "WARNING: RTCLAUNCHER is currently disabled, please contact your system administrator" On Web-client side this:
|
Anonymization
Field Name | Description |
---|---|
Save Chat History | Unchecked by default. If checked chat messages will still be saved, but instead of original message will be the following string: 'data got anonymized'. |
Save Client IP | Unchecked by default. If unchecked client IP will be saved as '0.0.0.0' |
Modalities
Field Name | Description |
---|---|
IM | Check box enables the Instant Messaging modality for a specific tenant and defines if this modality will be available for the customers on RTC web-client. The option is enabled by default. |
Audio/Video | Check box enables the Audio/Video modalities for a specific tenant and defines if this modality will be available for the customers on RTC web-client. The option is enabled by default. |
Pexip Server | Setting is available if 'Pexip' is set as RTC implementation. Filed is mandatory and defines the Pexip ulr for the tenant. Generation of the group/contact div will now include also the URL for the PexipNode. |
Co-Browsing | Check box enables the co-browsing option for a specific tenant. The option is disabled by default. Setting is available if 'IM' or 'Audio/Video' is enabled. |
Max amount of concurrent co-browsing sessions | The maximum amount of concurrent co-browsing session allowed for the tenant. 2 sessions is set by default. An indicator of the total amount of system wide concurrent co-browsing sessions is shown. It's not allowed to set more than the system wide setting for the tenant. |
Overwrite System Settings | If unchecked, the System settings will be applied for the tenant. |
Surfly Server URL | The co-browsing server URL. The value is predefined (from System Settings) after saving. |
Surfly REST APIKey | A unique Surfly key for credentials. The value is predefined (from System Settings) after saving. |
Surfly Agent E-mail | The e-mail which is generated automatically after saving in format: name+@rtclauncher.sample |
Surfly Agent Password | The password of the agent. |
Surfly Client Key | Upon tenant creation, a new client on Surfly site is created. Client Key is automatically taken from Surfly after saving. |
Surfly Widget Key | Upon tenant creation, a new client on Surfly site is created. Widget Key is automatically taken from Surfly after saving. |
Callbacks
Visible only when enabled in RTC Launcher System Settings.
This feature requires a LUCS Service to be configured. The Service needs has "InboundOutbound" DirectionType selected →
See Call Distribution Policy settings in the LUCS Knowledgebase.
Field Name | Description |
---|---|
Callbacks Enabled | Check-box enabled the callback option for the Tenant |
Overwrite System Settings | If unchecked, the System settings will be applied for the tenant. |
LUCS APIURL | |
LUCS APIKey | Required field. LUCS APIKey in format: e36f5a98-2799-4d3a-931e-0deea1e639eb .
|
Test LUCS APIConnection | Button to check LUCS APIConnection. Upon click shows the successful or failed connection status label. |
Default User
Office 365 User | Allows to add O365 users
|
UPN |
UPN address of O365 user in format: firstname.lastname@domain.onmicrosoft.com |
First Name | First name of the default user. The user is automatically created as TENANT ADMIN |
Last Name | Last name of the default user. The user is automatically created as TENANT ADMIN |
User Name |
|
Password |
Can be edited on creation. |
Notes
- The 'Save' button remains disabled and when invalid or no values are provided
- Duplicate Tenants are not allowed
Edit Tenant
SYSTEM ADMIN
Select any tenant in the list and click the "Edit" button. Details are the same as when adding a new tenant.
Delete Tenant
SYSTEM ADMIN
To delete a tenant, simply select the entry and click on "Delete".→ A confirmation dialogue will appear.
Good to know
- After confirming deletion the tenant will be removed from the tenants list.
- Data will be kept and can be downloaded from database (Needs to be requested from a system administrator).
- When recreating a new tenant with exact the same name, a pop-up will remind you that previous data from the tenant will be reattached.
If the antecedent data is no longer needed, recreate a new tenant, with another name.