Release Notes
Abstract
Android 13 introduces a new runtime notification permission, allowing users to focus on the most important notifications. The notification permission is turned off by default on Android 13 devices. Apps that are installed on Android 13 devices (or devices that upgraded to Android 13) will now request the notification permission before posting notifications. Users must explicitly grant the permission for the notifications to work.
Content
The notification permission is critical for MaaS360 apps to function properly.
- MaaS360 core app
Show notifications for the following events: new app distribution, Out of compliance, admin messages, device password, expiration, and malware detection.
- PIM apps
Shows notifications for new email, calendar, and meeting invites.
- Docs
Shows notifications when documents and content sources are distributed to users.
- VPN
Shows the VPN connection status in the form of a persistent notification.
- Browser
Shows the progress of active downloads and alerts from user-permitted websites.
- Remote Control
Informs users about remote access sessions.
Tracking the notification permission in the Device Summary page
Administrators can track the devices that have the notification permission blocked in the Device Summary > Android Blocked Permissions section.
Impact
Android Enterprise devices (DO, PO, and WPCO):
Since the notification permission is critical for MaaS360 apps to properly function, MaaS360 automatically grants the notification permission to core (agent) apps, PIM, Docs, Browser, VPN, and Remote control.
Granting the notification permission to managed apps
You can use security policies to remotely grant notification permission to managed apps.
- From the MaaS360 Portal Home page, navigate to Security > Policies.
- Open an Android MDM policy and then navigate to Android Enterprise Settings > Security > Configure Runtime App Permissions.
- Provide an App ID and then select Show Notifications in Permission.
- Select Always Allow in Default runtime permission grant.
Blocking apps that use the notification permission
You can use security policies to remotely block apps that use notification permission. When the notification permission is blocked, all the apps that use that permission are disabled.
Follow these steps to block the notification permission for managed apps:
- From the MaaS360 Portal Home page, navigate to Security > Policies.
- Open an Android MDM policy and then navigate to Android Enterprise Settings > App Compliance > Configure Restricted Applications by App Permissions.
- In the Permissions dropdown, select Show Notifications.
Device Admin and SPS activated devices
Administrators cannot control notification permission from security policies. Users must explicitly grant notification permission from the corresponding app.
MaaS360 core (agent) app
PIM
MaaS360 displays a one-time notification prompt when the app is launched. If the permission is not granted, a notification request is displayed in the form of a yellow ribbon in the PIM app. Users can always change the notification permission preference from the General Settings screen.
Docs
MaaS360 displays a one-time notification prompt when the Docs app is launched. If the permission is not granted, the notification request is displayed in the form of a yellow ribbon in the Docs app. Users can always change the notification permission preference from the Docs Settings screen.
VPN
MaaS360 displays a notification prompt when the app is launched.
Remote Control
MaaS360 displays a full screen notification request prompt when the app is launched.
Browser
MaaS360 displays a one-time notification prompt when the app is launched. If the permission is not granted, MaaS360 displays a yellow alert in the new tab. Users can always change the notification permission preference from the Browser Settings.
Was this topic helpful?
Document Information
Modified date:
25 July 2022
UID
ibm16606617