In its Oct. 9, 2026 weekly recap, Google said it is now rolling out the previously announced secondary calendar lifecycle change for non-personal Workspace accounts. When a user account is deleted, any secondary calendars owned by that user will be deleted as well.

Many small firms run their scheduling on shared Google calendars that one person happened to create. Examples include "Dispatch," "Truck 3," "Office PTO" and "Court dates." That person owns the calendar. Under this change, deleting their account deletes the calendar for everyone. Take an 18-person plumbing company where a former office manager built the "Dispatch" calendar. Assume it holds about 250 booked jobs for the next six weeks. If IT deletes her account during offboarding, those 250 entries disappear from all 6 techs' phones. Rebuilding them from invoices and texts at about 2 minutes each takes roughly 8 hours, and some appointments will be missed. Any business on Google Workspace that uses shared calendars should care, especially if the calendar's creator has left or might leave. Personal Gmail users are not affected. Businesses on Microsoft 365, or businesses that schedule only inside ServiceTitan, Jobber or Housecall Pro, can ignore this.

On Oct. 9, 2026, Google said the October release for Workspace Studio adds nested conditionals, a Gmail "skip replies" option for thread triggers, richer Meet and Calendar outputs (including full invitee lists), and a Drive step that searches for a document. Rollout starts Oct. 13 and takes up to 15 days, and the features are on by default for all Workspace customers who have Studio.

This is a no-code tool that comes with Workspace, so the change costs nothing extra; the question is whether it replaces work you pay a second tool or a person to do. The two features that matter most are "skip replies" and nested conditions. Take a 15-person accounting firm with a shared intake inbox that gets 40 new client emails a day, with about 3 replies per thread. A flow triggered on Gmail threads that files a Drive folder or creates a task can fire on every reply, up to 160 runs a day instead of 40, which leaves staff about 120 duplicates to clean up. Skip replies stops that at the trigger. Nested conditions let one flow sort by client type and then by document type, in place of four separate flows. Who should care: Workspace shops that already route email into Drive or tasks. Who can ignore it: Microsoft 365 shops, and anyone whose email routing lives in a practice-management or field-service app. Because the features are on by default, admins who do not want staff building flows should check their Studio policy for the domain or org unit.

On Oct. 9, 2026, Zapier reported that file links on its storage domain, zapier-dev-files.s3.amazonaws.com, may be blocked or show a security warning because Google Safe Browsing has flagged the domain as a dangerous site. Zapier says Forms and Tables users are most affected and Zaps continue to run, and as of its 21:20 UTC update it was waiting for Google to confirm the issue is fixed.

Most owners can ignore this. If your Zaps only move data between apps and nobody clicks a Zapier-hosted file link, nothing changes. It matters if you collect uploads through Zapier Forms or store files in Zapier Tables.

Example: a 14-person plumbing shop uses a Zapier Form for quote requests, and customers attach photos of the leak. A Zap emails the dispatcher a link to each photo. On Oct. 9 those links open to a red Chrome warning. Assume 20 requests a day and 3 minutes per request to text the customer for the photo again. That is 1 hour a day, about $35 at $35/hr. The Zap still runs and the submission is still recorded.

The bigger risk faces customers. If a Zap emails customers links to Zapier-hosted files, such as an estimate PDF, they see a 'dangerous site' warning on an email with your name on it. Zapier says server-side file access is not affected in the same way. A Zap step that copies the file to Google Drive, or attaches it directly, is a likely workaround. Do not train staff to click past the warning.

In an Oct. 7, 2026 post, Microsoft said Copilot on Windows will be able to use local context from a PC and take actions on the user's behalf, "with your permission." The same post says Microsoft Execution Containers, which let an organization set which files and networks an AI agent can reach, are now generally available on Windows 11.

Microsoft's post gives no price, no plan requirement and no ship date for the Copilot file features; a news report quotes a Microsoft executive saying "the next couple months." The effect on most shops this month is small. Take a 14-person accounting firm with 10 Windows 11 PCs where one admin spends about 3 hours a week finding and sending client documents. If an assistant halved that, the firm would get back about 78 hours a year, roughly $2,340 at $30/hr. That upside is unproven. The risk is an assistant that can read local folders and draft emails attaching the wrong client's file. Firms that keep client tax, legal or payroll files on desktops should care most. Trades shops whose job files live in a field-service app can mostly ignore this for now.