SharePoint Document Library Best Practices: What I Set Up on Every Library

Our events team asked me why nobody could find last quarter’s summit invitation. The Documents library on their site had folders inside folders, files named Final v3, and three copies of the same flyer. Adding yet another folder level was their fix, and it only made the next search slower.

In this tutorial, I’ll walk through the SharePoint document library best practices I now set up on every library, tested on that same events library on 11/06/2026: metadata columns and grouped views instead of deep folders, defaults, version limits, permissions, labels and the real service limits.

Quick answer: Plan one library per content purpose, tag files with a few Choice or managed metadata columns, and give people views grouped by those columns instead of folders more than one or two levels deep. Set column defaults, keep versioning on with the Automatic version limit, keep permissions at the site or library level, and stay well inside the 5,000-item view threshold and 400-character path limit.

Plan your libraries before anyone uploads a file

Every site comes with one Documents library, but you aren’t limited to it. I create a library per content purpose (contracts, event materials, policies) so each one gets its own columns, views and settings. You can add one in a minute with the steps to create a document library.

Keep the site structure flat too. Microsoft no longer recommends subsites; create one site per team or project and connect related sites with a hub. More setup guides live on our SharePoint tutorials page.

Use metadata columns instead of deep folders

Microsoft’s own information architecture guidance says folder structures nested more than one or two levels create a real discoverability burden. Metadata fixes that, because one file can show up in every view that needs it. On the events library I added two Choice columns:

1. Open the library and select + Add column.
2. Pick Choice in the Create a column panel and select Next.
3. Name it Document Type and enter Agenda, Calendar, Flyer, Invitation and Policy as the choices.
4. Select Save, then repeat for Event Quarter with Q1 2026 to Q4 2026.

Choice columns are perfect for short, stable lists. If users need to add their own value, use a Choice column with fill-in options; for company-wide terms, use managed metadata. Then I tagged the four demo files, such as Spring Webinar Agenda 2026 as Agenda and Q1 2026.

Folders still have a place for security and very large libraries. If you need them, follow our SharePoint folder structure best practices and keep them shallow.

Build views people actually use

Tags only help when a view uses them. I created a public view named By Document Type that groups by Document Type and shows Name, Document Type, Event Quarter, Approval Status and Modified. The steps are the same as for any SharePoint list view.

The result shows groups like Document Type: Agenda (1) and Document Type: Flyer (1), with no folders at all. Make the most useful view the default, and add filtered views (this quarter, my documents) so no view tries to load thousands of files.

Set defaults and required columns so tagging happens

People skip optional columns. Two settings fix that, and both live on the library settings page (gear icon, then Library settings, then More library settings):

Make the one or two columns that drive your views required, and use Column default value settings to fill a value automatically, even per folder. I explain the details in how to set a column default value.

Important: our library has content approval turned on. When I tagged the approved files, every one went back to Pending, so tag files before approval or plan a re-approval.

Use content types when documents need different columns

Columns and content types are the two main metadata tools in SharePoint. When a contract needs Vendor and Renewal Date but a flyer doesn’t, create a Contract content type with its own columns and template, and add both types to the library. To share them across sites, publish them from the content type hub.

Know the limits before the library gets big

These are the current SharePoint in Microsoft 365 limits that shape how I design a library:

Limit	Value	What I do about it
Files and folders per library	30 million	Split by purpose long before that
List view threshold	5,000 items per query	Index the columns you filter on, use filtered views
Break permission inheritance	Not on a library or folder over 100,000 items	Set unique permissions early, or use a separate library
Unique permissions per library	50,000 supported, 5,000 recommended	Keep item-level sharing rare
Full path length	400 characters, decoded, incl. file name	Short library, folder and file names
File size	250 GB per file	Rarely the problem; path length usually is
Sync	Up to 300,000 files per library recommended	Sync only the folders people need

The 5,000 threshold doesn’t cap how many files you can store. It limits what one query can process, which is why indexed columns in SharePoint matter on busy libraries.

Choose a version history limit on purpose

Versioning is on by default for document libraries, so the real decision is how many versions to keep. Open Versioning settings and look at the version time limit and the count limit:

• No time limit keeps up to the major version count (500 by default on our library).
• Automatic deletes versions over time based on activity and file age. Microsoft recommends it for optimized storage.
• Manual sets a count, an expiration in days, or both. The UI won’t accept fewer than 100 versions or 30 days.

Versions over the limit are deleted permanently, not sent to the recycle bin. Files under a retention policy or eDiscovery hold ignore the library limit. I only turn off versioning on scratch libraries.

Keep permissions at the site or library level

Give access through the site’s groups and let the library inherit. When a library needs a different audience, break inheritance at the library, not on hundreds of files. Use our SharePoint permissions best practices for groups and audits, and check Contribute vs Edit permissions before you pick a level.

Protect and retain files with labels

If your organization uses Microsoft Purview, set a default sensitivity label on the library. New files and edited files get that label unless they already have a higher-priority or manually applied one; existing files at rest aren’t labeled. Start with creating sensitivity labels in Microsoft 365.

For records, the library settings page has Apply label to items in this list or library for a default retention label. Site-wide rules belong in a site retention policy instead of manual cleanup.

Common mistakes and how to fix them

• The view stops loading past 5,000 items: add an index on the filtered column and filter the view. See the list view threshold error.
• Files won’t open or sync because the path is too long: rename deep folders and long file names until the full path is under 400 characters.
• All approved files are suddenly Pending: content approval resets the status when metadata changes. Tag files before approval.
• Nobody fills in the columns: make the view-driving column required and set a default value.
• Storage keeps growing: switch the version time limit to Automatic, or set a Manual count of 100 or more.

If you’re tidying up more libraries this month, these guides help next:

• SharePoint Document Management System
• SharePoint Document Set vs Folder: Which One Should You Use?
• How to Create Document Library in SharePoint Using PnP PowerShell (With Multiple Folders)
• How to Get SharePoint Document Library Size Using PnP PowerShell (3 Easy Methods)

Frequently Asked Questions