Why start with a map
When a user says "Meet is broken", Meet is often not the part that has failed. The recording went to Drive. The meeting link came from Calendar. The space lost half its members because someone edited a Google Group. Senior support engineers fix things quickly because they work out which service owns the symptom before they open any settings.
Think of Meet and Chat as the front of a shop. The user sees the counter, but the stock room (Drive), the booking diary (Calendar), the staff list (Groups), the manager's office (Admin console) and the fixtures (Meet hardware) sit behind it. This level gives you the floor plan.
About this course. This guide is independent. Google did not write it, has not endorsed it, and is not connected to it. It copies none of Google's documentation. Google changes screens, menu paths, licences and limits often. When a screen or a number matters, Google's current help pages are the authority. User help is at support.google.com/meet and support.google.com/chat. Admin articles are at support.google.com/a and, more and more, at knowledge.workspace.google.com. Every path in this course was checked in November 2026. Treat each one as "true when written".
The one-page map
Copy this into your team wiki and keep it next to your ticket queue:
WHAT THE USER SEES WHAT SITS BEHIND IT (owner of most faults)
------------------------------ ----------------------------------------------
Meet: joining a meeting Meet service + browser/OS permissions
Meet: link on an invite Calendar (the event creates and carries the link)
Meet: recording Drive -> organiser's My Drive > "Google Meet" > per-meeting subfolder
Meet: transcript Drive (a Google Doc in the same folder) + Calendar (attached to the event)
Meet: tenant-wide behaviour Admin console > Apps > Google Workspace > Google Meet
Chat: direct messages Chat service
Chat: spaces & membership Chat + Groups (a group added to a space syncs its members into it)
Chat: files in a message Drive / Chat attachments ("Add to Drive" puts a copy in the user's Drive)
Chat: who can talk externally Admin console > Apps > Google Workspace > Google Chat
Meeting room devices Admin console > Devices > Google Meet hardware > Devices
Read it from left to right. Find the user's words on the left, and the right-hand column tells you where to start looking.
Walkthrough 1: "I can't find my recording"
Ticket: "Recorded Tuesday's client call, recording has vanished."
Step 1 Who OWNS this? Recording = file -> Drive, not Meet
Step 2 Whose Drive? The meeting ORGANISER's, not necessarily the person who pressed Record
Step 3 Which folder? My Drive > Google Meet > <meeting subfolder>
# Since July 2026 Google has used a "Google Meet" folder with one subfolder per meeting.
# The old "Meet Recordings" folder was renamed "Legacy Meet Recordings"
# and moved inside it. Old links still work.
Step 4 Other clues The organiser and the person who started recording get an email with a link
Result Found in the organiser's Drive. User was searching their own Drive.
Gotcha: a user who has used Meet for years will look for "Meet Recordings" and assume it has been deleted. Explain the rename and the move before you start a restore.
Walkthrough 2: "People keep disappearing from our space"
Step 1 Who OWNS this? Space membership -> Chat, BUT check for Groups first
Step 2 Read-only check Open the space > space settings > Manage members
# Is a Google Group listed as a member?
Step 3 If yes Membership syncs ONE WAY: Groups -> Chat
# Someone removed from the group is removed from the space.
# Editing the space does not change the group.
Result The fix belongs with whoever owns the Google Group, not with a Chat setting.
Best practice: record "owning service: Groups" in the ticket. If it comes back, the next engineer knows where to look straight away.
Walkthrough 3: "The Meet link on my invite is wrong"
The link belongs to the Calendar event. If the user copied an old event or another tool replaced the conferencing, the problem is in Calendar, even though they will call it a Meet problem. Open the event before you look at any Meet setting.
The triage habit: owner first, settings second
Before you change anything, write a one-line ownership guess in the ticket:
Symptom: "Transcript missing from invite"
Owner guess: Calendar (attachment) -> Drive (file) -> Meet (was transcription on?)
First read-only check: open the Calendar event's attachments
Why do this? A wrong guess costs you a minute. A setting changed in the wrong service can break things for the whole organisation, and you may not find out for a week. Admin console settings for Meet and Chat often apply to an entire organisational unit, so a "quick fix" there can reach far more people than the user who raised the ticket.
Trade-off to accept: some symptoms involve two services. A recording can exist in Drive while the Calendar event shows nothing. Name the service you will check first, then follow the chain.
What to tell the user
When a user quotes a screenshot from an article or asks "what's the limit?", say something like:
"Our support guides are our own and aren't from Google. For the exact current screen or limit, Google's help page is the authority. Here's the link."
This keeps you honest when Google changes a screen, and it gives the user a source they can check for themselves.
Key takeaways
- Each thing a user sees in Meet or Chat is backed by a service: Calendar (links, attachments), Drive (recordings, transcripts, saved files), Groups (synced space membership), the Admin console (tenant-wide settings) or Meet hardware (rooms).
- Recordings and transcripts go to the organiser's Drive, in a Google Meet folder with one subfolder per meeting. Pre-July-2026 recordings are in Legacy Meet Recordings inside that folder.
- A Google Group added to a space syncs its members one way, from Groups to Chat.
- Name the owning service before you touch any setting, and start with read-only checks.
- This course is independent of Google and copies none of its documentation. Google's current help pages are the authority for screens and limits.