Our Products
At ShareMancer, we build practical information-management governance solutions for the SharePoint Online Modern Experience that run inside your own SharePoint, Power Platform, and Azure environments.
Root Folder Cop™
Prevent clutter in libraries.
Folders, root-level clutter and nesting all undermine SharePoint’s metadata-driven design. Root Folder Cop protects your classification structure by preventing users from copying or moving files and folders into library root folders or nesting folders inside document sets, helping keep libraries clean, organized, and metadata-driven.
Because SharePoint Modern no longer supports server-side event receivers that can block these operations in real time, Root Folder Cop™ uses webhooks to detect misfiled items after they are created. When a violation is detected, the solution automatically moves the item to a secure parking lot (our “impound lot”) library, breaking role inheritance so that only the original author can access it.
Users are notified immediately through Teams Adaptive Cards and email notifications. This allows them to re-file the item right away, before they’ve started working on it or added content that would make relocation more difficult. The result is a clean, secure, and self-correcting environment that reinforces good information management habits without disrupting user productivity.
Restricted DocSets™
Time-limited, self-service control of sensitive content.
Restricted DocSets™ let users temporarily lock down access to document sets and folders without involving IT. A simple form allows them to restrict or unrestrict a document set or folder, specify contributors, view expiry dates (when role inheritance will be restored), and transfer ownership if responsibilities change.
Two deployment options are available:
- Full Edition (Azure-backed): Uses an Azure Function and Automation Runbook to enforce inheritance breaks, send reminder emails two weeks before expiry, and automatically restore access after a configurable number of weeks (with options to extend or make permanent).
- Light Edition (Power Automate): Provides the same self-service restriction form and expiry handling through a Power Automate flow — ideal for organizations without an Azure subscription.
Both editions deliver secure collaboration, built-in governance, and zero helpdesk overhead.
Blueprints™
Reliable, SharePoint site provisioning at scale.
Blueprints™ provides a clean, intuitive interface for designing, validating, and publishing parameter-driven SharePoint “blueprints” — high-fidelity site definitions built on top of PnP Provisioning Templates.
It eliminates the common gaps, UI-only limitations, and reliability issues of the PnP Provisioning Engine by adding automation logic that performs tasks that currently require the SharePoint user interface (such as applying Document Set welcome-page views and advanced site settings).
Blueprints are stored as XML and executed through the ShareMancer Provisioning Engine, which consumes the blueprint along with a simple JSON parameter file. This enables the same blueprint to be deployed consistently across DEV, UAT, and PROD environments — without modification — by adjusting only the parameter values.
The result: repeatable, automated, and environment-aware SharePoint provisioning with the precision and reliability modern enterprise deployments demand.
CaseBridge™
CRM-to-SharePoint metadata synchronization.
Dynamics 365 can link cases to SharePoint folders, but many implementations need more structure to support records management. CaseBridge™ converts these folders into Document Sets and keeps their metadata synchronized with CRM case data.
When a case is created or updated, a lightweight CRM plug-in generates an XML snapshot of key fields and sends it through a Logic App to an Azure Service Bus queue (one session per case). An Azure Function processes the message and applies the updates in SharePoint.
CaseBridge™ provides:
- Conversion of CRM-linked folders into Document Sets
- Mapping of CRM case fields to Document Set metadata
- Ongoing synchronization of changes
- Ordered processing per case through queue sessions
- Parallel processing across different cases
This ensures CRM cases are consistently represented as structured, metadata-rich Document Sets in SharePoint.
Zones™
Organize sites into logical groups with shared settings.
ShareMancer Zones™ creates fully independent configuration zones—such as DEV, UAT, and PROD—within a single tenant, each with its own landing site and its own settings in ConfigHub™. Zones give organizations a clean way to separate environments without requiring multiple tenants, ensuring that code, automation, and provisioning scripts always pick up the correct configuration for the environment they’re operating in.
A dedicated PowerShell module lets administrators work with zones programmatically—for example, listing all sites within a given zone, enumerating all defined zones across the tenant, or applying scripted operations to zone-scoped site collections.
ConfigHub™ is fully zone-aware: product settings can be defined at multiple levels, including tenant-wide defaults, zone-specific values, site-specific overrides, and even library-level settings. This structured hierarchy provides consistent, predictable configuration behaviour while giving administrators fine-grained control where needed.
ConfigHub™
A single place for product settings across your tenant.
ShareMancer ConfigHub™ provides a consistent way for multiple solutions to store and manage their settings in SharePoint. Administrators gain a standard, centralized experience for configuration management, while developers benefit from efficient, reliable access to product settings through both pro-code and low-code components of their solutions.
ConfigHub can also push settings to supported product components, allowing them to access configuration data more efficiently instead of repeatedly querying the ConfigHub site. For example, settings can be propagated to environment variables of Azure Functions, automation variables of Azure Runbooks, and parameters of Logic Apps. For SPFx components, settings must be read directly from ConfigHub, since the SharePoint Framework does not support external configuration injection.
Various client APIs are provided to access configuration data directly from code — including JavaScript, C#, and PowerShell modules. The identity under which the code runs must, of course, have appropriate permissions to read the product’s configuration from ConfigHub.