Lesson 1: Google Drive on One Page

Learners map what the user sees (My Drive, Shared with me, shared drives, Drive for desktop, Docs editors) to what sits behind it (the Workspace tenant, organisational units, licences and Admin console policy), and learn that this course is independent of Google and that every screen, role and limit it names must be checked against Google's current documentation and dated.

Why start with a map

Most Drive tickets begin with the user's words: "my folder vanished", "I can't share with the client", "the G: drive is empty". Your job is to turn what the user saw into the place where the cause sits. Before you can do that, you need a mental map. Some things the user sees in a browser or in File Explorer, and some sit in the tenant behind them.

Think of a block of serviced offices. Each tenant has a private locker (My Drive). There are team rooms that belong to the company, not to whoever booked them (shared drives). There's a pigeonhole of things colleagues have handed you (Shared with me). Building management (the Admin console) writes the house rules, floor by floor (organisational units). Your licence is your access pass. Support staff don't rewrite the house rules. They read them, explain them and escalate them.

About this course: LevelUpWith is independent of Google and is not endorsed by it. Admin screens, role names, licences and limits change often. Every path and limit here was checked against Google's documentation on 3 November 2026. Check them again before you rely on them.

The one-page map

WHAT THE USER SEES                WHAT SITS BEHIND IT
------------------------------    -------------------------------------------------
My Drive                       -> Files OWNED by that user; use that user's share
                                  of the organisation's storage
Shared with me                 -> Files OWNED by someone else; they use the
                                  owner's storage, not the viewer's
Shared drives                  -> Files OWNED by the organisation (the team),
                                  not by any one person
Docs, Sheets, Slides, Forms    -> Drive and Docs service + its feature settings
Drive for desktop (Windows/Mac) -> Desktop client; admin settings under
                                  Drive and Docs > Google Drive for desktop
Trash                          -> Items are deleted for good after 30 days
                                  (My Drive and shared drives)

EVERYTHING ABOVE DEPENDS ON
  Workspace tenant (your organisation's account at admin.google.com)
   |- Licence / edition -> which features exist and how much pooled storage
   |- Organisational unit (OU) -> which policy applies to this user
   '- Admin console policy -> Menu > Apps > Google Workspace > Drive and Docs

Two lines on this map settle a surprising number of tickets:

Ownership decides where a file lives and whose storage it uses. If someone created a file in My Drive, they own it. A file in a shared drive belongs to the organisation. That's why shared drive files stay put when a leaver's account is deleted.
Policy follows the user's OU. Two people in the same office can see different sharing options because they sit in different OUs.

Walkthrough: tracing one ticket across the map

Ticket: "Priya can't see the Drive for desktop option to keep files offline, but her colleague can."

Step 1  What did the user see?
        Drive for desktop > Settings > Preferences > Folders from Drive
        > "My Drive syncing options": Stream files / Mirror files

Step 2  Which part of the map is it?
        Desktop client, My Drive. (Note: shared drives can only be
        STREAMED, never mirrored. A user who asks to mirror a shared
        drive has hit a product limit, not a fault.)

Step 3  What sits behind it?
        Admin console (read-only look first):
        Menu > Apps > Google Workspace > Drive and Docs
             > Google Drive for desktop
        Select Priya's OU in the left panel, then her colleague's OU.

Step 4  Read the label under each setting.
        "Inherited"  = takes the parent OU's value
        "Overridden" = someone set it for this OU on purpose

Step 5  Explain, don't change.
        If the OUs differ, the behaviour is policy, not a bug.
        Tell the user why, then escalate to whoever owns the policy.

Gotcha: Changes to OU settings can take up to 24 hours to apply, although they usually apply sooner. If someone "just changed it" and the user still sees the old behaviour, wait for the change to come through before you dig into the fault.

Explaining it to a user in plain language

Users don't need the words "tenant" or "OU". Here's a script that works:

"Files in My Drive are yours. You own them and they use your storage. Shared with me is a list of files other people own and have given you access to. They use the owner's storage, not yours. Files in a shared drive belong to the company, so they stay put if someone leaves. What you're allowed to do, such as sharing outside the company, is set by IT for your part of the organisation. That's why a colleague's options can look different from yours."

And for storage: most Workspace editions have pooled storage. Each licence adds space to one shared pot for the whole organisation, and admins can set limits for individual users and shared drives. "Storage full" can therefore mean the user's own limit or the organisation's pot, and those are different conversations.

Writing a dated verification note

This is the habit that sets a professional apart from someone repeating a forum post. Whenever you put a console path, role or limit into a ticket, a knowledge base article or a runbook, add a note like this:

VERIFICATION NOTE
Claim:   Drive for desktop admin settings are at
         Menu > Apps > Google Workspace > Drive and Docs
         > Google Drive for desktop
Source:  support.google.com/a/answer/7491144
         ("Set up Drive for desktop for your organization")
Checked: 2026-11-03 by J. Okafor
Seen in tenant? Yes, test tenant, same path
Status:  CONFIRMED  (alternatives: PREVIEW / BETA / UNCONFIRMED)
Recheck: before next KB review, or when the screen looks different

The best-practice rules:

Use Google's own pages. Google's admin help lives at support.google.com/a, and newer articles also appear at knowledge.workspace.google.com. Blogs and forums are leads, not sources.
Date everything. A limit with no date is a guess with a time bomb attached.
Mark preview or beta features. They may be missing from your tenant or change before general release.
Write UNCONFIRMED honestly. "I couldn't confirm this" is useful information. A confident wrong path wastes the next engineer's hour.

Trade-off: Verifying everything is slower on day one. But the screens change often, and a runbook with dated notes tells you exactly which lines to recheck instead of making you distrust all of it.

Key takeaways

Map every symptom to a layer: My Drive, Shared with me, shared drives, Docs editors, Drive for desktop, and behind them the tenant, licence, OU and Admin console policy.
Ownership decides where a file lives and whose storage it uses. Shared drive files belong to the organisation.
Drive policy is read at Menu > Apps > Google Workspace > Drive and Docs, per OU. Look for Inherited or Overridden.
Shared drives can only be streamed in Drive for desktop. Only My Drive can be mirrored.
Support reads and explains policy and escalates it. It doesn't redesign it.
This course is independent of Google. Date every path and limit you use, and mark anything that's preview or unconfirmed.

A 6-question knowledge check follows this lesson in the app, free and without an account.

By the end of this level you'll be able to