Enable and configure your apps for Teams meetings

• 6/10/2021
• 6 minutes to read
• • l
  • v

Every team has a different way of communicating and collaborating tasks. You can achieve these different tasks by customizing Teams with apps for meetings. To customize and to achieve different tasks, you must enable your apps for Teams meetings and configure your apps to be available in meeting scope within their app manifest.

Enable your app for Teams meetings

To enable your app for Teams meetings, you must update your app manifest and use the context properties to determine where your app must appear.

Update your app manifest

The meetings app capabilities are declared in your app manifest using the configurableTabs, scopes, and context arrays. Scope defines to whom and context defines where your app is available.

The app manifest must include the following code snippet:

"configurableTabs": [
    {
      "configurationUrl": "https://contoso.com/teamstab/configure",
      "canUpdateConfiguration": true,
      "scopes": [
        "team",
        "groupchat"
      ],
      "context":[
        "channelTab",
        "privateChatTab",
        "meetingChatTab",
        "meetingDetailsTab",
        "meetingSidePanel",
        "meetingStage"
     ]
    }
  ]

Context property

The context property determines what must be shown when a user invokes an app in a meeting depending on where the user invokes the app. The tab context and scopes properties enable you to determine where your app must appear. Tabs in the team or groupchat scope can have more than one context. Following are the values for the context property from which you can use all or some of the values:

After you enable your app for Teams meetings, you must configure your app before a meeting, during a meeting, and after a meeting.

Configure your app for meeting scenarios

Teams meetings provides a unique collaborative experience for your organization. It provides the opportunity to configure your app for different meeting scenarios. You can configure your apps to enhance the meeting experience based on participant role or user type. Now you can identify what actions can be taken in the following meeting scenarios:

• Pre-meeting
• In-meeting
• Post-meeting

Pre-meeting

Before a meeting, users can add tabs, bots, and messaging extensions. Users with organizer and presenter roles can add tabs to a meeting.

To add a tab to a meeting

1. In your calendar, select a meeting to which you want to add a tab.

2. Select the Details tab and select .

   

3. In the tab gallery that appears, select the app that you want to add and follow the steps as required. The app is installed as a tab.

   Note

   Currently, in meetings tab, getting meeting details and participant information is not supported.

To add a messaging extension to a meeting

1. Select the ellipses ●●● located in the compose message area in the chat.
2. Select the app that you want to add and follow the steps as required. The app is installed as a messaging extension.

To add a bot to a meeting

In a meeting chat, enter the @ key and select Get bots.

In-meeting

During a meeting, you can use the meetingSidePanel or the in-meeting dialog box to build unique experiences for your apps.

meetingSidePanel

With the meetingSidePanel, you can customize experiences in a meeting that enable organizers and presenters to have different set of views and actions. In your app manifest, you must add meetingSidePanel to the context array. In the meeting and in all scenarios, the app is rendered in an in-meeting tab that is 320 pixels in width. For more information, see FrameContext interface.

To use the userContext API to route requests accordingly, see Teams SDK. For more information, see Teams authentication flow for tabs. Authentication flow for tabs is very similar to the authentication flow for websites. So tabs can use OAuth 2.0 directly. For more information, see Microsoft identity platform and OAuth 2.0 authorization code flow.

Messaging extension works as expected when a user is in an in-meeting view, and the user can post compose message extension cards. AppName in-meeting is a tooltip that states the app name in-meeting U-bar.

In-meeting dialog box

The in-meeting dialog box can be used to engage participants during the meeting and collect information or feedback during the meeting. Use the NotificationSignal API to signal that a bubble notification must be triggered. As part of the notification request payload, include the URL where the content to be shown is hosted.

In-meeting dialog must not use task module. Task module is not invoked in a meeting chat. An external resource URL is used to display content bubble in a meeting. You can use the submitTask method to submit data in a meeting chat.

Share to stage

This capability gives developers the ability to share an app to the meeting stage. By enabling share to the meeting stage, meeting participants can collaborate in real-time.

The required context is meetingStage in the app manifest. A prerequisite for this is to have the meetingSidePanel context. This enables Share in the meetingSidePanel.

The manifest change that is needed to enable this capability is as follows:

"configurableTabs": [
    {
      "configurationUrl": "https://contoso.com/teamstab/configure",
      "canUpdateConfiguration": true,
      "scopes": [
        "groupchat"
      ],
      "context":[
        "meetingSidePanel",
        "meetingStage"
     ]
    }
  ]

Post-meeting

The post-meeting and pre-meeting configurations are the same.

Code sample

See also

• In-meeting dialog design guidelines
• Teams authentication flow for tabs