Lines Matching refs:permissions

2 page.metaDescription=How to manage permissions to give users context and control.
3 page.tags=permissions, user data
4 meta.tags="permissions", "user data"
36       <li><a href="{@docRoot}guide/topics/security/permissions.html">System Permissions</a></li>
37       <li><a href="{@docRoot}training/permissions/index.html">Working with System
48   to such information; it is not an exhaustive discussion of how permissions
53   For a more general look at Android permissions, please see <a href=
55   and User Data</a>. For details on how to work with permissions in your code,
56   see <a href="{@docRoot}training/permissions/index.html">Working with System Permissions</a>.
66   We recommend following these tenets when working with Android permissions:
70   <em><strong>#1: Only use the permissions necessary for your app to
71   work</strong></em>. Depending on how you are using the permissions, there may
78   <em><strong>#2: Pay attention to permissions required by
81   permissions they require, and what those permissions are used for.
85   <em><strong>#3: Be transparent.</strong></em> When you make a permissions
107   "{@docRoot}training/permissions/requesting.html">new permissions model</a> that
108   lets apps request permissions from the user at runtime, rather than prior to
109   installation. Apps that support the new model request permissions when the app
128   <em><strong>Greater flexibility in granting permissions</strong></em>: Users
129   can deny access to individual permissions at the time they’re requested
132   permissions (e.g. using Google Analytics) so that you can either refactor
136   deny permission requests or toggle off permissions in settings.
142   makes it extremely important to minimize the number of permissions you’re
143   requesting because it increases the user burden for granting permissions and
153   of user-surfaced permissions requested affects downloads compared to other
154   similar apps requesting fewer permissions, it’s best to avoid requesting
155   permissions for unnecessary functionality.
172   applications can use without requiring permissions because the user chooses
209   doesn't require explicit permissions (because it does not access sensitive
294   Sometimes permissions are required by the libraries you use in your app. For
296   <code>Location</code> or <code>Identity</code> permissions groups to
302   Just as users select apps that use fewer permissions for the same
304   third-party SDKs that are not using unnecessary permissions. For example, try
306   unless there is a clear user-facing reason why the app needs those permissions.
315 that users are much less uncomfortable with permissions requests if they know
348   a permission group, it helps to explicitly list which of those permissions
372   know why you need the most sensitive permissions.