Skip to main content

Document Set

A document set is a supercharged folder, a content type that groups related documents into a single unit with shared metadata, a customizable welcome page, and its own version snapshots. Tag the set once and every document inside inherits the values, which makes document sets ideal for repeatable bundles like project files, client folders, or HR employee records. Each new set can start with default template documents already in place, so every project, client, or case begins with the same structure.
Related Features
Content Type, Content Type Gallery
See It In Action

Common Use Cases

  • Project documentation: store all files related to a project with shared metadata
  • Client or case files: group contracts, correspondence, and deliverables together
  • HR employee files: manage onboarding, reviews, and forms per employee
  • Legal matters: organize documents by case or matter with consistent classification
  • Proposals and engagements: bundle drafts, approvals, and final versions
  • Repeatable processes: use document sets for consistent, recurring document groupings

Benefits

  • Shared metadata: tag once at the document set level and apply it to all documents inside
  • Consistency: enforces standardized metadata and structure across related files
  • Single unit management: move, copy, or apply policies to all documents at once
  • Metadata over folders: adds intelligence missing from traditional folder structures
  • Repeatable by design: well-suited for smaller, predictable document sets
  • Governance-friendly: supports policies and automation at scale

How It Works

  • Welcome page: each set opens to a page showing the shared properties and the documents inside, customizable with web parts
  • Shared metadata: enter values once at the set level and they push to every document inside automatically
  • Default content: every new set starts with the right template documents already provisioned
  • Version snapshots: capture the state of the whole set, properties plus documents, at key milestones
  • One unit: the entire set can be moved, copied, shared as a link, approved, or secured with permissions together

Limits and Nuances

  • Not on by default: a site collection administrator must activate the Document Sets feature before any sets can be created
  • Not a regular folder: a document set must be configured as a content type and added to the library before anyone can create one
  • Plan before you build: columns, default content, and shared metadata require real upfront design; changing the structure later touches every existing set
  • Best for small, repeatable bundles: one set per project, client, or employee; not for large or unstructured collections
  • One library architecture: all sets live in a single library, so the usual library limits apply; watch the 5,000 item view threshold and index columns early
  • Sync flattens sets: OneDrive sync shows document sets as ordinary folders; the welcome page and shared metadata stay in the browser, and folders created locally do not become sets
  • User training matters: if people cannot tell when to create a set versus a folder, the library structure erodes quickly

Common Questions About Document Sets

What is a document set in SharePoint?

A document set is a folder-like content type that groups related documents and manages them as one unit. It carries shared metadata that every document inside inherits, opens to a welcome page showing the set’s properties and contents, and supports version snapshots of the whole bundle. It is built for repeatable groupings like projects, client files, or legal matters.

How do I enable document sets in SharePoint?

Two steps. First, a site collection administrator activates the Document Sets feature under Site settings, Site collection features. Second, on the library, turn on Allow management of content types in Advanced settings and add the document set content type. After that, users create new sets straight from the library’s New menu, just like a document.

What is the difference between a document set and a folder?

A folder only contains files. A document set contains files plus intelligence: shared metadata applied to everything inside, a welcome page that explains the set, default documents provisioned automatically, and the ability to version, route, and secure the whole bundle as one item. Folders are fine for casual storage; document sets are for repeatable, managed work products.

Do document sets work with OneDrive sync?

Partially. When you sync a library that contains document sets, each set appears in File Explorer as an ordinary folder – the welcome page, shared metadata, and set-level commands stay behind in the browser. Folders created locally do not become document sets either. Teams that live in File Explorer should weigh that trade-off before standardizing on document sets.

When should I use document sets instead of separate libraries?

Use document sets when the same small bundle of documents repeats over and over – one set per project, client, case, or employee – and you want consistent metadata and templates each time. Use separate libraries when content areas are genuinely different, need different permissions, or will grow large. Sets shine at repeatability; libraries shine at separation and scale.

Can each document set have its own permissions?

Yes – a document set can be secured individually, which suits scenarios like HR employee files where each set should only be visible to certain people. Use this sparingly, though: every uniquely permissioned set is one more thing to govern, and large numbers of broken inheritance points complicate audits and slow administration. Where possible, secure at the library level instead.