GAS Project Creator

Setup tool for creating and configuring Google Apps Script projects

Setup & Configuration

Include Google Authentication (adds sign-in gate to both GAS & HTML — unchecked = no auth, open access)

Google Account Setup
Enable the Apps Script API at script.google.com/home/usersettings
Create or use a GCP project where you have Owner access. If you don't have one, create a new project at console.cloud.google.com
Enable the Apps Script API in your GCP project
APIs & Services → Library → search "Apps Script API" → Enable
OAuth Setup (Auth Only)
Configure the OAuth consent screen in your GCP project
APIs & Services → OAuth consent screen → User Type: External (or Internal for Workspace) → fill in app name and support email → Add scopes: email, profile, openid
Create an OAuth 2.0 Client ID (Web application type)
APIs & Services → Credentials → + Create Credentials → OAuth client ID → Application type: Web application → Authorized JavaScript origins: add your GitHub Pages URL (e.g. https://yourusername.github.io) → Create

Copy the Client ID (ends in .apps.googleusercontent.com). You’ll paste it in the Auth Settings section below.
New Apps Script Project
Create a new Apps Script project via Google Sheets (recommended): open a new or existing Google Sheet → Extensions → Apps Script. This creates a script linked to that spreadsheet, which is needed for version-tracking features.
Alternatively, for a standalone script (no spreadsheet link), create one at script.google.com
GAS Project Settings
In Project Settings, enable Show appsscript.json manifest file
Project Settings → General settings → Show “appsscript.json” manifest file
Link the GCP project in Apps Script
Project Settings → Google Cloud Platform (GCP) Project → Change project
Potential Troubleshooting: “You cannot switch to a Cloud Platform project in an Apps Script-managed folder”
This error means your GCP project ended up inside Google’s hidden apps-script managed folder. Even projects you created manually can land there on Workspace accounts.

How to diagnose
1. Go to Manage Resources
2. Look for: your org → system-gsuite → apps-script
3. If your project is inside that folder, that’s the problem
Fix — Option A: Move the project

Requires the Project Mover IAM role — you likely don’t have it by default, even as org owner/admin.
1. Go to IAM & Admin → use the top dropdown to select your organization (not a project)
2. Click Grant Access → enter your own email
3. Select role: Resource Manager → Project Mover → Save
4. Go to Manage Resources → find your project in the apps-script folder
5. Three-dot menu → Migrate → move to org root or “No organization”
6. Retry changing the GCP project in Apps Script settings
Fix — Option B: Create a new project
1. Go to Google Cloud Console → create a new project
2. Set Location to your org root or “No organization”
3. Verify the project number does not start with sys-
4. Enable the Apps Script API in the new project
5. Use this project’s number in Apps Script settings
Set Script Properties in your Apps Script project
Project Settings → Script Properties → Add the following properties:

GITHUB_TOKEN — your fine-grained personal access token

Note: CACHE_EPOCH are auto-generated/distributed on first deploy — no manual setup needed.

To create a token: GitHub.com → Settings → Developer settings → Fine-grained tokens → Generate new token. Under "Repository access" select Public repositories (read-only). No additional permissions are needed. Copy the github_pat_... value.

Reuse across projects: The same token works for all your GAS projects — you don't need a new one per repo. Just paste the same token into each project's Script Properties. Note: GitHub only shows the token once at the time of creation and permanently hides it afterward — save it somewhere secure before closing the page.
GAS Editor

Set the appsscript.json manifest contents to:

{
  "timeZone": "America/New_York",
  "runtimeVersion": "V8",
  "dependencies": {},
  "webapp": {
    "executeAs": "USER_DEPLOYING",
    "access": "ANYONE_ANONYMOUS"
  },
  "exceptionLogging": "STACKDRIVER",
  "oauthScopes": [
    "https://www.googleapis.com/auth/script.projects",
    "https://www.googleapis.com/auth/script.external_request",
    "https://www.googleapis.com/auth/script.deployments",
    "https://www.googleapis.com/auth/spreadsheets",
    "https://www.googleapis.com/auth/script.send_mail",
    "https://www.googleapis.com/auth/script.scriptapp"
  ]
}

Deploy #1 — Create the Web app deployment
Deploy → New deployment → Select type: Web app → Execute as: Me → Who has access: Anyone

Copy the Deployment ID (starts with AKfycb...). You’ll need it for the config below.
Fill in your project values below (paste the Deployment ID from step 9) and copy the configured Code.gs
Paste this code into your Apps Script project, replacing the existing code

Deployment ID (required)
From Apps Script: Deploy → Manage deployments — required before using Test GAS Connection, Copy, or GAS Preview 💡 If the GAS preview shows “Script function not found: doGet”, the deployment ID is valid — proceed with entering your other fields, then copy Code.gs for GAS into the Apps Script editor

Project Configuration

Project Environment Name (required)
Base name for all project files — e.g. test creates test.html, test.gs, html-versions/testhtml.version.txt, etc.

Title (optional)
Shown in browser tab and GAS UI

Spreadsheet ID (optional)
Google Sheets ID for version tracking

Sheet Name (optional)
Tab name in the spreadsheet

Sound File ID (optional)
Google Drive file ID for notification sound

Splash Logo URL (optional)
Logo shown on the GAS splash screen

Authentication Settings

OAuth Client ID (required for auth)
From Google Cloud Console → APIs & Services → Credentials → OAuth 2.0 Client ID (Web application type)

Auth Preset Controls session duration, security features, and token exchange method. See 6-UNIFIED-TOGGLEABLE-AUTH-PATTERN.md for details

Allowed Domains (optional)
Comma-separated list of allowed email domains. Leave blank to allow all Google accounts. Required for HIPAA preset

Master ACL Spreadsheet (optional — centralized access control)
This project’s spreadsheet is the master ACL (uses the Spreadsheet ID above as the centralized access control sheet for all projects)
Master ACL Spreadsheet ID
A single spreadsheet that controls access to all GAS-powered pages. Row 1 = headers (Email, page1, page2, ...), rows 2+ = email + TRUE/FALSE per page. Leave blank to use the legacy editor/viewer sharing-list check on the data spreadsheet

ACL Sheet Name
The sheet tab name in the master ACL spreadsheet where authorized emails are listed

ACL Page Name
The column header in the ACL sheet that identifies this page. Defaults to the Environment Name if left blank

Include test/diagnostic features (sound, quotas, sheet embed, buttons — for verifying Google connections, not production use. Unchecked = minimal: version display + auto-update only)
In the Apps Script editor, replace all contents of Code.gs with the copied code
Run any function from the Apps Script editor to trigger the initial OAuth authorization prompt
This ensures the script has all required permissions before the final deployment
Deploy #2 — Update the deployment with the new code
Deploy → Manage deployments → Edit (pencil icon) → Version: New version → Deploy

Why two deploys? Deploy #1 creates the deployment URL and gives you the Deployment ID. But the code you pasted in step 10 needs that ID to auto-update itself. Deploy #2 pushes the code (now containing the real Deployment ID) to the live deployment with all OAuth permissions granted. After this, all future updates are automatic — pushes to GitHub trigger the GAS to pull and redeploy itself.
GAS Triggers
(Optional) If using an installable trigger for sheet caching:
Apps Script editor → Triggers → + Add Trigger → Function: onEditWriteB1ToCache, Event source: From spreadsheet, Event type: On edit

GAS Project Creator

How to diagnose

Fix — Option A: Move the project

Fix — Option B: Create a new project