"oauthScopes": [ "https://www.googleapis.com/auth/spreadsheets.currentonly", "https://www.googleapis.com/auth/gmail.compose" ]
If you want a native web application experience with a custom domain and zero Google branding, you should move your backend logic away from Apps Script web apps and host it on . Why This Works:
to migrate a project away from Apps Script, or should we refine the narrative arc of the story?
Keep your Google Sheets, Forms, or Drive logic in Apps Script. "oauthScopes": [ "https://www
The security warnings are in place for a reason—to protect users. Removing them should only be done through the official processes once your application is trustworthy and compliant.
AppSheet is Google's official no-code development platform. Because AppSheet apps require user authentication and follow rigid enterprise compliance rules, Google does not place the "Apps Script User" warning banner on AppSheet user interfaces.
In essence, Google is saying: “We don’t know who built this. Be careful.” The security warnings are in place for a
To completely remove the banner from your web application, you must link your Apps Script project to a verified Google Cloud Platform (GCP) project and complete the OAuth consent screen verification process . Google automatically injects this disclaimer banner into standalone Google Apps Script web apps as a security safeguard. The warning alerts external, anonymous users that the application was written by an independent developer rather than by Google directly.
If you use restricted scopes, be prepared to pay for a third-party security assessment (costing thousands of dollars). To remove the message cheaply, where possible.
: Free for personal use / core Google Workspace accounts; nominal fee per user for advanced corporate sharing. Summary Comparison of Workarounds Effort Level Professional Look Ideal Use Case Iframe Embedding Public landing pages, client portals, simple forms. Google Cloud API Commercial software, SaaS products, large user bases. Google AppSheet Internal company tools, mobile databases. Because AppSheet apps require user authentication and follow
Your users will visit your domain name, viewing a completely clean interface without any Google warning bars. Method 2: Restrict Access to a Google Workspace Domain
If you share a Workspace script with someone outside your domain, the banner may reappear to warn them. 2. Embed the App in an Iframe
This is the preferred method if you want a professional presentation without requiring users to install anything. 2. Verify Your Project with Google Cloud (GCP)