Remove This Application Was Created By A Google Apps Script User
: If your script requires broad scopes (such as accessing a user's Google Drive or Gmail account), follow the official guidelines on Apps Script Authorization to avoid triggering aggressive browser-level phishing warnings. Summary Comparison of Solutions Technical Difficulty Branding Freedom Workspace Enterprise Corporate/Internal tools High (Internal only) API Architecture Public Saas, Client Tools 100% Total Control Reverse Proxy Legacy HTML Apps
The banner will only disappear once Google trusts the application.
However, if you are just trying to delete a specific file (like a document named "Paper"), you can use the following code snippet:
While you cannot truly remove the Google Apps Script warning banner, you can effectively hide it from your end users. Here's my recommendation based on your needs:
: If the application isn't one you've developed and you're seeing this notice, it might be related to an organizational setting or a specific app configuration. Reach out to the app's developer or your Google Workspace administrator for assistance. : If your script requires broad scopes (such
/* Note: This does NOT work */ .apps-share-banner display: none !important; Use code with caution. Why this fails:
In the Apps Script editor, click Deploy > New Deployment . Select Web App and set "Who has access" to Anyone . Copy the Web App URL: It will look like https://google.com .
Before applying a fix, it helps to understand why the notice appears:
Under , select Anyone within [Your Organization] . Here's my recommendation based on your needs: :
The banner is particularly problematic on mobile devices. Since September 2023, the banner forces the web app to zoom out to accommodate the extra header, making the content below very difficult to operate. The IFRAME hosting method is your best defense against this issue, as it completely bypasses Google's banner display on the wrapper page.
, the warning banner typically does not appear. This requires more development work and often a verified Google Cloud project, but it is the "official" way to remove such warnings for professional applications. 3. Use within the Same Workspace Domain
This is the most popular and reliable method among developers. By embedding your GAS web app as an IFRAME within another HTML page, you can effectively hide the warning banner from view. The banner is still present in the iframed content, but it's not visible due to the iframe's viewing constraints.
Allows you to run code in any language (Python, Node.js, Go) without any forced headers. Why this fails: In the Apps Script editor,
If you are building a professional application and want total branding control, moving away from the Google Apps Script Web App environment is the best long-term choice.
Link your script to a new project in the Google Cloud Console .
If your goal is to create a professional-looking interface without the "Apps Script" branding, consider . It converts Google Sheets into mobile/web apps.
Under the section, click Change project . Enter your copied Project Number and click Set project . Step 3: Configure and Verify the OAuth Consent Screen