Skip to main content

SharePoint Site Provisioning for Teams and Channels (Beta)

Rob avatar
Written by Rob
Updated this week

Overview

nBold now lets you provision the entire SharePoint site that backs each Microsoft Teams team and Private / Shared Channel ones. When a new team is created from a template, the corresponding SharePoint sites (including those from Private and Shared Channels) are cloned so that every workspace starts with the same pages, lists, libraries, navigation and metadata.

Why it matters: Many collaboration processes depend on carefully‑designed SharePoint information architecture. With this feature you no longer need to recreate that structure manually or maintain a separate site template solution—nBold handles it for you


What gets copied

Area

Details

Document Libraries with Files, Folders & Columns.

All Files, Folders and Metadata, from every document library in the source team site and the SharePoint source Sites (from Standard Channels, Private / Shared Channels)

Microsoft Lists with Items & Columns

All Microsoft Lists plus their items, custom columns and column settings.

Views

Views for Lists and Document Libraries.

Site Pages

Modern pages and their web‑parts; the home page is preserved.

Site Navigation

Global navigation ("mega‑menu") and Quick Links web‑parts.

Sensitivity Labels

Labels applied to each document library are retained.

Document‑Library Settings (Partial)

The following properties are cloned:
Basic: Title, Description, OnQuickLaunch
Advanced: ContentTypesEnabled, EnableFolderCreation, ForceCheckout, Hidden, NoCrawl, AllowContentTypes, DefaultItemOpenUseListSetting

Versioning: EnableVersioning


About SharePoint Tabs

In the template you may add several SharePoint Tabs such as Pages, Lists, or Document Libraries. When Advanced cloning is enabled, those tabs will be reconfigured to display the new Page, List or Library created in the new site.


What is not copied (current limitations)

  • Site‑level permissions (e.g., owners, members, visitors, SharePoint groups)

  • Unique user permissions set at library or list level

  • Document‑library settings outside the property list above

  • Sub‑sites, publishing features and classic web‑parts

If you rely on custom permission models, plan to configure them manually or via a post‑provisioning automation.



How to enable it in a template

  1. Open nBold → Templates and select the template you want to edit (or create a new one).

  2. In the bottom check "Advanced Cloning".

  3. Need help or have feedback? Contact us at [email protected] or use the in‑app chat.

Did this answer your question?