This article deals with the following topics:
...
- Click Create Tenant on the Tenant Management page.
- On the Tenant details section, specify the following information:
- Tenant name.
- The tenant which is used when logging into the Bot Builder.
- The tenant ID which must fall in the range from 1000 to 999999999. If you do not specify the tenant id, a unique id is auto-generated after the tenant is created.
- Specify the symbol. This symbol is used internally to identify the tenant in the database. The maximum number of characters is limited to 6. The allowed characters are A-Z, a-z, 0-9,_. Values must start with a letter and must not end with _(underscore).
- Click on Next to add Default Bot & Domain Details. By default, the data is automatically populated based on the Tenant Details section. However, you can configure the bot and domain details, if required.
- The bot name. This is used to identify the bot easily in the Bot Builder.
- Select the language that the bot can communicate with the user. Currently, the bot supports the following languages:
- English
- Chinese
- Japanese
- Spanish
- Portuguese
- Build and Publish Service: The Service assigned to the Tenant is required to build and publish the training data to the bot. It could be AWS Sagemaker or RASA Adapter.
- The bot symbol. This symbol is used internally to identify the bot in the database. The maximum number of characters is limited to 6. The allowed characters are A-Z, a-z, 0-9,_. Values must start with a letter and must not end with _(underscore).
- The domain name. The skills and attributes are associated with a domain.
The unique identifier for the domain.
Info title AWS Sagemaker - RASA adapter runs the Build and Publish process on the Local infrastructure.
- Run time performance is better on AWS SageMaker.
- Customers must subscribe to AWS services and configure AWS SageMaker for On-Premise implementations.
- Click Next to navigate to Tenant Administrator Details to define the tenant administrator information:
- The username of the tenant administrator.
- The email id of the tenant administrator.
- The password using which the tenant administrator can log in to the Bot Builder.
- Select the language from English or Chinese. This is the language to be used across the Bot Builder UI.
- The first name of the tenant administrator.
- The last name of the tenant administrator.
- Click Next to navigate to Generative AI Configuration to enable Azure Open AI for the tenant. The configuration should be enabled if you want to enable Generative AI capabilities for your tenant.
To enable Generative AI, follow the below steps:- Enable Generative AI
- Add the following configurations:
- Azure Resource Name.
- Endpoint
- Deployment name for gpt-35-turbo
- Deployment name for gpt-35-turbo-16k
- API Key to connect to your Generative AI instance.
- Azure Resource Name.
- Enable the features required for Luma Virtual Agent and Luma Knowledge.
Under ‘Features available in Virtual Agent’ you can view the Generative AI Features used in Virtual Agent. The skill developer uses these features to integrate Generative AI into skill building and execution seamlessly.
Auto Phrase Generation for Skills enables the Skill developer to automatically generate user phrases that the end-user can use to request the skill.
AI Task in Skill Conversation Flow enables the skill developer to add an AI Task as a step in a skill. The conversation step, AI Task, can be added to the canvas or is executed only if the feature is available for your tenant.
Under ‘Features available in Knowledge,’ you can view the functionalities available in Luma Knowledge. Using these capabilities, Luma can adeptly curate and oversee your Knowledge Articles. For more information, refer to Integrating Advanced Language Models.
Keyword and Keypharses generation allows Luma to automatically extract relevant keywords from documents and data, making information retrieval faster and more effective.
Automatic Summarization allows the automatic summary generation based on the artifact content.
Question and Answer generation(FAQ) generates Questions and corresponding answers, which can be quickly presented to the user, reducing the time spent on answering customer inquiries.
Suggest Content on Knowledge Gap Resolution enables the curator to use Generative AI to build Knowledge to resolve unanswered user queries.
Precise Answering enables Luma Knowledge to interpret and understand the user’s request and generate answers specific to the question.
- Click Next to navigate to Automation Integration, to enable automation for the tenant.
To configure automation, follow the below steps:- Enable Provision Automation.
- Select ‘Automation Version’ as V2
- Add Automation Tenant Identifier and Access Token retrieved from ITAS Tenant Provisioning API in ‘Tenant Secret Key’ fields in VSA.
Click Save.
Info The above information is generated through ITAS Tenant Provisioning API. Contact the Serviceaide support team to create your tenant in ITAS and obtain the details required to enable automation for your tenant in Luma VA.
- Click Next to navigate to the Subscription tab.
The screen allows super admin to distribute licenses as per the organization's contract so that they can use the Luma application based on the Llicense type.
License entitlement details
This section provides License entitlement details to Super Administrator. New Tenant creation or License distribution is allowed based on the availability of licenses. The information is populated from the License file registered for the Organisation and MSPs and is non-editable.
...
- Contract start date
- Contract end date
- Serviceaide Accounting email idID: Serviceaide Account Manager's contact mail id ID for all license-related communication/notifications
License Consumption
This section holds limited information regarding allocated vs available limited information. 'Available limits' are populated from the License file, and 'allocated details' are calculated from the Tenants created and Licenses allocated.
...
Info |
---|
|
...
- License Type: Select the license type for the tenant based on the contract.
For User-Based Licensing:
- Select 'Users' as License Type.
- Add User Licenses to be allocated to the Tenant.
For Session-Based Licensing:
- Select 'Sessions per month' as License Type.
- Add Sessions to be allocated to the Tenant.
- The session duration will be populated based on the license file.
- Contract: Add Contract start date and Contract End date. The dates should be within the contract start and end date as available in Licensing Information.
- Technical Email: License Consumption and Alerts will be sent to this mail ID.
- Billing Email : License Consumption and Billing details will be sent to this mail ID.
Info |
---|
|
6. Click Create. A new Tenant with the above-specified details will be created. Once the tenant is created, the new tenant is displayed in the Tenant Management list. The tenant administrator can now login log in to the Bot Builder with the given credentials.
Info |
---|
Please ensure that the correct Subscription subscription type is selected while Tenant during tenant creation. Once Tenant is created created, License Type and Contract duration cannot be updated. |
View Tenant Details
To view the tenant details, select one of the tenants Select one tenant from the Tenant Management list to view the tenant details.
Tenant Details
Tenant Details the section on the page displays the following information:
...
- Name: The name of the tenant.
- Tenant ID: This is the unique Tenant identifier, which is automatically generated after the tenant is successfully created. You can also specify the ID based on your requirement requirements when creating the tenant. The Tenant ID must be in the range of 1000 to 999999999.
- Tenant: This is the name that is used when logging into the Bot Builder interface.
- Tenant External ID: This is the unique the the identifier used by external applications to communicate with this Tenant.
- Status: Status of the tenant, such as Active or Inactive.
- Tenant Description: Description of the tenant.
...