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. ShareMancer Root Folder Cop™ protects your classification structure by preventing users from copying or moving files and folders into library root folders or nesting folders and document sets inside document sets, helping keep libraries 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 “impound lot” library, breaking role inheritance on the item so that only the original author can access it.

Users are notified immediately through Teams Adaptive Cards, email notifications or both (configurable). 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 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.

ShareMancer Restricted DocSets let users lock down access to document sets without involving IT. A simple form allows them to restrict or unrestrict a document set, specify contributors, view expiry dates (when role inheritance will be restored), and transfer ownership if responsibilities change.

Access control works differently depending on whether SharePoint sharing is enabled or disabled on the site:

• Sharing disabled (Full Edition only): The Restricted DocSets form includes a contributors field where the restriction owner specifies who should have access. These contributors are recorded in the control record metadata for the docset, giving administrators a clear, authoritative record of who has access.
• Sharing enabled: Because users can grant access directly through SharePoint's native sharing, maintaining a contributor list in the control record would create a drift problem — the recorded list would quickly diverge from actual permissions. In this mode, the Restricted DocSets form does not include a contributors field and the control record does not track contributors. Access is limited initially to the restriction owner (the user who created the docset) and the Site Owners group, who always retain full control. Additional access is managed through native SharePoint sharing.

Expiry and drift cleanup: When a restriction expires, the expiry job restores role inheritance on the docset. In environments where sharing is enabled, the expiry job can also restore role inheritance on individual documents within the docset, cleaning up any permissions that users may have applied directly through SharePoint sharing during the restriction period. In the Full Edition, this behavior is configurable. In the Light Edition, inheritance on contained documents is always restored along with the docset.

Notifications and approval: The restriction owner and their manager receive an email notification a configurable number of days before restrictions are due to be lifted, giving them time to deal with any sensitive content, extend the restriction period, or make the restriction permanent. The product can also be configured to send an approval workflow to site owners before role inheritance is restored, allowing information management staff to assess whether the content remains sensitive and prevent restoration if necessary. This approval responsibility is assigned to site owners rather than managers, as managers may not respond in a timely manner, whereas site owners are better positioned to make disposition decisions about content on their sites.

Two deployment options are available:

• Full Edition (Azure-backed): Uses an Azure Function and Automation Runbook to enforce inheritance breaks, send reminder emails a configurable number of days before expiry, and automatically restore access after a configurable number of weeks (with options to extend or make permanent). Supports both sharing-enabled and sharing-disabled sites.
• Light Edition (Power Automate): Provides the same self-service restriction form and expiry handling through a Power Automate flow, which is ideal for organizations without an Azure subscription. Supports sharing-enabled sites only.

Notebook Guardian™

Safe OneNote-SharePoint Integration.

In governed SharePoint Online environments where mandatory metadata is enforced on the Document content type and document sets are the only available folder-type container, OneNote integration can break down. A SharePoint Online notebook is technically a folder containing multiple underlying .one files. When mandatory metadata is enforced at the document level, users are prompted to supply metadata for each .one file. Once entered, those files disappear from standard views and their metadata cannot be corrected, creating downstream risks for retention, reporting, and automation. In some cases, SharePoint may even apply a document set content type to the notebook container, preventing OneNote from launching altogether. These behaviours make standard EDRMS governance incompatible with out-of-the-box notebook handling.

ShareMancer Notebook Guardian™ resolves this conflict by provisioning a dedicated Notebooks library across one or more sites using an automated script. The library is configured with only the out-of-the-box Document content type (with no mandatory fields) and a custom folder-based Notebook content type to which customer-specific metadata fields can be added. An Azure Function, triggered by a SharePoint webhook, detects newly created notebooks and automatically applies the custom folder content type to the notebook container. An accompanying SPFx component allows users to create a notebook from within a document set; the notebook is created in the Notebooks library and a link is added to the document set. The result is a OneNote experience that preserves required metadata, supports retention and disposition, and maintains OneNote–SharePoint interoperability.

SignFlow™

Streamlined PDF signing without SharePoint Sync.

ShareMancer SignFlow™ enables controlled PDF signing in SharePoint environments where OneDrive Sync is disabled. Many governed EDRMS implementations disable Sync to avoid issues with mandatory metadata enforcement and co-authoring conflicts. However, disabling Sync makes digital signing inconvenient and error-prone, requiring users to manually download, sign, and re-upload PDFs.

SignFlow introduces a controlled, per-user signing workspace hosted on a dedicated SharePoint site where Sync is enabled. Each user is provisioned a private workspace with unique permissions (user’s eyes only). During a one-time registration step, the user is guided through synchronizing their OneDrive client to their signing workspace. The registration app launches the workspace and provides step-by-step instructions to enable Sync on that specific folder using the SharePoint Sync command. This signing workspace site is separate from regular EDRMS sites and exists specifically to allow Sync in a controlled manner while Sync remains disabled elsewhere.

When a user initiates signing from a document set, the system securely copies the PDF to the user’s private workspace, where it opens locally in Acrobat via the synced folder. After signing, the solution validates the result and returns the signed file to the originating document set according to configured copy/replace rules. The process eliminates manual download/upload errors while preserving metadata integrity, auditability, and governance controls across the EDRMS.

CaseBridge™

CRM-to-SharePoint metadata synchronization.

Dynamics 365 can link cases to SharePoint folders, but many implementations need more structure to support records management. ShareMancer CaseBridge™ converts these folders into Document Sets and keeps their metadata synchronized with CRM case data.

When a case is created or updated, a 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 automatic synchronization of changes
• Ordered processing per case through queue sessions
• Parallel processing across different cases

This ensures CRM cases are consistently represented in SharePoint using metadata-rich Document Sets.

ConfigHub™

A single place for product settings across your tenant.

ShareMancer ConfigHub™ provides a single place to define and manage settings for all components of a SharePoint solution. Modern solutions often span multiple technologies: SPFx web parts, Azure Functions, Logic Apps, Azure Runbooks, Power Automate flows, and Power Apps. Each technology has its own way of storing configuration. ConfigHub eliminates the need to manage settings separately across all of them.

Administrators get a centralized, consistent experience for managing configuration across all components of a solution. Developers get reliable access to those settings through provided client APIs for JavaScript, C#, PowerShell and REST.

Where supported, ConfigHub can push settings directly to each component's native configuration store — environment variables for Azure Functions and Power Automate flows, automation variables for Azure Runbooks, and parameters for Logic Apps — so components can access their settings locally rather than querying ConfigHub at runtime. SPFx components read settings directly from ConfigHub, as the SharePoint Framework does not support external configuration injection.

All ShareMancer products use ConfigHub to manage their own settings, which means ConfigHub is included automatically when any ShareMancer product is deployed to a client environment.

Zones™

Organize sites into logical groups with shared settings.

ShareMancer Zones™ creates independent configuration zones—such as DEV, UAT, and PROD—within a single tenant, each with its own landing site and its own settings in ShareMancer ConfigHub. Zones give organizations a 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.

ShareMancer ConfigHub is zone-aware: product settings can be defined at multiple levels, including tenant-wide defaults, zone-specific values, site-specific overrides, and library-level settings. This structured hierarchy provides consistent, predictable configuration behaviour for SharePoint solutions, giving administrators control over scope-specific solution settings.