Google Sheet — the fine print
The highest-staleness details behind the Google Sheet option page: why viewing is account-free but editing usually isn't, why publishing isn't sharing, the work/school block, and the read/write API setup.
Last verified: 2026-06-07
Viewing by link needs no account; editing in practice does
Set a sheet to anyone with the link and a stranger can read, sort, and filter it with no sign-in at all — Google's own help page says so outright. [confirmed] (Share files from Google Drive)
The moment that visitor wants to add or edit a row, two things have to line up: the link's role must be Editor (or Commenter), and in practice they sign in with a free Google account — ~1 min, one most people already have. Viewing alone never needs one. [unclear]
Why this is tagged [unclear]: Google's consumer docs confirm no-account viewing and the share roles, but are silent on a hard sign-in requirement for editing — neither stated nor ruled out (checked 2026-06-07). Treat "they'll need to sign in to edit" as the safe assumption, not a documented rule.
"Anyone with the link" is not private
A link forwards, and whoever holds the string is in. Keep anything sensitive on named-people access instead, and remember a published CSV is fully public. → Who can see it? [confirmed]
Publishing is not sharing
File → Share → Publish to web makes a separate read-only public copy that updates when you edit; it grants nobody edit access to the real file. Pick a format — CSV included — and you get a link any app, script, or agent can fetch (IMPORTDATA), no account, no auth. [confirmed]
One caveat: the gviz CSV-export shortcut is widely used but not a documented stable API — treat it as best-effort. [unclear]
Work/school accounts can block external link-sharing
If anyone with the link is greyed out, a Workspace admin has restricted sharing outside your domain. Use a personal Google account for fully public sharing. [unclear] (not in the consumer docs; varies by org — checked 2026-06-07)
The read/write API setup, once
For the path where your agent keeps the sheet current by code, you wire up a Google Cloud project with Sheets credentials once — ~10 min, the same setup any Google API CLI needs. Not needed just to share with people. [confirmed] (Hartree clocks it at ~10 min)
Sources
- Share files from Google Drive — "Anyone who has the link can use your file, without signing in"; Viewer / Commenter / Editor roles; Copy link.
- Stop, limit, or change sharing — remove a person, revert to Restricted.
- Publish a file from Google Drive — Publish to web, whole spreadsheet or single sheet, published copy updates with edits.
- Sheets API — concepts and reading & writing values — read and modify cells by code, by range.
- Google Cloud Console setup for CLI tools — the Google Cloud project + credentials setup is "~10 minutes" (unofficial — wow.pjh.is journal, seen 2026-06-07).