Book a demo

One Template, Full Workspace: Teams and Their SharePoint Sites, Cloned Together

January 30, 2026 · nBold

nBold turns playbooks into ready-to-work workspaces — the point is that teams reuse a proven setup instead of rebuilding it. A template that only recreates channels and tabs doesn’t deliver on that: the SharePoint site underneath, with its pages, lists, and libraries, still had to be rebuilt by hand every time, leaving half the workspace behind. Creating a team from a template now clones the associated SharePoint sites along with it — including private and shared channel sites — so the workspace arrives whole, not half-built.

What’s new

  • Team creation from a template now provisions the linked SharePoint site(s) as part of the same step, not as a separate follow-up task.
  • Pages, lists, and libraries from the template’s source site are cloned into the new site — not just the folder structure.
  • Navigation and metadata carry over too, so the new site looks and behaves like the one it was modeled on.
  • Private and shared channel sites are included, so channel-level SharePoint content is no longer the one piece left out of template cloning.

Why it matters

Most of the manual work in “setting up a new team” was never the Teams part — it was rebuilding the SharePoint site behind it: recreating pages, re-adding the same lists, restoring the folder layout someone else already built once. That work now happens automatically, every time, from the template. Teams built the same way stay the same way, without anyone doing the rebuild by hand.

See how this fits into the bigger picture on the platform overview, or read how standardized templates keep delivery consistent across every team in Repeatable Work at Scale. Want a walkthrough with your own templates? Book a demo.

All resources