Workplace Productivity and Office Skills
Collaboration, file sharing and meetings
Most documents now have several authors at once, and most meetings happen through a screen. Collaboration skill means knowing where a file should live, who can open it, how to recover last week's version and how to run a call that ends in decisions rather than a recording nobody watches. Teams, SharePoint, OneDrive, Google Drive and Meet offer the same building blocks; this page is about using them so a team can still find its work a year later.
Why this topic exists: Co-authoring, version history, sharing and permissions, channels, document libraries and online meetings in Teams, SharePoint, OneDrive, Drive and Meet: DigComp 2.2's communication and collaboration area (six competences) and ICDL's Teamwork module.
Collaboration tools solved the problem of emailed attachments and created a new one: nobody knows where anything is. One team can hold files in personal OneDrive folders, a SharePoint library, several Teams channels and a Google Drive shared by a partner, each with its own permissions. This topic is less about any single product than about deciding where work lives, who can reach it and how the team finds it again. DigComp 2.2 files it under communication and collaboration, the largest of its five areas with six competences.
Where a file should live
| Kind of file | Sensible home | Why |
|---|---|---|
| A draft only you are working on | Your own OneDrive or My Drive | Private until you share it, and backed up |
| A document the whole team maintains | The team's channel or SharePoint library; a shared drive in Google Workspace | The team owns it, so it survives when the author leaves |
| Material for people outside the organisation | A link with the narrowest access that works, with an expiry where the tool allows | External sharing is where leaks start |
| Meeting notes and decisions | Attached to the meeting or the channel, not in one person's inbox | The next person to join needs to find them |
Co-authoring works once files sit in shared locations: several people type at once, and version history lets anyone view or restore an earlier state. It breaks when someone downloads a copy, edits offline and uploads a file called final_v3 next to the original. The habit to teach a team is short: open from the shared location, send links rather than attachments, and restore from history instead of hoarding private copies. Setting up libraries, retention and external-sharing policies is an administrator's job and belongs to IT; this page serves the people working inside them.
Meetings that earn their time
Online meetings in Teams, Zoom or Meet are now the normal way many teams talk, and their failures are familiar: no agenda, the wrong people, and outcomes nobody wrote down, remembered differently by each person who attended. Recordings and transcripts help those who missed the call, yet they do not replace a short written summary. Nor does every question need a meeting: a decision one person can make after reading a page is usually faster by message, and a meeting of eight people for thirty minutes costs four working hours. A few habits make the difference.
- Put the purpose in the invitation. One line naming what must be decided lets people judge whether they need to come.
- Open the shared file instead of presenting your screen when the group has to edit something, so everyone can type into it during the call.
- End with owners and dates posted in the meeting chat or channel, where they stay attached to the conversation.
- Move running discussions into a channel and keep meetings for what needs voices; many weekly status calls can become a thread.
- Link to the tracker, do not retell it. Where work items live in a tool such as Jira, point to them rather than restating their status in chat.
Next to this topic
- Digital literacy and computer essentialsFiles and folders, the browser, accounts and passwords, safety habits and typing: DigComp 2.2's information, safety and problem-solving areas and ICDL's Computer & Online Essentials; the entry point of the whole field.
- SpreadsheetsCells, ranges, tables, formulas and charts in Excel and Google Sheets: the MO-210 blueprint's five areas and ICDL Spreadsheets; the single most examined office skill.
- Documents and word processingStyles, sections, references, tables and document collaboration in Word and Google Docs: the MO-110 blueprint and ICDL Documents; mail merge and templates are the daily craft the exam leaves out, and the skill hiring managers assume and rarely test.
- PresentationsSlide masters, layouts, themes, notes, transitions and export in PowerPoint, Google Slides and Keynote: the MO-310 exam and ICDL Presentation; design taste is the part no exam covers.
- Email and calendarRules, folders and labels, shared mailboxes, delegation, scheduling and etiquette in Outlook and Gmail: DigComp's communication area and the MO-400 Outlook exam that still counts towards MOS Associate.
- Notes and personal knowledge managementNotebooks, tags, links and search in OneNote, Loop, Notion, Evernote and Obsidian: DigComp's managing of data, information and content; a field with practices and products but no examining body, an honest gap.
- Workplace automation: Power Automate and Power AppsFlows, triggers, connectors, approvals and canvas apps built by the people who use them, plus Copilot Studio agents: the PL-900 blueprint's five areas; robotic process automation for the desktop belongs here too.
- AI assistants in the officeCopilot in Word, Excel, PowerPoint and Outlook, Gemini in Workspace, ChatGPT for everyday work, and the questions of grounding and data protection: the Applied Skills business-user lab, ICDL AI Essentials, DigComp 2.2's AI examples.
- Enterprise systems for end users: SAP and OracleModules, transactions, master data and the daily screens of SAP S/4HANA, Oracle E-Business Suite and Fusion, Dynamics 365 and Workday: SAP Learning's certifications name the consultant behind each module; the end user is who this topic serves.
Concepts to know
Glossary entries with the reason each one matters here.
- Track changes
Formal review inside shared documents.
- Co-authoring
Simultaneous editing of one stored file.
- Version history
Restoring and naming earlier states.
- Sensitivity label
Classification that travels with shared files.
Tools of the trade
- Jira
Where many teams' work items live next to their chat.
Frequently asked
- Should team files live in Teams or in SharePoint?
- In Microsoft 365 they are largely the same place: files shared in a standard Teams channel are stored in the team's SharePoint site, while files shared in a private chat go to the sender's OneDrive. Use the channel when the conversation around a file matters, and the SharePoint site directly when the library needs its own structure or a wider audience.
- What is the difference between sharing a link and sending an attachment?
- An attachment is a copy that starts drifting from the original the moment it is sent. A link points everyone at one file with one version history, and lets you change or withdraw access later.
- Is there a certificate for collaboration skills?
- Not a common one for end users. Google's Workspace Learning Center lists guides but no end-user exam, and ICDL's CORE programme has no dedicated collaboration module. The skill shows in how you run shared files and projects, which is what a reference will describe.
Courses in the directory
119 courses are filed here; the top 6 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital