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

Google places scopes into three categories:

When deploying, select and change it from Anyone to Anyone within [Your Company Name] .

Are you building this app for or for external clients ?

: Include your own footer with copyright data, support links, and terms of service to show users the application is actively maintained. Google places scopes into three categories: When deploying,

For commercial applications or polished presentation layouts, the definitive development standard is with a full-window iframe targeting the script execution node. This respects Google's background sandboxing architecture while providing a custom, banner-free UI to your user base. To figure out your next steps, let me know: Who is the target audience for your web app? Where do you plan to host or display the application? AI responses may include mistakes. Learn more Share public link

However, if you are building an internal tool for your company or a polished client-facing application, this prominent footer or header can break your branding, look unprofessional, and confuse your users.

If you are a Google Workspace administrator and your application is intended for internal use only, you can remove the warning without going through the full, formal verification process. Google's policy states that verification is for Apps Script projects whose owner and users belong to the same Google Workspace domain or customer. Where do you plan to host or display the application

Troubleshooting tips (2–3 bullets): common pitfalls and fixes.

Configure your inside the GCP console, uploading your own branding and logos.

When you deploy a Google Apps Script project as a , Google shows a security/permission screen before the app runs. One of the lines often displayed is: Configure your inside the GCP console

The banner automatically hides if the user viewing the app belongs to the exact same Google Workspace enterprise domain as the script creator.

While the banner technically still exists inside the execution environment, embedding it inside a styled container on your own domain masks the default Google wrapping interface, making it look like an integrated part of your website.

While this method is highly effective for internal tools, it does not resolve the issue for external users outside your organization.