KLapper Admin User Guide

KLapper Admin User Guide



KLapper Admin User Guide

V1.0






Introduction 


This guide details all features available to an Admin in KLapper, a comprehensive and advanced platform for building and managing intelligent assistants. KLapper is designed to be both intuitive and flexible, catering to users with varying levels of technical expertise. The platform supports extensive customization, enabling users to tailor the behavior, appearance, and functionality of their assistants to meet specific needs. Additionally, it offers seamless integration with a wide range of services, enhancing the capabilities and reach of the assistants created. 

KLapper provides a user-friendly interface that guides users through the process of creating and managing assistants. Key features include: 

  1. Assistant Builder: The platform allows users to create new assistants from scratch, starting with a basic template that can be customized extensively. Users can define the assistant's purpose, name, and description. 
  2. Knowledge Builder: Users can build a comprehensive knowledge base by uploading documents, providing URLs, or linking to external data sources. The platform supports various file formats and ensures that the knowledge base is easily searchable and updatable. 
  3. Skill Builder: The Skill Dashboard feature provides efficient skill management and integration through a user-friendly interface. This will allow users to add, edit, and manage various skill builders. Users can configure skill-specific properties, select knowledge bases, and perform essential actions such as editing, saving, deleting, and publishing components effortlessly. 
  4. Assistant Customization: KLapper offers a range of customization options, including the ability to modify the assistant's appearance, define its personality, and set specific behaviors. Users can also configure response settings to ensure the assistant interacts effectively with end-users. 
  5. Integration Capabilities: The platform supports integration with popular services such as SharePoint, NetDocuments, and iManage. This allows assistants to access and retrieve information from these services, enhancing their utility and efficiency. 
  6. Deployment: Once the assistant is configured, it can be deployed across various channels, including websites, messaging platforms, and mobile apps. The KLapper Admin Center provides tools for monitoring and managing the assistant's performance, ensuring it continues to meet user needs over time. 

This document will provide the admin user a guide to navigate, create, customize, and deploy assistants using KLapper Assistant and Skill Builder. It will cover all aspects of the platform, from initial setup to advanced customization and integration, ensuring users have the knowledge and tools needed to build effective and intelligent assistants. 



Login

  1. Open the KLapper Builder Tool 
  2. Navigate to the KLapper Assistant Builder application
  3. Enter Credentials
  4. Ensure the email address is registered and verified within the KLapper system. 
  5. Complete any additional security steps if prompted, such as entering a verification code sent to your email. 
  6. Click the “Login” button prominently displayed on the main screen. 
  7. New users will be prompted to contact portal administrator to activate to use this platform. 
A screenshot of a login pageDescription automatically generated


Assistant Navigation Header

To assist users in navigating through different sections or features of this application with clear, intuitive access to important functions enhancing overall user experience and efficiency.


Header Navigation

  1. KLapper Version 
    View the current version of KLapper, including updates and enhancements, to stay informed about the latest features and improvements. 

    • Assistant Builder 
      Easily create and configure your chatbot’s personality, functions, and responses with the Assistant Builder tool, tailoring it to your business needs. 

    • Skill Builder 
      Develop specific skills and responses for your assistant, customizing how it interacts with users based on different scenarios and requirements. 

    • Global Settings 
      Adjust platform-wide configurations, such as language preferences, time zones, and user permissions, through the Global Settings menu for streamlined operations. 

    • Reports 
      Access detailed analytics and performance reports that track interactions, user engagement, and assistant efficiency to optimize and enhance the chatbot’s capabilities. 

    • Account Details 
      Manage your personal and business account information, including access to0 user guides, and user access, within the Account Details section. 



    • User Guide 
      Access the comprehensive User Guide to understand the platform’s features, tools, and functionalities, with step-by-step instructions for optimal use. 

    • Policy 
      Review the platform’s policies, including privacy, data security, and usage terms, to ensure compliance and informed decision-making. 

    • Send Feedback 
      Provide feedback directly to the development team, sharing your suggestions, concerns, or issues to help improve the platform’s performance and user experience. 


System updates

  1. Latest version updates can be accessed through the Global Settings
  2. Click on Update version button to update the latest version of the software
  3. Covered in detail here Updating KLapper

Global Settings

Global settings allow administrators to add, delete, give permissions and edit user settings straight from the KLapper Admin Center.  They also allow connections to be made to iManage, NetDocuments, SharePoint and Microsoft Azure.  Lastly, they are used to change your Open AI System Information.



Users


Features

  1. Click on Add button, a modal popup will appear where you can type in to add a user
  2. Click on the bin icon to delete user
  3. Click on the pen icon to be able to edit the role and to disable access of the user
  4. Once done click on the save icon to save updates or ‘x’ to exit without saving

Note: Once admin reaches the user limit based on the license, an error is thrown when clicking the Add button or activating a disabled user. In this case, please contact license@klapper.ai 

General


Features

  1. Welcome Message
  1.     User can add a message here that is displayed as the first message sent from the bot when a new conversation is started
  1. Builder API URL
  1.     Links to the Builder API that is provisioned when the app is deployed, this should automatically be filled in
  1. Framework URL
  1.     Links to the Framework that is provisioned when the app is deployed, this should automatically be filled in
  1. File Manager URL
  1.     Links to the File Manager URL that is provisioned when the app is deployed, this should automatically be filled in
  1. KLapper License Id
  1.     This is the KLapper License Id that is generated when the app is provisioned


Microsoft Azure Open AI Details

Features

  1. API URL
  1.     This links to the API URL for the Azure OpenAI deployment used for KLapper
  1. API Key
  1.     Key generated for accessing the OpenAI API
  1. Deployment Name
  1.     Name of the Azure OpenAI deployment
  1. API Version
  1.     Version of the Azure OpenAI deployment that is being used

Open AI System Information


Features

  1. Intent Identifier
  2. JSON To Adaptive Card
  3. JSON To Text
  4. JSON Convert Output Prompt

Microsoft Azure App Details


Features

Administrators are required to have the following details to connect their Azure App to the KLapper environment. 
  1. Tenant ID 
  2. Client ID 
  3. Client Password 
  4. Resource Group Name 
  5. Subscription ID 

NetDocuments


How to add NetDocuments connection

Step 1:

Open your NetDocuments site and navigate to the admin page for your repository

Step 2:

Make note of the Repository ID within the URL


Step 3:


Head to https://support.netdocuments.com and log in. Click App Registration and choose App

A screenshot of a computer Description automatically generated

A screen shot of a computer Description automatically generated


Step 4:

If creating a new app, choose REST and add the Redirect URL from KLapper Builder Global Settings, under NetDocuments. Now press Create

Step 5:
Once returned to the main App Registration page, you can edit your newly created application to get the Client Id and Client Secret, or make any post creation changes. To edit an application, click the far-right control handle and select “Edit” in the menu.

A screenshot of a computer Description automatically generated

A screenshot of a phone Description automatically generated
Step 6:
Next, enter the Input Parameters under NetDocuments in the new settings information
API URL: (Varies by region)
  1. US Region - https://api.vault.netvoyage.com/v2
  2. EU Region - https://api.eu.netdocuments.com/v2
  3. DE Region - https://api.de.netdocuments.com/v2
  4. AU Region - https://api.au.netdocuments.com/v2
  5. CAN Region - https://api.can.netdocuments.com/v2
Web URL: (Varies by region)
  1. US Region - https://vault.netvoyage.com/neWeb2
  2. EU Region - https://eu.netdocuments.com/neWeb2
  3. DE Region - https://de.netdocuments.com/neWeb2
  4. AU Region - https://au.netdocuments.com/neWeb2
  5. CAN Region - https://can.netdocuments.com/neWeb2
Client ID: Client ID from the app created within support.netdocuments
Client Secret: Client Secret from the app created within support.netdocuments
Repository ID: The Repository ID that was noted in the Admin URL

Step 7:
Configure the repository service account within NetDocuments.

Service accounts are not allowed to log in to the NetDocuments portal.
The service account needs to be added to the admin group or directly added to cabinets with VESA permission. 


  2. Log in to NetDocuments Admin account and click the log in username. You will be able to see the “Admin” option. On hover, it will show the Cabinets under Repository.
  1. Clicking on the Repository or Cabinet will navigate you to the “Admin” page.
  2. Click on the Options Menu and then click on Users & Groups
  3. This action will navigate you to the page below. In that page you can select the Service Accounts tab. On clicking the CREATE button, you will be able to add the Service Account.
  1. After clicking on the CREATE Service Account button, it will open a popup. Please enter the email id and click CREATE button.

  1. This will lead to another popup window for mapping the Client id. Map the Client ID and press Save

iManage

Administrators can connect their iManage environment to the KLapper environment by filling out the iManage section in the global settings 

How to add iManage connection (On-Premises)

Step 1:

Go to your iManage homepage and click your profile icon in the top-right, then select Control Center

A screenshot of a computerDescription automatically generated


Step 2:

Click Applications from the left column and select “Add Application”

Step 3:

Select Configure Manually

A screenshot of a computerDescription automatically generated

Configure the application with these fields specifically as shown below and fill in the remaining fields

    API Key: Client ID (From Azure API)

    API Secret: Client Secret (From Azure API)




Step 4:

Click Authentication and insert the Redirect URL from KLapper Builder

Select to Enable Refresh Token

A screenshot of a computerDescription automatically generated

Click fill out the rest of the fields and click Finish

Step 5:

Please open the Klapper Builder page and go to the global settings.

Next, enter the Input Parameters under iManage in the new settings information

  1. Client ID: Value copied from Azure
  2. Client Secret: Value copied from Azure
  3. Host Name: Name of domain for iManage
  4. User Name: Encrypted User Name
  5. Password: Encrypted Password

How to add iManage connection (Cloud)

Step 1:

Go to your iManage homepage and click your profile icon in the top-right, then select Control Center


Step 2:

Send a request to iManage support to add a new application

    Include redirect URL from the KLapper Builder Global Settings, under iManage

Step 3:

Once the Application is created by support, configure the application

    Allow Refresh Tokens: Yes

    Client ID: Client ID (From Azure API)

    API Secret: Client Secret (From Azure API)

Step 4:

Click Authentication and insert the Redirect URL from KLapper Builder

Select to Enable Refresh Token

Proceed through other settings and press Finish

Click Finish

Step 5:

Please open the Klapper Builder page and go to the global settings.

Next, enter the Input Parameters under iManage in the new settings information

  1. Client ID: Value copied from earlier
  2. Client Secret: Value copied from earlier
  3. Host Name: Name of domain for iManage
  4. User Name: Encrypted User Name
  5. Password: Encrypted Password

SharePoint

How to add SharePoint Connection

Step 1:

You need to register the App in the Azure portal. If it is already registered, please check the configurations. Azure Portal URL : https://portal.azure.com

After accessing the Azure portal, navigate to “App registrations” under Azure Services.

Step 2:

Open the “App registration” page and click “New registration” 

Step 3:

Upon opening the registration page, enter the following information.

  1. Name – Enter the App Name 
  2. Account Type - Choose the (“Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)”) option.
  3. Redirect URI – Web -> Kindly locate the redirect URL within the Klapper builder site, under Global Settings in the Sharepoint Tab.

Once you click the "Register" button at the bottom of the page, it will be complete.



Step 4:

Navigate to Manage -> API permissions and add the required permissions:

Microsoft Graph (Delegated):

Calendars.ReadWrite

Sites.Read.All

User.Read

SharePoint (Delegated):

    AllSites.Read

    Sites.Search.All

Refer to the snapshot below for guidance.

After adding permissions, click the "Grant admin consent" link.

Step 5:

After adding permissions, create the secret key under Manage -> Certificates & secrets.

A screenshot of a computerDescription automatically generated

A “New client secret” needs to be generated. Please fill the below options.

Description - Need to enter the description secret key

Expires – Choose the option of secret key expires

After generating the secret key, make sure to record the value in a notepad or another secure location. 



Step 6:

Please also note down the client ID and tenant ID, which can be found in the overview section.



Step 7:

After the setup is finished, you need to open the SharePoint admin portal. In the URL below, replace your SharePoint tenant name.

https://${tenant name}-admin.sharepoint.com/_layouts/15/appinv.aspx

Enter your Azure app registration client ID into the "App Id" field and click "Lookup". The Title and redirect URL will be populated automatically. To complete the App permissions XML, use the following and need to fill the App domain.

<AppPermissionRequests AllowAppOnlyPolicy="true"> 

    <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="FullControl"/> 

</AppPermissionRequests>

After completing the form, click the “Create” button. This will take you to the “trust page,” where you should click the “Trust It” button.


Step 8:


Please open the Klapper Builder page and go to the global settings.

Next, enter the Input Parameters under SharePoint in the new settings information.

  1. Tenant Name: Tenant’s Name
  2. Tenant URL:  Tenant site URL
  3. Tenant ID: Tenant id, you copied from azure App registrations
  4. Client ID: Client id, you copied from azure App registrations
  5. Client Secret: Client secret, you copied from azure App registrations

Step 9:

After clicking "Test Connection" and verifying it, press the "Add Tenant" button.

KLapper Update History

This is where the admin can see the version history and date updated on by the Admin user

Features

  1. Version Number
  2. Status
  3. Error 
  4. Started On
  5. Ended On
  6. Created On
  7. Created By

Updating KLapper


Go to global settings


Click update and initiate (By default, this update will run during afterhours)



To start the WebJob process manually, go to builder UI app service, click on WebJobs and press Run

Assistant Builder

The Assistant Builder enables the admin user to create, customize and train assistants that they can then deploy to various environments

Steps to Create a New Assistant


Add a Title 

The first step in creating an Assistant by giving it a name

Description

Add a description that provides a purpose that the assistant is going to serve

Create Assistant


Click on Create Assistant to activate the assistant

Add Skills 

Select from an existing set of skills (a maximum of 5 can be added)



List of skills that KLapper ships with:

Who Is

    Will give details about people from the provided SQL

Create Meeting

    Will create a meeting using KLapper’s API

Timesheet

    Will add entries to a Harvest timesheet

Create Service Now

    Creates a new support ticket for the user’s issue

Get Service Now Incident

    Gets information on service tickets

Alerts

    Details all alerts for the signed in user

Matter

    Provides details about a matter that the user sends a query about

Preview Assistant

The Preview Assistant enables the admin user to test and train the Assistant in its responses before deploying the assistant into the different applications for the end users



Click the ‘Preview Assistant’ which launches the Assistant bot 

Chat box

  1. Attach- ability to attach documents
  2. Suggestions -  prompts that the user can use to prompt the assistant to act
    1. Create Document
    2. Compare Document
    3. Review Document
    4. Review NetDocuments Content
    5. Review iManage Content
    6. Review SharePoint Content
    7. Switch to Documents
    8. Stop
    9. Exit
  3. Send
  4. Version History
  5. Expand
  6. Start New Conversation
  7. Minimize

Chat message

  1. Like
  2. Dislike
  3. Voice 
  4. Leave comment on response
  5. Share response
  6. Report legal issue


Assistant Settings

This is where the admin can set up all the parameters for the assistant bots to not only connect to multiple data sources but also the look and feel of the bot.



Assistant Header & Bubble 

(These all change the appearance of the assistant)
  1. Header Text Color
    1.     The color of the Bot Name in the assistant
  2. Header Background Color
    1.     The background color of the header in the assistant
  3. Header Button Background Color
    1.     The background color of the buttons when they are hovered in the header
  4. Header Icon Color
    1.     The color of the header icons
  5. Assistant Background Color
    1.     The background color of the assistant

Assistant Bubble 

(These all change the appearance of the assistant bubbles)

  1. Assistant Bubble Border Color
  1.     The color border around the text boxes
  1. Assistant Bubble Background Color
  1.     The background color of the text boxes in the assistant
  1.    Assistant Bubble Text Color
  1.    The font color within the text boxes in the assistant

User Bubble

  1. User Bubble Border Color
    The color border around the user’s text boxes 
  1. User Bubble Background Color
    The background color of the user’s text boxes
  1. User Bubble Text Color
    The font color within the user’s text boxes

Assistant Icon

  1. Color
Changes the picture of the assistant icon
  1. Outline 
The Teams requires outline picture of the assistant icon

Assistant Settings

  1. Welcome Message
    This determines the unique welcome message for this assistant. This message sends at the beginning of a new conversation
  1. Maximize Button
    Determines whether the maximize button will appear on the assistant
  1. Restart Conversation Button
    Determines whether the restart conversation button will appear on the assistant
  1. Settings Button
    Determines whether the settings button will appear on the assistant
  1. Feedback Button

    Determines whether the feedback button will appear on the assistant

  1. Show NetDocuments
    Determines whether NetDocuments will be configurable for this assistant’s Knowledge Base or from within the Assistant
  1. Show iManage
    Determines whether iManage will be configurable for this assistant’s Knowledge Base or from within the Assistant
  1. Show SharePoint
      Determines whether SharePoint will be configurable for this assistant’s Knowledge Base or from within the Assistant
  1. Confirm Skills vs KB selection

    If selected, the assistant will confirm whether the user intends on using a Skill or information from the Knowledge Base when asking a question that triggers both

  1. Exclude Internet Knowledge Base
   If selected, will not use the internet for any query asked, and will solely refer to the Knowledge Base/Skills
  1. Modify Response

    Determines the length of every message sent from the bot by default

  1. Upload Limit

    Determines the upload limit on files to this assistant

  1. Idle Timeout for Switch/Compare Document
    Determines how long the bot will allow you to sit idle while it has learned a document that it is switched into or is comparing

Microsoft Azure Settings

  1. App ID
    The ID of this bot from within Azure
  1. App Secret
    The app secret of this bot from within Azure
  1. Messaging Endpoint
    Endpoint used specifically for this bot when messaging it

Knowledge Builder

To help the assistants to learn matters and documents across workspaces by

  1. dragging and dropping
  2. selecting a file, folder 
  3. adding a URL, and/or
  4. connecting to SharePoint, NetDocuments, iManage connectors

Default Knowledge Base

My Computer - Upload files directly from a computer. This option supports various file formats and allows for easy addition of local documents.
  1. Select the option from the Knowledge Builder
  2. Drag or upload a file, folder or compressed (zip, rar).  
  3. Select the Upload option to add the file or folder to the Knowledge Builder
Web URL - Input a URL to add content from a web source. This feature is useful for integrating online resources and up-to-date information.
  1. Select the option from the Knowledge Builder. 
  2. Enter the web URL for the assistant to learn. 
  3. Once added select the add button to add the URL to the Knowledge Builder 
File URL - Provide a URL link to a file. This method is ideal for linking to cloud storage or other online document repositories.
  1. Select the option from the Knowledge Builder. 
  2. Enter the File URL for the assistant to learn. 
  3. Once added select the Add button to add the URL to the Knowledge Builder. 


Connectors to learn documents

SharePoint - Configure and connect to a SharePoint site. This integration is particularly beneficial for organizations using SharePoint for document management.
  1. Select the option from the Knowledge Builder 
  2. Select the Tenant from dropdown. 
  3. Log in to SharePoint and configure the site and column descriptions.  
  4. Detailed instructions are provided within the interface to guide through the setup process. 


NetDocuments - Connect to a NetDocuments Cabinet. This feature allows for seamless integration with NetDocuments, a popular document management system.
  1. Select the option from the Knowledge Builder 
  2. Log in to NetDocuments and select a Cabinet  
  3. Detailed configuration options are available to ensure secure and efficient integration 
iManage - Log in and configure an iManage library and workspaces. iManage is widely used in legal and professional services firms for document and email management.
  1. Select the option from the Knowledge base 
  2. Log in to iManage when prompted, select the library, and configure workspaces.  
  3. The setup process includes authentication and selection of specific libraries and workspaces. 




Note: Avoid selecting a NetDocuments or iManage Cabinet or Workspace as a knowledge builder for security reasons.  These repositories often contain sensitive information, and caution should be exercised. 


Skill Builder

To create and add new skills so that the admin can add these skills to the various assistants and then deploy those assistants to the different channels to help attorneys and legal staff with their day to day work and documentation.

Steps to Create a New Skill

  1. Click Skill Builder tab in the dashboard
  2. Click + Add New Skill button



  1. Add skill name
  2. Select create

Input Prompt

Require confirmation message

    If selected, requires the user to confirm that they want to use the skill before initiating it.

Additional System Message

    Enter any specific information you want the bot to check for in the messages sent by the user. For instance, if you want to find dates in a MM-DD-YYYY format, you can specify that here

+ Add Prompt

    Adds a prompt to the set of possible phrases that can be used to trigger the Skill. Each prompt contains a sample message such as “get details for the ticket 1234”.

+Add Suggestion Prompt

    Adds an additional prompt that can be used to trigger the skill. Here you can set the bot’s response and what Skill should be initiated upon trying that prompt

+Add Entity

    Adds an entity which allows you to connect a key with a value. For example, in the previous sample prompt “get details for the ticket 1234”, you could add the key “ticketNumber” and the value as “1234” which connects the two values.

Test Prompt

    This allows you to end a sample Prompt and verify that the bot recognizes the key/value pairs you have set up.

Connector

Select Connector

    Choose between two connector types

Universal Web Connector: Connect to a REST API to receive data

SQL Connector: Connect to a SQL Server via Stored Procedures to receive data

Connector Details

Universal Web Connector: add API endpoint and configure headers and body as if you were creating a normal REST API call. You can use the key/value pairs created in the Input Prompt here to add to the query strings

Settings

Methods: select the appropriate method either Get / Post to be performed

A screenshot of a web pageDescription automatically generated

Auth

Four types of authentication methods are available.

A screenshot of a computerDescription automatically generated

None: No authentication method will be used while executing skill http endpoint. This method is used for unauthenticated endpoints.

Basic: We need to provide User Id and Password for this which will be passed as base64 encoded during execution.

Token: We can provide an Access token which will be used as authentication bearer token. We can add a prefix to be used, by default Bearer will be used.

OAuth2: This method provides options to execute the endpoint on behalf of the user by using OAuth token. For this method we need to configure a few parameters as below.

  1. Application Name: The name that needs to be displayed in the login card which will be presented to user to generate token on behalf of the user.
  2. Auth URL: The auth endpoint of the application for which we are generating access code.
  3. Add Param: Add the needed parameters that are passed for generating access code like client id, response_type, etc.
  4. Redirect Uri: Enter it as need based on the application, common usage is redirect Uri
  5. Code property: Enter the property in which the access code will be returned from the auth process, e.g.: code
  6. Click on the Get Access Code button and a pop up will appear in which login into the application and provide needed concern. Once login is successfully authenticated will be redirected to the URL that we have provided, and the pop will be closed automatically.
  7. Token URL: Enter the endpoint of the application to generate access token by exchanging the obtained access code.
  8. Add Param: Use this option to add all needed parameters that need to be passed like client id, client secret, code, etc.
  9. Click on Get Access Token to generate token.
  10. Header: Add all parameters that need to be passed in the header while executing the http call.
  11. Query: Use the Map param option to map query string that needs to be replaced with extracted entity values. Use Add Param to add hardcoded query params.

A screenshot of a computerDescription automatically generated

  1. Body- Following body types are supported:
  2. None
  3. Json
  4. Xml
  5. Text
  6. Form
  7. Select the corresponding body method and values for it. To dynamically replace the entity values place them inside <<entityname>> 
  8. For example {"project_id":"<<project>>","task_id":"<<task>>","spent_date":"<<date>>","hours":"<<hour>>"}
  9. Sample request details are shown below, and we can use the Post/ Get button to execute and see the result.
  10. Select the properties that need to be displayed to end user and leave unwanted properties unchecked.
  11. Filtered JSON will be displayed with the output values so that we can add or remove from previous section.

A white background with black textDescription automatically generated

SQL Connector: Add the details for the fields mentioned about your SQL Database. Then choose a stored procedure. Then map any input fields for the stored procedure with the key/value pairs created earlier in the Input Prompt if required

A white background with black linesDescription automatically generated with medium confidence


Get Result

Once you set up the connector, press Get Results to get a sample results from your API/SQL. Here you can select the values that should be returned by the bot to the user.

A text on a white backgroundDescription automatically generated

Output

Output Prompt

    Write any guidelines you want the bot to follow when creating your output. For example, you could ask the bot to sort results from lowest value to highest value.

Output Format

Text: Bot will return regular text respond containing the results

Adaptive Card: Bot will return a card that can contain an Adaptive Card which can include details such as images or buttons. With this option selected, there will be an additional field called Adaptive Card Data which is where you insert the Adaptive Card code to format the results

Test output

    This will trigger the Skill and return a sample output based on the configurations that were set up

Skill Update

Edit existing skill

    Skills can be updated after they are created to add/change/remove any details that were created initially

Deploy To

Admin can click on “Deploy to” option and download a package that package can be deployed to multiple applications to ease an Attorney’s Day to day work.

A screenshot of a computerDescription automatically generated

Microsoft Teams

  1. Select “Deploy to Microsoft Teams.” 
  2. A zip file will be downloaded with the Assistant's name.  
  3. This file contains all necessary components for the Assistant.   
  4. This Assistant can be installed by Administrator or You can side load it. 
  5. Navigate to Teams, go to the apps section, and select “manage your apps” at the bottom. 
  6. Select “Upload an App” and “upload custom app” to add the Assistant to Teams.   
  7. Add the app to the left-side navigation window, pin the Assistant, and see a welcome message.  
  8. The Assistant will now be available for use within Microsoft Teams. 

SharePoint

  1. Download the SharePoint SPPKG package from the deploy dropdown menu. 
  2. Deploy the SPPKG package to the SharePoint environment app catalog.   
  3. Navigate to the site for KLapper deployment and add the app in “site contents.” 
  4. See the KLapper app in the site apps and start using it.  
  5. The Assistant will be fully integrated into the SharePoint environment, providing seamless access to its features. 


SharePoint Online

  1. Download the SharePoint Online SPPKG package from the deploy dropdown menu. 
  2. Deploy the SPPKG package to the SharePoint environment app catalog.   
  3. Navigate to the site for KLapper deployment and add the app in “site contents.”   
  4. The Assistant will be fully integrated into the SharePoint environment, providing seamless access to its features. 


SharePoint Online Search EXTN

  1. Download the SharePoint Search Extension SPPKG package from the deploy dropdown menu. 
  2. Deploy the SPPKG package to the SharePoint environment app catalog.   
  3. Navigate to the site for KLapper deployment and add the app in “site contents.”   
  4. The Assistant will be fully integrated into the SharePoint environment search, providing seamless access to its features. 

Website

  1. Download the file.
  2. It will contain html which can be added to a website where they want to deploy the assistant. 

Reports

Summary report of Users and Assistants 

User

Features

  1. List of Assistants that have been created, conversations, messages, comments, likes, dislikes and tokens and report.
  2. Channels used by Admin
  3. Assistants List View 
  1. Click on the Assistant's name to see detailed conversation information, including comments, likes, dislikes, reports, and token usage for each message.


Assistant


Select the username to view comprehensive conversation details, encompassing comments, likes, dislikes, reports, and token usage for every
message where the user chose the assistant.


  1. Tokens
A token can be as short as one character or as long as one word or even part of a word, depending on the text. OpenAI models, such as GPT-3 or GPT-4, split text into tokens before processing. For example, the word "beautiful" could be considered one token, while "snowfall" might be split into two tokens: "snow" and "fall."

Below is the link that provides information on how to calculate tokens and their pricing details.


https://help.openai.com/en/articles/4936856-what-are-tokens-and-how-to-count-them

User Account

This is where the User can manage his account details from and access the User Guide and give Feedback.








    • Related Articles

    • KLapper Deployment Guide

      KLapper Deployment Guide V1.0 Introduction This document details the deployment process for our KLapper virtual assistant builder. Prerequisites The deployment process is on Azure Cloud, we need the following prerequisites: Azure Cloud Subscription. ...

    • KLapper End User Guide

      KLapper End User Guide V1.0 Introduction Your Virtual Assistant for Intelligent Counsel, Everywhere! KLapper is an advanced virtual legal assistant designed to enhance the efficiency and productivity of legal professionals. Built specifically for the ...