google-workspace-ops

To edit Google Workspace assets without exporting, use Drive as the unified entry point to locate files, segment them by Docs, Sheets, or Slides, and apply changes directly using the respective editing tools for each format.

Yes, you can find and update shared documents across teams by searching Drive to locate collaborative assets, then applying sequential steps to inspect and edit cross-file updates safely without manual file-by-file processing.

Cleaning up Google Drive assets involves searching Drive for target files, segmenting them by type—Docs, Sheets, or Slides—and applying safe editing or removal steps to consolidate shared documents without dropping to raw tool calls.

Yes, handling cross-file updates safely is a core mechanism; it segments assets by Docs, Sheets, and Slides from Drive, applying sequential steps to locate, inspect, and edit so updates across files remain coordinated.

No, you do not need raw API tool calls to track project progress or assemble decks; the workflow operates Google Slides and Sheets directly as a unified surface, abstracting raw tool calls into sequential editing steps.

The primary limitation is that Google Workspace asset management requires using Drive as the entry point and segmenting by Docs, Sheets, and Slides; assets outside Drive or requiring formats beyond these three cannot be processed.