Organising Google Drive and Sharing Files Safely

Build a clear folder structure, understand access roles and plan file sharing without exposing a whole project.

Part 4 of 10 | Email and Google Workspace for Beginners

Learning goals

Organise the fictional training-session files in Drive and distinguish viewing, commenting and editing. Explain why copying a link is different from granting access. Prepare a permission plan that gives each person only the access needed for their task and records any limits you cannot verify.

Before you begin

Use only practice files and an account you control. Keep the project folder restricted and do not add real collaborators during this exercise. Where a sharing action would notify another person, inspect the available choices and cancel without sending. A written access plan is sufficient for the course; do not claim that another person's access has been tested.

Build a folder structure around the work

Create a clearly named practice folder in Drive using New and the folder option. A name such as Email_Course_Practice makes its purpose easy to recognise. Inside it, plan folders for Working, Reviewed and Reference. These names describe stages rather than arbitrary locations, making it easier to decide where a new file belongs.

Upload the fictional agenda file from Part 3 and confirm that the upload finishes. Open it from Drive to check that the intended file arrived. A filename in a list is not enough if the upload failed or the file is not the version you expected. Keep the original local practice copy until you have checked the uploaded result.

Understand copies and working versions

Uploading a file and creating a native Google document are related but different actions. A Word file can exist in Drive without becoming the same object as a newly created Google Doc. If you create another copy or convert a file, give it a name that distinguishes it from the source and review the result before relying on it.

Choose one working version for the project and record where it is. If three people edit three downloaded copies, their changes do not automatically combine into a single agreed document. A shared working file can reduce that confusion, but only when the collaborators understand which file is authoritative and who is responsible for reviewing changes.

Match roles to a real need

Google Drive provides roles such as Viewer, Commenter and Editor. A viewer reads, a commenter can provide feedback and an editor can change content. For the fictional project, a reviewer who only needs to suggest improvements should not automatically receive editing rights. Choose the least access that still allows the intended work.

In the file's Share controls, inspect named access and general access separately. Restricted access differs from allowing anyone with the link. Organisation policy and folder permissions can affect the result. A file placed inside a shared folder may have access inherited from that folder, so check the effective access rather than assuming the file's name or location makes it private.

Treat links as references rather than proof

Copying a file link does not by itself establish that a particular recipient can open it. Conversely, a link configured for broad access can travel beyond the people you originally intended. Before a real share, confirm the recipient, role and general-access setting, then test through an authorised process that represents the intended recipient's access.

Do not treat your own successful opening as proof that another account can open the file; you may be the owner. In this course, record the desired test without contacting someone. Where access cannot be tested, state that limitation. Never make a private file broadly accessible merely to avoid investigating an access problem.

Review what is inside the shared material

Permission choices cannot repair a document that already contains unnecessary private information. Review the file, comments, related material and folder contents before sharing. If a reviewer needs only the agenda, sharing the entire project folder may expose draft attendance information and unrelated notes. Prefer a deliberate file-level decision based on the purpose.

Removing access later should not be described as retrieving every copy someone may already have made. Keep distribution limited from the start and follow any applicable organisational requirements. For practice, use fictional information even when a file remains restricted. This makes accidental exposure less harmful while you learn the controls.

Keep a simple access record

Create a permission plan with columns for file, intended role, reason, access method and review date. Use role names such as agenda reviewer instead of real addresses. After a project ends, review which access is still needed through the appropriate owner or administrator. Do not remove another person's legitimate access to a real shared project as part of a classroom exercise.

An organised Drive also needs a retrieval habit. Search by a distinctive file name, open the result and confirm its contents and owner. A shortcut or shared item may point to a file owned elsewhere. Record the authoritative project location so that a renamed or moved item does not become an excuse to create unnecessary duplicate versions.

Guided exercise

1. Create a restricted practice folder and upload the fictional agenda. Open the file and verify its contents.

2. Prepare a three-folder structure and explain which stage belongs in each folder. Identify the authoritative working version.

3. Write a permission plan for an agenda reviewer, a presentation editor and an information-only reader. Use role descriptions, not real addresses.

4. Inspect sharing controls without applying new external access. Record the difference between named access and general access.

5. Explain why opening your own copied link is not a recipient-access test. Write the controlled test you would use before a future authorised share.

Knowledge check

1. Which role suits someone who only needs to provide feedback?

2. Does copying a restricted link automatically give everyone access?

3. Why check the containing folder's permissions?

Answer guide

1. Commenter is often suitable, subject to the actual task and available controls.

2. No. Access depends on permissions and applicable settings.

3. Folder access can affect who can access the file.

Completion standard

Provide an organised restricted practice folder, verified upload and three-role permission plan. Distinguish a link from permission and an owner check from a recipient test. No real collaborator should be added or notified, and any untested access must remain labelled as untested.

Sources and verification notes

Share files from Google Drive. Checked 15 September 2026. Official roles and access guidance. Organisation policies and folder access can affect effective permissions.