Ensure project owner and editor email addresses are up to date.Before getting started, review the Drive updates to the user data policy and FAQ.
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). 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. If you’re not a developer, you don’t need to do anything to prepare for these changes. As always, G Suite administrators are in control of their users’ apps. This means that only certain types of apps can request restricted scopes from consumer Google accounts. Apps should move to a per-file user consent model, allowing users to more precisely determine what files an app is allowed to access. With this updated policy, we’ll limit the types of apps that have broad access to content or data via Drive APIs. Today we’re announcing plans to extend the same policy to Google Drive as part of Project Strobe.
As a result, we rolled out an updated user data policy further restricting access to Gmail data. 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.
0 kommentar(er)
