OAuth verification is not required for Google Apps Script projects "whose owner and users belong to the same domain or Google Workspace organization". This means if everyone using your script is within the same Google Workspace account, you won't see the warning regardless of verification status.
Once you remove access, the next time you try to use that specific script, Google may ask you to re-authorize it. But the pop-up will no longer appear automatically.
Each scenario requires a different approach. Below, we cover .
For developers using a free version of Google Apps Script, this notice is intentionally challenging to remove. It is designed as a security and transparency feature. However, a clever, free, and purely technical workaround allows you to hide it completely without compromising your app's functionality.
Instead of serving HTML using HtmlService , configure your script to receive GET or POST requests and return data in JSON format using ContentService . javascript OAuth verification is not required for Google Apps
Fill out the app information, developer contact details, and add your official business branding. 4. Submit Your App for Verification
// Set XFrameOptionsMode to ALLOWALL to enable IFrame embedding html.setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL);
Not automatically. The warning is just a visual notice—it doesn't prevent the script from functioning. Users can still choose to proceed by acknowledging the risks and continuing with the authorization.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. But the pop-up will no longer appear automatically
Before attempting to remove the notice, it is important to understand why it exists. Google automatically attaches this disclaimer to any Web App or script-based UI that is not part of a verified Google Workspace domain or a published Google Cloud project. It serves as a warning to end-users that the application is third-party and not officially vetted by Google. Method 1: Upgrade to a Google Workspace Account
If you want to completely remove the message and not replace it with a custom title, you can use the following approach:
function doGet() return HtmlService.createHtmlOutputFromFile('Index') .setXFrameOptionsMode(HtmlService.XFrameOptionsMode.ALLOWALL); Use code with caution. Copied to clipboard
Enter the of your standard GCP project. (If you do not have one, go to the Google Cloud Console, create a new project, and copy the Project Number from the dashboard). Click Set project . Step 2: Configure the OAuth Consent Screen For developers using a free version of Google
Go to your Google Sites project, click Embed , paste the URL, and publish the site. 2. Self-Host with a GitHub Pages Wrapper
If you’ve built a Google Apps Script project and shared it with others, you may have noticed an authorization screen that says:
Sometimes users want to "remove this application" not just hide the warning, but completely revoke access for a third-party app they no longer trust.