65 Apps Script / add-on / AI-agent governance

Caveats

• Blocking Apps Script does not remove already-authorised script triggers¹
• Apps Script on/off and per-app blocking work on all editions²
• The API-controls half is the same screen as №8 and №9³

Setup steps

1. open ↗

   

   https://admin.google.com/ac/appslist/additional · captured 2026-07-15

   Apps › Additional Google services › Google Apps Script ↗

   Set Apps Script service status per OU (organizational unit) — off by default, on only for the OU that actually builds automation.

   Service status = Off for everyone; On for the automation OU

   Turn Apps Script on or off for users ↗

2. open ↗

   

   https://admin.google.com/ac/owl/settings · captured 2026-07-15

   Security › Access and data control › API controls › App access control ↗

   Restrict Apps Script to organisation-owned projects via App access control: with unconfigured third-party apps blocked (next step), enable Trust internal apps so only organisation-owned script projects keep working.

   Trust internal, domain-owned apps = On (organisation-owned scripts allowed; external/unknown scripts fall under the unconfigured-apps block)

3. Security › Access and data control › API controls › App access control ↗

   Set unconfigured third-party apps (which includes new add-ons and agent integrations) to "Don't allow users to access any third-party apps" on the Settings tab, then allowlist by client id in the configured-apps list (№8).

   Settings: Unconfigured third-party apps = Don't allow users to access any third-party apps; Manage third-party app access: trusted apps added explicitly (№8)

   Control which apps access Google Workspace data ↗ Control which third-party & internal apps access Google Workspace data ↗

4. open ↗

   

   https://admin.google.com/ac/owl/domainwidedelegation · captured 2026-07-15

   Security › Access and data control › API controls › Domain-wide delegation ↗

   Review the domain-wide delegation (DWD) client list (№8 audits the same register) — a delegated service account bypasses per-user consent entirely and is the most dangerous 'add-on' of all.

   Remove any client id without a named owner and a justified scope list

   Control API access with domain-wide delegation ↗

Ongoing maintenance

• automatable: AI agent Monthly: review newly created Apps Script projects and add-on grants against the register.

How to verify

1. From a test account, run a script that calls a restricted API/scope — the consent or execution must be refused per the policy.