Remove This Application Was Created By A Google Apps Script User

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 Google Cloud Console. Phase 2: Configure the OAuth Consent Screen To remove the "This application was created by

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. Method 2: Removing Google Workspace Add-ons If the

Add the Scopes your script uses (e.g., https://googleapis.com). 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. Open a Google Doc, Sheet, or Slide

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 /exec URL and not the /dev URL, as the development mode always shows debugging headers.

Custom Domain: Embedding the script in a site via an </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? To remove the "This application was created by a Google Apps Script user" banner, you generally need to embed your web app in an iframe on another site, or use a Google Workspace (paid) account to deploy it within your own domain. How to Remove the "Created by a Google Apps Script User" Banner If you’ve ever built a web app with Google Apps Script, you’ve likely seen that persistent blue or gray banner at the top of your page. While it serves as a security feature for Google, it can make your professional project look like a "test script." Here is the reality of how to handle it. 1. The "Free" Workaround: Use an iFrame The most common way to hide the banner without spending money is to embed your Apps Script web app into another website using an How it works: When the script is rendered inside an iframe on an external site, the banner is typically suppressed. You must update your script’s function to allow embedding: javascript HtmlService.createHtmlOutputFromFile( ) .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); } Use code with caution. Copied to clipboard Users have reported success embedding these apps into Google Sites , which often removes the warning for viewers. 2. The Professional Solution: Google Workspace The banner is a "price" of using the free consumer platform. If you use a paid Google Workspace account (Business or Education), you can deploy apps that don't show this warning to other users in your same domain. Internal Access: When you deploy and set access to "Anyone within [Your Domain]," the banner is removed for your colleagues. Verification: For apps intended for the general public, you must link your script to a standard Google Cloud Project (GCP) and go through the OAuth verification process to be recognized as a "verified publisher". 3. What Doesn't Work It is important to note that you cannot hide this banner using internal CSS or JavaScript within your script. Google intentionally isolates the web app in a different domain (e.g., googleusercontent.com ) to prevent your code from accessing the parent page's elements, including the banner itself. Summary Table: Removal Options Difficulty iFrame Embedding Hides banner on the host site Google Sites Often suppresses banner for viewers Workspace (Internal) No banner for users in your domain GCP Verification Removes banner for public users linking to a GCP project Google Apps Script remove warning banner - Stack Overflow The message "This application was created by a Google Apps Script user" is a mandatory security banner displayed by Google on web apps created with Google Apps Script. It is designed to alert users that the application was not created by Google and may request sensitive permissions. While there is no single button to "turn off" this banner for free consumer accounts, there are several methods to remove or bypass it depending on your environment. 1. Embed the Web App in a Google Site The most reliable "no-cost" way to remove the banner for external users is to embed your Apps Script web app into a Google Site. When a web app is viewed through an <a href="https://www.youtube.com/watch?v=6mLzzTVbNWU">iframe on a Google Site</a>, Google typically suppresses the author warning banner. Requirement: Ensure your web app deployment is set to "Anyone" or "Anyone with a Google Account" and that the site itself is shared with your target audience. 2. Use a Google Workspace Account (Internal Use) If you are developing for an organization, the banner is automatically hidden for users within the same domain. If you own a Google Workspace (Business, Enterprise, or Education) account and deploy the script so only "People within [Your Domain]" can access it, they will not see the banner. The warning only appears when the script is accessed by someone outside your Workspace organization or by a consumer (Gmail) account user. 3. Complete Google Cloud Project Verification For public-facing applications that cannot be restricted to a Workspace domain, the official way to remove security warnings is through Google Cloud verification. Process: You must associate your Apps Script with a standard Google Cloud Platform (GCP) project instead of the default "default" project. Outcome: Once your project is verified as a "Verified Publisher" by Google, the banner and "unverified app" warnings will disappear for all users. Note that this process can take several weeks and may require a security audit if you use restricted data scopes. 4. Technical Workarounds (For Personal Viewing) If you only need to hide the banner for yourself (e.g., on a public display or TV), you can use browser-based tools: Custom JavaScript Extensions: Extensions like "Custom JavaScript for websites" can be used to inject code that sets the CSS of the banner to <code>display: none;</code>. GitHub Solutions: Community-made plugins such as <a href="https://github.com/luanpotter/apps-script-remove-warning">apps-script-remove-warning</a> on GitHub are designed to auto-hide these elements in your browser. Note: These methods only hide the banner for you and anyone else who has the extension installed; they do not remove it for the general public. Comparison of Methods Complexity Google Sites Embedding General Public Workspace (Internal) Employees/Team Paid Account GCP Verification General Public Free (but time-intensive) Browser Extension <hr> <h3>Method 2: Removing Google Workspace Add-ons</h3> 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: <ol> <li>Open a Google Doc, Sheet, or Slide.</li> <li>Go to the top menu and click Extensions > Add-ons > Manage add-ons.</li> <li>A sidebar will appear listing your installed add-ons.</li> <li>Find the application in the list.</li> <li>Click the Manage button (usually a blue icon with a pencil or gear) and select Uninstall.</li> </ol> <h2>Part 10: Future-Proofing – How to Design Apps That Never Show the Warning</h2> The best long-term strategy is to design your Apps Script projects from the start to avoid the unverified warning. <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> <h3>Step 4: Submit for Verification</h3> Once your consent screen is saved: <ol> <li>Scroll to the bottom of the OAuth consent screen page.</li> <li>Click Submit for verification.</li> <li>Google will ask you to justify why you need sensitive scopes. Provide a clear, honest explanation.</li> <li>Wait for Google’s review. You will receive emails with approval or requests for changes.</li> </ol> <h2>Part 5: Quick Workaround – Remove the Message Without Full Verification</h2> If you cannot or do not want to go through verification, there is a non-official workaround for small, trusted audiences. <h3>If the Application is a Google Apps Script Project</h3> <ol> <li> Check the Script's UI Settings: If you're using a custom UI (like an HTML service), ensure that the notice isn't hardcoded into the HTML or the script's interface settings. </li> <li> Review Script Properties and Settings: Sometimes, Google Apps Script projects have project properties or settings that could be influencing the display of such notices. Make sure there's no setting or property that you're overlooking. </li> </ol>