Document reading, editing and public links
Choose the audience for the document and keep public sharing deliberate.
Grant appropriate reading or editing access, or let the owner create a time-limited public document URL with a restricted public representation.
An external reader does not need the entire internal document environment.
Internal collaboration and public document sharing are different uses. Docs allows an audience to read or edit according to document authority. A public URL is a separate owner-controlled choice for a saved document representation. It does not provide comments, live collaboration or unrestricted access to business data merely because the internal page contains them.
Choose internal readers and editors intentionally.
Give editing authority only where someone should change the document, rather than using editing as a convenient way to let them read. A shared location or related customer record does not settle document permissions. Test the page with the actual people who should consume it, including someone whose access must remain read-only.
- Separate read and edit authority
Use the owner's finite public URL when appropriate.
The document owner can issue a public link lasting 30 days. Creating a replacement rotates the URL and revokes the earlier live link; the owner can also revoke explicitly. Anyone holding a valid URL may open it without account-based audience checks, so treat it as forwardable. A revocation cannot recall copies already retained by a recipient.
- Owner-issued 30-day URL with rotation and revocation
Inspect the restricted public representation.
The public reader receives saved document content, not internal comments, bindings, Lists, objects or collaboration state. Check what that means for the intended recipient before sending. This is not the same mechanism as Drive's version-pinned file links: do not promise a fixed file snapshot or copy the 1, 7 and 30-day Drive choices onto the document feature.
- Public document content without internal working state
A concrete workflow
Choose audience
Decide whether the recipient should read, edit or use a public URL.
Review content
Inspect facts and any information not appropriate for external disclosure.
Inspect public view
Check the actual saved representation before sending the public link.
Maintain sharing
Rotate or revoke when the intended sharing changes.
An illustrative working example
Illustrative scenario: sharing a reviewed explanation
A consultancy prepares an explanatory document with internal working context. The owner reviews the saved public representation and checks that the recipient receives useful text without the internal material. After issuing the URL, the owner communicates its purpose and lifespan. A later sharing change leads to rotation or revocation. The pilot explicitly distinguishes this document link from a Drive file snapshot and tests the recipient experience before using it for a client.
Questions about this topic
Who can create a public document link?
Issuance is owner-controlled. Having reading or general editing access is not by itself authority to create that public capability.
How long does the document URL last?
The public document URL has a 30-day lifetime. The owner can revoke it, and creating a replacement revokes the previously active URL.
Are comments and linked records public?
The public representation excludes internal comments, bindings, Lists, objects and collaboration state. Inspect it for the recipient's actual needs.
Is it the same as a Drive file link?
No. Drive shares a specific file version with its own expiry choices. Public Docs sharing presents saved document content through a different controlled URL.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Gmail
Application concept: Prepare a Gmail handover with the reviewed public document link and clear explanation of its thirty-day expiry.
Outlook
Application concept: Plan an Outlook correction when a rotated document link replaces an old one, checking recipients again.
Slack
Application concept: Explain to colleagues in Slack that a public Doc snapshot excludes private comments and connected business data.