UI guidelines for permissions and data

To facilitate a smooth, reassuring user experience, your UX should feature permissions screens that clearly outline how your app is accessing data used by Health Connect, and display data sources in a way that helps users understand how their data is being used.

How to request permissions

Whenever your app requests permissions, your UX should clearly articulate the data types that you are attempting to access:

Main permissions

New Health Connect users

Here are three examples of how your app could request permissions from new Health Connect users:

Promo card on your app's home screen

New user - Home screen

Option within your Settings menu

All other entry points are optional, but your app should always feature an option to request permissions within your Settings menu:

New user - Settings

Integrated into your app's onboarding flow

New user - First time setup

Revoked and canceled permissions

Your app's "Settings" screen should offer users a simple way to revoke permissions to Health Connect data types:

Revoking permissions

Insufficient access

If your app has insufficient Health Connect API access, users are presented with the following screen across all entry points:

App having insufficient access to Health Connect

Permissions canceled twice

If the user selects "Cancel" on the permissions request screen twice in a row, your app should present the user with a screen similar to the following:

Permission request blocked


To build trust and offer reassurance, it's important to show users how your app obtains data. There are two ways to achieve this:

  1. Basic attribution
  2. Attribution with education

Basic attribution

At a minimum, your user interface (UI) should display the app source icon and name (or only the app name if the icon can't be shown).

Basic attribution is suitable for the following screens:

  • Home
  • Activity log
  • Activity details

Icon in the home screen

Basic attribution - Example 1

Icon and app name in the activity log

Basic attribution - Example 2

Attribution with education

You should make it easy for users to obtain information about where data originates from, with a direct link to the "App permissions" screen in Health Connect.

This type of attribution is suitable for the following screens:

  • Activity details
  • Reports and insights

Button in activity details screen

Attribution with education - Example 1

App bar icon or button in report screen

Attribution with education - Example 2

Embedded information

Attribution with education - Example 3

Both of the preceding screens should link to an "About this data" screen that allows users to control which apps are accessing data via Health Connect.

Managing Health Connect permissions

Data sync

You should inform users when a data sync is occurring, especially if the operation is likely to take a while to finish:

Sync notification