Turning down the in-app passcode feature in Google Drive, Docs, Sheets, and Slides on iOS

In the past, we’ve heard feedback that customers want more security for the files on their iOS devices, which led us to enable an in-app passcode feature specifically for the Google Drive, Docs, Sheets, and Slides iOS apps. Over time, however, we’ve come to learn that it’s not just the content within Google Drive that’s valuable to you. Your contacts, calendars, and emails—it’s important that all of this is secure as well.

As a result, we began putting particular emphasis on supporting mobile device management (MDM) on iOS. For example, recent launches give G Suite admins greater visibility and control over enterprise-deployed iOS devices. In fact, with MDM, admins can enforce a passcode on all iOS devices that access corporate data, and they can wipe account data on a device if it’s compromised.

Owing to this increased investment in security on iOS devices, we’re ending support for the in-app passcode feature in Google Drive, Docs, Sheets and Slides on iOS devices signed in with G Suite accounts. Support will end on December 4th, 2017, and we’ll remove the feature entirely no earlier than January 8th, 2018.

We highly recommend that administrators use MDM to deploy passcode requirements at the system level on all of their iOS devices by following these instructions. This will provide better security than the in-app passcode feature in two key ways:

  • These passcode policies protect all of the content on your managed devices, including photos, contacts, and other content besides Google Drive, Docs, Sheets, and Slides content.
  • These passcode policies give you more control over passcode type, strength, expiration, and failure cases. See this Help Center article for more details.

Beginning on December 4th, 2017, any user signed in with a G Suite account who has this feature will see a message asking them to either acknowledge and turn off the functionality or to ignore the message temporarily. Beginning on January 8th, 2018, all new versions of the Google Drive, Docs, Sheets, and Slides iOS apps will no longer contain in-app passcode functionality.


Reference by

New features in Google’s Contacts app on Android

Today we’re releasing version 2.2 of the Google Contacts app on Android. This release contains several changes to the look and management of your contacts. Read on for more information.

Changes to the Contact view

  • Large photos are back: A popular request from G Suite users, we’ll now display a larger, more vibrant contact photo.
  • Action buttons under the photo make it easier to connect: Under the contact’s name, you’ll now see new buttons to call, text, video chat or email that contact. Additionally, if there’s at least one street address in the contact’s info, a Directions button will appear.
  • Directory card shows directory profile information: In this card, you’ll see things like the contact’s job title, work phone number, manager name, and office location.
    Contacts Photo

Changes to Suggestions

  • Suggested contacts to add: New in this release, you’ll see suggestions to add contacts you frequently communicate with across Google’s products. These appear under the “Add people you contact often” summary card.
  • Merge all duplicates: The duplicates suggestion view now has a “MERGE ALL” button which allows you to accept all duplicates suggestions at once.Duplicates

Customized “Contacts” view

Lastly, you can now customize the “Contacts” list view to show just the labels you want. This is accessed via a new menu item in the main list screen called “Customize view.” This feature was available in previous releases for the “All contacts” list view, but it has now been made available for individual accounts as well.

We hope these changes make managing your contacts simpler and more efficient. For more information on using Google Contacts, please visit the Help Center.

Launch Details
Launching to both Rapid Release and Scheduled Release
Available to all G Suite editions
Rollout pace:
Full rollout (1–3 days for feature visibility)
All end users
Change management suggested/FYI
Reference by