Every SharePoint site, structured and governed from the first minute.
Provision SharePoint sites with libraries, metadata, files, Lists, and governance built in — standalone or alongside a Team, structured and compliant by default.
A blank site is not a ready workspace.
Out of the box, a new SharePoint site has no libraries configured, no folder structure, no document templates, no metadata columns, no Lists and no reference pages. Every team starts from zero and rebuilds the same structure — inconsistently, and every single time. The cost is slow starts, scattered documents and a sprawl of sites no two of which look alike.
Slow, inconsistent starts
Each team improvises its own libraries and folders, so no two workspaces of the same type are organised the same way.
Content scatters
Without pre-set libraries and metadata, documents land wherever is convenient — and become impossible to find or report on later.
Governance arrives late
Sites created ungoverned have to be labelled, capped and brought into policy after the fact, if anyone remembers at all.
Defined once, provisioned every time.
Every element below is set in the template. Every site created from that template gets exactly the same structure — automatically, in the same pass that creates it.
Document libraries with metadata
Libraries arrive pre-configured with the right columns, metadata and default views — a Contracts library here, a Deliverables library there — not an empty Documents folder every team rebuilds by hand.
Folder structures and file templates
Folder hierarchies and document templates (Word, Excel, PowerPoint) are cloned into every site. Teams open to the SOW, the proposal and the discovery questionnaire already in place, in your formatting.
Microsoft Lists, pre-configured
Lists land with columns, items and settings ready to use — a risk register, a stakeholder tracker, an action log — so each site has structured tracking from the first minute, not a blank list shell.
Site pages
Onboarding guides, charters, playbooks and process documentation are cloned into every site, giving each team its reference content immediately instead of a home page nobody fills in.
Site navigation
Every provisioned site inherits the same navigation, so libraries, lists and pages stay findable in the same place across every workspace of that type.
Storage quota per template
A maximum storage quota is set per template, giving IT control over consumption by workspace type — a 5 GB event site, a larger major-account site — rather than one tenant-wide cap.
Standalone, or alongside a Team.
SharePoint provisioning is a first-class scenario in nBold, not a by-product of creating a Team. Provision a site on its own for document-led work, or provision a site and a Team together from a single template when both belong to the same workspace — the same engine, configured to the scenario.
SharePoint only
A standalone site for document-centric work — a policy library, a knowledge base, a records hub — with structure and governance, no Team required.
Teams + SharePoint
A Team and its site provisioned together from one template, with channels, Planner, Lists and the full site structure in place from day one.
One governance model
Whichever shape the workspace takes, the same naming, labels, membership, quota and lifecycle policies apply.
The same engine, configured per scenario
A few examples of how one provisioning engine produces a different ready-to-use site for each kind of work.
| Workspace type | Key libraries | Key Lists | Key site pages |
|---|---|---|---|
| Project workspace | Deliverables, Client Communications | Risk Register, Action Items | Project charter, meeting-notes template |
| Deal room | Contracts, Proposals | Milestone Tracker, Contact List | Deal playbook, discovery checklist |
| Account management | Account Documents, Renewal Docs | QBR Tracker, Issue Log | Account overview, success plan |
| IT / operations | Runbooks, Change Requests | Change Log, Asset Register | Team charter, escalation guide |
Governed from the moment it exists.
Provisioning and governance arrive together. There is no gap between "site created" and "site governed" — the guardrails are applied in the same pass that builds the structure.
Applied at creation
Naming convention, sensitivity label and privacy setting are set on the site as it is provisioned — not retrofitted later.
Bounded by design
Membership rules and a per-template storage quota cap who can access the site and how much it can consume.
Governed for life
The site follows the same lifecycle policy as the rest of the workspace — inactivity detection, owner notification, archival or deletion.
nBold acts on your Microsoft 365 tenant through the Microsoft Graph API, under a service account you control — no custom SharePoint development and no separate infrastructure to maintain. ISO 27001 and SOC 2 Type II certified.
Part of the wider platform.
Site provisioning is one expression of the same templating engine that provisions Teams and applies governance across your estate.
Templates
Encode the site once — libraries, files, Lists, pages and quota — and provision it consistently every time.
Explore TemplatesTeams templates
Provision a Team and its SharePoint site together from one template, governed end to end.
Explore Teams templatesGovernance
Naming, labels, membership and lifecycle applied to every site at the moment it is created.
Explore GovernanceFrequently asked questions
Can nBold provision SharePoint without creating a Team?
Yes. SharePoint provisioning is a first-class scenario in nBold, not just a side-effect of Teams. You can provision a standalone site — libraries, folders, files, Lists, pages, navigation, and storage quota — without creating a Team, or provision a site and a Team together from a single template when both belong to the same workspace.
Can templates include document structures?
Yes. Any file you add to an nBold template is cloned into the provisioned SharePoint library when a site is created — including Office files carrying your formatting, headers, and standard structure. Templates can also include folder hierarchies, metadata columns, Lists, site pages, and navigation.
Can site storage be controlled?
Yes. The storage quota is configured per template. A deal-room site can be capped lower than a major-account site, giving IT granular control over storage consumption by workspace type rather than only across the whole tenant.
Does this require custom SharePoint development or a migration?
No. nBold provisions sites through the Microsoft Graph API on your Microsoft 365 tenant — no custom SharePoint development and no separate infrastructure. The structure is defined once in a template and applied automatically at provisioning.
What happens to the SharePoint site when a workspace reaches end of life?
Lifecycle management governs the site the same way it governs the rest of the workspace. Inactivity detection, owner notification, and archival or deletion apply to the site — so a provisioned site never becomes ungoverned content sitting outside your policies.
See a complete site provisioned in a single pass.
Watch nBold provision a structured, governed SharePoint site — libraries, files, Lists, pages and quota — standalone or alongside a Team, in your own tenant.