5.3Collaboration & co-editing (OneDrive / sharing)
The essentials in 30 seconds
- A single cloud file replaces attachments: the collaborative golden rule.
- Nominated sections = clear division of work (and no editing conflicts).
- The @mentioned comments notify: feedback is no longer lost in emails.
Spun mini-case — Collaboration & co-editing (OneDrive / sharing)
Amel co-edits the file with management and the sales team on OneDrive. It must manage versions, comments and sharing without sending conflicting attachments.
Continuation of the common theme: the Blida agri-food SME is preparing its market launch.
1. The single file shared, not copies
Save to OneDrive/SharePoint, share the link (File → Share: “People with the link can comment/edit”). A single living version: no more “Bilan-FINAL-Marie-v3” by email. Co-editing shows live cursors.
2. Comments and revision without chaos
Comments (Ctrl + Alt + M) to discuss, @mentions to assign, Resolve when processed. Version History to go back. Team rule: we never delete someone else's slide without comment, we suggest it.
3. Before diffusion: freeze properly
Proofread in Sorter (multiple voices = style breaks), pass the accessibility checker, inspect (resolved comments, personal notes), export the broadcast PDF. The link remains alive for the rest, the PDF freezes the validated version.
🔎 Concrete example — Concrete example — Report co-written by three people without pain
1. “Bilan-2026” on SharePoint, “can modify” link to Lina and Karim
2. Assigned sections (Lina: Diagnosis, Karim: Budget)
3. @mentions for arbitrations, Resolve over time
4. Proofreading Sorter + accessibility + PDF “Bilan-2026-validated”Reading: each one has its own section, the trade-offs outlined.
Lesson: History saves when “someone broke everything”.
Section vocabulary
- Co-edition
- Simultaneous editing of a .pptx stored in the cloud: colleagues' cursors and selections are visible live.
Simple example: Amel mobilizes “Co-publishing” in the preparation of the launch.
What it is not: treat “Co-editing” as a detail unrelated to the message.
Reflex: Does this choice make the presentation clearer for the audience?
- Share link
- Share button: rights (edit/read) × scope (selected people/organization). Always check before sending.
Simple example: Amel mobilizes “Sharing Link” in preparation for the launch.
What it is not: treat “Share link” as a detail unrelated to the message.
Reflex: Does this choice make the presentation clearer for the audience?
- Comments + @mention
- Anchor a remark on a slide or object; @First name notifies the person by email.
Simple example: Amel mobilizes “Comments + @mention” in preparing for the launch.
What it is not: treat “Comments + @mention” as a detail unrelated to the message.
Reflex: Does this choice make the presentation clearer for the audience?
- Version history
- File → Information → Version history: restore the state before the “crash”.
Simple example: Amel uses “Version History” in preparing for the launch.
What it is not: Treat “Version History” as a detail unrelated to the message.
Reflex: Does this choice make the presentation clearer for the audience?
In practice — Set up the team production circuit
- Save the presentation on OneDrive and create the named sections (one per contributor — the sections in 2.5 take on their full meaning).
- Share as “People you choose / Can edit” and send the link.
- Open with two people (or on two devices): each edit your section — look at the colored sliders.
- Leave a comment with @mention on a colleague's slide, then explore the version history.
Script ready to say — Collaboration & co-editing (OneDrive / sharing) (25 s)
“Share and co-edit a presentation in real time, manage comments and versions. Concretely, I check this point before planning: a single cloud file replaces attachments: the collaborative golden rule. »
Short wording, to be adapted to the audience and the context of the meeting.
Copy and paste template — “Collaboration & co-editing (OneDrive / sharing)” checklist
CHECKLIST — Collaboration & co-publishing (OneDrive / sharing)
1. A single cloud file replaces attachments: the collaborative golden rule.
2. Named sections = clear division of work (and no editing conflicts).
3. Comments @mentioned notify: feedback is no longer lost in emails.
4. Version history absolves all missteps.
EXPECTED RESULT: A single file, distributed sections, traced returns: team production without version chaos.Express version
Apply only the essentials and the first key point, then check the rendering in projection.
Remote
Share the file and check fonts, contrasts and text size before the video conference.
As a team
Lock in the common model and document choices to keep colleagues consistent.
Printed version
Keep the message titles and the text outline; remove animations that are no longer needed.
✓ Best practices
- One link, zero attachments.
- @mentions + Resolve, no long emails.
- PDF frozen for distribution, live link for continuation.
✗ Common pitfalls
- Round-trip attachments (ghost versions).
- Modify someone else's game without warning.
- Distribute the editable link to the committee.
Key takeaways
- A single cloud file replaces attachments: the collaborative golden rule.
- Nominated sections = clear division of work (and no editing conflicts).
- The @mentioned comments notify: feedback is no longer lost in emails.
- Version history absolves all wrongdoing.
48 hour challenge — apply tomorrow
Resume setting up the team production circuit on the Amel launch presentation: Save the presentation on OneDrive and create the named sections (one per contributor — the sections in 2.5 take on their full meaning).. Time 20 minutes and note what has changed for the audience.
- I can explain and apply: A single cloud file replaces attachments: the collaborative golden rule.
- I can explain and apply: Nominated sections = clear division of labor (and no editing conflicts).
- I can explain and apply: The @mentioned comments notify: feedback is no longer lost in emails.
Frequently asked questions
Can two people edit the SAME slide at the same time?
Yes technically, but it is a source of surprises (objects moved before your eyes). Good practice: one section – therefore slides – per person.
How do you collect someone's opinion WITHOUT them being able to modify it?
Share a link in “Can display”: it sees and can comment depending on the setting, but does not touch anything. For a fixed milestone, send a PDF.
How to co-publish a .pptx with several people?