This method removes the visible footer by masking the GAS URL behind your own domain using a reverse proxy.
Once verified or approved for your organization, the security banner is entirely omitted because the application is recognized as a verified enterprise extension. 3. Deploy Internally Within a Google Workspace Organization
Many developers initially try to hide the banner using simple frontend CSS overrides or JavaScript DOM manipulation. They inspect the page, find the container element (often an or a specific class), and attempt something like this:
There is no CSS or JavaScript trick to hide the banner within the Apps Script environment itself. Google injects this at the top level of the iframe for security. This method removes the visible footer by masking
:
: If your project uses add-ons or libraries, ensure they're not contributing to the notice.
This message is designed to prevent phishing and unauthorized data access. However, for a trusted internal application, it is merely a roadblock. Solutions to Remove the Warning : : If your project uses add-ons or
: If you're using a custom UI (like an HTML service), ensure that the notice isn't hardcoded into the HTML or the script's interface settings.
I can provide the exact code or deployment settings for your specific setup. Share public link
while (files.hasNext()) var file = files.next(); // Check if it is the correct file before deleting // Note: .setTrashed(true) moves it to the Trash bin file.setTrashed(true); // Logger.log('Moved to trash: ' + file.getId()); Client-Side Workarounds (Developer/Internal Use)
: The alert banner is omitted automatically whenever a web app created by a Google Workspace enterprise profile is accessed by another worker belonging to that exact same managed domain.
By understanding these limitations, you can better plan your project's user experience from the start.
To remove the "This application was created by a Google Apps Script user" banner, you generally need to embed your web app in an iframe on another site, or use a Google Workspace (paid) account to deploy it within your own domain.
: Instead of the default project, create a new Google Cloud (GCP) project, associate it with your script, and go through the official OAuth verification process . Client-Side Workarounds (Developer/Internal Use)