Remove This Application Was Created By A Google Apps Script User -
Deploy your script in the Google Apps Script Editor by clicking .
The banner automatically hides if the user viewing the app belongs to the exact same Google Workspace enterprise domain as the script creator.
For most serious developers building public-facing tools, bite the bullet and start the verification process today. For everyone else, either embrace the warning—or choose a different development platform. Deploy your script in the Google Apps Script
This is a that Google automatically adds to Apps Script web apps when certain conditions are met. According to a Google Issue Tracker entry from July 2017, Google intentionally expanded this banner to all cases where:
Click on the gear icon on the left sidebar to open . For everyone else, either embrace the warning—or choose
If you have ever built a custom Google Workspace add-on, a simple automation script, or a web app using Google Apps Script, you have likely encountered the infamous grey warning banner that reads:
⚠️ : A significant limitation of client-side methods is that your script's own code cannot hide this banner . Because the script runs within an iframe hosted on a script.google.com subdomain, it is blocked by the browser's same-origin policy from accessing the parent page that contains the warning element. Additionally, these methods are solely for your own convenience; they do not remove the warning for anyone else accessing your application, nor do they build trust with your users. If you have ever built a custom Google
The warning's behavior depends heavily on the type of Google account involved. The following table outlines who sees what under different conditions.
When deploying, set Execute the app as to "Me" and Who has access to "Anyone" . This ensures the script uses your credentials rather than asking the end-user for permissions, which can sometimes bypass the warning.
If you are building the application exclusively for your personal use or a tiny tech-savvy team, you can block the DOM element locally using content filters.
: Standard CSS within your HtmlService file cannot hide the banner because the banner exists in the "parent" frame, and browser security policies prevent scripts inside an iframe from modifying the parent page.
