Secure distribution of Google Sheets templates with Apps Script — OAuth verification

Subject: Secure commercial distribution of a Google Sheets template with Apps Script — OAuth verification and simple triggers

Hello Google Apps Script Support Team,

I’m developing a personal finance management system in Google Sheets, intended for commercial distribution as independent spreadsheet copies.

The system uses a container-bound Apps Script project to process financial transactions, preserve transaction history, prevent duplicate entries, and update balances.

Our objective is to distribute a template that customers can copy into their own Google accounts and use independently, without requiring access to the developer’s account, external infrastructure, or ongoing subscriptions.

Problem encountered

We successfully tested the financial processing system in Google Sheets, including a checkbox-based transaction submission mechanism.

However, while preparing the template for independent distribution, we encountered the following Google security warning:

“This app isn’t verified by Google.”

The warning appeared during the authorization process associated with the function fpdPrepararModeloParaCopia.

We stopped the authorization process because we do not want to distribute a commercial product that requires customers to bypass security warnings.

We subsequently investigated distributing the functionality as a Google Sheets Editor add-on, but this introduced additional OAuth verification, Google Cloud configuration, and Marketplace distribution requirements.

Before investing further development time, we would appreciate clarification regarding the officially supported approaches.

Questions

  1. Can a commercial Google Sheets template include a container-bound Apps Script project that is automatically copied when a customer selects “Make a copy”?

  2. If the script uses only a simple onEdit(e) trigger and operations within the copied spreadsheet, can it execute without requiring the customer to authorize an unverified application?

  3. Can a simple onEdit(e) trigger reliably process a checkbox-based submission initiated through the Google Sheets iOS application?

  4. Are there specific restrictions or recommended design patterns for preventing duplicate transactions, handling concurrent edits, and ensuring reliable processing with simple triggers?

  5. If installable triggers are required, what is the recommended compliant distribution method for independent consumer accounts? Would OAuth verification or Google Workspace Marketplace publication be mandatory?

  6. Is there an officially supported approach for distributing this type of financial template commercially without requiring each customer to manually configure scripts, install triggers, or bypass security warnings?

  7. Are there any specific commercial-use, security, licensing, or distribution restrictions that we should consider?

The application does not require banking credentials or access to external financial accounts. Our goal is to keep each customer’s financial information within their independently owned spreadsheet.

We are willing to follow Google’s official verification or publication requirements if necessary. However, we would first like to determine the simplest supported architecture that is secure, reliable, and practical for individual customers.

Any references to official documentation or recommended implementation patterns would be greatly appreciated.

Thank you for your assistance.