Theory
The whole point, and the whole danger
Sharing is why the team uses Google Docs at all, and it is also where things go wrong. Priya wants: her team to edit the report, her teacher to leave feedback but not change the text, and nobody else to see it.
Give the wrong access and a classmate could edit their marks, or the whole college could stumble on the draft.
Google solves this with permission roles, Viewer, Commenter, Editor, granted per person. Getting sharing right is the single most important skill in cloud collaboration, and the exam's favourite topic here. Let us get it exactly right.
Theory
Keys to a room, at different levels
Think of the document as a room. A Viewer gets a key that only lets them look through the window (read). A Commenter may enter and leave sticky notes but not move the furniture (read + comment). An Editor can rearrange the room (change the content). You hand out the right key to the right person, the teacher gets a look-and-comment key, teammates get a full key, strangers get none. Access is deliberate, not all-or-nothing.
At a glance
The three permission roles
| Role | Can | Cannot |
|---|---|---|
| Viewer | Read the document | Comment or edit |
| Commenter | Read and add comments/suggestions | Change the content |
| Editor | Read, comment and edit content | (by default can also re-share) |
Theory
Two ways to share
Click Share and choose how:
- Invite specific people by email: each person gets a chosen role (team as Editor, teacher as Commenter). The most secure way, only invited people have access.
- Share by link: set 'anyone with the link' to a role (Viewer/Commenter/Editor). Convenient, but anyone who gets that link has that access, forwarded, leaked, or guessed. A real trade-off.
The owner stays in control: change anyone's role, remove access anytime, and even stop Editors from re-sharing or downloading. Principle: grant the least access each person needs.
Quiz
Priya wants her teacher to give feedback on the report but NOT be able to change the text. Which role should she grant?
- Commenter, can read and comment but not edit the content
- Editor, so the teacher can help
- Viewer, so the teacher cannot do anything
- Owner, to be safe
Show the answer
Commenter, can read and comment but not edit the content
Commenter lets the teacher read and leave comments/suggestions for feedback, without the power to change the text, exactly what Priya wants. Editor would let them alter content; Viewer would block feedback entirely (read-only). Matching the role to the need, feedback without edit rights equals Commenter, is the core sharing judgement, and grants the least access necessary.
Think first
Email invite or 'anyone with the link'?
For the confidential report, Priya considers setting 'anyone with the link can edit' because it is quick. Why is inviting specific emails much safer, and when might link-sharing be acceptable?
Show the answer
'Anyone with the link' means the access travels with the link, if it is forwarded, posted, or leaked, any stranger gets that access (here, editing a confidential report, a disaster). Inviting specific emails ties access to named people you chose; nobody else can get in even with the link. So email invites are far safer for anything private. Link-sharing is acceptable for genuinely public or low-risk content (a public info sheet set to Viewer). Match the sharing method to the sensitivity, least privilege again.
Watch out
Where marks leak
Not knowing the three roles and exactly what each can do (Viewer = read, Commenter = read+comment, Editor = edit). Confusing email-invite sharing (secure, named people) with link sharing (convenient but anyone with the link). Forgetting the owner can change/revoke access anytime and restrict re-sharing. And missing the principle of least privilege (give only the access needed). This topic is the exam's richest source of marks in the subject.
Theory
Permissions are everywhere in computing
Viewer/Commenter/Editor is the same idea as file permissions in an operating system (read/write) and user privileges in a database (BCA105, who can SELECT vs UPDATE). Controlling who-can-do-what is a universal computing concept; you are meeting it in a friendly form. Next lesson pairs perfectly with sharing: revision history, which records every change by every collaborator, so you can always see, and undo, what anyone did.
Summary
Key takeaways
- Sharing grants each person a role: Viewer (read), Commenter (read + comment), Editor (edit content).
- Share by inviting specific emails (secure, named people) or by link (convenient but anyone with the link gets access).
- The owner can change or revoke anyone's access anytime and restrict re-sharing/downloading.
- Grant the LEAST access each person needs (teacher = Commenter, team = Editor, others = none).
- This is the same idea as OS file permissions and database user privileges.
- Memory hook: keys to a room, look through the window (Viewer), leave notes (Commenter), rearrange (Editor).