Files, Co-authoring & the SharePoint Connection

When you drag a file into a Teams channel, it feels like it lives in Teams. It does not. Understanding where your files actually go — and who can see them — clears up a whole category of confusion: the vanished document, the “why can’t they open this?” mystery, and the panic over an overwritten file. Spoiler: nothing is overwritten, and almost everything traces back to one quiet engine humming behind Teams.

Where Teams files really live

Files you post in a channel are stored in that team’s SharePoint site — a document library that came free with the team. Files you share in a chat (a direct or group message) are stored in your OneDrive and shared with the other people in the chat. Teams is really a friendly window onto these two storage places; the Files tab in any channel is just a view of that channel’s SharePoint folder.

Why does this matter? Because it explains the surprises. A file someone shared in a chat is theirs, in their OneDrive — if they leave the company, access can change. A file in a channel belongs to the whole team via SharePoint, so it sticks around. Knowing which is which tells you how durable and how visible a file really is.

Co-authoring: everyone in the same document

Because the files live in SharePoint or OneDrive, several people can open and edit the same Word, Excel, or PowerPoint file at the same time. This is co-authoring. You see colleagues’ cursors moving and their changes appearing live, and there is no “final_v3_REALLYfinal.docx” to email around — there is one file, and everyone is in it. Open it right inside Teams, or in the desktop or web app; it is all the same document. This single habit eliminates most version chaos on its own.

Version history: the undo you forgot you had

Worried someone wrecked the document? They did not, not permanently. Every file in SharePoint and OneDrive keeps a version history — a timeline of saved states you can view and restore. If a section gets deleted or a formula gets mangled, open version history, find the earlier version, and roll back. Nothing is ever truly lost, which means you can relax about co-authoring; mistakes are reversible.

Rule of thumb: if a file matters to a whole team, put it in the channel (SharePoint), not a chat. Channel files are durable and shared; chat files are personal and easy to lose track of.

Permissions and the sharing surprise

The most common file headache is permissions. Someone in the channel cannot open a document, or an external partner gets an “access denied” wall. This usually happens because a file’s sharing settings do not match where it lives. Channel members automatically have access to channel files — but if you grabbed a link from your own OneDrive and pasted it, the recipient may not be allowed in. When you share a link, check the sharing settings: who is this link for — people in the org, specific people, or anyone? Matching the audience to the link prevents most “I can’t open it” messages.

Spot it: where the file lives

Read each situation and decide for yourself, then tap a card to flip it and check your answer.

Sort the file scenarios

Drag each item into the bucket it belongs to — or tap an item, then tap a bucket. Hit Check placement when you’re done.

How to use it

Treat the channel Files tab as the team’s shelf for anything shared, and let chat files be for quick, personal hand-offs. Stop emailing attachments back and forth — co-author the one real file instead, opening it straight from Teams. If something goes wrong, reach for version history before you panic. And when you send a link, glance at the sharing settings so the right people can actually open it. Useful phrases: “I’ve put it in the channel Files so it stays with the team.” “Let’s co-author it rather than trade copies.” “Check version history — your edits are still there.” Knowing where files live makes you the calm one when others are hunting for a lost document.