| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Add Default Install Scope | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/add-default-install-scope.md | To configure details in app manifest: ## Block apps by default for users until an admin approves -To enhance Teams app experience, you can hide an app from users by default until admin allows the app. For example, consider a help desk app created by Contoso Electronics for Teams. To enable appropriate functioning of the app, Contoso ElectronicsΓÇÖ wants the customers to first configure specific properties of the app. The app is hidden by default and is available to users only after the admin allows it. +To enhance Teams app experience, you can block an app for users by default until admin allows the app. For example, consider a help desk app created by Contoso Electronics for Teams. To ensure the app functions properly, Contoso Electronics wants customers to configure specific properties of the app first. The app is blocked by default and is available to users only after an admin allows it. -To block the app by default, in the app manifest file, set the `defaultBlockUntilAdminAction` property to `true`. When the property is set to `true`, the status of the app in Teams admin center is **Blocked by publisher** in the [Manage apps](https://admin.teams.microsoft.com/policies/manage-apps) page. +To block the app by default, set the `defaultBlockUntilAdminAction` property to `true` in the app manifest file. When the property is set to `true`, the status of the app in Teams admin center is **Blocked by publisher** in the [Manage apps](https://admin.teams.microsoft.com/policies/manage-apps) page. :::image type="content" source="../../assets/images/manage-apps-status.png" alt-text="Screenshot shows an app blocked by publisher." lightbox="../../assets/images/manage-apps-status-expanded.png"::: -The admin gets a request to take action before a user can access the app. Under **Manage apps**, the admins can select **Allow** to allow the app with **Blocked by publisher** status: +The admin gets a request to take action before a user can access the app. In the **[Manage apps](https://admin.teams.microsoft.com/policies/manage-apps)** page in Teams admin center, an admin can select **Allow** to allow the app with **Blocked by publisher** status. :::image type="content" source="../../assets/images/manage-apps-allow.png" alt-text="Screenshot shows the Allow option for the app blocked by publisher." lightbox="../../assets/images/manage-apps-allow-expanded.png"::: If by default, you don't want the app to be hidden, you can update the `defaultBlockUntilAdminAction` property to `false`. When the new version of the app is approved, by default the app is allowed as long as the admin hasn't taken any explicit action. > [!NOTE]-> For custom apps built for your org (LOB apps), `defaultBlockUntilAdminAction` isn't supported. The app isn't blocked if you upload a custom app built for your org with this property. +For custom apps built for your org, `defaultBlockUntilAdminAction` isn't supported. If you upload a custom app built for your organization with this property, the app isn't blocked. ## Next step |
| platform | Promote App Adoption | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/promote-app-adoption.md | Title: Facilitate adoption of your app and create awareness + Title: Facilitate adoption of your app and help customers promote your app ++ description: Learn about the best practices and guidance for app adoption and promotion. ms.localizationpriority: medium- Previously updated : 03/02/2023 Last updated : 01/04/2024 # Five steps to drive adoption of your app Your app might require purchasing a service subscription to experience the app's ### Allow custom apps in an organization -If an organization uses custom apps or custom apps built for your org (LOB apps), then understand how admins control who can upload and use these custom apps. There are three settings that determine whether a user can upload a custom app to a team. These settings don't affect the ability to allow or block third-party apps. +If an organization uses custom apps or custom apps built for your org, then understand how admins control who can upload and use these custom apps. There are three settings that determine whether a user can upload a custom app to a team. These settings don't affect the ability to allow or block third-party apps. 1. User app setup policy setting: As part of [app setup policies](/microsoftteams/teams-app-setup-policies), admins can control whether a user can upload custom apps to Teams. In your appΓÇÖs help documentation, consider providing some or all the following * Contact method with support information, for example, email, phone, or web portal. * Links to help documentation about rollout for admins, features for users, and troubleshooting to supporting functions.+* Understanding of how IT admins can control which users have access to apps by using [app centric management](/microsoftteams/app-centric-management) and [permission policies](/microsoftteams/app-policies#app-permission-policies), depending on their tenant configuration. * Language support provided by the app in case the app is available in any non-English language. * Latest release date and version that imparts app freshness and hence inspires confidence. * Call out any app-specific configuration or permissions that might be required. Also, call out any app-specific uptime information link if your app relies on a backend infrastructure to work. * If you [block an app by default](concepts/design/enable-app-customization.md), provide documentation for the requirements before admins can allow the app. For example, the required configuration or subscription purchase that admins must do. -Your customers can find [support information for your app](/microsoftteams/manage-apps#support-information-for-apps) and self-serve themselves. The following table provides the support information that you already submitted to Microsoft with your app and the interface in Teams where this information is displayed: +To learn more about how your customers access the support information for your app, see [support information for Teams apps](/microsoftteams/manage-apps#support-information-for-apps). The following table explains what support information you can submit with your app and where Teams displays it for app users and administrators. -|Input source when creating app|Parameter|Description and meaning|Visibility of the information in Teams| -|--|--|--|--| -|[Manifest file](resources/schem)|`websiteUrl`|The web page at this URL provides support information for an app.|App details page in Teams admin center displays the website URL.| -|[Manifest file](resources/schem)|`privacyUrl`|The URL to the page that provides privacy information for the app.|ΓÇó Displayed in app details page in Teams admin center. <br> ΓÇó Displayed in Appsource listing.| -|[Manifest file](resources/schem)|`termsOfUseUrl`|The URL to the page that provides the terms of use for the app.|ΓÇó Displayed in app details page in Teams admin center. <br> ΓÇó Displayed in Appsource listing.| -|[Manifest file](resources/schem)|`publisherDocsUrl`|The URL destination provides app documentation for the admins to use to understand, allow, configure, and rollout the app. | URL is available in Teams admin center for those apps where app developer provide it in their manifest file.| -|[Partner Center submission](/azure/marketplace/add-in-submission-guide)|NA|Support or help documentation URL.|Displayed in [Microsoft AppSource](https://appsource.microsoft.com/), in the **Details + support** tab.| +| Input source when creating app | Parameter | Description and meaning | Visibility of the information in Teams | +|-|--|-|--| +| [Manifest file](resources/schem) | `websiteUrl` | The web page at this URL provides support information for an app. | App details page in Teams admin center displays the website URL. | +| [Manifest file](resources/schem) | `privacyUrl` | The URL to the page that provides privacy information for the app. | ΓÇó Displayed in app details page in Teams admin center. <br> ΓÇó Displayed in Appsource listing. | +| [Manifest file](resources/schem) | `termsOfUseUrl` | The URL to the page that provides the terms of use for the app. | ΓÇó Displayed in app details page in Teams admin center. <br> ΓÇó Displayed in Appsource listing. | +| [Manifest file](resources/schem) | `publisherDocsUrl` | The URL destination provides app documentation for the admins to use to understand, allow, configure, and rollout the app. | Teams admin center displays the URL if the app developer provides it in the manifest file. | +| [Partner Center submission](/azure/marketplace/add-in-submission-guide) | NA | Support or help documentation URL. | Displayed in [Microsoft AppSource](https://appsource.microsoft.com/), in the **Details + support** tab. | > [!div class="nextstepaction"] > [Back to top](#understand-how-you-can-drive-app-adoption) |