Skip to content
Site Manager· an app for Microsoft 365

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.

Who it's for Companies where anyone can create sites and teams for IT and Microsoft 365 administrators
What it costs from €89 per month by company size, unlimited sites and requests
How fast Deployed usually within 4 hours users need no training

Runs in your Microsoft 365 — no third-party cloud, no new passwords.

Book a demo
How it works

Three steps from request to clean-up.

A colleague requests, the approver clicks, the app takes care of the rest — from creation to archival.

  1. 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
  2. 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
  3. 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
Inside the app

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.

What changes

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.

Today “In a year we have hundreds of sites and nobody knows what half of them are for.”Anyone can create a team or a site. Nobody knows who owns them or whether they're still in use.
With the app A new site only through a request and an approvalIt follows the rules of its type, with a template and an owner from the start.
Today “The project ended, the site stayed.”The data sits there, access keeps piling up. Nobody has time to clean up sites past their time — and in an audit you drown in them.
With the app The app watches the lifecycleThe owner confirms that the site is still needed — what reaches the end of its life is closed or archived.
Today “Why does this site even exist?”There is no trace of who approved the site, what classification it has and when it expires.
With the app Who, why and when — in black and whiteA catalogue with owner and classification and a change log of every action with export. You capture the sites you already have, too.
Customer experience
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.
A company with 320 employees · IT department · 180+ sites in the register

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.

0unclassified sites after a month
180+sites captured in the catalogue
1× a yearowner recertification
The fastest route

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
Pick a demo slot → Free and without obligation · online in Teams
18 areas — click one for details

Site types as provisioning rules

In Settings → Site types you create your own types, such as Project, Department or External collaboration. Each defines what is technically created, a name and address template (for example “PRJ — {Code} — {Name}”), the minimum number of owners, default co-owners and members, custom request questions, who approves the requests, validity, the recertification interval and the allowed classifications. The type and the answers are saved in the site's record.

A step-by-step request

The requester picks the site type and the step-by-step form enforces its rules: the left side shows what has been entered and the summary shows what is still missing. Owners and initial members are chosen by searching the directory — for members, including which group to add them to. An address derived from the name drops Czech diacritics, and after sending, the form says whether the approvers were notified.

Request a site from any page

An editor adds the “EP365 Request a new site” web part to any page of any site — the intranet or an IT support page. The web part finds the app on its own, offers the same form as the app and shows “My requests” with their status below it. Who may request is set by the Requesters role; a requester does not need to be a member of the app's site.

Simple approval

The approver reviews the request and creates the site with one click, or returns it with a reason; the link in the new-request email opens that very request, and the detail shows whether it meets the type's rules. The requester can withdraw a pending request — it stays in the register as a trace with the Withdrawn status — and a failed creation can be retried.

Automatic creation with a template and a hub

Three technical kinds of site — a team site with a Microsoft 365 group (optionally with a team in Teams), a communication site and a team site without a group — create themselves. The site type also determines a template from a source site (libraries, folders, pages and permissions, always the latest revision; the snapshot of the source site is taken in the EP365 Atlas app) and the hub the site joins; the approver sees the plan beforehand. Existing sites are brought in line by the administrator with “Align with site type”.

Requester view

Anyone who is not an administrator or approver sees only their own requests and sites: the Overview with what is waiting for a decision and which sites are about to expire, My requests with every request for a new site or a change, and My sites they own or that were created from their request.

Site change request

From the site card anyone can ask for a new owner, a validity extension, a different assignment (type, department, classification) or closing the site. The request goes to the same approvers as a new-site request, and the approver sees a “now → after the change” comparison and whether the requester owns the site. Closing follows the type's rules: it removes guests, leaves members read-only and can archive the team in Teams.

Site catalogue

A register of all governed sites with owner, type, department, classification, status and expiry. Filters by type, classification and department, sorting, search that ignores diacritics and export to CSV that opens in Excel. For team sites the app loads the owners and members, and you edit a site's details right in the detail.

Naming rules and type compliance

A name and address template per type, a minimum address length, a mandatory prefix and reserved words; the uniqueness of the address is checked as the request is being typed. Type rules also apply to sites that already exist: the Catalogue flags a site whose name doesn't match the pattern, that lacks a required value, has a classification that isn't allowed or too few owners, and the detail offers a fix — such as renaming to the pattern.

Lifecycle and confirmation by the owner

Locking and archival, recertification and an email reminder. 60 days before expiry, the site owner confirms “I still need this site” themselves, and validity is extended by the recertification interval of its type (otherwise the one from Settings) — the same as with recertification by an administrator. Optionally also real archival of the site in Microsoft 365 Archive straight from the site detail, with the live archive state.

Access reviews by owners

The administrator or an approver issues a review for selected sites and the owner of each site goes through who can access it — members, guests, sharing links and places with unique permissions. For each row they choose Keep, Remove or Not sure and confirm whether the site is still needed. The administrator tracks progress, sends reminders and documents the review with an export or a printable record.

Import sites in groups

A scan of your environment finds sites created earlier or outside the app. You filter them by part of the address, owner, site type, hub, creator or date and bring a whole group into the register with “Select all matching”; the app finds the owners itself and records them right away.

Overview

At the top only what is really waiting for you — requests to approve, expired and expiring validity, sites ready for Microsoft 365 Archive, sites with a single owner — and a click opens the queue or the Catalogue already filtered. Below it, registry health with an explanation of every number, the breakdown of sites, the trend over 6 months and recent activity from the change log.

Change log and notifications

Who did what and when in the app — request, approval, creation, change, validity confirmation, closure, archival — with filters and export. Emails to the requester, the approver and the owner.

Site classification

Public, internal or confidential as a mandatory field on every site; the site type defines which classifications are allowed. A basis for governance and audit — you know at once how sensitive the content of a site is.

Roles and permissions

Requesters, approvers and administrators — everyone sees only what they need. The requester submits a request and sees their own requests and sites, the site owner confirms validity and handles access reviews, the approver creates the site, the administrator has the catalogue and the settings. One button fills the Requesters role with everyone except external users.

Czech and English

The language is chosen automatically from the language set on the hub, otherwise from each user's Microsoft 365 account language; the administrator can fix it for the whole organisation. Screens, forms, help, the app guide, emails and exports are all translated.

Branding from the company intranet

Emails and look and feel follow the global EP365 configuration — the logo, company, accent colour and reply-to address stay consistent across apps.
Area
EP365 Site Manager
Manual creation
IT scripts and tools
Data in your Microsoft 365
yes, entirely
yes
depends on the tool
Request and approval included
yes, ready to use
handled by email and chat
has to be built
Catalogue and register of sites
yes, with filters and export
none
partly
Import of sites you already have
scan and bulk import
by hand, one at a time
only with your own script
Recertification and expiry
yes, with a reminder
—
must be watched by hand
Access reviews by site owners
yes, with a record
—
has to be built
Deployment
in hours
right away
days to weeks of development
Change log of all actions
yes, with export
none
depends on logs
No extra installation and no third-party cloud
runs in your SharePoint
none
often outside your M365

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.

Licence

Price by company size

Up to 25 M365 users
€89 / month
26–70 M365 users
€145 / month
71–150 M365 users
€205 / month
More than 150 M365 users
Individual

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.

Rollout

Implementation at your company

€509 one-off

Installation, a workshop for administrators, and setup of site types, roles, naming rules and the lifecycle policy to fit your organisation.

What is not included

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.

Extended support

Support rate

€110 / hour

Consulting, environment changes or user support beyond the regular rollout.

How we count support

Support is billed per each started 15 minutes of work. We always tell you the expected scope in advance.

All prices exclude VAT
Does the app create sites itself, or only keep a register of them?
Both. It creates a new site or team on its own — it makes the group, the SharePoint site and the team in Teams, under the approver's permissions — and, according to the site type, applies a template from a source site and joins the site to a hub straight away. If the template or the hub fails, the site stays created and the progress log says what to fix. At the same time it keeps the register, watches expiry and records who approved a site and when it was created.
What about the sites we already have?
The import section captures them. The scan finds sites that were created earlier or outside the app; you filter them in groups (by part of the address, owner, type, hub or date) and bring them into the register at once, together with the owners the app finds itself. They then fall under regular management — catalogue, expiry, recertification, access reviews — like all the others, and the Catalogue shows which of them don't match the rules of their type.
Does a requester have to be a member of the app's site?
No. Who may request is set by the Requesters role in Settings → User roles — one button adds everyone except external users. A requester files a request in the app or from the “EP365 Request a new site” web part on any intranet page and sees only their own requests and sites in the app. The web part requires a one-time upload of the new app package to the app catalogue; everything else works without it.
Is the app available in English?
Yes. The language is chosen automatically from the language set on the hub, otherwise from each user's Microsoft 365 account language (Czech and Slovak = Czech, everything else = English). The administrator can fix it for the whole organisation in Settings → General. The administrator's own texts, such as the names of site types, stay as they were written.
Can the app lock or archive a site?
The register layer (a locked / archived status in the catalogue) — yes, for every app administrator. It can also really archive a site into Microsoft 365 Archive straight from the site detail: it shows the live archive state, archives and reactivates the site and explains the impact before every step. This is offered only to accounts with the SharePoint Administrator role. It requires Microsoft 365 Archive to be turned on in the tenant and the Sites.Archive.All permission to be approved; you switch the feature on in the app's Settings. A tenant-level site lock (read-only / no access) is only available in PowerShell from Microsoft — the app prepares the command for you to copy.
Does it need any third-party cloud or another server?
No. Everything runs directly in your Microsoft 365 in the browser, under the signed-in user's permissions. From our content delivery network the app downloads its digitally signed code, the licence file and supporting files (fonts, the what's-new overview). No sites, requests or personal data are sent to us — only a bug report that you send yourself by email.
What permissions does it need?
For full creation of team sites, the IT administrator approves a set of Microsoft company permissions (working with groups, the directory, Teams and sending notifications). Communication sites can also be created without them, under a regular user's permissions.
How long does the rollout take?
Usually within four hours: adding it to the target page in your SharePoint, approving the permissions and automatically creating the required register on first open. Plus a short workshop for administrators — regular users need no training, the request explains itself.
What do we need to have?
Just Microsoft 365 with SharePoint Online and Microsoft Teams — what most companies already pay for. Nothing is installed on computers or phones, and people sign in with their company account.
How do app updates work?
You upload the package to your App Catalog just once. New versions then load on their own and your admin manages them right inside the app — on the Version management card in Settings they can pin a version or roll back to an earlier one. No repeated package deployments: we ship improvements continuously — without a pinned version your site gets them automatically, with a pinned version you switch when you choose.