Google plans to roll out a change soon that it says improves the privacy and security of Google customers when web applications request access to a user's account.
Web applications may request access to Google account data, for example when the app needs to interact with data such as calendars, documents, files, or emails of a Google user account.
Up until now, Google customers see a single screen that lists all requested permissions (after selecting an account if multiple are linked to that particular user).
Each permission is listed on the same page and a small (i) icon next to each permission provides additional information when selected.
In the near future, applications will have to separate permission requests so that each is displayed on its own screen in the process.
Going forward, consumers will get more fine-grained control over what account data they choose to share with each app. Instead of seeing all requested permissions in a single screen, apps will have to show you each requested permission, one at a time, within its own dialog box.
So, instead of requiring a customer to hit "allow" just once to accept all permission requests, Google customers get individual screens for each requested permission that they need to accept individually.
One consequence of that is that the process takes longer if an application requests more than one permission.
Google will prompt the customer to allow or deny access to each requested permission individually. Permission prompts will state the requested permissions, e.g. save, edit, share, and permanently delete, and the data or product, e.g. Google Calendar or Google Drive, the permissions apply to.
One core difference, apart from the splitting of permissions, is that the prompt reveals more about the requested access type right away. Current prompts just state "manage your calendars" or "view and manage the files in your Google Drive" but lack additional details. Some users may find the current permission requests unclear and the new prompts change that.
Google displays all requested permissions and the customer's response (deny or allow) on a final screen. The "finish signing in" screen features another option to cancel the entire process but also a sign in button to give the application the requested permissions.
It remains to be seen if the splitting of permission requests improves user awareness and choice, or if it results in another "allow, allow, allow" kind of behavior similar to next, next, next of Windows program installation dialogs.
Now You: What is your take on the change?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.