Remove This Application Was Created By A Google Apps Script User 【RECENT】

Method 3: Switching to Google Cloud Run (The Professional Path)

Keep your Google Sheets, Forms, or Drive logic in Apps Script.

Elias smiled, remembering the gray banner that had once haunted him. "It had humble beginnings," he said, "but it grew up." technical steps

If you do not want to manage external web servers or code repositories, you can use Google's ecosystem to swallow the banner natively. Open or build a page inside Google Sites. Click the tool from the right-hand panel.

If you own a (Business, Enterprise, or Education) account and deploy the script so only "People within [Your Domain]" can access it, they will not see the banner. Method 3: Switching to Google Cloud Run (The

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

: For internal tools where you control the browser, you can use extensions like GAS WebApp Warning Remover (Firefox) or Custom JavaScript for Websites (Chrome) to inject CSS that sets display: none on the banner's HTML ID (usually GCP Project Association : Associating your Apps Script with a standard Google Cloud (GCP) project

. This "wraps" the app in your own branding, though it may require specific X-Frame-Options settings in your script to allow embedding. Browser Extensions (Client-Side)

I can provide the exact code or deployment settings for your specific setup. Share public link Open or build a page inside Google Sites

Click directly on the light blue banner container to target its structural CSS class.

⚠️ : 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.

One common but approach attempts to hide the footer using injected CSS or DOM manipulation:

If the application is an "Add-on" installed inside Google Docs, Sheets, or Slides, revoking access (Method 1) disconnects it, but the menu items might remain visible. To fully uninstall it: When the application's access permissions match the exact

For client-facing portals or public-facing dashboards, the "untrusted user" warning can alarm users and lower conversion rates.

Google injects the banner into a parent frame wrapper outside of your application's accessible DOM environment. Browser security policies prevent your script from reaching "up" into the parent frame to alter it. Summary of Solutions Difficulty Paid Subscription Internal business teams and enterprise tools iFrame Slicing Personal portfolios or simple embedded tools Firebase / Cloud Run Free Tier / Pay-as-you-go Professional SaaS products and public apps

How to Remove "This Application Was Created by a Google Apps Script User" Warning