Gemini now writes Apps Script for anyone with a Google Sheet. Read the permission screen before you click Allow
Twenty minutes after asking, the script works. Then Google shows a screen listing everything it wants to do with your account, and there's a blue Allow button at the bottom. That screen is the most important thing Gemini puts in front of you.

Gemini in the Apps Script editor became generally available on November 16, 2026, for Business Standard and higher Workspace plans, so anyone can describe a repetitive task and get a working script. The script runs with your own permissions once you approve Google's OAuth screen. Before you click Allow, check what it reads, what it changes and where it sends data, test it on a copy, and give anything with a trigger a named owner.
Twenty minutes, then the blue button
Picture an office manager at a small property firm. Urgent maintenance emails keep slipping past, so she opens the Apps Script editor from a Google Sheet and types what she wants: when an email marked urgent arrives, create a calendar event and add a row to the maintenance sheet. Google uses almost exactly that example, Calendar events from urgent Gmail messages, to describe the new feature. Gemini writes the code. She accepts the changes, clicks Run, and a screen appears.
It says the script needs her permission, and lists what it wants to do with her Google account. For a job like this, the list will include reading her email and changing her calendars and spreadsheets. At the bottom there's a blue Allow button.
That screen is the most important thing Gemini puts in front of her, and it's the one people read least.
What changed on November 16
Google made the Gemini side panel in the Apps Script editor generally available on November 16, after a beta earlier this year. Apps Script is the automation layer built into Sheets, Docs, Slides and Forms, under Extensions, then Apps Script. Until now, using it meant writing JavaScript. Google's announcement says anyone can now "create, customize, and troubleshoot scripts using plain language with no coding experience required."
Three parts do the work. You describe a task and Gemini writes the script, including time-based triggers if you ask. You review its changes block by block, accepting or rejecting each one. And when a run fails, a Fix errors button in the execution log has Gemini explain the problem and propose a change.
It's rolling out gradually from November 12, taking up to 15 days to appear. It's included with Business Standard and Plus, Enterprise Standard and Plus, the AI Expanded Access add-on, Google AI Pro for Education, and consumer Google AI Pro and Ultra. Business Starter isn't on the list. Google's guide adds a few practical limits: the panel only appears when your language is set to English or the default, it can misbehave if you're signed into several Google accounts in one browser, and it sometimes leaves out web addresses for security reasons, so you may need to give it the exact URL.
Gemini writes the script. The Allow button decides what it can touch.
Read the screen like a contract
Gemini writes the script. The Allow button decides what it can touch.
Google is clear about how this works. Scripts "run natively in Workspace with a user's existing permissions and standard OAuth consent," and the guide tells you to "review the requested permissions before clicking Allow." In other words, the script can do anything you can do, in the areas you approve. If you can read the finance shared drive, so can a script you've allowed to read your Drive.
Read the screen in three passes. First, what can it read: email, files, calendars, contacts? Second, what can it change: can it send, edit, create or delete? Third, where does it send things: does it connect to an outside service, and if so, which address and what data?
Then compare that with the job. A script that adds a row to one sheet shouldn't need to delete files. A script that tidies your own calendar shouldn't need to send email. When the list is wider than the task, ask Gemini to narrow it, or ask someone who knows Apps Script. Developers can go further and set the exact permissions in the project's manifest, which Google's scopes guide recommends for anything shared widely.
How the work moves
Read the Allow screen in three passes
- Reads
Which of your email, files, calendars or contacts can it see?
- Changes
Can it edit, send, create or delete anything, and does the task need that?
- Sends
Does it connect to an external service? Which address, and what goes there?
- Decide
Allow, ask Gemini to narrow the script, or stop and ask someone.
Before you click Allow
Test on a copy. Make a copy of the sheet, point the script at it, and let it run against real-looking data before it touches the real thing. That's especially true for anything that deletes rows, sends email or moves files.
Use the block-by-block review properly. Ask Gemini to explain each block in plain language before you accept it. If the explanation and the code don't match your request, reject it.
Treat Fix errors as a suggestion. It's a fast way to understand a failure. It's not a guarantee that the fix does what you meant, so run the copy again before you go back to the real data.
Write down what you approved. Add a comment at the top of the script saying what it does, who asked for it and which files it uses, and note the permissions you allowed. When someone opens it in six months, that note is the difference between a quick edit and an afternoon of reverse engineering. And check the Triggers page in the editor, so you know exactly what will run when you're not watching.
What happens after you go home
The risk with a script isn't the first run. It's the months after, especially if it runs on a trigger.
A daily trigger keeps running as the person who set it up. Someone renames a column and the script starts failing quietly at 6 a.m. A colleague copies it for another team. The person who clicked Allow moves to another job or leaves the company, and nobody remembers the trigger exists until something stops happening.
So give every triggered script a named owner and a line in a shared list: what it does, which files it touches, who to call when it breaks. If you're the Workspace admin, Google says the panel respects your existing Apps Script settings and your generative AI access controls. You can turn it on by organizational unit or group, control which apps can use OAuth access, limit outside addresses with an allowlist, and see script activity in the Drive and OAuth audit logs. It's worth deciding who gets it before everyone does.
Sequence of work
What happens after you click Allow
- Day 1
Tested on a copy, then switched to the real sheet with a daily trigger.
- Week 2
Someone renames a column. The script fails quietly at 6 a.m.
- Month 3
A colleague copies it for another team, with the same permissions.
- Month 9
The person who clicked Allow leaves. Nobody knows the trigger exists.
When a script should become something more
Plenty of jobs are perfect for a script: a weekly report, a reminder, a tidy-up. When a script starts carrying a process the business depends on, with several people, money or customer data in the loop, it's time to give it proper error handling, logging and an owner who isn't one person's account.
That step, from a useful script to dependable automation, is what our business automation work is for. Talk to us.
Related work: Spin:Market
We build alongside the people doing the work.
Bring us the problem you’re thinking about.