Remove This Application Was Created By A Google Apps Script User -

The banner "This application was created by a Google Apps Script user" is a built-in security disclaimer designed by Google to warn users that the application has not been verified by Google and may be untrustworthy. Direct Solutions

There is no single "off" switch in the script settings, but you can remove or hide it using these methods: The banner "This application was created by a

Embed in Google Sites: The most reliable official method is to embed your web app URL into a Google Site. When viewed through the Google Sites interface, the banner is typically suppressed. Myth 4: Paying for a Google Workspace account

Self-Hosting via Iframe: You can host a simple HTML file on your own domain (e.g., via GitHub Pages) and embed the Apps Script URL within an </code>. While the banner may still technically exist within the frame, it is isolated from your main site's branding. Google Workspace Accounts: For internal apps, the banner is often not shown to users who are part of the same Google Workspace domain as the script owner. Why the Banner Exists Security & Phishing Prevention: Google uses this banner to prevent malicious actors from creating fake login pages or data-collection forms that look like official Google products. Verification Status: The banner appears for scripts that have not undergone the formal <a href="https://support.google.com/googleapi/answer/6158841?hl=en">Google Workspace Add-on verification process</a>. Even with a verified brand, simple web apps may still trigger it if they are not published as official Add-ons. Limitations and Technical Challenges CSS/JavaScript Blocking: You cannot hide the banner by adding CSS like <code>display: none</code> directly to your Apps Script HTML file. Google hosts the banner in a parent frame with a different origin, and browser security policies (<a href="https://stackoverflow.com/questions/33635284/google-apps-script-remove-warning-banner">Same-Origin Policy</a>) prevent your script from interacting with or hiding elements in that parent frame. Browser Extensions: While browser extensions can hide the banner locally for a specific user, this will not remove it for external clients or visitors to your web app. Executive Recommendation For a professional, "white-label" experience: Use a Google Workspace Business or Education account to host the script for internal users. For public-facing apps, embed the script into a parent website or Google Site to mask the standard Apps Script header. Ensure your script is associated with a <a href="https://developers.google.com/apps-script/guides/projects">Standard Google Cloud Project</a> rather than a default project to improve brand credibility. Are you building this app for internal team use or for external clients? To remove the "This application was created by a Google Apps Script user" banner, you must transition from a personal script to a Google Cloud Project (GCP) with an OAuth consent screen that has been verified by Google. Phase 1: Create a Standard Google Cloud Project By default, Apps Script uses a "Default" project that triggers the warning. You need to link it to a manual project. Open your script at google.com. Go to Project Settings (gear icon). Under Google Cloud Platform (GCP) Project, click Change project. Enter the Project Number of a project you created in the <a href="https://console.cloud.google.com/">Google Cloud Console</a>. Phase 2: Configure the OAuth Consent Screen The banner acts as a safety warning for unverified developers. To lift it, you must identify your "app." In the GCP Console, go to APIs & Services > OAuth consent screen. Select External (if you want people outside your workspace to use it) or Internal (for Google Workspace users only). Fill out the required App Information: App name: The name users will see. User support email: Your email. Developer contact info: Your email. Add the Scopes your script uses (e.g., <code>https://googleapis.com</code>). Phase 3: Verification (The Critical Step) The banner will only disappear once Google trusts the application. For Internal Apps: If you are a Google Workspace user and set the app to "Internal," the banner usually disappears immediately for members of your organization. For External Apps: You must click Submit for Verification. Google will review your privacy policy and terms of service. Once approved, the "unverified app" warning and the footer banner are removed. Quick Workarounds If you cannot go through full verification: Google Workspace: Deploy the script within a managed organization. If the script and the user are in the same domain, the banner is often suppressed. Web App URL: Ensure you are using the <code>/exec</code> URL and not the <code>/dev</code> URL, as the development mode always shows debugging headers. Custom Domain: Embedding the script in a site via an <code><iframe></code> can sometimes hide the footer, but it may still appear if the user interacts with a Google-hosted UI element. 💡 Note: Google keeps this banner as a security measure to prevent phishing. If your script is for public use, verification is the only official way to remove it. If you tell me more about your setup, I can help further: Using a personal Gmail or Workspace account? Targeting internal colleagues or public users? Linking to a Google Form or a Web App? There is no direct "off" switch to remove the "This application was created by a Google Apps Script user" banner from a standard web app, as it is a built-in security measure by Google . However, you can bypass or hide it using several workarounds depending on your environment. 1. Embed the Web App in an Iframe The most common way to hide the banner is to host your own HTML page (on GitHub Pages, for example) and embed the Apps Script web app URL inside an "YOUR_WEB_APP_URL" "width:100%; height:100vh; border:none;" Use code with caution. Copied to clipboard : Ensure your script allows iframing by setting the XFrameOptionsMode javascript HtmlService.createHtmlOutputFromFile( ) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); } Use code with caution. Copied to clipboard 2. Publish as a Workspace Add-on If you publish your script as a verified Google Workspace Add-on , 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 If you are part of a Google Workspace organization, the banner is to other users within the same domain. If your intended audience is internal to your company or school, simply deploying it to your organization will solve the issue. 4. Client-Side Browser Extensions (For Personal Use) If you only want to hide the banner for yourself, you can use browser extensions like uBlock Origin or a custom CSS injector to set the warning element's display to CSS Selector #warning display: none !important; GitHub Pages site to host the iframe for your application? AI responses may include mistakes. Learn more <hr> <h3>Myth 4: Paying for a Google Workspace account removes it</h3> No. Even paid Workspace accounts see the warning for external apps. Only internal trust (domain-level) removes it. <hr> <h3>4.3 Embedding in Google Sites (New Experience)</h3> Google Sites (the modern version) can embed a GAS web app via an “Embed” URL block. When embedded, the surrounding Site interface does not display the Apps Script footer inside the embedded pane, though it appears briefly during initial load. Process: <ol> <li>Deploy your GAS web app as “Execute as me” with access to “Anyone”.</li> <li>In Google Sites → Insert → Embed → By URL → Paste your GAS URL.</li> <li>Adjust height/width to hide the small footer offset (e.g., set iframe height to cover it).</li> </ol> Result: The footer is visually clipped or appears outside the viewport, effectively hidden without code modification. This is the simplest zero-infrastructure solution. <h3>3. Accept the limitation</h3> The banner is not a bug — it's a deliberate security feature by Google. End users will always see a disclaimer when running unverified or user-created scripts. <h3>Step 5: Wait and respond</h3> Google will email you with questions or approval. Once approved, your OAuth consent screen will show a checkmark (“Verified”). Your users will then see a clean permission dialog without the “created by a Google Apps Script user” warning. <hr> <h2>Part 7: Common Mistakes That Prevent Removal</h2> Even after verification, many developers fail to remove the warning because of these errors: | Mistake | Why It Fails | |---------|---------------| | Using default GCP project | Cannot be verified. Must use your own project. | | Privacy policy missing or invalid | Google rejects verification. | | Sensitive scopes not justified | Vague descriptions cause rejection. | | App still deployed under old version | You must create a new deployment after verification. | | Access set to “Only myself” | External users won’t see the verified status. | | Using <code>@gmail.com</code> as owner | Verification is impossible. | <hr> <h3>For Google Workspace Apps (Gmail, Google Drive, etc.)</h3> <ol> <li> Check App-Specific Settings: Some Google Workspace apps have settings that allow developers to add notices or disclaimers. Review the settings of the app in question. </li> <li> Contact the Developer or Google Support: 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. </li> </ol> For Google Workspace Apps (Gmail

Save up to 85% On All Software! Limited Time Offer

Remove This Application Was Created By A Google Apps Script User -