Site Manager: Every site with an owner and a purpose.
No jungle a year later.
A new site or team comes into being through a request and an approval and creates itself — and you have every site in one catalogue with an owner, a classification and an expiry, including the ones you already have.
Runs in your Microsoft 365 — no third-party cloud, no new passwords.
Three steps from request to clean-up.
A colleague requests, the approver clicks, the app takes care of the rest — from creation to archival.
-
A colleague requests a site
They pick the site type — Project, Department or External collaboration, for example — and the step-by-step form enforces its rules: the name, the owners and the classification.
Even from any intranet page -
The approver clicks, the site creates itself
One click approves the request and the site is created — including the team in Teams, a template from a source site and joining the hub.
With an owner and a type from the first minute -
The app watches its life
Expiry with a reminder, confirmation by the owner and access reviews. What reaches the end of its life is closed according to the type's rules or archived.
No zombie sites
See it in practice
An overview of requests and the site register, a request for a new site with a choice of type and an instant summary, and approval with one click after which the site creates itself.
Today vs. with Site Manager
This is what companies tell us before they roll out Site Manager — anyone can create sites and teams, and without a process it turns into a jungle within a year.
From ninety unclassified sites down to zero in a month. And a new site now comes into being only with an owner and a purpose — no more Teams created on the side that nobody claimed.
Deployed in four hours: adding it to a SharePoint page, approving the permissions and importing 180 existing sites into the register. Administrators took an hour to learn it, regular users nothing — the request explains itself.
30 minutes on screen, no company presentation
- 5 minYour current practice — how sites and teams come into being today
- 10 minRequest and approval through the eyes of a colleague and of the approver
- 10 minThe site catalogue, expiry watching and import of the sites you already have
- 5 minWhat a rollout would mean for you + an indicative price
Site types as provisioning rules
A step-by-step request
Request a site from any page
Simple approval
Automatic creation with a template and a hub
Requester view
Site change request
Site catalogue
Naming rules and type compliance
Lifecycle and confirmation by the owner
Access reviews by owners
Import sites in groups
Overview
Change log and notifications
Site classification
Roles and permissions
Czech and English
Branding from the company intranet
Data stays with you
Requests, the site catalogue and the audit trail are stored solely in your Microsoft 365 environment. No third-party cloud, no transfer of data outside the company.
No new passwords
People sign in with their company Microsoft account. Creation and the register run under their own permissions — there is no separate application with its own access to your environment.
Everyone sees only their own
A requester sees their own requests and sites, an approver the pending requests, an administrator the catalogue. For requesters the boundary is held by SharePoint permissions, not just a filter in the app: from the register they read only their own items. Validity confirmations and access-review answers are visible only to their author, administrators and approvers. The scan of existing sites respects permissions — it shows only what the person has access to.
Classification on every site
Public, internal or confidential as a mandatory field. You know at once how sensitive the content of a site is — a basis for governance and audit.
A verifiable history
Who approved a site, when it was created, who confirmed its validity, when it was closed or archived. A change log of all actions with export — without manual digging. A confirmation from someone who isn't an owner according to the register doesn't count, and the administrator sees it.
Verified app code
The code of the app and of the site request web part is digitally signed. The signature is verified before start-up and code that fails the check does not run — instead, the app shows that the version could not be verified, and the help explains what to do.
Clean-up without risk
Statuses in the register don't touch production sites. Real archival into Microsoft 365 Archive can be started from the app only by an account with the SharePoint Administrator role, which sees the impact before every step. A tenant-level site lock is set by an administrator in PowerShell — the app prepares the command.
Price by company size
The subscription follows the total number of internal users in your Microsoft 365. Within a given size, the number of governed sites and requests is unlimited.
Implementation at your company
Installation, a workshop for administrators, and setup of site types, roles, naming rules and the lifecycle policy to fit your organisation.
A bulk clean-up of a large existing environment, look-and-feel changes beyond the themes and connections to other systems. We will send a precise quote after a short call.
Support rate
Consulting, environment changes or user support beyond the regular rollout.
Support is billed per each started 15 minutes of work. We always tell you the expected scope in advance.
Does the app create sites itself, or only keep a register of them?
What about the sites we already have?
Does a requester have to be a member of the app's site?
Is the app available in English?
Can the app lock or archive a site?
Does it need any third-party cloud or another server?
What permissions does it need?
How long does the rollout take?
What do we need to have?
How do app updates work?
Often added alongside Site Manager
Further reading on the blog
Need help putting your SharePoint in order first? Explore our audit, governance and care services
What exactly do you want to discuss?
Pick what's burning most right now. We'll get back to you, walk through your situation and propose next steps, including an indicative price.