The 15 practices we’ve outlined are aimed at everyday users rather than IT administrators. They’re grouped into five areas: managing documents, searching effectively, handling permissions safely, working more efficiently day-to-day, and building an intranet people actually want to use.
Document Management
1. Tag documents with metadata instead of relying on folders.
Folders force every file into exactly one place, which breaks down the moment a document logically belongs in more than one category. Think of a signed vendor contract that’s simultaneously “Legal,” “2026,” and “Active.”
Metadata columns let you describe a file along several dimensions at once, so it can be found by department, by year, or by status without ever being duplicated. It also plays to SharePoint’s strengths: the search index reads metadata directly, so well-tagged files surface immediately, while files buried three folders deep often don’t.
2. Settle on a file-naming convention before anyone starts uploading.
Once a library fills up with files like “Proposal_final_v3_useThisOne.docx”
Then there’s no clean way to fix it retroactively.
Pick a simple, consistent pattern up front — something like Client_DocType_YYYY-MM-DD — and hold the team to it. Skip spaces and special characters, and drop “final” from filenames altogether; a date does the same job without the ambiguity of a colleague’s “final” being someone else’s second draft.
3. Turn on version history for every document library.
This is one of SharePoint’s best features and one of the least used. With versioning enabled, every save is kept as a retrievable snapshot, so if a document gets overwritten or a draft goes sideways, you can roll back to any earlier point in seconds rather than emailing around asking if anyone has a backup copy.
Turn it on under Library Settings → Versioning Settings, and cap it at a reasonable number of versions (50 is generous for most libraries) so the library doesn’t bloat.
4. Co-author instead of passing attachments back and forth.
Emailing a Word or Excel file for review is how organizations end up with five slightly different versions of the same document and no way to tell which one is current.
Opening the file directly in SharePoint — in the browser or the desktop app — lets several people edit it at once, with changes syncing live. Share the link to the file rather than the file itself, and there’s only ever one version to keep track of.
5. Automate approvals with Power Automate rather than chasing them by email.
Any process where a document needs a sign-off; an expense form, a policy revision, a contract; can be automated without writing any code.
Power Automate, included with Microsoft 365, can watch a library, kick off a notification when a document lands, route it to the right approver, and log the outcome automatically. Start from one of the built-in SharePoint approval templates rather than building a flow from a blank canvas.
Making Search Actually Work
6. Put exact phrases in quotation marks.
A search for budget review returns anything containing either word anywhere in the document, which on a large site can mean hundreds of loosely related results.
Searching “budget review” in quotes narrows that down to documents containing that exact phrase, cutting out most of the noise in one step.
7. Search from within the site you already know, not the global index.
SharePoint’s default search spans your entire Microsoft 365 tenant, which is helpful when you have no idea where a file lives and unhelpful when you do. If you know roughly where a document should be, navigate to that site or library first and search from there – the results are automatically scoped to that location and tend to be far more relevant.
It’s also worth remembering that SharePoint indexes the actual text inside documents, not just filenames, so a phrase you recall from the body of a file will surface it even if the title gives no hint.
Permissions and Sharing, Done Safely
8. Understand permission inheritance before you break it.
By default, a file inherits its permissions from its folder, which inherits from its library, which inherits from the site. That’s a feature, not a limitation, it means access can be managed in one place and it flows down automatically.
The trouble starts when inheritance gets broken to share one file differently; each break creates an exception that’s easy to lose track of later. Only break inheritance when there’s a genuine reason to.
9. Share the specific file, not the library it lives in.
When someone needs one document, send them a link to that document, not access to the whole library.
Using the Share option on the file itself and choosing a specific person or a “people with the link” option means the recipient sees only what they were sent, not everything else sitting alongside it.
10. Set an expiration date on any external sharing link.
When a file goes out to a client, contractor, or partner, Microsoft 365 lets you attach an expiry date to that link at the point of sharing.
It’s a small habit that removes a much bigger risk: forgetting to manually revoke access once a project has wrapped up.
11. Periodically review who actually has access.
Permissions tend to accumulate and rarely get cleaned up on their own. People switch teams, contractors move on, but their access often lingers.
Every few months, check Site Settings → Site Permissions and prune anyone who no longer needs to be there.
For libraries holding sensitive material, run a permissions report to catch any files where inheritance has quietly been broken.
Everyday Productivity
12. Sync a document library to your desktop.
OneDrive Sync maps a SharePoint library onto your local file system, so it shows up as an ordinary folder in Windows Explorer or macOS Finder and updates automatically as files change.
From a document library, click Sync in the toolbar, and within a minute the library behaves like any other folder on your machine – no browser required.
13. Keep your most-used links at the top of every intranet page.
People visit an intranet to find something specific, be it a form, a policy, a tool, and if that takes scrolling or digging, most will give up and ask a colleague instead.
A Quick Links section near the top of the page, grouped around what people are actually looking for, solves this directly. A useful test: if the same question comes up more than twice, the answer belongs in a quick link.
Designing an Intranet People Use
14. Map out the structure before building a single page.
The costliest mistakes in an intranet project happen in week one, decisions about sections, ownership, and navigation that everything else gets built on top of.
Reorganizing later isn’t a tweak, it’s a rebuild.
Before creating anything, settle three questions: what are the main sections, who owns each one, and how will people move between them. Get that agreed with stakeholders first.
15. Use hub sites to tie related team sites together.
A hub site lets other sites associate with it and share navigation, branding, and search scope. In practice, most organizations end up with one hub, the company intranet homepage, with department sites (HR, IT, Finance, and so on) connected underneath it.
That way employees can move between departments without hunting for links, and a search from anywhere in the hub reaches everything connected to it.
Bringing It All Together
None of these require special licensing or admin rights beyond what’s already built into a standard Microsoft 365 subscription – they’re mostly a matter of habit.
Adopting even four or five of them (naming conventions, version history, scoped search, and permission audits are the highest-leverage ones) tends to fix most of the day-to-day friction people associate with SharePoint.