Share a cloud document with the right permissions, work together with comments and suggestions, and use version history.
Why it matters
Project plans, lab protocols, design specs, meeting notes and course feedback are increasingly written in cloud documents that several people edit at once. Used well, cloud tools end the "which version is the latest?" problem. Used badly, they leak data to the wrong people or let one careless edit wipe out a colleague's work. Knowing the sharing and history features is a basic professional skill.
The core idea: one copy, many people
With a traditional file, everyone has their own copy and you email versions back and forth. A cloud document lives on a server (for example Google Docs, Microsoft 365 / Word on the web, or similar tools). Everyone opens the same document through a browser or app, sees each other's changes within seconds, and the service keeps a full history of edits.
Cloud storage (Google Drive, OneDrive, Dropbox, iCloud Drive) is the related idea for ordinary files: a folder on your computer that syncs to the server and to your other devices.
Sharing: who can do what
Every cloud tool has the same basic choices. Names vary slightly, but the ideas are the same.
Who:
- Specific people: only the accounts you invite. Best for most work.
- Your organisation: anyone signed in with your company or school account.
- Anyone with the link: anyone who gets the URL, including people it is forwarded to. Use with care.
What they can do (roles):
| Role | Can read | Can comment | Can edit |
|---|---|---|---|
| Viewer | yes | no | no |
| Commenter | yes | yes | no (in Google Docs they can suggest changes) |
| Editor | yes | yes | yes, including changing sharing in many setups |
Least privilege is the rule: give people the lowest role that lets them do their job. A reviewer needs comment access, not edit access. Check your employer's policy before sharing anything outside the organisation; client, patient and personal data often must never be link-shared.
Working together
- Comments: select text and add a comment to ask a question or flag a problem without changing the text. Type
@and a name (or email) to mention someone; they get notified, and in some tools you can assign the comment to them as a task. - Resolve: when a comment has been dealt with, resolve it. It disappears from the margin but stays in the comment history.
- Suggesting mode (Google Docs) or Track Changes (Word): your edits show as proposals the owner can accept or reject. Use it when editing someone else's document.
- Presence: coloured cursors show who is editing where, so you can avoid typing over each other.
Version history
The service saves versions automatically as people edit.
- Google Docs: File > Version history > See version history. You can name the current version (for example "Sent to supervisor 2026-10-20") and restore any earlier one.
- Word / Microsoft 365: File > Info > Version History (or the title bar's version history option) shows saved versions you can open or restore.
Naming a version at key moments (submitted, approved, sent to client) gives you a clean checkpoint. Restoring an old version does not delete the newer ones; they stay in the history.
Worked example: a lab protocol review
Priya writes a sample-prep protocol and needs two reviewers.
- She clicks Share, adds both reviewers' work emails as Commenters, and writes a short note: "Please review steps 4-7 by Friday."
- Reviewer A selects step 5 and comments: "@Priya should this be 4 °C, not room temperature?" Priya checks the method, fixes it and resolves the comment.
- Reviewer B uses suggesting mode to reword step 7. Priya accepts the suggestion.
- Priya names the version "v1 approved 2026-10-24".
- A week later someone accidentally deletes a section. Priya opens version history, finds "v1 approved" and restores it in seconds.
No files were emailed, nobody worked on an old copy, and there is a record of who changed what.
Common mistakes
- "Anyone with the link can edit" on a document with sensitive information.
- Downloading and emailing a copy, which creates the version mess cloud tools exist to solve. Share the link instead.
- Editing directly in someone else's document when a comment or suggestion would be clearer.
- Leaving old shares open. Remove access when a project ends or someone leaves the team.
- Forgetting offline limits. Some tools need setup to work offline; do not rely on a document you cannot reach on site.
Quick recap
- A cloud document is one shared copy with automatic history.
- Share with specific people and the lowest role that works (least privilege).
- Use comments, mentions, suggestions and resolve to collaborate cleanly.
- Name versions at milestones, and restore from history when things go wrong.
Try it
Open the Do tab to share a document, collect a comment and restore a version.