RobotnixAcademy

Week 02 · lesson

Sharing Is an Access-Control Decision

The Share button is not a social feature. It changes who can do what with information.

Google Drive commonly exposes roles such as Viewer, Commenter, and Editor. The exact interface can change, but the reasoning stays stable: grant the least capability that still allows the intended job.

Start with the job

Suppose a class partner needs to review your draft and leave feedback.

  • Viewer can read but may not support the feedback workflow.
  • Editor can change the original content directly.
  • Commenter can usually support feedback without granting full editing authority.

The best role is not the most powerful role. It is the smallest role that meets the requirement.

Permission is a relationship

Model sharing as:

IDENTITY → RESOURCE → ALLOWED ACTION

Example:

class_partner@example.school
        ↓
W04 Technology Brief
        ↓
comment

“Anyone with the link” changes the identity side of that relationship. Before using a broad-link setting, ask whether the audience actually requires it and whether school policy allows it.

Worked decision table

NeedMinimum reasonable roleWhy
teacher reads final copyViewerno editing required
peer leaves feedbackCommenterfeedback without direct rewrite
project coauthor edits shared draftEditorediting is the job
public internet has no legitimate needno accesscapability has no purpose

These are classroom examples, not universal policy. A school may restrict options further.

The test most people skip

Seeing the file while signed into the owner account proves almost nothing about the recipient experience.

For a course-safe sample file, configure an allowed sharing relationship and verify it from the intended recipient context if your classroom environment supports that test. Otherwise, inspect the sharing panel together and reason from the recorded identity/role.

Record:

  • owner/controller;
  • intended person or group;
  • required action;
  • granted role;
  • verification result.

Permission Decision Matrix

Evaluate these fictional situations:

  1. A teammate needs to add three paragraphs to a shared project draft.
  2. A classmate needs to review a finished chart and report one concern.
  3. A teacher needs to open the final submission.
  4. A link was accidentally set broader than the intended class audience.

For each, choose a permission, explain the required function, and name one risk of granting more access than needed.

Misconception: “shared” means “accessible to everyone”

Sharing is not one state. It is a set of relationships and roles. A file can be shared with exactly one account and completely unavailable to everyone else.

Keep the Permission Decision Matrix. Week 3 will use the same reasoning when a Calendar invitation contains a Drive link.