If your team backs up Zoom recordings to Google Drive at all, here's the question worth asking before you trust that archive: whose Drive? If the honest answer is "whoever hosted the call, into their own personal My Drive," the archive isn't really an archive. It's a folder someone else can take with them, forget the password to, or accidentally leave out of the next reorg's file-sharing pass. The fix isn't a better backup habit — it's a different kind of Drive folder, one the organization owns instead of any one person, and a way to save every member's recordings to it automatically.
Why personal Drive backups don't hold up for a team
A file dropped into someone's My Drive belongs to that person's Google account, full stop. That's fine for a solo coach archiving their own sessions. It breaks down the moment a team is involved: each member's recordings land in a different personal Drive, so there's no single place to look, no consistent folder structure across members, and no guarantee the files survive whatever happens to that person's account.
Google is explicit about this distinction for its own Shared Drives feature: "files in shared drives belong to the team instead of an individual," and when someone leaves the organization and an admin removes their account, files they added or created in a shared drive stay right where they are — visible and accessible to the rest of the team (Google Workspace Admin Help). My Drive doesn't offer that guarantee; ownership transfer is a manual step someone has to remember to do before an account is closed, and it's an easy one to miss during an offboarding rush.
For a small org — a coaching collective, a faculty, an agency, a nonprofit running cohort programs — that gap is exactly where recordings go missing. Not because Zoom deleted them, but because they were never in a place the organization controlled to begin with.
How to back up team Zoom recordings to a Shared Drive
- Create the Shared Drive. In Google Drive, choose Shared drives → New, name it something a new admin would understand at a glance (
Team Recordings,2026 Session Archive), and add the people who should have standing access. Shared drives are available on Google Workspace Business Starter and up, plus Education and Nonprofits editions — though Business Starter can't configure sharing restrictions on its shared drives the way Standard and up can, so check your plan's controls before you rely on them. A personal Gmail account with no Workspace subscription won't see the option at all (Google Workspace Admin Help). - Set member roles deliberately. Shared drives support five access levels — Viewer, Commenter, Contributor, Content Manager, and Manager — so you can give most of the team Contributor access (they can see and add files) while reserving Manager for whoever owns the archive long-term.
- Point your Zoom-to-Drive automation at the Shared Drive, not a personal folder. If you're using RecordFlow as the account admin, the Drive-connection step lets you pick any folder in either My Drive or a Shared Drive as the archive root — select the Shared Drive you just created.
- Enroll members from the admin dashboard. Once the archive root is a Shared Drive, every member you enroll gets the same sub-folder treatment as before — one folder per member, named after them — except now that whole structure lives inside a Drive the org owns, not any one person's account.
- Confirm the first few recordings land correctly, then let it run. New recordings continue to file themselves into each member's sub-folder inside the Shared Drive, automatically, as Zoom marks them ready.
What to check if recordings aren't landing in the Shared Drive
How RecordFlow fits
RecordFlow's account-wide admin app already lets you pick any Drive folder as the archive root — a Shared Drive works exactly the same way a personal folder does. One install, one Shared Drive, a sub-folder per member, and every recording lands there automatically within minutes of Zoom marking it ready — no one has to remember to move files out of their own account. If you haven't set up the account-wide archive yet, Archive Every Zoom Recording Across Your Account covers the full admin install; this post is specifically about pointing that archive at a Shared Drive instead of a personal one so the files stay with the org, not the person.
If you're archiving your own recordings rather than a whole team's, the individual backup guide and the Drive vs Zoom Cloud comparison cover that path — and if your team is a tutoring institute or training academy specifically, saving session recordings to Drive walks through the per-student or per-cohort version of the same idea.
Give your team's recordings a home the org actually owns.
Install the admin app once, point the archive at a Shared Drive, and every member's recordings land in a sub-folder the organization controls — not a personal account that walks out the door. Free during beta.
