Skip to main content
Following consistent practices from the start saves significant time as your files and teams grow. This guide covers six areas where small habits create large compounding benefits.

​
Naming conventions and file organisation

A consistent naming system means you and your teammates can find files without searching — the folder structure alone tells you where to look.

​
File names

Use names that describe the content and its context at a glance. A good file name answers: what is it, who or what project it belongs to, and when or what stage. Recommended pattern: [Project or team] — [Document type] — [Version or date] Examples:
  • Acme Proposal — Statement of Work — v2
  • Marketing — Q2 Campaign Brief — 2026-04
  • Engineering — API Design — Draft
Use em dashes (—) or hyphens (-) as separators instead of underscores or camelCase. They’re easier to read in Drive’s file list and work well across operating systems.
Avoid:
  • Vague names like Untitled document, Draft, or Final
  • Date-only names like 2026-04-01 with no description
  • Sequential numbers without context (v1, v2, v3 without a base name)

​
Folder structure

Keep your folder hierarchy shallow — two to three levels is usually enough: 
My Drive/
├── [Team or Department]/
│   ├── [Project name]/
│   │   ├── Working docs
│   │   └── Deliverables
│   └── Templates/
└── Archive/
    └── [Year]/
Create an Archive folder and move completed projects there periodically. This keeps your active Drive uncluttered while preserving records. Archived files remain searchable and accessible.
Use Starred for the five to ten files you open every day. Don’t rely on starring as a substitute for proper organisation — it’s a shortcut, not a structure.

​
Managing permissions and access control

Giving people the right level of access — not more — protects your files and prevents accidental changes.

​
Choose the right permission level

PermissionWhat they can doWhen to use it
ViewerRead, download, printStakeholders who need to read but not change content
CommenterAdd and reply to commentsReviewers providing feedback
EditorMake changes, add/remove othersActive collaborators working on the file
OwnerAll editor rights plus delete and transfer ownershipUse carefully; each file has one owner
Avoid making shared team folders editable by large groups. Instead, share specific files with specific people. This reduces the risk of accidental deletions or overwrites.

​
Restrict sharing and download

For sensitive documents, limit what recipients can do with the file:
  1. Open the Share dialog.
  2. Click the gear icon (Settings) at the top of the dialog.
  3. Untick Editors can change permissions and share to prevent editors from adding more people.
  4. Untick Viewers and commenters can see the option to download, print, and copy to restrict exporting.

​
Use groups for team access

If you share a file with an entire team, use a Google Group email address rather than adding individuals one by one. When team members join or leave, their Drive access updates automatically without you needing to adjust each file.

​
Audit access periodically

Review who has access to important files every few months:
  1. Right-click the file in Drive and select Share.
  2. Scroll through the people listed and remove anyone who no longer needs access.
  3. For files shared publicly (“Anyone with the link”), verify this is still intentional.

​
Using version history effectively

Every file in Google Product saves a complete version history automatically. Use it to recover earlier content and track how work evolved.

​
Name important versions

Automatic versions appear with timestamps, which can be hard to navigate in a long history. Name milestones so they’re easy to find:
  1. Go to File → Version history → Name current version.
  2. Type a meaningful label such as Sent to client for review or Post-meeting revisions.
  3. Click Save.
Named versions are pinned at the top of the version history panel and never get automatically consolidated.

​
Restore a previous version

  1. Go to File → Version history → See version history.
  2. Browse the timeline in the right panel. Click a version to preview it — the current document is unaffected until you explicitly restore.
  3. Click Restore this version if you want to roll back.
Restoring a version does not delete the history between that version and the current one. The restore itself becomes an entry in the version history, so you can always undo a restoration.

​
Copy content from an older version

Instead of restoring a whole version, you can copy specific paragraphs or sections from an old version:
  1. Open version history and click the version you want.
  2. Select the text you need and copy it (Ctrl+C).
  3. Close version history (click Back at the top left).
  4. Paste the content where you need it in the current document.

​
Collaboration etiquette

Good collaboration habits reduce friction and keep work moving — especially in shared documents with multiple contributors.

​
Use Suggesting mode for proposed changes

When editing a file you don’t own, switch to Suggesting mode before making changes (the pencil icon in the top-right of a document → Suggesting). Your edits appear as suggestions that the owner can accept or reject. This keeps the original content visible and prevents accidental overwrites. Reserve Editing mode for documents you own or where you’ve been explicitly asked to make direct changes.

​
Keep comments actionable

Comments are most useful when they include a clear action or question:
  • Vague: “This section seems off.”
  • Actionable: “Can you clarify whether this figure includes tax? Reviewers may ask.”
Tag the right person with @mention so the responsibility is clear. Assign action items for anything that requires a follow-up step.

​
Resolve comments when done

Once a comment thread is addressed — whether you accepted the feedback or decided against it — mark it as resolved. Leave a brief reply explaining what you did if the decision isn’t obvious. This keeps the comments panel focused on open issues.
Before sending a document for review, check View → Show → Comments to confirm there are no lingering unresolved threads from earlier rounds.

​
Communicate changes in version notes

When you finish a significant round of edits, name the version and write a short note. If you’re sharing a revised document via email or chat, include a one-sentence summary of what changed — for example, “I’ve addressed all review comments and added the new pricing section.”

​
Security best practices

​
Limit external sharing

Files shared with “Anyone with the link” are accessible to people outside your organisation. Use this setting only for genuinely public content, and review your shared files periodically. For internal collaboration, prefer sharing with specific email addresses or Google Groups within your domain.

​
Revoke access when people leave

When a team member leaves your organisation or a collaborator finishes their engagement, remove their access from shared files promptly. Open the Share dialog and remove them from the access list.
If someone with Editor access downloaded a copy of a file before their access was revoked, they retain that copy. Version history does not protect against downloads made while access was valid. Treat sensitive documents accordingly.
Never set a file to “Anyone with the link can edit” unless the content is entirely non-sensitive. Link-edit access is difficult to track because the link can be forwarded to anyone. Use “Anyone with the link can view” at most for broad distribution.

​
Enable two-factor authentication

Secure your Google account with two-step verification at myaccount.google.com/security. This protects all files in your Drive even if your password is compromised.

​
Review third-party app permissions

Periodically check which apps and add-ons have access to your Google account:
  1. Go to myaccount.google.com/permissions.
  2. Review each app listed.
  3. Remove access for any app you no longer use or don’t recognise.

​
Performance tips for large documents

Very large documents — hundreds of pages, many embedded images, or complex spreadsheets with thousands of rows — can become slow to load and edit. These practices help.

​
For large documents

  • Break large documents into smaller files. Use a dedicated document for each major section and link between them, rather than keeping everything in a single file.
  • Compress images before inserting. Resize images to the display size you need before uploading. A 4K photo embedded in a document that displays it at 400px wide adds unnecessary load time.
  • Avoid excessive inline comments in large documents. Many unresolved comments increase rendering load. Resolve or delete outdated comments regularly.
  • Use headings consistently. A well-structured document with proper heading levels enables the document outline panel, making navigation faster without scrolling through the entire file.

​
For large spreadsheets

  • Avoid volatile functions in large ranges. Functions like NOW(), TODAY(), RAND(), and INDIRECT() recalculate every time the sheet changes. Use them only where necessary.
  • Use named ranges for formulas that reference large datasets. Named ranges are easier to read and can improve formula evaluation performance.
  • Filter before sorting. In spreadsheets with thousands of rows, apply a filter to work with the relevant subset rather than the full dataset.
  • Archive old data. Move historical rows to a separate sheet or file and keep your working sheet to the most recent and relevant records.
If a spreadsheet loads slowly, check for circular references (Tools → Error checking → Circular dependencies) and excessive conditional formatting rules applied to entire columns. Both are common sources of slowness.

​
For large presentations

  • Limit high-resolution images per slide. Compress images and use PNG or JPEG instead of uncompressed formats.
  • Avoid complex animations on every slide. Animations are processed on the client side; presentations with many complex transitions can lag during playback on lower-powered devices.
  • Split very long decks. For presentations over 80–100 slides, consider splitting into separate files by section for faster editing and loading.