Four New Steps Landed in Workspace Studio, and I Am Opening the Reply Ones a Week Later

I read the announcement on a morning when I was pulling together the monthly report for a client site I look after. Four new steps in Workspace Studio: copy a Drive file, move a Drive file, reply in Chat, reply to an email. All four sounded useful, and my first reaction was simple relief.

What stopped me, though, was not the feature list. It was the rollout table, where the admin controls and the features have different dates — and where Drive/Chat and Gmail each get their own pair of dates.

That table is what made me decide not to open all four on the same day.

Four steps, but two different characters

Here is what arrived, laid out by date. The schedule comes from the Google Workspace Updates post published on September 2, 2026.

The steps reach Business Starter, Standard and Plus, Enterprise Standard and Plus, and the Education tiers, and they are on by default if Gemini for Google Workspace steps are allowed. Admins get switches to disable individual steps, and a setting that requires end-user approval when an action might share data outside the organisation.

Line them up and the four look like siblings. To me, the first three and the last one are not the same kind of thing at all.

There is a week where the admin settings arrive before the feature

Look at the dates once more. For Drive and Chat, admin controls start September 1 and the feature starts September 8. For Gmail, admin controls start September 8 and the feature starts September 14. In both cases the admin side runs roughly a week ahead.

It may read as backwards, but I take it as deliberate breathing room. Before anyone in the organisation can build a flow with these steps, there is a window in which the policy can already be settled.

For a long time I treated new features as something to think about once they showed up. That did not serve me well. By the time I went looking for the setting, someone had already tried the feature, and switching something off afterwards costs more than never switching it on. Now, on the day I read an announcement, the date I put in my calendar is the admin-control date, not the feature date.

I decide the order by what I can undo, not by what looks useful. That single line is the whole reason I split these four into two groups.

Copy and move stay inside my own house; replies go outside

Copying and moving in Drive stays within my own storage. If a file lands somewhere I did not intend, I move it back. A Chat reply in an internal space is much the same — I can post a correction in the very next message.

Replying to email is different. It goes into an existing thread, under my name, into someone else's inbox. When I picture explaining afterwards that the message was automated, I feel it in my stomach. With a client I work with regularly, more so.

So the three Drive and Chat steps went live for me in the week of September 8, and Reply to email is parked until after September 14. While it waits, I only need to settle two things: where the approval setting for outside-the-organisation actions actually lives, and whether I can write down, in my own words, which threads may be answered automatically.

Until I can write that condition down, the step stays closed. Anything I cannot put into a sentence will not survive as a flow condition either.

Before the move step, I look at the destination folder's sharing

There is one behaviour worth confirming before you point Move Drive file at a folder. When a file moves between shared folders in My Drive, the permissions it inherited from the old folder are removed and it inherits the permissions of the new one. Permissions set directly on the file survive; the folder-derived layer is swapped.

An automated move, in other words, does not only tidy your storage. It can change who is able to open the file. When I carried files by hand I would remember that a folder was shared. A flow remembers nothing.

So before a folder goes into a flow as a destination, I dump its sharing state once with Apps Script.

/**
 * Inventory the folders you plan to use as destinations
 * for the Workspace Studio Move / Copy steps.
 * Logs each folder's sharing scope and the people shared with directly.
 */
function listDestinationSharing() {
  // IDs of the folders you intend to point a flow at
  const FOLDER_IDS = [
    'DESTINATION_FOLDER_ID_1',
    'DESTINATION_FOLDER_ID_2',
  ];
 
  FOLDER_IDS.forEach((id) => {
    let folder;
    try {
      folder = DriveApp.getFolderById(id);
    } catch (e) {
      // Typos and missing access surface here, where they are easy to see
      Logger.log('SKIP %s : %s', id, e.message);
      return;
    }
 
    const access = folder.getSharingAccess();         // PRIVATE / DOMAIN / ANYONE ...
    const permission = folder.getSharingPermission(); // VIEW / EDIT / NONE
    const editors = folder.getEditors().map((u) => u.getEmail());
    const viewers = folder.getViewers().map((u) => u.getEmail());
 
    Logger.log(
      '%s | access=%s(%s) | editors=%s | viewers=%s',
      folder.getName(),
      access,
      permission,
      editors.length ? editors.join(', ') : '(none)',
      viewers.length ? viewers.join(', ') : '(none)'
    );
  });
}

I read one line per folder. If access is anything other than PRIVATE, or if an address I do not recognise sits in the editors list, that folder does not become an automated destination. The judgement takes about ten seconds. Whether or not you spend those ten seconds decides whether a half-day of tracing sharing history happens later.

If a step has not appeared in your own domain yet, telling waiting apart from a real fault is the piece I would read next. If the concern is narrowing what Gemini can reach in the first place, the setting that keeps Gemini out before you unshare anything is closer to the point.

Chat replies now accept Markdown

Send a Chat reply gained Markdown support, so bold text, lists and code blocks come through as written. As an indie developer running a few sites, my first instinct was to pipe monitoring output straight into a space.

Being able to paste and being read are two different things, though. Even for notifications only I will see, I settled on one line of conclusion first and the detail down in the thread. Code blocks widened what I can paste, and by the same amount they widened what I need to decide not to paste.

Markdown improves how text looks, not how much attention a reader brings — an obvious thing I still managed to half-forget.

One step for today

Go and look at two things in the admin console: the toggles for the four steps, and where the approval setting for outside-the-organisation actions sits. Building the flow can wait. Reply to email does not start rolling out until September 14, so the time you have right now is time to look rather than build.

Three of the four are already part of my week; the fourth is waiting until next week. If that ordering saves someone else a few minutes of deliberation, I am glad to have written it down.