Borrar búsqueda
Cerrar la búsqueda
Google Apps
Menú principal
La página que solicitaste no está disponible en tu idioma. Puedes seleccionar otro idioma en la parte inferior de la página o traducir cualquier página web al idioma que desees de forma inmediata a través de la función de traducción integrada de Google Chrome.

Unverified apps

To protect users and their data from deceptive applications, your new or updated web application or Apps Script might be affected in the following ways:

  • The app or script might display an "unverified app" screen before it displays the consent screen.
  • Security Checkup might show your app as "risky" and from an "unverified developer."
Unverified app

To remove this screen from your app, or to prevent your app from being marked as risky, you will need to go through the verification process.

When do I need to go through the verification process?

If you create user-facing apps, go through the verification process before you launch your application. You can continue to build and test your application while waiting to complete verification. Upon successful completion of the process, the unverified app screen will be removed from your client.

Note: Subsequent modifications of your client or the usage of new scopes after verification may require you to go through verification again.

If you are developing an experimental app or setting up an OAuth-based plugin for a popular platform, such as SMTP for Wordpress, you do not need to go through the verification process.

If you're creating an internal web app for which all users belong to the same G Suite domain, or your project is associated with a Cloud Organization that your users belong to, you don't need to go through verification. Internal users of your application won't see the unverified app screen.

How do I start the verification process?

  1. Ensure the information in your Consent Screen configuration on the Google API Console is up to date. Include URLs for your Home Page and Terms of Service if you have them. A privacy policy is required.
  2. Verify your website ownership through Search Console by using an account that is either a Project Owner or a Project Editor on your OAuth Project. This also means this same account must be a verified owner of the property in Search Console. We won't be able to approve your OAuth verification request until your site ownership verification is complete. Learn more about site verification. Learn more about Search Console permissions.
  3. Submit a verification request at https://support.google.com/code/contact/oauth_app_verification to begin the verification process.
NOTE: You will be required to repeat this approval process if you add any new redirect URLs, new JavaScript origins, or change your Product Name after approval.

How does verification work for Apps Script?

Newly published Apps Scripts that request OAuth access to data belonging to consumers or users in other domains may also have the "unverified app" screen attached to their OAuth consent flow. For more information about how these changes affect Apps Script developers and users, including instructions for verifying Apps Script OAuth clients, see the Apps Script OAuth client verification documentation.

¿Te ha sido útil este artículo?
¿Cómo podemos mejorar esta página?