4.1Files & co-editing (SharePoint / OneDrive)
The essentials in 30 seconds
- Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
- Real-time co-editing removes divergent versions: one file, several authors.
- Share the LINK, not the attachment: lightweight, unique, always up to date.
Nassim’s thread — Files & co-editing (SharePoint / OneDrive)
Nassim and two colleagues must modify the same document. It chooses a shared file in the channel, checks for co-authorship, and avoids divergent copies sent by email.
Continuation of the common thread: a digital services SME in Algiers structures its exchanges.
1. Understand
The revelation that clarifies everything: files in a Teams channel are stored in SharePoint, and your personal files in OneDrive. Teams is just a convenient window on it. Direct consequence: a file posted in a channel is a team file, co-editable in real time by all members — no more “file_v3_final_VRAI.docx” which circulates by email.
You will co-edit a document in a channel (multiple live cursors), understand the OneDrive (personal) / SharePoint (team) difference, and adopt the life-changing reflex: share the link, not the attachment — a single file, always up to date, for everyone.
2. Key points
Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
Real-time co-editing removes divergent versions: one file, several authors.
Share the LINK, not the attachment: lightweight, unique, always up to date.
The version history makes any error reversible: co-edit without fear.
🔎 Concrete example — Concrete example — Files & co-editing (SharePoint / OneDrive)
In a Teams channel, Files tab: drop (or create) a Word/Excel document.
Open it in Teams and edit it while a colleague opens it too: watch the sliders live (co-editing).
See the actual storage: click “Open in SharePoint” — the file lives there, Teams is just a view.
Reflex to anchor: to share this file, send its LINK (Copy link) and not a copy as an attachment.A single team file, co-edited and versioned: the chaos of multiple attachments is a thing of the past.
Section vocabulary
- Channel Files Tab
- The channel's storage space — physically in SharePoint: any file posted or deposited is found there.
Simple example: Nassim uses “Channel Files Tab” in his daily life for files & co-editing (sharepoint / onedrive).
What it is not: Confusing “Channel Files Tab” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Co-edition
- Several people editing the same file at the same time (colored cursors visible): the end of divergent versions.
Simple example: Nassim uses “Co-editing” in his daily life for files & co-editing (sharepoint / onedrive).
What it is not: Confuse “Co-publishing” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- OneDrive vs SharePoint (reminder)
- OneDrive = your personal work files; SharePoint = team files (Teams channels). The same engine, two perimeters.
Simple example: Nassim uses “OneDrive vs SharePoint (reminder)” in his daily life for files & co-editing (sharepoint / onedrive).
What it is not: Confusing “OneDrive vs SharePoint (reminder)” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Share link
- The link to the single file (adjustable rights): lightweight, up-to-date, co-editable — replaces the attachment which freezes a copy.
Simple example: Nassim uses “Share link” in his daily life for files & co-editing (sharepoint / onedrive).
What it is not: Confuse “Sharing link” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Version history
- Each file keeps its previous versions (SharePoint/OneDrive): going back after an error is always possible.
Simple example: Nassim uses “Version History” in his daily life for files & co-editing (sharepoint / onedrive).
What it is not: Confusing “Version History” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
In practice — The end of email releases
- In a Teams channel, Files tab: drop (or create) a Word/Excel document.
- Open it in Teams and edit it while a colleague opens it too: watch the sliders live (co-editing).
- See the actual storage: click “Open in SharePoint” — the file lives there, Teams is just a view.
- Reflex to anchor: to share this file, send its LINK (Copy link) and not a copy as an attachment.
Script ready to say — Files & co-editing (SharePoint / OneDrive) (25 s)
“Store, share and co-edit files in channels (SharePoint) and understand the link with OneDrive. I rely on this key point: files of a channel = stored in sharepoint; personal files = onedrive. teams is a window on it.”
Short formulation, to be adapted to the recipient and the context.
Copy and paste template — “Files & co-editing (SharePoint / OneDrive)” checklist
CHECKLIST — Files & co-editing (SharePoint / OneDrive)
1. Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
2. Real-time co-editing removes divergent versions: one file, several authors.
3. Share the LINK, not the attachment: lightweight, unique, always up to date.
4. Version history makes any error reversible: co-edit without fear.
EXPECTED RESULT: A single team file, co-edited and versioned: the chaos of multiple attachments is a thing of the past.Express version
Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
As a team
Real-time co-editing removes divergent versions: one file, several authors.
Point of vigilance
Share the LINK, not the attachment: lightweight, unique, always up to date.
Control before distribution
A single team file, co-edited and versioned: the chaos of multiple attachments is a thing of the past.
✓ Best practices
- Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
- Real-time co-editing removes divergent versions: one file, several authors.
- Share the LINK, not the attachment: lightweight, unique, always up to date.
✗ Common pitfalls
- Treat “Files & co-editing (SharePoint / OneDrive)” by intuition without checking the context.
- Multiply channels and notifications for the same subject.
- Send or share without rereading recipients and rights.
Key takeaways
- Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
- Real-time co-editing removes divergent versions: one file, several authors.
- Share the LINK, not the attachment: lightweight, unique, always up to date.
- The version history makes any error reversible: co-edit without fear.
48 hour challenge — apply tomorrow
Put “The end of versions by email” into practice in a real case of Nassim’s SME: In a Teams channel, Files tab: submit (or create) a Word/Excel document. Time it for 20 minutes and note what has changed.
- I can explain and apply: Files in a channel = stored in SharePoint; personal files = OneDrive. Teams is a window on it.
- I can explain and apply: Real-time co-editing removes divergent versions: one file, several authors.
- I can explain and apply: Share the LINK, not the attachment: light, unique, always up to date.
Frequently asked questions
Where does a file sent in a private CHAT (not a channel) go?
In YOUR OneDrive (“Microsoft Teams Chat Files” folder), shared with chat participants. The channel files go to the team's SharePoint. Hence the interest in the canal for what must remain accessible to all.
Does a member who leaves the team take the files?
No: files in a channel belong to the team (SharePoint), not the person. They stay. On the other hand, files from his personal OneDrive (private chats) follow his account – one more argument for working in channels.
What should you remember from “Files & co-editing (SharePoint / OneDrive)”?