Assistant components

UI Component of the Virtual Assistant

Meeting Content page

A page in the portal showing all Video and Transcripts of meetings and the status of the insights they have in such as tasks, summary and sentiments :

A meeting can have either:

1. Video without transcript

2. Video with Transcript

3. Transcript without video

Each meeting has only 1 Transcript file and can have multiple videos.

If there are multiple videos and 1 transcript - the same transcript is show for all videos.

In this pave each line is either a video or a Transcript. When line is Video, the attributes of AI are not relevant and are shown NULL (empty)

Open

Meeting Assistant App

A page showing list of meeting with the number of tasks in each meeting and link to Assistant insights page.

This page is used by both Monday widget and Teams Meeting app and has a separate site (separate from the portal) hosting it.

It is managed here in Asana https://app.asana.com/0/1202413461416060/list

The App location is:

\fs\Build Versions\Test\MeetingAssistantApp

The meeting Assistant App includes an API that exposes a list of meetings per user and the tasks in each meeting.

The Assistant App can be published as a widget on Monday (under iFrame) or as a Teams app (under a tab).

In Teams it will apear like this:

Open

In monday.com it will apear like this:

Meeting Assistant insights page

A page in the Portal that is used to show all the insights of a meeting.

Monday Widget

The widget is configure in a dashboard showing the meeting Assistant App

The widget shows the page in an iFrame.
See here info on how to configure it:https://agatsoftware.atlassian.net/wiki/spaces/SKYP/pages/2574417978/Monday.com+integration

Teams meeting assistant Azure app

In MS Teams there is a meeting assistant application that can be added by admin to all users. It shows the meeting Assistant App in a tab.

This app is managed in the Teams admin center.

It is defined using a config file which is managed as part of the code of the Assistant App and is located here: \\fs\Build Versions\Test\MeetingAssistantApp\Teams App Manifests

In addition, there is an Azure app that is responsible for passing authentication between Teams client and Teams Meeting assistant app. The Azure app name is Meeting Assistant Authentication app.

The Azure app has the following permissions:

Smart Text engine - how it works

Task detection flow using Smart Text analyser

The Assistant has a configuration file setting phrases / words to trigger insights such as Tasks, Summary, Agenda and more.

The config includes 3 level of confident:

1. High- when detecting open triggers indicating speaking to the Assistant such as “OK Agi” or “Agi please”. These are defined in the config in the section of Open triggers.

2. Medium- Words that most likely indicate insights such as “Create a task” or “Create a summary”

3. Low- Words that might imply of insights.

When the system detects a High level open trigger, it will include all lower level words to understand what is the insights / Action item.

When setting in the portal sensitivity level - the system will only check of the level set and above. For example if set to High, only phrases starting with an open trigger will be detected.

If close triggers are found, the system will mark the confident level as higher that just Open trigger.

Dataflow

Once the service has identified a new meeting that needs to be analyzed, it will download the recording into the database.

The Assistant Business Logic will then send the transcript for inspection.

Detailed

Security

Authenticating into the portal is done by using the Azure OAuth token prompting an MS authentication window

In general, only the admin should have access to the portal.

You can also allow specific groups to access specific reports/sections of the portal if needed.

Authenticating into the Meeting Assistant App is done by Single Sign On (SSO).

The server receives a JWT token of the user from the client-provider. In our case, the client-provider can be Microsoft Teams or monday.com. The JWT token is passed to our web services in the Authentication header through an SSL connection, and on the server side, we are verifying the user’s JWT token signature by a key of Microsoft Teams/monday.com, and we are validating the claims like audience/tenant id, etc., then we return the result of this user just if the validation is succeeded.

This authentication method protects our web services from unwanted access.

In the following image, you can see how our SSO works on Microsoft teams:
For more information, please click here.

Azure Assistant App Required Permissions

Production

The information below covers the permissions needed by our released Azure applications

AGI for Meetings

This application retrieves meeting recordings and transcriptions from users' OneDrive drives.

This application does not apply to chat and channel messages.

AGI for Meetings + Chat

This application retrieves meeting recordings and transcriptions from users' OneDrive drives and chat and channel messages.

It can also send notifications when it has user credentials and create an insights tab in meeting chats.

AGAT CASB API - AGI for Meetings Minimal

For companies with compliance requirements, AGAT offers a solution requiring limited permissions, while still allowing use of the core functionality of AGI.

This application retrieves meeting recordings and transcriptions from users' OneDrive drives.

This application does not apply to chat and channel messages, which means tasks will not be identified by AGI based on your Teams' chat messages.

To restrict access to specific meetings that the user would like to analyze, the customer is required to define an “application user” (e.g. agi@yourCompany.com). Only the meetings where AGI was added by one of the participants and that was recorded will be analyzed.

AGAT CASB API - Minimal AGI for Meetings

This application retrieves meeting recordings and transcriptions from users' OneDrive drives.

This application does not apply to chat and channel messages.

It is possible to configure a user for AGI and define that only meetings that AGI participated in will be processed.

User Delegation solutions

The deployment options below assume AGI is added manually to every meeting the user would like to be inspected.

This approach gives the user control over which meetings should be analyzed and which should not be analyzed.

The apps below are Delegated, which means that the app only has access to the users that have installed it and not to the whole company.

Delegate (user-based) - Recordings+Transcripts Option

AGI will download both the recording and transcript for each meeting.

This app allows AGI only to access users' meetings that have given content to this app.

These apps are in the process of certification for the Microsoft Teams marketplace.

Delegate (user-based) - Transcripts Only Option

AGI will only download the transcript. The limitation of this solution is that you must invite AGI to the meeting before it starts in the calendar and can’t add her to the meeting inside the meeting after starting.

This app allows AGI only to access users' meetings that have given content to this app.