How to Link SharePoint Document Set Defaults to Library Templates
Question details
The user wants to dynamically link a SharePoint Document Set's default files to a central library template, rather than uploading static copies.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Configuring default documents that automatically populate when a new Document Set is created in a SharePoint library.
- Observed behavior
- SharePoint currently requires administrators to upload a static copy of the default document into the Document Set settings, rather than allowing a dynamic reference link to an existing template in a separate library.
Verify that you have Site Collection Administrator permissions, as accessing and modifying Document Set content types and library settings requires elevated access rights.
Configure Document Set Default Content Manually
Since dynamic linking is not natively supported, you must upload a physical copy of your template directly into the Document Set configuration.
SharePoint's native Document Set settings do not support dynamic reference links to external template libraries. To set default files, you are required to upload a static copy of the document.
While this means you cannot link directly to a live template file, manually uploading ensures that the exact version you need is cloned whenever a user creates a new Document Set.
Navigate to the SharePoint document library where your Document Set is located. Click the Gear icon in the top right corner and select 'Library settings'.
Click on 'More library settings'. Under the 'Content Types' section, click on the specific Document Set content type you want to modify.
On the Content Type settings page, click on 'Document Set settings' to open the configuration panel.
Scroll down to the 'Default Content' section. Click 'Browse' to locate the template file on your computer, specify the content type, and click 'OK' to upload and save the default document.

Automate Template Syncing via Power Automate
Overcome the dynamic linking limitation by using Microsoft Power Automate to automatically copy updated templates into your Document Sets.
Create and Manage Standardized Templates with WPS Office
While SharePoint handles the storage and configuration of your Document Sets, you still need a reliable suite to create those library templates. WPS Office provides a highly compatible, lightweight, and free alternative to Microsoft Office, allowing you to design, edit, and standardize your organizational templates with ease.
- 1. Download and Install: Get WPS Office for free from the official website and install it on your device.
- 2. Design Your Templates: Open WPS Writer, Spreadsheet, or Presentation to design your standardized organizational templates and save them in standard Microsoft formats.
- 3. Upload to SharePoint: Upload your finished templates into your SharePoint Document Set settings for your team to use.

Frequently Asked Questions
Can I dynamically link a Document Set default file to another SharePoint library?
No, natively SharePoint does not support dynamically linking default documents in a Document Set to live files in another library. You must either upload a static copy into the Document Set settings or use a workflow automation tool like Power Automate to sync the files.
Where do I find the Document Set settings in SharePoint?
To access these settings, go to your document library, click the Gear icon, select 'Library settings', click 'More library settings', select your Document Set under 'Content Types', and finally click 'Document Set settings'.
What happens if I update the original template file after setting it as a default?
If you uploaded the template directly via the Document Set settings, updates to the original file in your local drive or another library will not reflect automatically. You will need to manually delete the old default and upload the newer version.
Why does Microsoft restrict linking to templates in Document Sets?
SharePoint handles Document Set defaults by physically provisioning the files when the folder is generated. Dynamic linking would introduce permission and versioning complexities during the creation process, so the system requires a static payload.




