Most permissions fall into one or more of the following categories:
- User-granted permissions
- The user is prompted when the app is first installed and run on the device. The user must explicitly grant your app permission to use the requested functionality or capability.
- Restricted permissions
- Permissions that require signing for by your app. You can use restricted permissions when your developer account has been granted access to use them. To be granted access to use a restricted permission, you must request permission from BlackBerry and have a vendor account. When you receive approval to use a restricted permission, you can sign your apps for deployment to the BlackBerry World storefront. For more information about applying for a vendor account, see Managing vendor portal accounts.
- Developer-driven permissions
- These permissions typically enable platform features that the developer wants to use to improve the experience of their app, such as the use_gamepad permission. These types of permissions are meant to enable platform features that most apps don't require or use but are useful in specific use cases.
|
Some permissions need other permissions. You don't need to request each nested permission; you need to request the main permission only. The user can choose whether to give your app access to all the permissions under the main permission or a subset of the permissions. If the user doesn't grant your app a permission that's nested under the main permission, your app can't use that subset of the functionality. For example, under the Connect to BBM permission, the user can choose whether to grant your app access to use the BBM Contact Invites, Profile Updates, both, or neither. |
|