Skip to content
Material Design 1
Main Navigation
v3
v2
v1

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

Appearance

Sidebar Navigation

Material Design

Environment

Material properties

Elevation & shadows

What's new

Motion

Material motion

Duration & easing

Movement

Transforming material

Choreography

Creative customization

Style

Color

Icons

Imagery

Typography

Writing

Layout

Principles

Units & measurements

Metrics & keylines

Structure

Responsive UI

Split screen

Components

Bottom navigation

Bottom sheets

Buttons

Buttons: Floating Action Button

Cards

Chips

Data tables

Dialogs

Dividers

Expansion panels

Grid lists

Lists

Lists: Controls

Menus

Pickers

Progress & activity

Selection controls

Sliders

Snackbars & toasts

Steppers

Subheaders

Tabs

Text fields

Toolbars

Tooltips

Widgets

Patterns

Confirmation & acknowledgement

Data formats

Empty states

Errors

Fingerprint

Gestures

Help & feedback

Launch screens

Loading images

Navigation

Navigation drawer

Navigational transitions

Notifications

Offline states

Permissions

Scrolling techniques

Search

Selection

Settings

Swipe to refresh

Growth & communications

Introduction

Onboarding

Feature discovery

Gesture education

Usability

Accessibility

Bidirectionality

Platforms

Platform adaptation

Android

Resources

Color palettes

Devices

Layout templates

Roboto & Noto fonts

Sticker sheets & icons

Shadows

On this page

Permissions ​

Permission requests should be simple, transparent, and understandable.

Apps should clarify why each permission request is needed, either through the feature name or an explanation provided.

Runtime permissions are requested at the moment a user needs to perform an action in an app.

Denied permissions should provide feedback and options.

Types of permissions

Educate before asking
Ask up-front
Ask in context
Educate in context
Provide an immediate benefit
Only ask for relevant permissions

Material Design: Clear and simple permission requests

Usage ​

Permission groups

Permissions are divided into nine groups, allowing users to grant all permissions encompassed by a single action. For instance, granting permission to Contacts includes the ability to both view and edit Contacts.

PermissionDescription
CalendarManaging calendars
CameraTaking photos and recording videos
ContactsManaging contacts
LocationCurrent device location
MicrophoneAudio recording
PhoneDialing and managing phone calls
Body SensorsHeart rate and similar data
SMSSending and viewing messages
StorageAccessing photos, media, and files

Implied permission

A user may perform an action that demonstrates clear intent, such as:

  • Taking a picture
  • Selecting a contact
  • Starting a call or text message

In these cases, the user’s action clearly demonstrates their intent, and no permission dialog is needed or authorized.

Intents and Intent Filters

Using intents to request actions from apps

Runtime permissions ​

Apps may request permission to access information or use device capabilities at any time after installation. When a user needs to perform an action in an app, such as using the device camera, the app may request permission at that moment.

Users may also allow or deny the permissions of any app from Android Settings anytime after installation.

Material Design app requesting permission example
Example of an app requesting permission

Request patterns ​

App permissions that users believe are relevant to the app’s function are more likely to be granted. The following request patterns will help you decide when and how to request permissions, based on:

  • A permission’s importance to the app’s core function
  • The clarity of the permission
Material Design: Request critical permissions upfront
Critical permissions should be requested up-front. Secondary permissions may be requested in-context.
In both cases, permissions that are less clear should provide education about what the permission involves.
Material Design: Provide a warm welcome and explain permissions

Educate before asking

If your app has a “warm welcome,” use it to explain what your app does and why unexpected permissions will be requested.

Material Design: Ask critical permissions at first launch

Ask up-front

Only ask for critical and obvious permissions on first launch. Because users expect a messaging app to request SMS permissions, requesting it up-front makes sense.

Request permissions contextually in Material Design

Ask in context

For non-critical permissions, wait until a feature is invoked to request permission. Users are more likely to allow a permission when they want to use the feature it enables.

Material Design: Explain non-critical permissions in context

Educate in context

Non-critical permissions that are less intuitive may benefit from being explained in context. Doing so improves users’ comprehension of the permission.

Material Design: Instant benefit for permission acceptance

Provide an immediate benefit

Provide instant gratification to make accepting a permission feel justified.

Request only the permissions needed for a feature to work

When more than one permission is needed for a feature to work, ask for those permissions only and nothing extra.

Denied permissions ​

Provide feedback whenever a permission is denied. Because denying permissions may prevent a feature from working as intended, whenever a permission is denied it should be explained to the user.

Permission denials occur in one of two ways:

  • A permission request is denied by the user
  • A permission is silently denied without warning because a user once selected “Don’t ask again” from a previous permission request

To ensure that features requiring permission always behave as intended, the app should state that permission is needed and provide a way to allow it.

Material Design snackbar for audio permission request
A snackbar displays the need for permission in order to use an audio feature.

Critical permissions

If the app can no longer run because a critical permission has been denied, explain why that permission must be allowed and offer a button to open Settings so the user can allow it.

Material Design: App needs permission to function
A screen explains that a permission is needed for an app to function, with a link to allow that permission in Settings.
Pager
Previous pageOffline states
Next pageScrolling techniques

Released under the Apache-2.0

Copyright © 2014-Present Google

https://m1.material.io/patterns/permissions.html

Released under the Apache-2.0

Copyright © 2014-Present Google