English edition · cyberattaques.org in FrenchFrançais
IT news

Gemini side panel in Google Apps Script reaches general availability in Workspace

Google has made the Gemini side panel in Apps Script generally available, letting users generate, edit and debug scripts by describing tasks in plain language. Workspace administrators are affected because staff without coding skills can now build automations that touch Gmail, Calendar, Sheets and Docs.

What to do now Illustration photo (office automation spreadsheet)

Google announced on 16 November 2026 that the Gemini side panel in Apps Script is now generally available, following a public beta earlier in the year. Apps Script is the scripting environment reached from Sheets, Docs, Slides and Forms through the Extensions menu, used to automate work and connect Workspace services.

With the assistant, a user describes a task in everyday language and Gemini writes the code. Google's examples include creating Calendar events from urgent Gmail messages, pulling and cleaning data into spreadsheets, and turning Sheets tables into formatted Docs reports. Gemini takes the files in the open project into account and can add features such as time-based triggers on request.

Suggested changes appear block by block in the editor, where users can accept or reject individual blocks or all suggestions at once before saving. When a script fails at runtime, a fix button in the execution log asks Gemini to diagnose the error.

For IT teams, the significant change is that far more people will be able to produce working scripts. Google states that scripts run with the user's existing permissions and go through standard OAuth consent, and that administrators keep visibility and control from the Admin console. The source does not specify which Workspace editions are included, the rollout schedule, or the exact admin settings used to enable or restrict the feature.

Action plan

What to do now

  1. Review the Admin console settings that govern Apps Script and Gemini in your organisation and decide who should have access to the assistant.
  2. Check your third-party app access and OAuth consent policies, since generated scripts rely on that mechanism and on users' own permissions.
  3. Tell users that scripts act with their author's rights and that proposed code should be read before it is accepted.
  4. As general good practice, monitor new Apps Script projects and automatic triggers created in your domain once the feature is in use.

Sources