There are a few considerations when you work with functionality that requires permissions:
Your app presents a dialog box asking for permissions to be granted when it starts. Your app can't request permission to be granted while it is running.
When a user changes the permissions for your app in the Settings app while your app is running, the changes are ignored. The user must restart the app to detect the changes that were made to the permissions.
You can't assume that your app has the required permission all the time. Users can change app permissions in the Settings app at any time. Users can also grant you permissions that they didn't grant to your app when it was first installed.
10.3.0 and earlier Permissions persist, even when your app is uninstalled. If a user reinstalls your app, the permissions that the user previously granted to your app are active. The user is not prompted to provide permissions when your app is reinstalled.
10.3.1 and later Permissions do not persist. If a user uninstalls your app, the permissions that the user previously granted to your app are removed. The user is prompted to provide permissions when your app is reinstalled.
For Personal Information Management (PIM) permissions, the app can access only data in the perimeter where it was installed. For example, an app that the user installs in the work perimeter has been granted the access_pimdomain_calendars permission. The permission allows the user to access calendar information stored in the work perimeter. However, the app can't access calendar information stored in the user's personal perimeter.
Restricted and developer-driven permissions often don't prompt the user to grant access to functionality or capabilities. These types of permissions require your developer account to be enabled to use, and sign apps with, the permission. For example, users aren't prompted if the app requests the Run as Active Frame (run_when_backgrounded) permission.
The use of restricted and developer-driven permissions often means that your app is subject to a more rigorous review process for acceptance to the BlackBerry World storefront.