Versions Compared

Old Version 10

changes.mady.by.user sneha.tripathi

Saved on

compared with

New Version Current

changes.mady.by.user sneha.tripathi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article deals with the following topics:

...

  1. Click Create Tenant on the Tenant Management page.

  2. On the Tenant details section, specify the following information:        
    1. Tenant name.
    2. The tenant which is used when logging into the Bot Builder.
    3. 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.
    4. 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).
  3. 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.

                                                      
    1. The bot name. This is used to identify the bot easily in the Bot Builder.
    2. Select the language that the bot can communicate with the user. Currently, the bot supports the following languages:
      • English
      • Chinese
      • Japanese
      • Spanish
      • Portuguese
    3. 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.
    4. 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).
    5. The domain name. The skills and attributes are associated with a domain.

    6. The unique identifier for the domain.    

      Info
      titleAWS 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.


  4.  Click Next to navigate to Tenant Administrator Details to define the tenant administrator information:
                    
                  
    1. The username of the tenant administrator.
    2. The email id of the tenant administrator.
    3. The password using which the tenant administrator can log in to the Bot Builder.
    4. Select the language from English or Chinese. This is the language to be used across the Bot Builder UI.
    5. The first name of the tenant administrator.
    6. The last name of the tenant administrator.    

  5. Click Next and select the additional capabilities for your Luma tenant.
     Image Added
    1. Select Provision Dashboard (Superset) to provision the Superset dashboard for your tenant. this is currently a BETA release.
    2. Select Provision Knowledge Management to provide Luma Knowledge to your Luma tenant. The Luma Knowledge Tenant will be provisioned automatically with the provided details. This also eliminates the need for a separate set of users and user sync between Luma and Luma Knowledge.
    3. Add any domain to be added to Luma Knowledge.
  6. 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:
    1. Enable Generative AI
    2. Add the following configurations:
      1. Azure Resource Name.
      2. Endpoint
      3. Deployment name for gpt-35-turbo
      4. Deployment name for gpt-35-turbo-16k
      5. API Key to connect to your Generative AI instance.
    3. Enable the features required for Luma Virtual Agent and Luma Knowledge.

      1. 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.

        1. Auto Phrase Generation for Skills enables the Skill developer to automatically generate user phrases that the end-user can use to request the skill.

        2. 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.

      2. 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.

        1. Keyword and Keypharses generation allows Luma to automatically extract relevant keywords from documents and data, making information retrieval faster and more effective.

        2. Automatic Summarization allows the automatic summary generation based on the artifact content.

        3. 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.

        4. Suggest Content on Knowledge Gap Resolution enables the curator to use Generative AI to build Knowledge to resolve unanswered user queries.

        5. Precise Answering enables Luma Knowledge to interpret and understand the user’s request and generate answers specific to the question.

  7. Click Next to navigate to Automation Integration, to enable automation for the tenant.


    To configure automation, follow the below steps:
    1. Enable Provision Automation.
    2. Select ‘Automation Version’ as V2
    3. Add Automation Tenant Identifier and Access Token retrieved from ITAS Tenant Provisioning API in ‘Tenant Secret Key’ fields in VSA.

    4. 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.


  8. Click Next to navigate to the Subscription tab.

...

Info
  1. A MSP Organisation, 
    1. can create a new Tenant only within available Tenant limits. The system will not allow Tenant creation if the allowed Tenant limit is reached. 
    2. can purchase a hybrid license, which is a combination of user-based licenses and sessions. Super Administrator  can create multiple Tenants and allocate these Licenses as per internal contracts. The system will not allow license allocation over and above the Permissible limit. 
  2. For the only User-based Licensing , Session information will be 0/0.
  3. For the only Session-based Licensing,
    1. Users' information will be 0/0.
    2. Sessions are incremented in packs of 500 by default. This can be manually incremented but not reduced below the consumption.


Subscription details

This section covers subscription information for the new tenant. Super admin uses this screen to define licensing type and Licenses for the Tenant. 

...

On the Tenant details screen, click on Edit Tenant to update Tenant details or subscription information. The screen is used by Super admins use the screen to add or remove allocated Licenses for a Tenant. You can also provision Superset Dashboard and Luma Knowledge for existing tenants. 

Follow the below steps to edit Tenant information:

  1. Search for a Tenant. Click on the record to open view Tenant details.
  2. Click Edit Tenant
  3. You can now update the below details:
    1. Tenant Details
      1. Tenant Name
      2. Description
      3. Status to mark the Tenant Active or Inactive
    2. Additional Capabilities: 
      1. Enable Dashboard (Superset) to provision Superset dashboard
      2. Enable Knowledge Management to provision Luma Knowledge automatically. (Note: This applies to Luma tenants provisioned after the unification of Luma and KM (Release 3.4). For tenants provisioned before the release, KM tenants should be created in the Luma Knowledge Superadmin portal.)
    3.  Subscription
      1.  Allocated Licenses.
        1. For License Type:  Users
          1. To allocate licenses, add the number of licenses in Users. License The license count cannot be more than the available Licenses exceed the licenses in the License Availability section. 
          2. To remove User Licenses, remove the number of Licenses in Users.  
        2.  For License Type:  Sessions
          1. To allocate licenses, add the number of Sessions in Sessions field. Session The session count cannot be more than exceed the available Sessions in the License Availability section.

          2. To remove licenses, remove the number of Sessions allocated in Sessions field. 

            Info

            If there are 60 Licenses available and the total number of licenses required is 100,  then enter the number of licenses as '100' and not 40.

            If there are 400 Licenses and 50 licenses to be removed, then enter the number of licenses as '350' and not 50.


    4. Contract Start Date and End Date
    5. Technical Email
    6. Billing Email
  4. Click Save. Tenant details will be updated.
  5. Changes to License subscription data will be available in the Licensing Transaction history for the Tenant Administrator. Refer to the article (Tenant settings→Subscription) for more details.

...