Starting March 27, 2025, we recommend using android-latest-release
instead of aosp-main
to build and contribute to AOSP. For more information, see Changes to AOSP.
Notification permission for opt-in notifications
Stay organized with collections
Save and categorize content based on your preferences.
Notifications in Android 13 use an opt-in model, which
is a change from previous Android versions, which use an opt-out model. In
Android 13, all apps must ask users for permission before
sending notification prompts. This model helps reduce notification
interruptions, minimizes information overload, and helps users control what
notifications appear based on what's important to them. To support the
opt-in model, OEMs must implement changes in the notification and runtime
permission systems.
This page describes what OEMs must implement to support this change and how
to validate the implementation.
Implement changes for opt-in notifications
Starting with Android 13, apps must declare their
intent to send notifications by requesting the
android.permission.POST_NOTIFICATION
runtime permission from the system before they can send notifications.
In Android 13 and higher, the setting that determines
if an app can send notifications to the user is stored in the permission system.
Prior to Android 13, this setting was stored in the
notification system. Hence, OEMs must migrate the existing notification data
about whether an app is allowed to send notifications, from the notification
system into the runtime permission system. OEMs must also maintain existing APIs
in the notification system that surface that data to app developers.
Changes to the notification and permission systems are based on the
opt-in model of user notification behavior and are
described in the Guidelines for implementation section.
Behavior of user notifications in an opt-in model
The following table illustrates the notification behavior for various app
versions on a device running Android 13:
Device on Android 13 |
Apps targeting Android 13 or higher |
Apps targeting versions lower than Android 13 |
New install
|
Notifications are blocked until prompted by the app.
Apps control when to ask for permission.
|
Notifications are blocked until prompted by the OS.
Permission is asked on the first run of the app.
|
Existing app (upgrade)
|
Notifications are allowed until prompted by the app.
Temporary permission is granted until the app asks on the first qualifying run.
|
Notifications are allowed until prompted by the OS.
Temporary permission is granted until the first run of the app.
|
Guidelines for implementation
For reference implementation, refer to
notification service,
permission service and
policy service. To implement exceptions
for default permission handlers see
Runtime Permissions.
During implementation, use the following guidelines on user notification
behavior for apps targeting Android 13 or lower SDKs:
- Freshly installed apps on an Android 13 device must
not send a notification without the user approving a permission prompt.
- If the app targets versions Android 13 and
higher, notifications must be blocked until prompted by the app as the app
controls when and if to ask for user permission.
- If the app targets versions lower than
Android 13, notifications must be blocked until
prompted by the OS. The OS must show the permission prompt on the first run of
the app.
Any app that existed on the device prior to an upgrade to
Android 13, or any app that was restored through backup
and restore, must be allowed to send notifications until the first time the user
launches an activity from that app.
For apps that target SDK of versions Android 13
and higher, if the user hasn't previously customized notification settings for
this app at the app or NotificationChannel
level, revoke the temporary
permission grant. Apps must then ask the user for permission before being
allowed to continue to send notifications.
If an upgraded app targeting Android 13 doesn't
currently have the notification permission through the temporary upgrade
grant, and the user has launched it at least once, the app must show a
notification permission prompt before it’s allowed to run any further foreground
services.
For apps that have a target SDK of versions lower than
Android 13,
intercept
the first activity launch after the app has created at least one NotificationChannel
to show a permission prompt asking if the user wants to receive notifications
from the app.
If a user previously customized notification settings at the
app or NotificationChannel
level for an app on the upgrading device or in a
backup being restored to the device, the app level setting must be migrated into
the permission system with the FLAG_PERMISSION_USER_SET
flag. No further
notification permission prompt must be shown to the user unless the app
specifically asks it to be.
Backup and restore must be backward and forward compatible between an
Android 13 device and a device from an earlier OS
version. Backup data generated from an Android 13
device must restore onto an earlier OS version, and backup data from an earlier
OS version must restore onto an Android 13 device.
Media notifications associated with ongoing media playback must be exempt
from the notification permission.
Validate changes to the notification and permission systems
To validate the implementation, run the following tests:
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-06-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-26 UTC."],[],[],null,["# Notification permission for opt-in notifications\n\nNotifications in Android 13 use an opt-in model, which\nis a change from previous Android versions, which use an opt-out model. In\nAndroid 13, all apps must ask users for permission before\nsending notification prompts. This model helps reduce notification\ninterruptions, minimizes information overload, and helps users control what\nnotifications appear based on what's important to them. To support the\nopt-in model, OEMs must implement changes in the notification and runtime\npermission systems.\n\nThis page describes what OEMs must implement to support this change and how\nto validate the implementation.\n\nImplement changes for opt-in notifications\n------------------------------------------\n\nStarting with Android 13, apps must declare their\nintent to send notifications by requesting the\n[`android.permission.POST_NOTIFICATION`](https://developer.android.com/about/versions/13/changes/notification-permission)\nruntime permission from the system before they can send notifications.\n\nIn Android 13 and higher, the setting that determines\nif an app can send notifications to the user is stored in the permission system.\nPrior to Android 13, this setting was stored in the\nnotification system. Hence, OEMs must migrate the existing notification data\nabout whether an app is allowed to send notifications, from the notification\nsystem into the runtime permission system. OEMs must also maintain existing APIs\nin the notification system that surface that data to app developers.\n\nChanges to the notification and permission systems are based on the\n[opt-in model of user notification behavior](#behavior-optin) and are\ndescribed in the [Guidelines for implementation](#guidelines-impl) section.\n\n### Behavior of user notifications in an opt-in model\n\nThe following table illustrates the notification behavior for various app\nversions on a device running Android 13:\n\n| Device on Android 13 | Apps targeting Android 13 or higher | Apps targeting versions lower than Android 13 |\n|------------------------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|\n| New install | Notifications are blocked until prompted by the app. Apps control when to ask for permission. | Notifications are blocked until prompted by the OS. Permission is asked on the first run of the app. |\n| Existing app (upgrade) | Notifications are allowed until prompted by the app. Temporary permission is granted until the app asks on the first qualifying run. | Notifications are allowed until prompted by the OS. Temporary permission is granted until the first run of the app. |\n\n### Guidelines for implementation\n\nFor reference implementation, refer to\n[notification service](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/core/java/com/android/server/notification/),\n[permission service](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/core/java/com/android/server/pm/permission/) and\n[policy service](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/core/java/com/android/server/policy). To implement exceptions\nfor default permission handlers see\n[Runtime Permissions](/docs/core/permissions/runtime_perms#integration).\n\nDuring implementation, use the following guidelines on user notification\nbehavior for apps targeting Android 13 or lower SDKs:\n\n- Freshly installed apps on an Android 13 device must not send a notification without the user approving a permission prompt.\n - If the app targets versions Android 13 and higher, notifications must be blocked until prompted by the app as the app controls when and if to ask for user permission.\n - If the app targets versions lower than Android 13, notifications must be blocked until prompted by the OS. The OS must show the permission prompt on the first run of the app.\n- Any app that existed on the device prior to an upgrade to\n Android 13, or any app that was restored through backup\n and restore, must be allowed to send notifications until the first time the user\n launches an activity from that app.\n\n - For apps that target SDK of versions Android 13\n and higher, if the user hasn't previously customized notification settings for\n this app at the app or `NotificationChannel` level, revoke the temporary\n permission grant. Apps must then ask the user for permission before being\n allowed to continue to send notifications.\n\n If an upgraded app targeting Android 13 doesn't\n currently have the notification permission through the temporary upgrade\n grant, and the user has launched it at least once, the app must show a\n notification permission prompt before it's allowed to run any further foreground\n services.\n - For apps that have a target SDK of versions lower than\n Android 13,\n [intercept](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/core/java/com/android/server/wm/ActivityInterceptorCallback.java)\n the first activity launch after the app has created at least one `NotificationChannel`\n to show a permission prompt asking if the user wants to receive notifications\n from the app.\n\n If a user previously customized notification settings at the\n app or `NotificationChannel` level for an app on the upgrading device or in a\n backup being restored to the device, the app level setting must be migrated into\n the permission system with the `FLAG_PERMISSION_USER_SET` flag. No further\n notification permission prompt must be shown to the user unless the app\n specifically asks it to be.\n- Backup and restore must be backward and forward compatible between an\n Android 13 device and a device from an earlier OS\n version. Backup data generated from an Android 13\n device must restore onto an earlier OS version, and backup data from an earlier\n OS version must restore onto an Android 13 device.\n\n- Media notifications associated with ongoing media playback must be exempt\n from the notification permission.\n\nValidate changes to the notification and permission systems\n-----------------------------------------------------------\n\nTo validate the implementation, run the following tests:\n\n- Unit tests as specified in [`PreferencesHelperTest`](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/tests/uiservicestests/src/com/android/server/notification/PreferencesHelperTest.java),\n [`NotificationManagerServiceTest`](https://cs.android.com/android/platform/superproject/+/android-latest-release:frameworks/base/services/tests/uiservicestests/src/com/android/server/notification/NotificationManagerServiceTest.java).\n\n- Any manual test that tests upgrades and backup and restore.\n\n- Any CTS Permission and Notification system test that sends notifications.\n Some of these tests are located in [cts/tests/tests/permission/](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Permission/tests/cts/permission/src/android/permission/cts/),\n [NotificationManagerTest.java](https://cs.android.com/android/platform/superproject/+/android-latest-release:cts/tests/tests/notification/src/android/app/notification/current/cts/NotificationManagerTest.java?q=NotificationManagerTest.java),\n and [cts/tests/tests/notificationlegacy/](https://cs.android.com/android/platform/superproject/+/android-latest-release:cts/tests/tests/notificationlegacy/)."]]