What Google Workspace Actually Is

This course assumes you already know Word, Excel, PowerPoint, and their LibreOffice equivalents. Rather than touring Docs/Sheets/Slides feature by feature the way the LibreOffice course toured Writer/Calc/Impress, this course focuses on what's genuinely, structurally different about Google Workspace — starting with the single biggest one: there's no local file at all, by default.

Every Prior Course Assumed a File

Word saves a .docx file. Writer saves a .odt file. Both are genuine files sitting on a disk somewhere, which you explicitly save, and which you could lose entirely if you forget to save before a crash — AutoRecover and background autosave features soften that risk, but the fundamental unit both applications work with is still a file you explicitly save.

A Google Doc Is Not a File — It's a Cloud Object

Opening a new document at docs.google.com (or the Sheets/Slides equivalent) creates something that lives on Google's own servers from the moment it's created — not a file on your own computer at all. There's no "Save As" step needed at the start, and normally no manual save step at any point afterward. Every keystroke syncs to the server automatically and continuously, typically within a second or two of typing it.

No "Save" Button, By Design

Unlike Word's or Writer's own Ctrl+S, Google Workspace documents genuinely don't have a primary Save command in the traditional sense — there's simply nothing to manually trigger, because there's no separate unsaved state to commit. File → Download exists, but that's a fundamentally different action: exporting a standalone copy, not saving the live document.

What "Autosave" Actually Means Here

This is not the same mechanism as Word's own AutoRecover, which quietly writes to a separate temporary recovery file you'd restore from after a crash, alongside whatever you last manually saved. Google Workspace's autosave writes directly to the single, canonical, live version of the document on Google's own servers, continuously — there is no separate "recovery" step needed after a crash, because there was never a separate, only-locally-held working copy to lose in the first place.

The Practical Implications

• Working offline requires an explicit setting (offline mode via the Google Docs offline extension/app) rather than being the assumed default the way a desktop application always works without an internet connection.
• Sharing a document means sharing a link to the one live cloud object — not attaching a file, and not sending a copy at all.
• Multiple browser tabs or devices viewing the same document all see the exact same live version — there are no separate local copies that could quietly drift apart from each other.

Hands-On Exercises