A new project starts, and it needs a home: a site, a document library set up the right way, the content types your templates expect, navigation people can follow, a task board, and permissions that match who is on the team. Today, getting all of that usually means a ticket to IT and a wait, or an evening one of your project managers spends assembling it by hand. Either way the project waits on setup work done by someone who is not running the project.
The reason the wait exists is worth naming, because it is the thing ProjectPoint removes. Most tools that can build a SharePoint site to a standard need administrator rights to do it, so the person who needs the site is structurally not the person who can make it. Take that one
constraint away and the ticket, the queue, and the evening all go with it.
What one flag does
In ProjectPoint, a project manager provisions a workspace by setting a flag on the project's row in your Projects list. That single action runs the whole sequence. A site is created and joined to your hub. The hub navigation updates, with audience targeting, so the right people
see it. Your golden site is cloned into it: site features, permissions, content types and site columns, the lists and libraries, the navigation, and the default folder content. A Planner board is created. The homepage is generated with the project's own details filled in. And the project record links itself back to the new site and its board, so the register stays the index of everything. It takes minutes, and the person who needs the site is the person who ran it.
Run by the project owner, not by an administrator
The design decision underneath that is the one worth understanding, because it is the product's strongest technical claim. The provisioning engine is a REST deployment tool that runs on connections owned by the site owner who installs it, calling SharePoint for actions that owner already has the right to perform. No tenant-wide application is consented into your directory, and no elevated role is required to run a provisioning. That is a deliberately precise claim: it is about the provisioning run, not about your whole tenant.
It matters because the alternatives ask for more. The commercial provisioning tools in this space generally require a global administrator to consent an application across the tenant before they will work at all. The free route got harder rather than easier, too: the widely used multi-tenant provisioning application many teams relied on was deleted on 2024-09-09, so even a scripted PowerShell approach now needs an application registered and admin-consented in your tenant. ProjectPoint asks for neither.
What that does not mean
One honest boundary keeps this claim clean. Whether people can create SharePoint sites at all is a single tenant-wide setting your IT team already controls. If they have turned it off, a site owner cannot create the target site no matter how the tool signs in, and that is exactly as it should be. Provisioning without an app consent is not the same as provisioning around a decision your administrators have already made, and we would never pitch it as the latter. It is a way to run project provisioning without new standing access, inside the rules IT already set.
Two honest notes for the reader who checks
Two things this reader will ask about, said plainly. A provisioning run is a sequence of steps, so a run that stops partway is picked up and finished by a person rather than rolled back on its own. And naming conventions and sensitivity labels stay with your standard tenant governance rather than being stamped by the engine at the moment of creation. Neither surprises a SharePoint team, and we would rather name them up front than have you meet them in a demo.
The reassuring half is real too. Two pieces of hardening, restricting and logging writes to the trigger column that starts a provisioning, and reviewing the engine's own identity for least privilege, sit inside the entry tier deliberately and are being completed before the first
sale, not deferred to a later one. This is the layer IT cares about most, and it is treated as launch work rather than roadmap.
Get in touch, and we will flag a row and let you watch the workspace build itself.
