Gemini now writes Apps Script for staff: what NZ admins should set

By DataForge team17 November 20265 min read

Google's Gemini side panel for Apps Script reached general availability on 12 November 2026. Here's what NZ Workspace admins should set before staff use it.

What Google released

On 12 November 2026, Google began a gradual rollout of the Gemini side panel in the Apps Script editor as a generally available feature, according to the Google Workspace Updates announcement. A staff member describes an automation in plain language, Gemini writes the script, and the person reviews the suggested code block by block before saving. The panel can add time-based triggers. A "Fix errors" option in the execution log explains a runtime failure and proposes a change. Google allows up to 15 days for the panel to appear in both Rapid Release and Scheduled Release domains, so most New Zealand Workspace tenants should have it before the end of November.

Some people have had the panel for months. Gemini first appeared in the Apps Script editor in August, but only for Gemini Beta users and paid consumer AI plans, as Apps Script Pulse reported at the time. The November release extends access to Business Standard and Plus, Enterprise Standard and Plus, Google AI Pro for Education and the AI Expanded Access add-on. Google's developer guide for the panel still calls the feature a beta and says suggested changes have to be accepted or rejected as a whole. The documentation is behind the announcement, so admins should check how the panel behaves in their own tenant instead of relying on the guide.

Why a script writer inside Sheets matters to operations

Many Google Workspace organisations already run Apps Script quietly in the background. A finance officer who wants overdue invoice reminders emailed from a spreadsheet every Monday could always build that in Apps Script if they could write JavaScript. Most staff can't, so small jobs like that either joined the IT queue or never got built. With Gemini in the editor, anyone on an eligible licence can open Extensions, then Apps Script, from a Sheet, Doc or Slides file and ask for the automation in a sentence. We expect the number of small, person-built automations in Workspace tenants to rise quickly.

Google says the generated scripts run with the user's existing permissions and standard OAuth consent. Under that design, a script can't see more than the person who authorised it. The weakness is that many staff have broad access. A script authorised by someone in accounts can read the shared finance folders, send email in that person's name and keep running on a timer long after its author has forgotten it exists. The August Apps Script Pulse article raised the same concern: staff may run generated code without understanding its logic or the permissions it requests, particularly when Gmail or Drive is involved.

Ownership is where we expect NZ firms to run into trouble first. Apps Script projects belong to individual accounts. When the person who built a weekly supplier report leaves and their account is suspended, the job can stop without anyone noticing, because nobody else knew the job existed. Generated scripts will add more automations like the supplier report, and more of them will be written by people who've never maintained code.

Data residency is a separate issue for organisations with contractual or sector obligations. In September, Google added data region support to Apps Script, keeping project files, triggers and stored values in the designated region for Enterprise Plus and Frontline Plus editions, according to the Apps Script release notes. The developer guide says plainly that the Gemini side panel "does not support regionalization". The guide also doesn't explain how prompts and script context are handled once they reach Gemini. Until Google publishes that detail, staff shouldn't paste customer records or other personal information into a prompt.

The admin controls Google points to

The announcement lists the controls Google expects admins to use. Access to the panel can be limited by organisational unit or group. OAuth app access controls and external URL allowlists decide which data and services a script can reach. Drive and OAuth audit logs show what scripts are doing. Google's admin page on controlling which apps access Workspace data explains the options in more detail. Admins can mark each app as Trusted, Specific Google data, Limited or Blocked, and can set a separate policy for apps that haven't been configured. Restricting Drive cuts off untrusted apps from the scopes Google classes as high risk, and that list includes Apps Script scopes such as script.projects and drive.scripts.

The same page describes a "Trust internal apps" option that lets apps built inside the organisation use restricted Workspace APIs. Admins should check whether that option is on in their tenant, because the setting affects how far an internally built automation can reach once Gemini makes building one easy. Few small and mid-sized firms have reviewed these settings since they first set up Workspace, and the generated-script rollout is a good reason to look at them now.

What NZ businesses should do this month

Most of the work is configuration and housekeeping, and the rollout window gives admins roughly two weeks to finish it.

  • Decide who gets the panel first. Use the organisational unit or group setting to start with a small pilot group of staff who already understand the data they work with, and widen access once the controls below are in place.
  • Review app access settings. Check the Trust internal apps option, the policy for unconfigured apps and whether Drive and Gmail are restricted. Write down why each setting is on or off so the next admin doesn't have to work it out again.
  • Build a register of scripted automations. Use the Drive and OAuth audit logs to find existing projects, then record the owner, the data each script touches, any trigger schedule and who takes over when the owner leaves. Add a step to the staff offboarding checklist that checks the register.
  • Set a prompt rule. Tell staff not to paste personal or commercially sensitive information into the panel until Google documents how the panel handles that data, keeping New Zealand Privacy Act obligations in mind.
  • Require a second look for risky scripts. A script that sends external email, deletes files or changes financial figures should be reviewed by someone other than its author before its trigger is switched on.
  • Decide when a script should move. When a generated script becomes something the business relies on, move it onto a managed workflow platform with logging, shared ownership and alerting.

Gemini in Apps Script will help with many small, repetitive tasks, and staff can now automate work that previously wasn't worth an IT ticket. The risk comes from scripts that nobody owns and that have more access than they need. Firms that want help deciding which automations belong in Apps Script and which belong on a managed platform can see our process and automation work, and our AI consultancy page covers policy for staff use of AI tools.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS