) to prevent your code from accessing the parent page's elements, including the banner itself. Summary Table: Removal Options Difficulty iFrame Embedding Hides banner on the host site Google Sites Often suppresses banner for viewers Workspace (Internal) No banner for users in your domain GCP Verification Removes banner for public users linking to a GCP project Google Apps Script remove warning banner - Stack Overflow
return HtmlService.createHtmlOutputFromFile( 'Index' ) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard 3. Transition to Google Cloud Project (GCP)
Because you cannot change Google's default web app rendering behavior, the only way to eliminate the banner is to change how you deliver the content to your users. Below are the three most reliable, production-ready methods to bypass the "Created by a Google Apps Script User" banner.
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. ) to prevent your code from accessing the
Google introduced this banner to combat abuse and inform users that the application they are about to use was not created by Google itself. The warning does not mean the app is malicious, but it signals that it comes from a third‑party developer, and users should be cautious.
Deploy your script project as a Web App from the Google Apps Script Editor: Click > New deployment . Set Execute as to Me .
The banner serves as a security notice [1, 2]. Because anyone can write a Google Apps Script to collect user data, Google wants to ensure that end-users know the application is hosted by a third-party developer and not officially built by Google [2]. It protects against: Transition to Google Cloud Project (GCP) Because you
When the application's access permissions match the exact domain infrastructure of the creator, Google recognizes it as a trusted internal tool and removes the notification banner for your employees. 3. Transition to a Verified Google Workspace Add-on
When deploying a web app, you can choose (the developer). In this configuration, the script runs under your identity, and users may not see the authorization banner—especially if the app does not require additional sensitive permissions. However, note that this setting does not always remove the “created by another user” banner if the user is not logged into a Google account or is outside your domain.
This process takes anywhere from , depending on how prepared you are. Google injects this at the top level of
: If your project uses add-ons or libraries, ensure they're not contributing to the notice.
If you are building an internal tool for a company or school using , you can instantly eliminate the banner without undergoing a rigorous public verification review. Google Apps Script overview