Permission pages ask for permission from the user to launch an app or execute certain features and should be easy to understand. For example, if your app lets users share their location, you can choose to obtain permission to collect location data before this feature is used for the first time.

  • Ask before running your app when permission is obviously needed and required.
  • Ask in context when permission is only needed to run specific functions of your app.

At the launch or execution of an app, your app must be able to determine if it has permission (Run time).

If not, permission request notification must be displayed.

  • If your app is developed with Tizen 4.0 and the app requires a permission for specific feature, then it must receive user’s permission. If the permission is not received, then the app may not run properly.
    • If permission is denied while Don’t repeat is selected, you need to provide a separate pop-up that guides users to allow permissions through Settings > Apps > Permissions when the user relaunches the app.
    • Users can configure permission for the app that require specific permissions in Settings > Apps > Permissions.
  • Permission requests are grouped as follows. For more information, see Security and API Privileges.













    User history


Permission pages should include:

  • Messages

    These should be clear for users to understand what they are permitting.

  • Actions

    Tapping the V on the right-hand side gives permission and activates the app or the function. Tapping the X closes the app or blocks the function.

  • Don't repeat

    You can ask users if their permission should apply every time they open the app. If users select the Don’t repeat option, the page won’t reappear.

TipIf you need to ask permission for a number of functions, show the permissions in sequence.