+ Title: Build apps for anonymous user

+description: Learn how to build apps for anonymous users and test the experience delivered to the anonymous users in meeting apps with all admin settings.

+ms.localizationpriority: medium

+# Build apps for anonymous users

+You can build bots, messaging extensions, cards and task modules in your app to engage with anonymous meeting participants.

+To test your app's experience for anonymous users, select the URL in the meeting invite and join the meeting from a private browser window.

+## Admin setting for anonymous user app interaction

+Teams admins can use the admin portal to enable or disable anonymous user app interaction for the entire tenant. This setting is enabled by default. For more information, see [allow anonymous users to interact with apps in meetings](/microsoftteams/meeting-settings-in-teams).

+## In-Meeting getContext from Teams client SDK

+Apps receive the following info for an anonymous user when they call the `getContext` API from the shared app stage. You can recognize anonymous users by checking for a `userLicenseType` value of **Unknown**.

+```csharp

+"userObjectId": "8:anon:<GUID1>",

+"userLicenseType": "Unknown",

+"loginHint": "8:teamsvisitor:<ID>",

+"userPrincipalName": "8:teamsvisitor:<ID>",

+"tid": "<meeting organizer tenant ID>"

+```

+| **Property name** | **Description** |

+| | |

+| `userObjectId` | Unique generated value for the anonymous user. This value cannot be used in calls to Graph APIs. |

+| `userLicenseType` | `Unknown`, represents anonymous user. |

+| `loginHint` | Unique generated value. This value cannot be used as a hint in login flows. |

+| `userPrincipalName` | Unique generated value. This value cannot be used in calls to Graph APIs. |

+| `tid` | Tenant ID of the meeting organizer. |

+> [!NOTE]

+> When an anonymous user joins a meeting, a new user ID is generated. Whenever the anonymous user re-joins a meeting, a different user ID is generated.

+## Bot activities and APIs

+With a few differences, the activities sent to your bot, and the responses that it receives from bot APIs, are consistent between anonymous and non-anonymous meeting participants. In general:

+* The user ID is a generated value that is different each time the anonymous user joins the meeting.

+* The `aadObjectId` property is omitted.

+* The `userRole` property is set to **anonymous**.

+* The provided tenant ID is set to the tenant ID of the meeting organizer.

+### Get members and get single member APIs

+The [get members](/microsoftteams/platform/bots/how-to/get-teams-context#fetch-the-roster-or-user-profile) and [get single member](/microsoftteams/platform/bots/how-to/get-teams-context#get-single-member-details) APIs return limited information for anonymous users:

+```json

+{

+ "id": "<GUID1>",

+ "name": "<AnonTest (Guest)>",

+ "tenantId": "<GUID2>",

+ "userRole": "anonymous"

+}

+```

+| **Property name** | **Description** |

+| | |

+| `id` | Unique generated value for the anonymous user. |

+| `name` | Name provided by the anonymous user when joining the meeting. |

+| `tenantId` | Tenant ID of the meeting organizer. |

+| `userRole` | `anonymous`, represents anonymous user. |

+> [!NOTE]

+> The ID received from the bot APIs and the Teams client SDK API are not the same.

+### ConversationUpdate activity MembersAdded and MembersRemoved

+```csharp

+{

+ "membersAdded": [

+ {

+ "id": "<GUID1>"

+ }

+ ],

+ "type": "conversationUpdate",

+ "timestamp": "<timestamp>",

+ "id": "<event unique identifier>",

+ "channelId": "msteams",

+ "serviceUrl": "<serviceURL>",

+ "from": {

+ "id": "<GUID2>"

+ },

+ "conversation": {

+ "isGroup": true,

+ "tenantId": "<tenant id>",

+ "id": "<conversation id>"

+ },

+ "recipient": {

+ "id": "<bot id>",

+ "name": "<bot name>"

+ },

+ "channelData": {

+ "tenant": {

+ "id": "<tenant id>"

+ },

+ "source": null,

+ "meeting": {

+ "id": "<meeting id>"

+ }

+ }

+}

+```

+| **Property name** | **Description** |

+| | |

+| `membersAdded.id` | Anonymous user ID. |

+| `from.id` | Meeting organizer ID. |

+| `conversation.tenantId` | Tenant ID of the meeting organizer. |

+| `conversation.id` | Conversation ID of the meeting chat. |

+| `tenant.id` | Tenant ID of the meeting organizer. |

+Similar changes apply to the `membersRemoved` activity payload.

+> [!NOTE]

+>

+> When an anonymous user joins or leaves a meeting, the `from` object in the payload always has the id of the meeting organizer, even if the action was taken by someone else.

+### Create Conversation API

+Bots are not allowed to initiate a One-on-One conversation with an anonymous user. If a bot calls the Create Conversation API with the user ID of an anonymous user, it will receive a `400` Bad Request status code and the following error response:

+```csharp

+{

+ "error": {

+ "code": "BadArgument",

+ "message": "Bot cannot create a conversation with an anonymous user"

+ }

+}

+```

+### Adaptive cards

+Anonymous users can view and interact with Adaptive Cards in the meeting chat. Adaptive card actions behave the same way for anonymous and non-anonymous users. For more information, see [Card actions](/microsoftteams/platform/task-modules-and-cards/cards/cards-actions?tabs=json).

+## Known issues and limitations

+* Side panel tabs and content bubbles aren't available for anonymous users. Anonymous users can still see app content shared to the meeting stage.

+* For an anonymous user, the user ID from `getContext` and the user ID received by the bot are different. It's not possible to correlate the two directly. If you need to track the user's identity between your tab and bot, you must prompt the user to authenticate with an external identity provider.

+* Anonymous users will see a generic app icon on bot messages and cards, instead of the app's actual icon. For example:

+ :::image type="content" source="../assets/images/apps-in-meetings/app-icon.png" alt-text="This screenshot shows you how the app icon displays for anonymous user.":::

+## See also

+* [Build apps for Teams meeting stage](build-apps-for-teams-meeting-stage.md)

+* [Meeting apps APIs](meeting-apps-apis.md)

+* [How Microsoft Teams bots work](/azure/bot-service/bot-builder-basics-teams)

+ Title: Build apps for Teams meeting stage

+description: Learn how to build apps for Teams meeting stage, share to stage APIs, and generate a deep link to share content to stage in meetings.

+ms.localizationpriority: medium

+# Build apps for Teams meeting stage

+Share to stage allows users to share an app to the meeting stage from the meeting side panel in an ongoing meeting. This sharing is interactive and collaborative in comparison to passive screen sharing.

+To invoke share to stage, users can select the **Share to Stage** icon on the top right side of the meeting side panel. **Share to Stage** icon is native to Teams client and selecting it shares the entire app to the meeting stage.

+## App manifest settings for apps in meeting stage

+To share an app to the meeting stage, update the `context` property in the app manifest as follows:

+```json

+"context":[

+ "meetingSidePanel",

+ "meetingStage"

+ ]

+```

+## Advanced share to stage APIs

+There are many scenarios where sharing the entire app to the meeting stage isn't as useful as sharing specific parts of the app:

+1. For a brainstorming or whiteboard app, a user may want to share a specific board in a meeting versus the entire app with all the boards.

+1. For a medical app, a doctor may want to share just the X-Ray on the screen with the patient versus sharing the entire app with all the patients records or results and so on.

+1. A user may want to share content from a single content provider at a time (for example, YouTube) versus sharing an entire video catalog onto stage.

+To help users in such scenarios, we released APIs within the Teams Client SDK that allows you to programmatically invoke share to stage for specific parts of the app from a button in the meeting side panel.

+Use the following APIs to share specific part of the app:

+|Method| Description| Source|

+|||-|

+|[**Share app content to stage**](#share-app-content-to-stage-api)| Share specific parts of the app to meeting stage from the meeting side panel in a meeting. | [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/meeting) |

+|[**Get app content stage sharing state**](#get-app-content-stage-sharing-state-api)| Fetch information about app's sharing state on the meeting stage. | [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/meeting.iappcontentstagesharingstate) |

+|[**Get app content stage sharing capabilities**](#get-app-content-stage-sharing-capabilities-api)| Fetch the app's capabilities for sharing to the meeting stage. | [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/meeting.iappcontentstagesharingcapabilities) |

+## Share app content to stage API

+The `shareAppContentToStage` API enables you to share specific parts of your app to the meeting stage. The API is available through the Teams client SDK.

+### Prerequisite

+* To use the `shareAppContentToStage` API, you must obtain the RSC permissions. In the app manifest, configure the `authorization` property, and the `name` and `type` in the `resourceSpecific` field. For example:

+ ```json

+ "authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "MeetingStage.Write.Chat",

+ "type": "Delegated"

+ }

+ ]

+ }

+ }

+ ```

+* `appContentUrl` must be allowed by `validDomains` array inside manifest.json, else the API returns a 501 error.

+### Query parameter

+The following table includes the query parameters:

+|Value|Type|Required|Description|

+|||-||

+|**callback**| String | Yes | Callback contains two parameters, error and result. The *error* can either contain an error of type *SdkError*, or null when share is successful. The *result* can either contain a true value, if there's a successful share, or null when the share fails. |

+|**appContentURL**| String | Yes | The URL that will be shared on to the stage. |

+### Example

+```javascript

+const appContentUrl = "https://www.bing.com/";

+microsoftTeams.meeting.shareAppContentToStage((err, result) => {

+ if (result) {

+ // handle success

+ }

+ if (err) {

+ // handle error

+ }

+}, appContentUrl);

+```

+### Response codes

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **500** | Internal error. |

+| **501** | API isn't supported in the current context.|

+| **1000** | App doesn't have proper permissions to allow share to stage.|

+## Get app content stage sharing state API

+The `getAppContentStageSharingState` API enables you to fetch information about apps sharing on the meeting stage.

+### Query parameter

+The following table includes the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**callback**| String | Yes | Callback contains two parameters, error, and result. The *error* can either contain an error of type *SdkError*, in case of an error, or null when share is successful. The *result* can either contain an `IAppContentStageSharingState` object, when share is successful, or null, in case of an error.|

+### Example

+```javascript

+microsoftTeams.meeting.getAppContentStageSharingState((err, result) => {

+ if (result.isAppSharing) {

+ // Indicates if app is sharing content on the meeting stage.

+ }

+});

+```

+The JSON response body for the `getAppContentStageSharingState` API is:

+```json

+{

+ "isAppSharing":true

+}

+```

+### Response codes

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **500** | Internal error. |

+| **501** | API isn't supported in the current context.|

+| **1000** | App doesn't have proper permissions to allow share to stage.|

+## Get app content stage sharing capabilities API

+The `getAppContentStageSharingCapabilities` API enables you to fetch the app's capabilities for sharing to meeting stage.

+### Query parameter

+The following table includes the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**callback**| String | Yes | Callback contains two parameters, error, and result. The *error* can either contain an error of type *SdkError*, or null when share is successful. The result can either contain an `IAppContentStageSharingCapabilities` object, when share is successful, or null, in case of an error.|

+### Example

+```javascript

+microsoftTeams.meeting.getAppContentStageSharingCapabilities((err, result) => {

+ if (result.doesAppHaveSharePermission) {

+ // Indicates app has permission to share contents to meeting stage.

+ }

+});

+```

+The JSON response body for `getAppContentStageSharingCapabilities` API is:

+```json

+{

+ "doesAppHaveSharePermission":true

+}

+```

+### Response codes

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **500** | Internal error. |

+| **501** | API isn't supported in the current context.|

+| **1000** | App doesn't have permissions to allow share to stage.|

+## Generate a deep link to share content to stage in meetings

+You can also generate a deep link to share the app to stage and start or join a meeting.

+> [!NOTE]

+>

+> * Currently, the deep link to share content to stage in meetings is undergoing UX improvements and is available only in [public developer preview](~/resources/dev-preview/developer-preview-intro.md).

+> * Deep link to share content to stage in meeting is supported in Teams desktop client only.

+When a deep link is selected in an app by a user who is part of an ongoing meeting, then the app is shared to the stage and a permission pop-up window appears. Users can grant access to the participants to collaborate with an app.

+When a user isn't in a meeting then the user is redirected to the Teams calendar where they can join a meeting or initiate instant meeting (Meet now).

+Once the user initiates an instant meeting (Meet now), they can add participants and interact with the app.

+To add a deep link to share content on stage, you need to have an app context. The app context allows the Teams client to fetch the app manifest and check if the sharing on stage is possible. The following is an example of an app context.

+`{ "appSharingUrl" : "https://teams.microsoft.com/extensibility-apps/meetingapis/view", "appId": "9ec80a73-1d41-4bcb-8190-4b9eA9e29fbb" , "useMeetNow": false }`

+The query parameters for the app context are:

+* `appID`: This is the ID that can be obtained from the app manifest.

+* `appSharingUrl`: The URL which needs to be shared on stage should be a valid domain defined in the app manifest. If the URL isn't a valid domain, an error dialog will pop up to provide the user with a description of the error.

+* `useMeetNow`: This includes a boolean parameter that can be either true or false.

+ * **True**: When the `UseMeetNow` value is true and if there's no ongoing meeting, a new Meet now meeting will be initiated. When there's an ongoing meeting, this value will be ignored.

+ * **False**: The default value of `UseMeetNow` is false, which means that when a deep link is shared to stage and there's no ongoing meeting, a calendar pop-up will appear. However, you can share directly during a meeting.

+Ensure that all the query parameters are properly URI encoded and the app context has to be encoded twice in the final URL. Following is an example.

+```json

+var appContext= JSON.stringify({ "appSharingUrl" : "https://teams.microsoft.com/extensibility-apps/meetingapis/view", "appId": "9cc80a93-1d41-4bcb-8170-4b9ec9e29fbb", "useMeetNow":false })

+var encodedContext = encodeURIComponent(appcontext).replace(/'/g,"%27").replace(/"/g,"%22")

+var encodedAppContext = encodeURIComponent(encodedContext).replace(/'/g,"%27").replace(/"/g,"%22")

+```

+A deep link can be launched either from the Teams web or from the Teams desktop client.

+* **Teams web**: Use the following format to launch a deep link from the Teams web to share content on stage.

+ `https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`

+ Example: `https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`

+ |Deep link|Format|Example|

+ ||||

+ |To share the app and open Teams calendar, when UseMeeetNow is **false**, default.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Afalse%257D`|

+ |To share the app and initiate instant meeting, when UseMeeetNow is **true**.|`https://teams.microsoft.com/l/meeting-share?deeplinkId={deeplinkid}&fqdn={fqdn}}&lm=deeplink%22&appContext={encoded app context}`|`https://teams.microsoft.com/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`|

+* **Team desktop client**: Use the following format to launch a deep link from the Teams desktop client to share content on stage.

+ `msteams:/l/meeting-share? deeplinkId={deeplinkid}&fqdn={fqdn}&lm=deeplink%22&appContext={encoded app context}`

+ Example: `msteams:/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`

+ |Deep link|Format|Example|

+ ||||

+ |To share the app and open Teams calendar, when UseMeeetNow is **false**, default.|`msteams:/l/meeting-share? deeplinkId={deeplinkid}&fqdn={fqdn}&lm=deeplink%22&appContext={encoded app context}`|`msteams:/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Afalse%257D`|

+ |To share the app and initiate instant meeting, when UseMeeetNow is **true**.|`msteams:/l/meeting-share? deeplinkId={deeplinkid}&fqdn={fqdn}&lm=deeplink%22&appContext={encoded app context}`|`msteams:/l/meeting-share?deeplinkId={sampleid}&fqdn=teams.microsoft.com&lm=deeplink%22&appContext=%257B%2522appSharingUrl%2522%253A%2522https%253A%252F%252Fteams.microsoft.com%252Fextensibility-apps%252Fmeetingapis%252Fview%2522%252C%2522appId%2522%253A%25229cc80a93-1d41-4bcb-8170-4b9ec9e29fbb%2522%252C%2522useMeetNow%2522%253Atrue%257D`|

+The query parameters are:

+* `deepLinkId`: Any identifier used for telemetry correlation.

+* `fqdn`: `fqdn` is an optional parameter, which can be used to switch to an appropriate environment of a meeting to share an app on stage. It supports scenarios where a specific app share happens in a particular environment. The default value of `fqdn` is enterprise URL and possible values are `Teams.live.com` for Teams for Life, `teams.microsoft.com`, or `teams.microsoft.us`.

+To share the entire app to stage, in the app manifest, you must configure `meetingStage` and `meetingSidePanel` as frame contexts, see [app manifest](../resources/schem). Otherwise, meeting attendees may not be able to see the content on stage.

+> [!NOTE]

+> For your app to pass validation, when you create a deep link from your website, web app, or Adaptive Card, use **Share in meeting** as the string or copy.

+## Code sample

+|Sample name | Description | C# | Node.js |

+|-|--|--|-|

+|Meeting stage sample | Sample app to show a tab in meeting stage for collaboration | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-stage-view/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-stage-view/nodejs) |

+| In-meeting notification | Demonstrates how to implement in-meeting notification using bot. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/nodejs) |

+| In-meeting document signing | Demonstrates how to implement a document signing Teams app. Includes sharing specific app content to stage, Teams SSO and user specific stage view. | [View](https://github.com/officedev/microsoft-teams-samples/tree/main/samples/meetings-share-to-stage-signing/csharp) | NA |

+## See also

+* [Teams authentication flow for tabs](../tabs/how-to/authentication/auth-flow-tab.md)

+* [Apps for Teams meetings](teams-apps-in-meetings.md)

+* [Build tabs for meeting](build-tabs-for-meeting.md)

+* [Build extensible conversation for meeting chat](build-extensible-conversation-for-meeting-chat.md)

+* [Build apps for anonymous users](build-apps-for-anonymous-user.md)

+* [Advanced meeting APIs](meeting-apps-apis.md)

+* [Custom Together Mode scenes](~/apps-in-teams-meetings/teams-together-mode.md)

+* [Live Share SDK](teams-live-share-overview.md)

+ Title: Build extensible conversation for meeting chat

+description: In this article, learn how to build extensible conversation for Microsoft Teams meeting chat with bots, cards and message extensions.

+ms.localizationpriority: medium

+# Build extensible conversation for meeting chat

+You can make conversations extensible in Microsoft Teams meetings. Bots, message extensions, cards, and task modules can be combined to deliver an intuitive experience.

+## Bots

+A bot is also referred to as a chatbot or conversational bot. It's an app that runs simple and repetitive tasks by users such as customer service or support staff. Everyday use of bots include, bots that provide information about the weather, make dinner reservations, or provide travel information. Interactions with bots can be quick questions and answers or complex conversations. A bot needs to be enabled in the `team` scope for a channel meeting and the `groupchat` scope for all other meeting types. To implement bots, start with [Build a bot](/microsoftteams/platform//sbs-gs-javascript?tabs=vscode%2Cvsc%2Cviscode).

+### Bot APIs

+The [Bot Framework](https://dev.botframework.com/) is a rich SDK used to create bots using C#, Java, Python, and JavaScript. If you already have a bot that is based on the Bot Framework, you can easily modify it to work in Teams. Use either C# or Node.js to take advantage of our [SDKs](/microsoftteams/platform/).

+### Code samples - Bots

+|Sample name | Description | .NETCore | Node.js | Python |

+|-|--|--|-|

+| Teams conversation bot | Messaging and conversation event handling | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/57.teams-conversation-bot) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/57.teams-conversation-bot) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/57.teams-conversation-bot) |

+|Bot samples | Set of bot samples | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python) |

+## Message extensions

+Message extensions allow the users to interact with your web service through buttons and forms in the Teams client. Users can search or initiate actions in an external system from the compose message area, the command box, or directly from a message. You can send back the results of that interaction to the Teams client in the form of a richly formatted card. Implementing message extensions for meeting chats is no different than regular chats. To implement message extension, start with [Message extensions](/microsoftteams/platform/messaging-extensions/what-are-messaging-extensions?tabs=dotnet).

+## Cards and Task modules

+Cards provide users with various visual, audio, and selectable messages and help in conversation flow. With task modules, you can create modal pop-up experiences in Teams. They're useful for starting and completing the tasks, or displaying rich information like videos or Power business intelligence (BI) dashboards. For more information, see [building cards and task modules](/microsoftteams/platform/task-modules-and-cards/cards-and-task-modules).

+## Feature compatibility by user types

+The following table provides the user types and lists the features that each user can access in meetings:

+| User type | Bots | Message extensions | Adaptive Cards | Task modules |

+| :-- | :-- | :-- | :-- | :-- |

+| In-tenant user | Available | Available | Available | Available |

+| Guest, part of the tenant Azure AD | Not available | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. |

+| Federated users, for more information, see [non-standard users](/microsoftteams/non-standard-users). | Interaction is allowed. Acquire, update, and delete aren't allowed. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. |

+| Anonymous user | Not available | Not available | Interactions in the meeting chat are allowed. | Not available |

+## See also

+* [Designing your Microsoft Teams message extension](../messaging-extensions/design/messaging-extension-design.md)

+* [Designing task modules for your Microsoft Teams app](../task-modules-and-cards/task-modules/design-teams-task-modules.md)

+ Title: Build tabs for meeting

+description: Learn how to build a tabs for a meeting chat, meeting side panel, and meeting stage in Microsoft Teams meeting.

+ms.localizationpriority: high

+# Build tabs for meeting

+Every team has a different way of communicating and collaborating tasks. To achieve these different tasks, customize Teams with apps for meetings. Enable your apps for Teams meetings and configure the apps to be available in the meeting scope within their app manifest.

+## Tabs in Teams meetings

+Tabs allow the meeting participants to access services and content in a specific space within a meeting. If you're new to Microsoft Teams tab development, see [Build tabs for Teams](/microsoftteams/platform/tabs/what-are-tabs).

+Before creating a meeting tab, it's important to learn about the surfaces that are available to target the meeting chat view, meeting details view, meeting side panel view and meeting stage view.

+### Meeting details view

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

+1. Select the **Details** tab and select :::image type="icon" source="../assets/icons/add-icon.png" Border = "false":::. The app gallery appears.

+ :::image type="content" source="~/assets/images/apps-in-meetings/Pre-Meeting-002.png" alt-text="This screenshot shows the pre-meeting app experience in Teams meeting.":::

+1. In the app gallery, select the app that you want to add and follow the steps as required. The tab is added to the meeting details page.

+# [Desktop](#tab/desktop)

+The following image shows a tab added to the meeting details page in the Teams desktop client:

+ :::image type="content" source="~/assets/images/apps-in-meetings/PreMeetingTab.png" alt-text="The screenshot shows desktop Teams tabs in the meeting details view in the Teams meeting.":::

+# [Mobile](#tab/mobile)

+The following image shows a tab added to the meeting details page in the Teams mobile client:

+ :::image type="content" source="../assets/images/mobile-tab.png" alt-text="The screenshot shows mobile Teams tabs in the meeting details view in the Teams meeting.":::

+### Meeting chat view

+1. From the Teams chat panel, select the meeting chat view.

+1. Select :::image type="icon" source="../assets/icons/add-icon.png" Border = "false"::: and the app gallery appears.

+1. In the app gallery, select the app that you want to add and follow the steps as required. The tab is added to the meeting chat.

+ :::image type="content" source="../assets/images/apps-in-meetings/meeting-chat-view.png" alt-text="The screenshot shows the meeting chat view in the Teams meeting.":::

+### Meeting side panel view

+1. During a meeting, you can select :::image type="icon" source="../assets/icons/add-icon.png" Border = "false"::: **Apps** from Teams meeting window to add apps to the meeting.

+ :::image type="content" source="../assets/images/apps-in-meetings/add-app.png" alt-text="This screenshot shows how to add an app in Teams meeting window.":::

+1. In the app gallery, select the app that you want to add and follow the steps as required. The app is added to the meeting side panel.

+ :::image type="content" source="../assets/images/side-panel-view.png" alt-text="This screenshot shows side panel view with the list of apps.":::

+### Meeting stage view

+1. After a tab is added to the meeting side panel, you can now choose to opt into global app sharing.

+1. This results in rendering tab on the stage for every participant in the meeting.

+ :::image type="content" source="../assets/images/meeting-stage-view.png" alt-text="This screenshot shows meeting stage view of the app you shared to meeting.":::

+### Apps in channel meeting

+A public scheduled channel meeting has the same list of apps as its parent team. Installing an app to a channel meeting also makes it available in the parent team, and vice versa.

+However, the tab instances in a channel meeting are separate from the tabs in the channel itself. For example, suppose a *Development* channel has a *Polly* tab. If you create a *Standup* meeting in that channel, that meeting would not have a *Polly* tab, until you explicitly [add the tab to the meeting](#meeting-details-view).

+In public scheduled channel meetings, after a meeting tab is added, you can select the meeting object in the meeting details page to access the tab.

+> [!NOTE]

+> On mobile, anonymous users can't access apps in scheduled public channel meetings.

+### App manifest settings for Tabs in meeting

+Update your [app manifest](/microsoftteams/platform/resources/schema/manifest-schema) with relevant context property to configure the different tab views. The meetings app capabilities are declared in your app manifest using the scopes and context arrays under the configurableTabs section.

+#### Scope

+The scope defines who can access the apps.

+* `groupchat` scope makes your app available in a group scope and enables the app to be added in a call or meeting (scheduled private meeting or instant meetings).

+* `team` scope makes your app available in a team scope and enables your app to be added in team or channel or scheduled channel meeting.

+#### Context

+The `context` property determines if the app is available in specific view after installation and configuration. Following are the values for the `context` property from which you can use all or some of the values:

+|Value|Description|

+|||

+| **channelTab** | A tab in the header of a team channel. |

+| **privateChatTab** | A tab in the header of a group chat between a set of users, not in the context of a team or meeting. |

+| **meetingChatTab** | A tab in the header of a group chat between a set of users for a scheduled meeting. You can specify either **meetingChatTab** or **meetingDetailsTab** to ensure the apps work in mobile. |

+| **meetingDetailsTab** | A tab in the header of the meeting details view of the calendar. You can specify either **meetingChatTab** or **meetingDetailsTab** to ensure the apps work in mobile. |

+| **meetingSidePanel** | An in-meeting panel opened through the unified bar (U-bar). |

+| **meetingStage** | An app from the `meetingSidePanel` can be shared to the meeting stage. You can't use this app either on mobile or Teams room clients. |

+#### Configure tab app for a meeting

+Apps in meetings can use the following contexts: `meetingChatTab`, `meetingDetailsTab`, `meetingSidePanel` and `meetingStage`. After a meeting participant installs an app and configures the tab in meeting, all the targeted other contexts of the app for the given meeting starts to render the tab.

+The following code snippet is an example of a configurable tab used in an app for Teams meetings:

+```json

+"configurableTabs": [

+ {

+ "configurationUrl": "https://contoso.com/teamstab/configure",

+ "canUpdateConfiguration": true,

+ "scopes": [

+ "team",

+ "groupchat"

+ ],

+ "context":[

+ "channelTab",

+ "privateChatTab",

+ "meetingChatTab",

+ "meetingDetailsTab",

+ "meetingSidePanel",

+ "meetingStage"

+ ]

+ }

+ ]

+```

+#### Other examples

+Default context for tabs (if not specified) is:ΓÇ»

+```json

+"context":[

+ "channelTab",

+ "privateChatTab",

+ "meetingChatTab",

+ "meetingDetailsTab"

+ ]

+```

+To prevent an app from showing in non-meeting group chats, you must set the following context:

+```json

+"context":[

+ "meetingSidePanel",

+ "meetingChatTab",

+ "meetingDetailsTab"

+ ]

+```

+For in-meeting side panel experience only:ΓÇ»

+```json

+"context":[

+ "meetingSidePanel"

+ ]

+```

+### Advanced Tab SDK APIs

+The Microsoft Teams JavaScript client SDK is a rich SDK used to create Tabs using JavaScript. Use the latest TeamsJS (V.2.0 or later) to work in Teams, Office, and Outlook. For more information, see [Teams JavaScript client SDK](/microsoftteams/platform/tabs/how-to/using-teams-client-sdk?tabs=javascript%2Cmanifest-teams-toolkit).

+### Frame context

+Microsoft Teams JavaScript library exposes the frameContext in which your meeting tab URL is loaded in the getContext API. The possible values of frameContext are content, task, setting, remove, sidePanel, and meetingStage. This allows you to build customized experiences based on where the app renders. For example, showing a specific collaboration focused UI when in the `meetingStage` and a different meeting preparation UI in the chat tab (`content`). For more information, see [getContext API](/microsoftteams/platform/tabs/how-to/access-teams-context?tabs=teamsjs-v2).

+## Code sample

+|Sample name | Description | C# | Node.js |

+|-|--|--|-|

+| Meeting app | Demonstrates how to use the Meeting Token Generator app to request a token. The token is generated sequentially so that each participant has a fair opportunity to contribute in a meeting. The token is useful in situations like scrum meetings and Q&A sessions. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/nodejs) |

+| Meeting stage sample | Sample app to show a tab in meeting stage for collaboration | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-stage-view/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-stage-view/nodejs) |

+| Meeting side panel | Sample app to show how to add agenda in a meeting side panel | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-sidepanel/csharp) |-|

+| In-meeting notification | Demonstrates how to implement in-meeting notification using bot. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/nodejs) |

+| In-meeting document signing | Demonstrates how to implement a document signing Teams app. Includes sharing specific app content to stage, Teams SSO and user specific stage view. | [View](https://github.com/officedev/microsoft-teams-samples/tree/main/samples/meetings-share-to-stage-signing/csharp) | NA |

+> [!NOTE]

+>

+> * Meeting apps (side panel and meeting stage) are supported in Teams desktop client.

+> * Meeting apps (side panel and meeting stage) in Teams web client is supported only when the [developer preview is enabled](/microsoftteams/platform/resources/dev-preview/developer-preview-intro#enable-developer-preview).

+## Step-by-step guides

+* Follow the [step-by-step guide](../sbs-meeting-token-generator.yml) to generate meeting token in your Teams meeting.

+* Follow the [step-by-step guide](../sbs-meetings-sidepanel.yml) to generate meeting side panel in your Teams meeting.

+* Follow the [step-by-step guide](../sbs-meetings-stage-view.yml) to share meeting stage view in your Teams meeting.

+* Follow the [step-by-step guide](../sbs-meeting-content-bubble.yml) to generate in-meeting notification in your Teams meeting.

+## See also

+* [In-meeting notification design guidelines](design/designing-apps-in-meetings.md#use-an-in-meeting-dialog)

+* [Teams authentication flow for tabs](../tabs/how-to/authentication/auth-flow-tab.md)

+* [Shared meeting stage experience design guidelines](~/apps-in-teams-meetings/design/designing-apps-in-meetings.md)

+* [Add apps to meetings via Microsoft Graph](/graph/api/chat-post-installedapps?view=graph-rest-1.0&tabs=http&preserve-view=true)

+> [Configure your app for meetings](~/apps-in-teams-meetings/build-tabs-for-meeting.md)

+ Title: Build in-meeting notification for Teams meeting

+description: In this article, learn how to build in-meeting notification for Microsoft Teams meeting and its code sample.

+ms.localizationpriority: medium

+# Build in-meeting notification for Teams meeting

+The in-meeting notification is used to engage participants and collect information or feedback during the meeting. Use an [in-meeting notification payload](meeting-apps-apis.md#send-an-in-meeting-notification) to trigger an in-meeting notification. As part of the notification payload request, include the URL where the content to be shown is hosted.

+An external resource URL is used to display in-meeting notification. You can use the `submitTask` method to submit data in a meeting chat.

+You can also add the Teams display picture and people card of the user to in-meeting notification based on `onBehalfOf` token with user MRI and display name passed in payload. Following is an example payload:

+```json

+ {

+ "type": "message",

+ "text": "John Phillips assigned you a weekly todo",

+ "summary": "Don't forget to meet with Marketing next week",

+ "channelData": {

+ onBehalfOf: [

+ {

+ itemId: 0,

+ mentionType: 'person',

+ mri: context.activity.from.id,

+ displayname: context.activity.from.name

+ }

+ ],

+ "notification": {

+ "alertInMeeting": true,

+ "externalResourceUrl": "https://teams.microsoft.com/l/bubble/APP_ID?url=<url>&height=<height>&width=<width>&title=<title>&completionBotId=BOT_APP_ID"

+ }

+ },

+ "replyToId": "1493070356924"

+ }

+```

+## Code sample

+Sample name | Description | C# | Node.js |

+|-|--|--|-|

+| In-meeting notification | Demonstrates how to implement in-meeting notification using bot. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/nodejs) |

+## Step-by-step guides

+Follow the [step-by-step guide](../sbs-meeting-content-bubble.yml) to generate in-meeting notification in your Teams meeting.

+## See also

+* [Build tabs for meeting](~/apps-in-teams-meetings/build-tabs-for-meeting.md)

+* [Build apps for Teams meeting stage](build-apps-for-teams-meeting-stage.md)

+* [Build extensible conversation for meeting chat](build-extensible-conversation-for-meeting-chat.md)

+* [Build apps for anonymous users](build-apps-for-anonymous-user.md)

+* [Advanced meeting APIs](meeting-apps-apis.md)

+ Title: Meeting apps APIs

+description: In this article, learn meeting apps API references that are available for Teams client and Bot Framework SDK's with examples, code samples, and response codes.

+ms.localizationpriority: medium

+# Meeting apps APIs

+The meeting extensibility provides APIs to enhance meeting experience. You can perform the following with help of the listed APIs:

+* Build apps or integrate existing apps within meeting lifecycle.

+* Use APIs to make your app aware of meeting.

+* Select required APIs to improve the meeting experience.

+> [!NOTE]

+> Use Teams [JavaScript SDK](/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true) (*Version*: 1.10 and later) for SSO to work in meeting side panel.

+The following table provides a list of APIs available across the Microsoft Teams JavaScript library and Microsoft Bot Framework SDKs:

+|Method| Description| Source|

+|||-|

+|[**Get user context**](#get-user-context-api)| Get contextual information to display relevant content in a Microsoft Teams tab.| [Microsoft Teams JavaScript library SDK](/microsoftteams/platform/tabs/how-to/access-teams-context#get-context-by-using-the-microsoft-teams-javascript-library) |

+|[**Get participant**](#get-participant-api)| Fetch participant information by meeting ID and participant ID. | [Microsoft Bot Framework SDK](/dotnet/api/microsoft.bot.builder.teams.teamsinfo.getmeetingparticipantasync?view=botbuilder-dotnet-stable&preserve-view=true)

+|[**Send in-meeting notification**](#send-an-in-meeting-notification)| Provide meeting signals using the existing conversation notification API for user-bot chat and allows to notify user action that shows an in-meeting notification. | [Microsoft Bot Framework SDK](/dotnet/api/microsoft.bot.builder.teams.teamsactivityextensions.teamsnotifyuser?view=botbuilder-dotnet-stable&preserve-view=true) |

+|[**Get meeting details**](#get-meeting-details-api)| Get a meeting's static metadata. | [Microsoft Bot Framework SDK](/dotnet/api/microsoft.bot.builder.teams.teamsinfo.getmeetinginfoasync?view=botbuilder-dotnet-stable&preserve-view=true) |

+|[**Send real-time captions**](#send-real-time-captions-api)| Send real-time captions to an ongoing meeting. | [Microsoft Teams JavaScript library SDK](/azure/cognitive-services/speech-service/speech-sdk?tabs=nodejs%2Cubuntu%2Cios-xcode%2Cmac-xcode%2Candroid-studio#get-the-speech-sdk&preserve-view=true) |

+|[**Share app content to stage**](build-apps-for-teams-meeting-stage.md#share-app-content-to-stage-api)| Share specific parts of the app to meeting stage from the app side panel in a meeting. | [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/meeting) |

+|[**Get real-time Teams meeting events**](#get-real-time-teams-meeting-events-api)|Fetch real-time meeting events, such as actual start and end time.| [Microsoft Bot Framework SDK](/dotnet/api/microsoft.bot.builder.teams.teamsactivityhandler.onteamsmeetingstartasync?view=botbuilder-dotnet-stable&preserve-view=true) |

+| [**Get incoming audio state**](#get-incoming-audio-state) | Allows an app to get the incoming audio state setting for the meeting user.| [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/microsoftteams.meeting?view=msteams-client-js-latest&preserve-view=true) |

+| [**Toggle incoming audio**](#toggle-incoming-audio) | Allows an app to toggle the incoming audio state setting for the meeting user from mute to unmute or vice-versa.| [Microsoft Teams JavaScript library SDK](/javascript/api/@microsoft/teams-js/microsoftteams.meeting?view=msteams-client-js-latest&preserve-view=true) |

+## Get user context API

+To identify and retrieve contextual information for your tab content, see [get context for your Teams tab](../tabs/how-to/access-teams-context.md#get-context-by-using-the-microsoft-teams-javascript-library). `meetingId` is used by a tab running in the meeting context and is added for the response payload.

+## Get participant API

+The `GetParticipant` API must have a bot registration and ID to generate auth tokens. For more information, see [bot registration and ID](../build-your-first-app/build-bot.md).

+> [!NOTE]

+>

+> * The user type is not included in the **getParticipantRole** API.

+> * Do not cache participant roles since the meeting organizer can change the roles any time.

+> * Currently, the `GetParticipant` API is only supported for distributions lists or rosters with less than 350 participants.

+### Query parameters

+> [!TIP]

+> Get participant IDs and tenant IDs from the [tab SSO authentication](../tabs/how-to/authentication/tab-sso-overview.md).

+The `Meeting` API must have `meetingId`, `participantId`, and `tenantId` as URL parameters. The parameters are available as part of the Teams Client SDK and bot activity.

+The following table includes the query parameters:

+|Value|Type|Required|Description|

+|||-||

+|**meetingId**| String | Yes | The meeting identifier is available through Bot Invoke and Teams Client SDK.|

+|**participantId**| String | Yes | The participant ID is the user ID. It's available in Tab SSO, Bot Invoke, and Teams Client SDK. It's recommended to get a participant ID from the Tab SSO. |

+|**tenantId**| String | Yes | The tenant ID is required for the tenant users. It's available in Tab SSO, Bot Invoke, and Teams Client SDK. It's recommended to get a tenant ID from the Tab SSO. |

+### Example

+# [C#](#tab/dotnet)

+```csharp

+protected override async Task OnMessageActivityAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)

+{

+ TeamsMeetingParticipant participant = await TeamsInfo.GetMeetingParticipantAsync(turnContext, "yourMeetingId", "yourParticipantId", "yourParticipantTenantId").ConfigureAwait(false);

+ TeamsChannelAccount member = participant.User;

+ MeetingParticipantInfo meetingInfo = participant.Meeting;

+ ConversationAccount conversation = participant.Conversation;

+ await turnContext.SendActivityAsync(MessageFactory.Text($"The participant role is: {meetingInfo.Role}"), cancellationToken);

+}

+```

+# [JavaScript](#tab/javascript)

+```typescript

+export class MyBot extends TeamsActivityHandler {

+ constructor() {

+ super();

+ this.onMessage(async (context, next) => {

+ TeamsMeetingParticipant participant = getMeetingParticipant(turnContext, "yourMeetingId", "yourParticipantId", "yourTenantId");

+ let member = participant.user;

+ let meetingInfo = participant.meeting;

+ let conversation = participant.conversation;

+

+ await context.sendActivity(`The participant role is: '${meetingInfo.role}'`);

+ await next();

+ });

+ }

+}

+```

+# [JSON](#tab/json)

+```http

+GET /v1/meetings/{meetingId}/participants/{participantId}?tenantId={tenantId}

+```

+```json

+{

+ "user":{

+ "id":"29:1JKiJGPAX9TTxtGxhVo0wLx_zwzo-gG8Z-X03306vBwi9p-xMTEbDXsT6KH7-0kkTS8cD-2zkrsoV6f5WJ6_aYw",

+ "aadObjectId":"e236c4bf-88b1-4f3a-b1d7-8891dfc332b5",

+ "name":"Bob Young",

+ "givenName":"Bob",

+ "surname":"Young",

+ "email":"Bob.young@microsoft.com",

+ "userPrincipalName":"Bob.young@microsoft.com",

+ "tenantId":"2fe477ab-0efc-4dfd-bde2-484374e2c373",

+ "userRole":"user"

+ },

+ "meeting":{

+ "role ":"Presenter",

+ "inMeeting":true

+ },

+ "conversation":{

+ "id":"<conversation id>",

+ "conversationType": "groupChat",

+ "isGroup":true

+ }

+}

+```

+| Property name | Description |

+|||

+| **user.id** | ID of the user. |

+| **user.aadObjectId** | Azure Active Directory object ID of the user. |

+| **user.name** | Name of the user. |

+| **user.givenName** | First Name of the user.|

+| **user.surname** | Last Name of the user. |

+| **user.email** | Mail ID of the user. |

+| **user.userPrincipalName** | UPN of the user. |

+| **user.tenantId** | Azure Active Directory tenant ID. |

+| **user.userRole** | Role of the user. For example, 'admin' or 'user'. |

+| **meeting.role** | The participant's role in the meeting. For example, 'Organizer' or 'Presenter' or 'Attendee'. |

+| **meeting.inMeeting** | The value indicating if the participant is in the meeting. |

+| **conversation.id** | The meeting chat ID. |

+| **conversation.isGroup** | Boolean indicating whether conversation has more than two participants. |

+### Response codes

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **403** | Get participant information isn't shared with the app. If the app isn't installed in the meeting, it triggers the error response 403. If the tenant admin disables or blocks the app during live site migration, it triggers the error response 403. |

+| **200** | The participant information is successfully retrieved.|

+| **401** | The app responds with an invalid token.|

+| **404** | The meeting has either expired or participants aren't available.|

+## Send an in-meeting notification

+All users in a meeting receive the notifications sent through in-meeting notification payload. In-meeting notification payload triggers an in-meeting notification and enables you to provide meeting signals that are delivered using the existing conversation notification API for user-bot chat. You can send an in-meeting notification based on user action. The payload is available through Bot Services.

+> [!NOTE]

+>

+> * When an in-meeting notification is invoked, the content is presented as a chat message.

+> * Currently, sending targeted notifications and support for webapp are not supported.

+> * You must invoke the [submitTask()](../task-modules-and-cards/task-modules/task-modules-bots.md#submit-the-result-of-a-task-module) function to dismiss automatically after a user takes an action in the web view. This is a requirement for app submission. For more information, see [Teams SDK task module](/javascript/api/@microsoft/teams-js/microsoftteams.tasks?view=msteams-client-js-latest#submittask-stringobject--stringstring&preserve-view=true).

+> * If you want your app to support anonymous users, initial invoke request payload must rely on `from.id` request metadata in `from` object, not `from.aadObjectId` request metadata. `from.id` is the user ID and `from.aadObjectId` is the Microsoft Azure Active Directory (Azure AD) ID of the user. For more information, see [using task modules in tabs](../task-modules-and-cards/task-modules/task-modules-tabs.md) and [create and send the task module](../messaging-extensions/how-to/action-commands/create-task-module.md?tabs=dotnet#the-initial-invoke-request).

+### Query parameter

+The following table includes the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**conversationId**| String | Yes | The conversation identifier is available as part of Bot Invoke. |

+### Examples

+The `Bot ID` is declared in the manifest and the bot receives a result object.

+> [!NOTE]

+>

+> * The `completionBotId` parameter of the `externalResourceUrl` is optional in the requested payload example.

+> * The `externalResourceUrl` width and height parameters must be in pixels. For more information, see [design guidelines](design/designing-apps-in-meetings.md).

+> * The URL is the page, which loads as `<iframe>` in the in-meeting notification. The domain must be in the apps' `validDomains` array in your app manifest.

+# [C#](#tab/dotnet)

+```csharp

+Activity activity = MessageFactory.Text("This is a meeting signal test");

+activity.TeamsNotifyUser(true, "https://teams.microsoft.com/l/bubble/APP_ID?url=<url>&height=<height>&width=<width>&title=<title>&completionBotId=BOT_APP_ID");

+await turnContext.SendActivityAsync(activity).ConfigureAwait(false);

+```

+# [JavaScript](#tab/javascript)

+```javascript

+const replyActivity = MessageFactory.text('Hi'); // this could be an adaptive card instead

+replyActivity.channelData = {

+ notification: {

+ alertInMeeting: true,

+ externalResourceUrl: 'https://teams.microsoft.com/l/bubble/APP_ID?url=<url>&height=<height>&width=<width>&title=<title>&completionBotId=BOT_APP_IDΓÇÖ

+ }

+};

+await context.sendActivity(replyActivity);

+```

+# [JSON](#tab/json)

+```http

+POST /v3/conversations/{conversationId}/activities

+```

+```json

+{

+ "type": "message",

+ "text": "John Phillips assigned you a weekly todo",

+ "summary": "Don't forget to meet with Marketing next week",

+ "channelData": {

+ "notification": {

+ "alertInMeeting": true,

+ "externalResourceUrl": "https://teams.microsoft.com/l/bubble/APP_ID?url=<url>&height=<height>&width=<width>&title=<title>&<completionBotId>=<BOT_APP_ID>"

+ }

+ },

+ "replyToId": "1493070356924"

+}

+```

+| Property name | Description |

+|||

+| **type** | Type of activity. |

+| **text** | The text content of the message. |

+| **summary** | The summary text of the message. |

+| **channelData.notification.alertInMeeting** | Boolean indicating if a notification is to be shown to the user while in a meeting. |

+| **channelData.notification.externalResourceUrl** | The value of the notification's external resource URL.|

+| **replyToId** | The ID of the parent or root message of the thread. |

+| **APP_ID** | App Id declared in manifest. |

+| **completionBotId** | Bot app Id |

+### Response codes

+The following table includes the response codes:

+|Response code|Description|

+|||

+| **201** | The activity with signal is successfully sent. |

+| **401** | The app responds with an invalid token. |

+| **403** | The app is unable to send the signal. 403 response code can occur because of various reasons, such as the tenant admin disables and blocks the app during live site migration. In this case, the payload contains a detailed error message. |

+| **404** | The meeting chat doesn't exist. |

+## Get meeting details API

+The Meeting Details API enables your app to get a meeting's static metadata. The metadata provides data points that don't change dynamically. The API is available through Bot Services. Currently, both private scheduled or recurring meetings and channel scheduled or recurring meetings support API with different RSC permissions respectively.

+The `Meeting Details` API must have a bot registration and bot ID. It requires Bot SDK to get `TurnContext`. To use the Meeting Details API, you must obtain different RSC permission based on the scope of any meeting, such as private meeting or channel meeting.

+### Prerequisite

+To use the Meeting Details API, you must obtain different RSC permission based on the scope of any meeting, such as private meeting or channel meeting.

+<br>

+<details>

+<summary><b>For app manifest version 1.12 and later</b></summary>

+Use the following example to configure your app manifest's `webApplicationInfo` and `authorization` properties for any private meeting:

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+},

+"authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "OnlineMeeting.ReadBasic.Chat",

+ "type": "Application"

+ }

+ ]

+ }

+}

+ ```

+Use the following example to configure your app manifest's `webApplicationInfo` and `authorization` properties for any channel meeting:

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+},

+"authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "ChannelMeeting.ReadBasic.Group",

+ "type": "Application"

+ }

+ ]

+ }

+}

+ ```

+<br>

+</details>

+<br>

+<details>

+<summary><b>For app manifest version 1.11 and earlier</b></summary>

+Use the following example to configure your app manifest's `webApplicationInfo` property for any private meeting:

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+ "applicationPermissions": [

+ "OnlineMeeting.ReadBasic.Chat"

+ ]

+}

+ ```

+Use the following example to configure your app manifest's `webApplicationInfo` property for any channel meeting:

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+ "applicationPermissions": [

+ "ChannelMeeting.ReadBasic.Group"

+ ]

+}

+ ```

+<br>

+</details>

+> [!NOTE]

+>

+> * The bot can receive meeting start or end events automatically from all the meetings created in all the channels by adding `ChannelMeeting.ReadBasic.Group` to manifest for RSC permission.

+> * For a one-on-one call `organizer` is the initiator of the chat and for group calls `organizer` is the call initiator. For public channel meetings `organizer` is the person who created the channel post.

+### Query parameter

+The following table lists the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**meetingId**| String | Yes | The meeting identifier is available through Bot Invoke and Teams Client SDK. |

+### Example

+# [C#](#tab/dotnet)

+```csharp

+MeetingInfo result = await TeamsInfo.GetMeetingInfoAsync(turnContext);

+await turnContext.SendActivityAsync(JsonConvert.SerializeObject(result));

+```

+# [JavaScript](#tab/javascript)

+```javascript

+Not available

+```

+# [JSON](#tab/json)

+```http

+GET /v1/meetings/{meetingId}

+```

+The JSON response body for Meeting Details API is as follows:

+* **Scheduled meetings:**

+ ```json

+ {

+ "details": {

+ "id": "<meeting ID>",

+ "msGraphResourceId": "MSowYmQ0M2I4OS1lN2QxLTQxNzAtOGZhYi00OWJjYjkwOTk1YWYqMCoqMTk6bWVldGluZ19OVEkyT0RjM01qUXROV1UyW",

+ "scheduledStartTime": "2022-04-24T22:00:00Z",

+ "scheduledEndTime": "2022-04-24T23:00:00Z",

+ "joinUrl": "https://teams.microsoft.com/l/xx",

+ "title": "All Hands",

+ "type": "Scheduled"

+ },

+ "conversation": {

+ "isGroup": true,

+ "conversationType": "groupChat",

+ "id": "meeting chat ID"

+ },

+ "organizer": {

+ "id": "<organizer user ID>",

+ "aadObjectId": "<AAD object ID>",

+ "objectId": "<organizer object ID>",

+ "tenantId": "<Tenant ID>"

+ }

+ }

+ ```

+* **Scheduled channel meetings:**

+ ```json

+ {

+ "details": {

+ "msGraphResourceId": "MSoxNmUwYjdiYi05M2Q1LTQzNTItOTllMC0yM2VlNWYyZmZmZTIqMTY2MDc1ODYwNzc0MCoqMTk6a0RtQkpEWFZsYWl0QWhHcVB2SzBtRExZbHVTWnJub01WX1MxeFNkTjQxNDFAdGhyZWFkLnRhY3Yy",

+ "scheduledStartTime": "2022-08-17T18:00:00Z",

+ "scheduledEndTime": "2022-08-17T18:30:00Z",

+ "type": "ChannelScheduled",

+ "id": "MCMxOTprRG1CSkRYVmxhaXRBaEdxUHZLMG1ETFlsdVNacm5vTVZfUzF4U2RONDE0MUB0aHJlYWQudGFjdjIjMTY2MDc1ODYwNzc0MA==",

+ "joinUrl": "https://teams.microsoft.com/l/meetup-join/19%3akDmBJDXVlaitAhGqPvK0mDLYluSZrnoMV_S1xSdN4141%40thread.tacv2/1660758607740?context=%7b%22Tid%22%3a%229f044231-b634-4bdd-b29d-2776e3dbd699%22%2c%22Oid%22%3a%2216e0b7bb-93d5-4352-99e0-23ee5f2fffe2%22%7d",

+ "title": "Test channel meeting"

+ },

+ "conversation": {

+ "isGroup": true,

+ "conversationType": "channel",

+ "id": "19:kDmBJDXVlaitAhGqPvK0mDLYluSZrnoMV_S1xSdN4141@thread.tacv2;messageid=1660758607740"

+ },

+ "organizer": {

+ "tenantId": "9f044231-b634-4bdd-b29d-2776e3dbd699",

+ "objectId": "16e0b7bb-93d5-4352-99e0-23ee5f2fffe2",

+ "id": "29:1q4D6ekLXEAALkrqyLXUIcwtVSdXx31bf6vMdfahmkTb9euYVYSsN9x4133pXLV_I2idpVriFe40e19XEZt57bQ",

+ "aadObjectId": "16e0b7bb-93d5-4352-99e0-23ee5f2fffe2"

+ }

+ }

+ ```

+* **One-on-one calls:**

+ ```json

+ {

+ "details": {

+ "id": "<meeting ID>",

+ "type": "OneToOneCall"

+ },

+ "conversation": {

+ "isGroup": true,

+ "conversationType": "groupChat",

+ "id": "meeting chat ID"

+ },

+ "organizer ": {

+ "id": "<organizer user ID>",

+ "aadObjectId": "<AAD object ID>",

+ "objectId": "<organizer object ID>",

+ "tenantId": "<Tenant ID>"

+ }

+ }

+

+ ```

+* **Group calls:**

+ ```json

+ {

+ "details": {

+ "id": "<meeting ID>",

+ "type": "GroupCall",

+ "joinUrl": "https://teams.microsoft.com/l/xx"

+ },

+ "conversation": {

+ "isGroup": true,

+ "conversationType": "groupChat",

+ "id": "meeting chat ID"

+ },

+ "organizer": {

+ "id": "<organizer user ID>",

+ "objectId": "<organizer object ID>",

+ "aadObjectId": "<AAD object ID>",

+ "tenantId": "<Tenant ID>"

+ }

+ }

+

+ ```

+* **Instant meetings:**

+ ```json

+ {

+ "details": {

+ "id": "<meeting ID>",

+ "msGraphResourceId": "MSowYmQ0M2I4OS1lN2QxLTQxNzAtOGZhYi00OWJjYjkwOTk1YWYqMCoqMTk6bWVldGluZ19OVEkyT0RjM01qUXROV1UyW",

+ "scheduledStartTime": "2022-04-24T22:00:00Z",

+ "scheduledEndTime": "2022-04-24T23:00:00Z",

+ "joinUrl": "https://teams.microsoft.com/l/xx",

+ "title": "All Hands",

+ "type": "MeetNow"

+ },

+ "conversation": {

+ "isGroup": true,

+ "conversationType": "groupChat",

+ "id": "meeting chat ID"

+ },

+ "organizer": {

+ "id": "<organizer user ID>",

+ "aadObjectId": "<AAD object ID>",

+ "tenantId": "<Tenant ID>" ,

+ "objectId": "<organizer object ID>"

+ }

+ }

+

+ ```

+| Property name | Description |

+|||

+| **details.id** | The meeting's ID, encoded as a BASE64 string. |

+| **details.msGraphResourceId** | The MsGraphResourceId, used specifically for MS Graph API calls. |

+| **details.scheduledStartTime** | The meeting's scheduled start time, in UTC. |

+| **details.scheduledEndTime** | The meeting's scheduled end time, in UTC. |

+| **details.joinUrl** | The URL used to join the meeting. |

+| **details.title** | The title of the meeting. |

+| **details.type** | The meeting's type (OneToOneCall, GroupCall, Scheduled, Recurring, MeetNow, ChannelScheduled, and ChannelRecurring). |

+| **conversation.isGroup** | Boolean indicating whether conversation has more than two participants. |

+| **conversation.conversationType** | The conversation type. |

+| **conversation.id** | The meeting chat ID. |

+| **organizer.id** | The Organizer's user ID. |

+| **organizer.aadObjectId** | The Organizer's Azure Active Directory object ID. |

+| **organizer.tenantId** | The Organizer's Azure Active Directory tenant ID. |

+In case of Recurring meeting type,

+**startDate**: Specifies the date to start applying the pattern. The value of startDate must correspond to the date value of the start property on the event resource. Note that the first occurrence of the meeting may not occur on this date if it doesn't fit the pattern.

+**endDate**: Specifies the date to stop applying the pattern. Note that the last occurrence of the meeting may not occur on this date if it doesn't fit the pattern.

+## Send real-time captions API

+The send real-time captions API exposes a POST endpoint for Teams communication access real-time translation (CART) captions, human-typed closed captions. Text content sent to this endpoint appears to end users in a Teams meeting when they have captions enabled.

+### CART URL

+You can get the CART URL for the POST endpoint from the **Meeting options** page in a Teams meeting. For more information, see [CART captions in a Microsoft Teams meeting](https://support.microsoft.com/office/use-cart-captions-in-a-microsoft-teams-meeting-human-generated-captions-2dd889e8-32a8-4582-98b8-6c96cf14eb47). You don't need to modify the CART URL to use CART captions.

+#### Query Parameter

+The CART URL includes the following query parameters:

+|Value|Type|Required|Description|

+|||-|-|

+|**meetingId**| String | Yes |The meeting identifier is available through Bot Invoke and Teams Client SDK. <br/>For example, meetingid=%7b%22tId%22%3a%2272f234bf-86f1-41af-91ab-2d7cd0321b47%22%2c%22oId%22%3a%22e071f268-4241-47f8-8cf3-fc6b84437f23%22%2c%22thId%22%3a%2219%3ameeting_NzJiMjNkMGQtYzk3NS00ZDI1LWJjN2QtMDgyODVhZmI3NzJj%40thread.v2%22%2c%22mId%22%3a%220%22%7d|

+|**token**| String | Yes |Authorization token.<br/> For example, token=04751eac |

+#### Example

+```http

+https://api.captions.office.microsoft.com/cartcaption?meetingid=%7b%22tId%22%3a%2272f234bf-86f1-41af-91ab-2d7cd0321b47%22%2c%22oId%22%3a%22e071f268-4241-47f8-8cf3-fc6b84437f23%22%2c%22thId%22%3a%2219%3ameeting_NzJiMjNkMGQtYzk3NS00ZDI1LWJjN2QtMDgyODVhZmI3NzJj%40thread.v2%22%2c%22mId%22%3a%220%22%7d&token=gjs44ra

+```

+### Method

+|Resource|Method|Description|

+|-|-|-|

+|/cartcaption|POST|Handle captions for meeting, which was started|

+> [!NOTE]

+> Ensure that the content type for all requests is plain text with UTF-8 encoding. The body of request contains only captions.

+#### Example

+```http

+POST /cartcaption?meetingid=04751eac-30e6-47d9-9c3f-0b4ebe8e30d9&token=04751eac&lang=en-us HTTP/1.1

+Host: api.captions.office.microsoft.com

+Content-Type: text/plain

+Content-Length: 22

+Hello IΓÇÖm Cortana, welcome to my meeting.

+```

+> [!NOTE]

+> Each POST request generates a new line of captions. To ensure that the end user has enough time to read the content, limit each POST request body to 80-120 characters.

+### Error codes

+The following table provides the error codes:

+|Error code|Description|

+|||

+| **400** | Bad request. The response body has more information. For example, not of all required parameters presented.|

+| **401** | Unauthorized. Bad or expired token. If you receive this error, generate a new CART URL in Teams. |

+| **404** | Meeting not found or not started. If you receive this error, ensure that you start the meeting and select start captions. After captions are enabled in the meeting, you can begin POSTing captions into the meeting.|

+| **500** |Internal server error. For more information, [contact support or provide feedback](../feedback.md).|

+## Get real-time Teams meeting events API

+> [!NOTE]

+> Real-time Teams meeting events are only supported for scheduled meetings.

+The user can receive real-time meeting events. As soon as any app is associated with a meeting, the actual meeting start and end time are shared with the bot. The actual start and end time of a meeting are different from scheduled start and end time. The Meeting Details API provides the scheduled start and end time. The event provides the actual start and end time.

+You must be familiar with the `TurnContext` object available through the Bot SDK. The `Activity` object in `TurnContext` contains the payload with the actual start and end time. Real-time meeting events require a registered bot ID from the Teams platform. The bot can automatically receive meeting start or end event by adding `ChannelMeeting.ReadBasic.Group` in the manifest.

+### Prerequisite

+Your app manifest must have the `webApplicationInfo` property to receive the meeting start and end events. Use the following examples to configure your manifest:

+<br>

+<details>

+<summary><b>For app manifest version 1.12 and later</b></summary>

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+ },

+"authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "OnlineMeeting.ReadBasic.Chat",

+ "type": "Application"

+ }

+ ]

+ }

+}

+ ```

+<br>

+</details>

+<br>

+<details>

+<summary><b>For app manifest version 1.11 and earlier</b></summary>

+```json

+"webApplicationInfo": {

+ "id": "<bot id>",

+ "resource": "https://RscPermission",

+ "applicationPermissions": [

+ "OnlineMeeting.ReadBasic.Chat"

+ ]

+}

+ ```

+<br>

+</details>

+### Example of getting `MeetingStartEndEventvalue`

+The bot receives event through the `OnEventActivityAsync` handler. To deserialize the JSON payload, a model object is introduced to get the metadata of a meeting. The metadata of a meeting is in the `value` property in the event payload. The `MeetingStartEndEventvalue` model object is created, whose member variables correspond to the keys under the `value` property in the event payload.

+> [!NOTE]

+>

+> * Get meeting ID from `turnContext.ChannelData`.

+> * Do not use conversation ID as meeting ID.

+> * Do not use meeting ID from meeting events payload `turncontext.activity.value`.

+The following code shows how to capture the metadata of a meeting that is `MeetingType`, `Title`, `Id`, `JoinUrl`, `StartTime`, and `EndTime` from a meeting start/end event:

+Meeting Start Event

+```csharp

+protected override async Task OnTeamsMeetingStartAsync(MeetingStartEventDetails meeting, ITurnContext<IEventActivity> turnContext, CancellationToken cancellationToken)

+{

+ await turnContext.SendActivityAsync(JsonConvert.SerializeObject(meeting));

+}

+```

+Meeting End Event

+```csharp

+protected override async Task OnTeamsMeetingEndAsync(MeetingEndEventDetails meeting, ITurnContext<IEventActivity> turnContext, CancellationToken cancellationToken)

+{

+ await turnContext.SendActivityAsync(JsonConvert.SerializeObject(meeting));

+}

+```

+### Example of meeting start event payload

+The following code provides an example of meeting start event payload:

+```json

+{

+ "name": "application/vnd.microsoft.meetingStart",

+ "type": "event",

+ "timestamp": "2021-04-29T16:10:41.1252256Z",

+ "id": "123",

+ "channelId": "msteams",

+ "serviceUrl": "https://microsoft.com",

+ "from": {

+ "id": "userID",

+ "aadObjectId": "aadOnjectId"

+ },

+ "conversation": {

+ "isGroup": true,

+ "tenantId": "tenantId",

+ "id": "thread id"

+ },

+ "recipient": {

+ "id": "user Id",

+ "name": "user name"

+ },

+ "entities": [

+ {

+ "locale": "en-US",

+ "country": "US",

+ "type": "clientInfo"

+ }

+ ],

+ "channelData": {

+ "tenant": {

+ "id": "channel id"

+ },

+ "source": null,

+ "meeting": {

+ "id": "meeting id"

+ }

+ },

+ "value": {

+ "MeetingType": "Scheduled",

+ "Title": "Meeting Start/End Event",

+ "Id": "meeting id",

+ "JoinUrl": "url"

+ "StartTime": "2021-04-29T16:17:17.4388966Z"

+ },

+ "locale": "en-US"

+}

+```

+### Example of meeting end event payload

+The following code provides an example of meeting end event payload:

+```json

+{

+ "name": "application/vnd.microsoft.meetingEnd",

+ "type": "event",

+ "timestamp": "2021-04-29T16:17:17.4388966Z",

+ "id": "123",

+ "channelId": "msteams",

+ "serviceUrl": "https://microsoft.com",

+ "from": {

+ "id": "user id",

+ "aadObjectId": "aadObjectId"

+ },

+ "conversation": {

+ "isGroup": true,

+ "tenantId": "tenantId",

+ "id": "thread id"

+ },

+ "recipient": {

+ "id": "user id",

+ "name": "user name"

+ },

+ "entities": [

+ {

+ "locale": "en-US",

+ "country": "US",

+ "type": "clientInfo"

+ }

+ ],

+ "channelData": {

+ "tenant": {

+ "id": "channel id"

+ },

+ "source": null,

+ "meeting": {

+ "id": "meeting Id"

+ }

+ },

+ "value": {

+ "MeetingType": "Scheduled",

+ "Title": "Meeting Start/End Event in Canary",

+ "Id": "19:meeting_NTM3ZDJjOTUtZGRhOS00MzYxLTk5NDAtMzY4M2IzZWFjZGE1@thread.v2",

+ "JoinUrl": "url",

+ "EndTime": "2021-04-29T16:17:17.4388966Z"

+ },

+ "locale": "en-US"

+}

+```

+| Property name | Description |

+|||

+| **name** | Name of the user.|

+| **type** | Activity type. |

+| **timestamp** | Local date and time of the message, expressed in ISO-8601 format. |

+| **id** | ID for the activity. |

+| **channelId** | Channel this activity is associated with. |

+| **serviceUrl** | Service URL where responses to this activity should be sent. |

+| **from.id** | ID of the user that sent the request. |

+| **from.aadObjectId** | Azure Active Directory object ID of the user that sent the request. |

+| **conversation.isGroup** | Boolean indicating whether conversation has more than two participants. |

+| **conversation.tenantId** | Azure Active Directory tenant ID of the conversation or meeting. |

+| **conversation.id** | The meeting chat ID. |

+| **recipient.id** | ID of the user that receive the request. |

+| **recipient.name** | Name of the user that receive the request. |

+| **entities.locale** | entity which contains metadata about locale. |

+| **entities.country** | entity which contains metadata about country. |

+| **entities.type** | entity which contains metadata about client. |

+| **channelData.tenant.id** | Azure Active Directory tenant ID. |

+| **channelData.source** | The source name from where event is fired or invoked. |

+| **channelData.meeting.id** | The default ID associated with the meeting. |

+| **value.MeetingType** | The type of meeting. |

+| **value.Title** | The subject of the meeting. |

+| **value.Id** | The default ID associated with the meeting. |

+| **value.JoinUrl** | The join URL of the meeting. |

+| **value.StartTime** | The meeting start time in UTC. |

+| **value.EndTime** | The meeting end time in UTC. |

+| **locale**| The locale of the message set by the client. |

+## Get incoming audio state

+The `getIncomingClientAudioState` API allows an app to get the incoming audio state setting for the meeting user. The API is available through the Teams client SDK.

+> [!NOTE]

+>

+> * The `getIncomingClientAudioState` API for mobile is currently available in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md).

+> * Resource specific consent is available for manifest version 1.12 and later versions, hence this API doesn't work for manifest version 1.11 and earlier versions.

+### Manifest

+```JSON

+"authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "OnlineMeetingParticipant.ToggleIncomingAudio.Chat",

+ "type": "Delegated"

+ }

+ ]

+ }

+ }

+```

+

+### Example

+```javascript

+callback = (errcode, result) => {

+ if (errcode) {

+ // Handle error code

+ }

+ else {

+ // Handle success code

+ }

+ }

+microsoftTeams.meeting.getIncomingClientAudioState(this.callback)

+```

+### Query parameter

+The following table includes the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**callback**| String | Yes | Callback contains two parameters `error` and `result`. The *error* can either contain an error type `SdkError` or `null` when the audio fetch is successful. The *result* can either contain true or false value when the audio fetch is successful or null when the audio fetch fails. The incoming audio is muted if the result is true and unmuted if the result is false. |

+

+### Response codes

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **500** | Internal error. |

+| **501** | API isn't supported in the current context.|

+| **1000** | App doesn't have proper permissions to allow share to stage.|

+## Toggle incoming audio

+The `toggleIncomingClientAudio` API allows an app to toggle the incoming audio state setting for the meeting user from mute to unmute or vice-versa. The API is available through the Teams client SDK.

+> [!NOTE]

+>

+> * The `toggleIncomingClientAudio` API for mobile is currently available in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md).

+> * Resource specific consent is available for manifest version 1.12 and later versions, hence this API doesn't work for manifest version 1.11 and earlier versions.

+### Manifest

+```JSON

+"authorization": {

+ "permissions": {

+ "resourceSpecific": [

+ {

+ "name": "OnlineMeetingParticipant.ToggleIncomingAudio.Chat",

+ "type": "Delegated"

+ }

+ ]

+ }

+}

+```

+### Example

+```javascript

+callback = (error, result) => {

+ if (error) {

+ // Handle error code

+ }

+ else {

+ // Handle success code

+ }

+ }

+microsoftTeams.meeting.toggleIncomingClientAudio(this.callback)

+```

+

+### Query parameter

+The following table includes the query parameter:

+|Value|Type|Required|Description|

+|||-||

+|**callback**| String | Yes | Callback contains two parameters `error` and `result`. The *error* can either contain an error type `SdkError` or `null` when the toggle is successful. The *result* can either contain true or false value, when the toggle is successful or null when the toggle fails. The incoming audio is muted if the result is true and unmuted if the result is false.

+

+### Response code

+The following table provides the response codes:

+|Response code|Description|

+|||

+| **500** | Internal error. |

+| **501** | API isn't supported in the current context.|

+| **1000** | App doesn't have proper permissions to allow share to stage.|

+## Code sample

+|Sample name | Description | C# | Node.js |

+|-|--|--|--|

+| Meetings extensibility | Teams meeting extensibility sample for passing tokens. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-token-app/nodejs) |

+| Meeting content bubble bot | Teams meeting extensibility sample for interacting with content bubble bot in a meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-content-bubble/nodejs)|

+| Meeting side panel | Teams meeting extensibility sample for interacting with the side panel in-meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-sidepanel/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-sidepanel/nodejs)|

+| Details Tab in Meeting | Teams meeting extensibility sample for interacting with Details Tab in-meeting. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-details-tab/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-details-tab/nodejs)|

+| Meeting Events Sample | Sample app to show real-time Teams meeting events|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-events/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-events/nodejs)|

+| Meeting Recruitment Sample |Sample app to show meeting experience for recruitment scenario.|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meeting-recruitment-app/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meeting-recruitment-app/nodejs)|

+| App installation using QR code |Sample app that generates the QR code and installs the app using the QR code|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-installation-using-qr-code/csharp)|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-installation-using-qr-code/nodejs)|

+## See also

+* [Teams authentication flow for tabs](../tabs/how-to/authentication/auth-flow-tab.md)

+* [Apps for Teams meetings](teams-apps-in-meetings.md)

+* [Live Share SDK](teams-live-share-overview.md)

+## Next steps

+[Build tabs for meeting](build-tabs-for-meeting.md)

+Meetings enable collaboration, partnership, informed communication, and shared feedback. The meeting space can deliver a user experience for each stage of the meeting lifecycle. The following illustration gives you an idea of the meeting app extensibility features:

+You must be familiar with the following product concepts to create custom meeting experiences with apps in Microsoft Teams.

+## Supported meeting types in Teams

+* [**Webinar**](https://support.microsoft.com/office/get-started-with-teams-webinars-42f3f874-22dc-4289-b53f-bbc1a69013e3): Webinar initiated through **Webinar** button under **New Meeting** dropdown.

+Learn more about [Teams meetings, expiration and policies](/MicrosoftTeams/meeting-expiration) and [meetings, webinars, and live events](/microsoftteams/quick-start-meetings-live-events).

+## Meeting lifecycle

+A meeting lifecycle includes pre-meeting, in-meeting, and post-meeting app experience, depending on the user type and user's role in a Teams meeting.

+## User types in Teams

+Teams supports user types, such as in-tenant, guest, federated or external user in a Teams meeting. Each user type can have one of the [user roles in Teams meeting](#user-roles-in-teams-meeting).

+The following list details the various user types along with their accessibility:

+* **In-tenant**: In-tenant users belong to the organization and have credentials in Azure Active Directory (AAD) for the tenant. They're full-time, onsite, or remote employees. An in-tenant user can be an organizer, presenter, or attendee.

+* **Guest**: A guest is a participant from another organization invited to access Teams or other resources in the organization's tenant. Guests are added to the organizationΓÇÖs Azure AD and have same Teams capabilities as a native team member. They have access to team chats, meetings, and files. A guest can be an organizer, presenter, or attendee. For more information, see [guest access in Teams](/microsoftteams/guest-access).

+* **Federated or external**: A federated or an external user is a Teams user from another organization who has been invited to join a meeting. Federated users have valid credentials with federated partners and are authorized by Teams. They don't have access to your Teams or other shared resources from your organization. Guest access is a better option for external users to have access to Teams and channels. For more information, see [manage external access in Teams](/microsoftteams/manage-external-access).

+ > [!NOTE]

+ > Teams users can add apps when they host meetings or chats with other organizations. When an external users share apps to the meeting, all the user can access the app. The host organization's data policies and data sharing practices of the third-party apps shared by that user's organization, will be in effect.

+* **Anonymous**: Anonymous users don't have an Azure AD identity and aren't federated with a tenant. The anonymous participants are like external users, but their identity isn't shown in the meeting. Anonymous users can't access apps in a meeting window. An anonymous user can be a presenter or an attendee, but can't be an organizer.

+ > [!NOTE]

+ > Anonymous users inherit the global default user-level app permission policy. For more information, see [manage Apps](/microsoftteams/non-standard-users#anonymous-user-in-meetings-access).

+## User roles in Teams meeting

+The following are the user roles in a Teams meeting:

+* **Organizer**: The organizer schedules a meeting, sets the meeting options, assigns meeting roles, controls attendee permissions, and starts the meeting. Only users with a Microsoft 365 account and Teams license can be the organizer. A meeting organizer can change the settings for a specific meeting from the [**Meeting options** page](https://support.microsoft.com/en-us/office/change-participant-settings-for-a-teams-meeting-53261366-dbd5-45f9-aae9-a70e6354f88e).

+* **Presenter**: Presenters in a meeting have similar capabilities as the organizer, with the exception of removing an organizer from the session and modifying meeting options for the session.

+* **Attendee**: An attendee is a user who is invited to attend the meeting. Attendees have limited capabilities during the meeting.

+> Only an organizer or presenter can add, remove, or uninstall apps.

+For more information, see [roles in a Teams meeting](https://support.microsoft.com/office/roles-in-a-teams-meeting-c16fa7d0-1666-4dde-8686-0a0bfe16e019).

+> [!TIP]

+>

+> * The [default participant settings](/microsoftteams/meeting-policies-participants-and-guests) are determined by an organization's IT administrator. As per default settings, participants joining a meeting have the presenter role.

+> * Presenter role isn't available in one-on-one calls.

+> * A user who starts the group call from a chat is considered as organizer.

+> [!IMPORTANT]

+>

+> * Currently, third-party apps are available in Government Community Cloud (GCC) but are not available for GCC-High and Department of Defense (DOD) tenants.

+> * Third-party apps are turned off by default for GCC. To turn on third-party apps for GCC, see [manage app permission policies](/microsoftteams/teams-app-permission-policies) and [manage apps](/microsoftteams/manage-apps).

+* [Build tabs for meeting](~/apps-in-teams-meetings/build-tabs-for-meeting.md)

+* [Build apps for Teams meeting stage](build-apps-for-teams-meeting-stage.md)

+* [Build extensible conversation for meeting chat](build-extensible-conversation-for-meeting-chat.md)

+* [Build apps for anonymous users](build-apps-for-anonymous-user.md)

+* [Meeting apps APIs](meeting-apps-apis.md)

+* [Custom Together Mode scenes](~/apps-in-teams-meetings/teams-together-mode.md)

+* For third-party apps, see [web apps](../samples/integrating-web-apps.md) and [meeting app extensibility](../apps-in-teams-meetings/teams-apps-in-meetings.md).

+* [Enable and configure your apps for meeting stage](../../apps-in-teams-meetings/build-tabs-for-meeting.md)

+| [In-meeting app experience](../apps-in-teams-meetings/teams-apps-in-meetings.md) | A stage of Teams meeting lifecycle. With the in-meeting app experience, you can engage participants during the meeting by using apps and the in-meeting dialog box. <br>**See also**: [Meeting lifecycle](#m) |

+| [Meeting lifecycle](../apps-in-teams-meetings/teams-apps-in-meetings.md) | It spans from pre-meeting, in-meeting, and post-meeting app experience. You can integrate tabs, bots, and message extensions in each stage of the meeting lifecycle. <br>**See also**: [In-meeting experience](#i) |

+- [Advanced meeting APIs](../../apps-in-teams-meetings/meeting-apps-apis.md)

+ Title: Create a channel tab or group tab

+# Create a channel tab or group tab

+| 07/28/2022 | Add the Teams display picture and people card for in-meeting notification| Build apps for Teams meetings and calls > Enable and configure apps for Teams meetings > [Build in-meeting notification for Teams meeting](apps-in-teams-meetings/in-meeting-notification-for-meeting.md) |

+| 02/11/2022 | Shared meeting stage| ΓÇó Build apps for Teams meetings > [Shared meeting stage](apps-in-teams-meetings/build-tabs-for-meeting.md) </br> ΓÇó Build apps for Teams meetings > [Build apps for Teams meetings](apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md) </br> ΓÇó App manifest > Public developer preview > [Developer preview manifest schema](resources/schem)|

+| 01/25/2022 | Send real-time captions API | Build apps for Teams meetings > Meeting apps API references> [Advanced meeting APIs](apps-in-teams-meetings/meeting-apps-apis.md)|

+|10/20/2021| Meeting stage is now available in GA | Build apps for Teams meetings > [Enable and configure your apps for Teams meetings](apps-in-teams-meetings/build-tabs-for-meeting.md) |

+|10/20/2021| Meeting Details API and real-time Teams meeting events | Build apps for Teams meetings > [Get meeting details API](apps-in-teams-meetings/meeting-apps-apis.md) |

+|07/08/2021|Teams mobile adds support for apps in meetings | Build apps for Teams meetings > [Build apps for Teams meeting](apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md) |

+***October 11, 2022***: [Generate a deep link to share content to stage in meetings.](apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md#generate-a-deep-link-to-share-content-to-stage-in-meetings)

+| 09/23/2022 | Introduced meeting app support for Scheduled Channel Meetings. | Build apps for Teams meetings and calls > [Apps for Teams meetings and calls](apps-in-teams-meetings/teams-apps-in-meetings.md) |