ntworld.ink
Digital Literacy: Workplace Skills

OneDrive, SharePoint & File Sense

Where your files actually live, how sharing and permissions work, how to share without accidentally exposing things, how to roll back a mistake, and a few habits that save hours over the course of a project.

STRAND · Digital Foundations LEVEL · Beginner-friendly FORMAT · Hands-on session
// where files live

Where Your Files Actually Live

There was a time when "my files" meant files on the C drive of the laptop in front of you. That time is gone. Your work files now live in the cloud, and the copy on your laptop is just a local mirror that keeps in sync with the master.

Your laptop is a window into your files. The files themselves are on Microsoft's servers.

Why that matters: you can break your laptop, drop it in a creek, leave it on a plane, and your files are still fine. You can sign in to any other device and everything comes back. That's the upside.

The downside: people still think files "live" in folders they see in File Explorer, and they end up confused about what's synced, what's backed up, and what's actually somewhere everyone on the team can see. This session is about clearing that confusion up.

// yours vs ours

OneDrive vs SharePoint

Two names, easy to confuse, different jobs.

Yours

OneDrive

Yours. Your personal work storage. Think of it as the new "Documents" folder, just in the cloud.

Default private. Nobody else can see your OneDrive unless you share something specifically.

Good for: drafts, personal notes, files you're working on before they're ready for a team, scans of reports, anything that's yours.

Leaves when you leave. When you exit the organisation, your OneDrive goes with your account.

Ours

SharePoint

Ours. Shared storage for a whole team, project, or branch.

Permissioned. Everyone on the site can see everything on the site unless folders are restricted.

Good for: final documents, policies, shared templates, project files the team all needs, records that survive staff changes.

Survives staff changes. When someone leaves, the files stay on the team's site.

The rule of thumb that works 90 percent of the time: if a file is just yours and nobody would ever need it if you won the lottery tomorrow, OneDrive is fine. If someone else might ever need the file and you're not there to email it to them, it belongs on SharePoint.

Under every Teams team is a SharePoint site

When you join a Microsoft Team, you're automatically joining a SharePoint site. The "Files" tab inside a Team is just a window into that site's document library. Knowing this makes a lot of Teams quirks make sense.

// sharing well

Sharing, in Plain English

There are two wrong ways to share a file, and one right way.

The old wrong way: email the file as an attachment. Now there are three or four versions in three or four inboxes. Nobody knows which is current. Edits get made in parallel. Chaos.

The other wrong way: send a link without thinking about permissions. Either the recipient hits a wall (no access) or you've opened it up to "anyone with the link" and now it's shareable with the whole internet.

The right way: use "Share" in the Office app, pick the right permission, paste the link. Everyone sees the live document. One version. Changes tracked. History preserved.

Don't email attachments. Share the link.

When you click Share in Word, Excel, PowerPoint, or right-click a file in OneDrive or SharePoint, you get a dialog. The three things to pay attention to:

Who can access. Specific people, people in your organisation, or anyone with the link. Default to "specific people" unless you have a reason otherwise.

Can edit or view only. If they don't need to edit, give view. You can always upgrade later.

Expiry date. Optional, but a good habit for external sharing. "Expires in 30 days" prevents links from living forever.

// permissions

The Four Permission Levels

Every sharing link in M365 falls into one of four buckets. Know which you're handing out.

Specific people

Only the named people can open the file. Safest default. Use this for anything sensitive, or anything you only need to share with a handful of people.

People in your organisation

Anyone signed into your org's tenant can open the file. Good for widely-useful documents (policy notes, templates) where you don't want to maintain a list. Not for sensitive content.

People with existing access

A way to send a link to a file without changing who can access it. Useful when you know the person already has access and you just want to point them to the exact file.

Anyone with the link (caution)

The link works for anyone who has it, inside or outside the organisation, no sign-in required. This is how accidental public disclosures happen. Only use if the content is genuinely fine for the public internet, and prefer to add an expiry date.

Check the default in your org

Some organisations default to "anyone with the link", others to "people in your org", others to "specific people". Whatever yours is, know it before you click Share. One moment of attention prevents a lot of later stress.

// version history

Version History, Your Safety Net

Every file in OneDrive and SharePoint keeps a version history, automatically. Every time you save (and it auto-saves every few seconds in the cloud apps), a new version is recorded. You can roll back to any previous version without losing the current one.

How to find it. Right-click a file in OneDrive or SharePoint in your browser, choose "Version history". You'll see a list of saved versions with timestamps and who changed them. Click any one to preview, open, or restore.

What it saves you from:

You almost never actually lose work in M365. You just have to know where the spare copy is.

How long it keeps versions. By default, 500 versions per file. For most users this is weeks or months of history. Deleted files also go to a Recycle Bin for 93 days before they're truly gone.

// sync & offline

Syncing and Working Offline

The OneDrive app on your laptop keeps a local copy of your cloud files, and syncs changes up and down automatically when you're online. That means you can work on a file on the plane, and when you land and reconnect, your changes go up to the cloud.

The little cloud icons in File Explorer tell you what's synced:

For travel to remote areas

Before you travel, right-click the OneDrive folders you'll need and choose "Always keep on this device". That pins them so they're guaranteed to work offline. When you're back in coverage, everything syncs back up. Copilot and Office web features won't work offline, but editing existing documents will.

// teams files

Teams Sites and Where Your Files Really Go

Teams is where most files end up in a modern workplace, and it's also where the most confusion happens. A quick explanation saves a lot of frustration.

Every Team has a SharePoint site behind it. The Files tab inside a Teams channel is a view of a folder on that site. If you upload a file to a channel, it's actually landing on SharePoint.

Every channel has its own folder. Files uploaded to "General" don't appear in "Project Alpha" and vice versa. If someone can't find the file you shared, it's usually because they're looking in the wrong channel.

A private channel has a separate site. Private channels have their own mini-SharePoint site, which is why their files are invisible to people not in the channel.

Chat files go to your OneDrive. When you send a file in a 1-on-1 or group chat (not a channel), it lands in your OneDrive in a folder called "Microsoft Teams Chat Files", and is auto-shared with the chat participants.

This matters for records and handover

Chat files live in the sender's OneDrive, which means they disappear when the sender leaves. Anything that needs to survive a staff change should be posted to a channel (goes to SharePoint) or uploaded directly to the team site, not sent as a chat file.

// file sense

A Few Habits That Save Hours

Small habits, big payoff.