![]() This allows the OS to prioritize saving battery life over performing important background tasks on the device. On API 31, apps that the user hasn’t interacted with for eight or more days may be placed in the “restricted” bucket. Devices already enrolled that are upgrading to Android 13 will continue to follow the current notification permissions on the device. Note that the prompt will only display for profiles that are enrolling into management on Android 13 devices. For example, if it's not allowed by default, as will be the case on Android 13 devices, the permission will remain disabled. If the user swipes away the prompt, the notifications permission state will not change. ![]() On corporate-owned devices with a work profile and on fully managed devices, the Microsoft Intune app will display the permission prompt. On device administrator and personally-owned work profile scenarios, we recommend guiding your users to allow permission, so they receive important notifications on device compliance. Users enrolling an Android 13 device into management will need to allow the permission for Intune client apps to enable the best user experience with notifications. Starting with the release of Android 13, there will be a new runtime permission for sending notifications from an app. It is important to note their differing release dates. Throughout this doc, you may see changes attributed to either Android 13 readiness or API 31 targeting readiness.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |