...
Name: Provide the Tenant Admin name which would be shown to the Tenant, when logged in, into the Virtual Agent application. The name could either be the name of the Tenant Admin or also could be the name of the organization. The name can contain alphanumeric characters.
Tenant: This The Tenant field is automatically populated when SuperAdmin enters the Tenant name. By default, it is the same as the Tenant name. required in the login process by the Tenant Admin.
Tenant ID: The Tenant ID is auto-generated by the system. This is used to identify the Tenant in the Backend.
Symbol: The Symbol is used to identify the bot Virtual Agent in the application. The symbol is prefixed in the code once generated which helps in easy identification of the botVirtual Agent. This needs to be unique. . The Symbol is automatically populated based on the name of the Tenant. The first 6 characters of the Tenant name is by default populated as the symbol.
Description: The description of the Tenant defines the Tenant details. It is used to identify the Tenant with details if SuperAdmin is not able to differentiate the Tenant on the list.
Step 3: The next step is to update the Default Bot and Domain details.
Bot Name, Bot Symbol: The Bot name and Bot symbol are pre-populated from the previous step.
Language: The language field defines the language in which the end-users of the Virtual Agent will interact. There is a varied list of languages supported which can be selected. Only 1 language can be selected as the Virtual Agent language.
Build and Publish Service: This defines the service required to Build and Publish the training data to the Virtual Agent so that the end-users can later use the Virtual Agent. Select the Build and Publish Service to be used as per your infrastructure size. This indicates where should Build and Publish serviceshould run for your tenant i.e AWS Sagemaker or Local Infrastructure.
Status: By default, the Status of the Virtual Agent will be active. The Status defines the availability of the Virtual Agent to the end-users.
Domain Name, Domain Identifier: The Domain Name and Domain Identifier will be loaded by default, based on the Bot Name.
Step 4: Next step is to provide the Tenant Administrator details which includes the following:
Username: SuperAdmin can assign a username using which the Tenant Administrator can log in to the application.
Email Address: The Email Address of the Tenant Administrator needs to be added here.
Password: The password of the Tenant Account needs to be entered here.
Language: The language in which the Bot Builder application will be displayed needs to be selected here. This can be changed again in the application after the Tenant Administrator logs in, to the application.
First Name: The first name of the Tenant Administrator will be entered here.
Last Name: The last name of the Tenant Administrator will be entered here.
Step 5: The second last step for Tenant Creation is the Automation Integration. This step allows SuperAdmin to share automation features with the newly created Tenant administrator. This step includes the details of the Domain, Organization, Email Address, Username, Password, Token, and the Automation Service provider Uuid(User ID).
Step 6: The last step for Tenant Creation is entering the Subscription details. Enter the contract details here as required in the respective fields. Add the License Type, Sessions purchased, Contract duration, and Contact Details. Contacts added here will receive notifications regarding Subscription, License usage, and renewal. The details of the amount and type of licenses that can be assigned to the Tenant Administrator is provided in the Subscription file in the backend.
For more details on the Licensing and Subscription, please refer Luma Virtual Agent Licensing Models
Step 7: Once the details are filled in, click on the Create button to complete Tenant Provisioning. The Tenant account is now successfully created. The Virtual Agent is now ready to be configured.