Remove This Application Was Created By A Google Apps Script User

This process takes anywhere from , depending on how prepared you are.

: Malicious actors trying to mimic Google login screens [2].

If you use Google Sheets, Forms, or Web Apps to run custom scripts, you have likely encountered a prominent warning banner. It reads: "This application was created by a Google Apps Script user."

: If the app is shared externally, the banner may still appear to outside users unless the script is bound to a Google Cloud Platform (GCP) project with a verified OAuth consent screen. 2. Embed the Web App in an iFrame with CSS Overflows This process takes anywhere from , depending on

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.

Outcome (single sentence): state the result and any residual issues. Example: "Banner gone across all users; no other UI changes observed." It reads: "This application was created by a

If you want absolute control over the user interface with zero Google branding, you should stop using Apps Script to serve the visual frontend. Instead, use Apps Script strictly as a backend API.

When you deploy a Web App from a Google Workspace account, the banner behavior changes based on who accesses it:

When users visit your custom domain, the code runs inside the container without showing the top Google warning header to the audience. 2. Transition to Google Workspace Add-ons For everyone else, either embrace the warning—or choose

This method removes the visible footer by masking the GAS URL behind your own domain using a reverse proxy.

The warning "This application was created by a user" is a security feature, not a bug, making scripts look unauthorized.

While the standard solutions above cover most cases, here are a few more scenarios and official references that may be helpful.