What's new

Register Now! Find useful tips, Interact /w Community Members and join the part the Best Community on the Internet!

Discussion More Google API changes - Enhancing security controls for Google Drive third-party apps


Legendary Member
PG Version
Mount Type
Blitz Encrypted
Server Type
Remote - Dedicated Server
just saw this https://cloud.google.com/blog/products/identity-security/enhancing-security-controls-for-google-drive-third-party-apps

any idea how/if this change impacts us?


Enhancing security controls for Google Drive third-party apps

In October of last year, we announced Project Strobe—a Google-wide effort to review third-party developer access to Google account and Android device data. As a result, we rolled out an updated user data policy further restricting access to Gmail data. Today we’re announcing plans to extend the same policy to Google Drive as part of Project Strobe.

With this updated policy, we’ll limit the types of apps that have broad access to content or data via Drive APIs. Apps should move to a per-file user consent model, allowing users to more precisely determine what files an app is allowed to access. This means that only certain types of apps can request restricted scopes from consumer Google accounts. As always, G Suite administrators are in control of their users’ apps.

How to prepare
If you’re not a developer, you don’t need to do anything to prepare for these changes. While changes will not go into effect until early next year, we recommend developers begin preparations ahead of time by taking the following steps to ensure their apps using Drive APIs stay compliant and keep working for users. You will not need to go through the verification process if your app is created and used by only your organization (and is marked as internal).

  1. Before getting started, review the Drive updates to the user data policy and FAQ.
  2. Ensure project owner and editor email addresses are up to date.
  3. If you've developed a Drive app that uses any of the restricted scopes, we recommend migrating your app to use the drive.file scope in combination with the Google Picker. This combination will enable users to select the specific files from their Google Drive that they want to allow your app to access. Apps that use the drive.file scope will not be required to go through the restricted scope verification and third-party security assessment outlined in the policy.
  4. If drive.file is not a possible option (e.g. for backup clients), you should begin preparing your app for the restricted scope verification, a process that, among other steps, ensures your use of data is compliant with the Limited Use Requirements and includes a security assessment if your app stores or transmits through servers. Restricted scope verification for the Drive API will begin early next year. Refer to the FAQ for more info.
In the next few months, we will start to notify impacted developers of the policy changes and will provide additional guidance on how to meet the updated policy requirements.


Full Member
Not liking the look of this. Somehow Google File Picker also may come into play? I wonder if you could use Internal Only check-mark to bypass the drama that ensues.
Last edited:

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Development Donations


Top NZB NewsGroups!

Members - Up To a 58% Discount!


Online statistics

Members online
Guests online
Total visitors