Deploy your script as a new version and publish it as a web app again for the changes to take effect.
Click and enter the Project Number of a standard GCP project you control. 3. Configure the OAuth Consent Screen Go to the Google Cloud Console.
For testing purposes, you can hide the warning via a browser user script, but and does not remove the underlying security notice. Use only for personal debugging. Deploy your script as a new version and
The most robust and official way to eliminate the banner is to execute the script from a paid Google Workspace (formerly G Suite) account rather than a free @gmail.com account.
for free on a personal (@gmail.com) account, as it is a fundamental security feature of the platform. However, there are several methods to work around it or minimize its visibility: 1. Embed the App in a Google Site (Recommended) Configure the OAuth Consent Screen Go to the
By using the , you get a clean, professional application for free, bypassing the "Created by a Google Apps Script User" banner entirely.
If you’ve developed a custom web app or tool using and deployed it as a web app, you are likely familiar with the annoying yellow banner that appears at the top of the screen. The most robust and official way to eliminate
If you are part of a organization, the banner is automatically hidden for other users within your same domain. It will only appear to external users outside of your organization. Workaround 3: Verified Add-ons
This clever method uses a parent HTML page to embed your Apps Script web app in an IFrame, which effectively hides the warning banner. This technique was detailed by a developer named paxtech on Qiita.
This removes the application , not the warning per se. The warning will only appear again if you re-authorize a script.
Write your HTML, CSS, and client-side JavaScript locally.
