Teams Recordings in SharePoint/OneDrive: Best Folder Setup + Permissions

Store Microsoft Teams recordings, transcripts, and minutes in one standard place, with clear permission tiers and link rules. The best setup uses a shared SharePoint site for the “official” meeting series library, a consistent folder path for every meeting, and separate folders for internal-only transcripts versus shareable minutes.

This guide gives you a practical folder structure, simple permission tiers, and a quick checklist an assistant can apply to recurring meetings to keep files easy to find and links from breaking.

Primary keyword: Teams recordings in SharePoint/OneDrive

Key takeaways

• Pick one “source of truth” location per meeting series (usually a SharePoint document library) and always file to the same path.
• Separate shareable minutes from internal-only transcripts using different folders and stricter permissions.
• Use folder-level permissions and Microsoft 365 sharing links that match your audience (owners, members, guests).
• Avoid broken links by linking to SharePoint files (not downloads), using stable folder names, and limiting moves after sharing.
• For recurring meetings, create the structure once, then copy the same meeting template folder each time.

How Teams recordings end up in OneDrive vs SharePoint (and why it matters)

Where Teams saves a recording affects who can access it and how you should file it later. If you treat the default save location as your long-term archive, you often end up with scattered files, confusing permissions, and links that stop working after reorganizing.

In many Microsoft 365 setups, channel meeting recordings save to the team’s SharePoint site, while non-channel meeting recordings can save to the organizer’s (or recorder’s) OneDrive. Your goal is to move or copy the final artifacts into a single, consistent SharePoint “home” for the meeting series.

Microsoft’s sharing model can also vary by tenant settings, so confirm your org’s defaults with IT if you work with external guests or sensitive content. For background on how sharing links work in SharePoint and OneDrive, see Microsoft’s overview of SharePoint file and folder sharing.

The recommended folder structure (simple, repeatable, and link-friendly)

Use one SharePoint site as the official home for each recurring meeting series, then standardize the same library and folder path. This reduces “where is it?” messages and makes permissions easier because you manage them once.

Choose one “source of truth” location

For most teams, a SharePoint site tied to the Microsoft Team (or a dedicated SharePoint communication site) works best because ownership survives staff changes. OneDrive is great for drafts, but it is person-owned and can become a bottleneck when roles change.

Library + folder pattern (recommended)

• Site: Team / Department SharePoint site
• Document library: “Meetings” (create one if you do not have it)
• Top-level folders: one folder per recurring meeting series

Example (copy/paste naming):

• Meetings
  • Leadership Weekly
    • 00_Templates
    • 01_Agendas
    • 02_Minutes (Shareable)
    • 03_Recordings
    • 04_Transcripts (Internal)
    • 05_Action Log
  • Project Alpha Steering
    • 00_Templates
    • 01_Agendas
    • 02_Minutes (Shareable)
    • 03_Recordings
    • 04_Transcripts (Internal)
    • 05_Decisions

Within each meeting: use a predictable subfolder name

Create one folder per meeting date so links stay neat and files group together. Use ISO-style dates so everything sorts correctly.

• YYYY-MM-DD (recommended)
• Optional add-on: YYYY-MM-DD – Topic (keep topics short)

Example:

• Leadership Weekly > 03_Recordings > 2026-04-21
• Leadership Weekly > 02_Minutes (Shareable) > 2026-04-21
• Leadership Weekly > 04_Transcripts (Internal) > 2026-04-21

File naming rules (so search works later)

Use the same naming pattern for every artifact, and include the meeting series name plus date. Keep names short and avoid special characters that can cause sync issues.

• [Series]_[YYYY-MM-DD]_Minutes
• [Series]_[YYYY-MM-DD]_Transcript_INTERNAL
• [Series]_[YYYY-MM-DD]_Recording

Permission tiers that match real meeting needs

Most Teams meeting artifacts need at least two permission levels: one for the core team and one for broader (or external) sharing. If you store everything in one folder with one permission setting, you will eventually share something you did not mean to.

Tier 1: Owners (full control)

• Who: meeting organizers, exec assistants, project leads, site owners.
• Access: manage permissions, delete, move, versioning decisions.

Tier 2: Members (edit)

• Who: regular attendees who help edit agendas or minutes.
• Access: edit minutes, upload files, collaborate on action items.

Tier 3: Visitors (read)

• Who: stakeholders who need visibility but should not change records.
• Access: read-only minutes and final materials.

Tier 4: Guests / external (read, limited)

If you work with vendors, clients, or partners, give access only to the “Shareable” areas. Keep internal transcripts and raw recordings out of guest-access spaces unless you have a clear reason to share them.

Where to apply permissions (practical recommendation)

• Set broad permissions at the meeting series folder (Owners/Members/Visitors).
• Break inheritance only for the sensitive folders:
  • 04_Transcripts (Internal) (tightest)
  • Sometimes 03_Recordings if recordings include confidential discussion
• Keep 02_Minutes (Shareable) readable by the widest intended audience.

This approach minimizes “unique permissions” sprawl while still protecting sensitive content. Too many unique-permission folders can become hard to maintain when staff changes.

Link-sharing rules for minutes and transcripts (without accidental over-sharing)

Link settings matter as much as folder permissions. A link can grant access beyond what you intended if you pick the wrong option.

Use these link types intentionally

• “People in your organization”: best default for internal minutes.
• “People with existing access”: safest for linking inside recurring emails and calendar invites because it does not expand access.
• “Specific people”: best for external sharing, because it ties access to named accounts.
• Avoid “Anyone with the link” unless your org explicitly allows it and the content is truly non-sensitive.

Minutes vs transcripts: default sharing stance

• Minutes: often safe to share broadly (internal), and sometimes externally after review.
• Transcripts: treat as internal by default because they contain verbatim content, side comments, and names.

Practical rule: share a minutes link, not a transcript link

When someone asks “Can you send me what was discussed?”, send the minutes link and offer the transcript only when needed. This keeps detailed language out of broad circulation and reduces the risk of quoting something out of context.

Where to paste links so they stay stable

• Use the SharePoint “Copy link” URL to the file.
• Avoid linking to a file on someone’s local synced path.
• Prefer linking to the minutes document that stays in one place, and include the recording/transcript link inside that document if required.

How to separate internal-only transcripts from shareable minutes

Separation works best when you combine three things: a clear folder boundary, a naming rule, and permission settings that enforce the boundary. If you rely only on “people knowing,” someone will eventually share the wrong file.

Use two different folders with clear labels

• 02_Minutes (Shareable): approved summary, decisions, actions.
• 04_Transcripts (Internal): verbatim text, speaker labels, raw exports.

Use a review step before anything becomes “shareable”

• Draft minutes can live in the Minutes folder with edit access for Members.
• Final minutes should be saved as a final version (or PDF) if your org prefers a locked record.
• Keep transcripts internal even after minutes finalize, unless the meeting group decides otherwise.

Redaction and cleanup (when you must share a transcript)

If someone truly needs a transcript outside the core group, consider creating a second file named “EXTERNAL” and remove sensitive segments. Keep the original internal transcript untouched for audit and context.

• Remove private data (phone numbers, addresses, HR topics).
• Confirm speaker names are acceptable to share.
• Share using “Specific people” links, not broad links.

How to avoid broken links (standardize storage, then stop moving files)

Most broken links happen after someone reorganizes folders, renames files, or moves a recording from OneDrive to SharePoint after people already saved the link. You can prevent most of this with a simple policy: set the final location first, then share.

Rules that prevent link rot

• Pick the permanent home first: store final artifacts in the meeting series folder before you email links.
• Keep folder names stable: do not rename “03_Recordings” to “Recordings (Old)” mid-year.
• Limit moves after publishing: if you must move, update the minutes document (the hub link) right away.
• Use a hub document: make the minutes file the single place that contains links to recording, transcript, and action log.

When you must move a Teams recording

If a recording landed in an organizer’s OneDrive, move or copy it into the standard SharePoint folder as soon as possible. Then share the SharePoint link going forward, and stop distributing the old OneDrive link.

Versioning tip (keeps changes safe)

Turn on version history for the “Meetings” library if it is not already enabled. SharePoint supports versioning for document libraries, and it helps you recover from accidental edits or overwrites.

Quick setup checklist for assistants (recurring meeting series)

Use this checklist once per recurring series, then repeat the meeting-date folders each session. Keep it simple so anyone can cover when you are out.

• 1) Create the meeting series home
  • Create (or pick) the SharePoint site for the team.
  • Create a “Meetings” document library if needed.
  • Create the meeting series folder (example: “Leadership Weekly”).
• 2) Create the standard subfolders
  • 00_Templates
  • 01_Agendas
  • 02_Minutes (Shareable)
  • 03_Recordings
  • 04_Transcripts (Internal)
  • 05_Action Log (or Decisions)
• 3) Set permission tiers
  • Set Owners/Members/Visitors at the meeting series folder.
  • Break inheritance only for “Transcripts (Internal)” (and Recordings if needed).
  • Confirm guests (if any) only see “Minutes (Shareable)” and agreed files.
• 4) Create templates
  • Minutes template with sections: decisions, action items, risks, parking lot.
  • Agenda template with timeboxes and owners.
  • Put both in 00_Templates.
• 5) For each meeting date
  • Create a YYYY-MM-DD folder under Minutes, Recordings, and Transcripts.
  • Save the minutes doc in the Minutes date folder and treat it as the “hub.”
  • Move/copy the recording into the Recordings date folder.
  • Save the transcript into the Transcripts date folder with “INTERNAL” in the name.
• 6) Share links safely
  • Share the minutes link using “People with existing access” (internal default).
  • For external sharing, use “Specific people” and link to a reviewed minutes file.
  • Avoid sharing transcript links unless approved.

Common questions

• Should we store everything in the Teams channel “Files” tab?
  That can work because it maps to SharePoint, but teams often mix many file types there. A dedicated “Meetings” library or clear meeting-series folder structure keeps artifacts easier to manage.
• Is it okay to keep recordings in an organizer’s OneDrive?
  It is fine for short-term handling, but it creates risk when the organizer changes roles or leaves. For recurring series, copy the final recording into a shared SharePoint location and share that link.
• Who should have access to transcripts?
  Default to the smallest practical internal group. Expand access only when there is a clear need, and consider an edited version for broader sharing.
• How do we share minutes with external attendees without exposing internal notes?
  Store minutes in a “Shareable” folder with separate permissions, then use “Specific people” links. Keep internal transcripts and raw notes in a different folder with tighter access.
• What is the simplest way to prevent broken links?
  Decide the permanent storage path first, file the artifact there, and only then share the link. Use the minutes document as the hub so you update links in one place if something changes.
• Should we save minutes as Word or PDF?
  Word works well when you want collaboration and version history. PDF can be better for a finalized record, but keep the editable source if your team expects updates.

When transcripts and captions become a workflow (not a one-off)

If your meetings repeat weekly, consider standardizing how you capture and polish transcripts, especially when you need consistent speaker labels or a clean record. Some teams start with automated text for speed, then proofread for accuracy before filing it as “internal.”

GoTranscript supports both AI and human workflows, including automated transcription and transcription proofreading services, so your meeting artifacts can match the level of detail your team needs.

If you want a reliable way to turn Teams recordings into organized minutes and transcripts that fit the folder and permission system above, GoTranscript can help with professional transcription services. You can then file the outputs into your SharePoint structure and share the right version with the right audience.