Questions: Document Collaboration Tools

Question 1

Your team is editing a shared Google Doc and accidentally deletes a large section of content. How do you recover it?

Model answer: Open the version history (File > Version history > See version history in Google Docs). Every edit is automatically logged; scroll back to a version before the deletion, find the missing content, and either restore the entire prior version or copy the deleted section back into the current document.

Version history is automatic in all major collaboration tools — no manual saving or exporting required. This is one of the most important practical skills: knowing that 'undo' in a collaborative document has a very long memory and that no edit is truly permanent.

Question 2

What is the difference between 'commenter' and 'editor' access in a shared document, and when would you grant each?

Model answer: An editor can directly change the document's content. A commenter can only leave comments and (in suggestion mode) propose changes — but cannot apply edits directly. Grant editor access to trusted collaborators who should write and revise freely. Grant commenter access to reviewers, stakeholders, or anyone who should give feedback without altering the document itself.

The access tier matches the level of trust and role. A manager reviewing a report should probably be a commenter; a co-author should be an editor. Mismatching roles (giving editor access to a reviewer who accidentally overwrites content) is a common practical mistake.

Question 3

Why does sharing a Google Doc with 'View only' access not prevent the viewer from copying the text?

Model answer: Sharing permissions control what the viewer can do within the Google Docs interface (they cannot edit, comment, or suggest). But the viewer can still select and copy text, take screenshots, or use browser extensions to extract content. Permissions govern platform-level actions, not access to the underlying rendered content that the viewer can already see.

This is a common misconception with real consequences: people sometimes share sensitive documents with 'view only' access believing the content is protected. It is not. For genuinely sensitive content, access must be restricted to people who are authorized to see it at all — not just people who can't click 'Edit'.