SSS DMS replaces the native Dynamics document grid with a Power Apps Code App that reads Dataverse and SharePoint together. Folder structure is enforced, not hoped for. It's configured from a model-driven app and ships as a single managed solution — no Azure resources to provision, no server to maintain.
It isn't generally available, and nothing on this page should be read as shipping today. We're building it against real Dynamics 365 document workloads and opening early access to a limited number of environments before general release. Everything described below is what the product does — join the list and we'll tell you when you can put it in an environment, not before.
Three parts, one solution file. The Code App is what users see; the model-driven app is where a consultant maps entities to document libraries and defines the folder convention; the managed solution is how all of it reaches an environment. Scope is deliberate: one SharePoint site, multiple document libraries — that is what SSS DMS covers, and we'd rather say so than let you discover it after purchase.
// one managed solution, imported into the target environment ▸ Code App the document workspace users open from a record // reads Dataverse and SharePoint in one view ▸ Model-driven app where a consultant configures the workspace // entity → library mapping, folder convention ▸ Dataverse tables the configuration itself, as data // what it reads ▸ Dataverse documents held as records and attachments ▸ SharePoint one site, multiple document libraries // what it does not need ✕ Azure subscription // no container, no function, no key vault ✕ Servers to maintain // nothing runs outside the Power Platform ✕ Seat counting // licensed per environment, see pricing
Dataverse records and SharePoint library contents in a single workspace, so nobody has to know which system a given file happened to land in.
Define the convention once in the model-driven app and it applies to every record. Structure stops being a habit people are asked to maintain and becomes something the app does.
Built as a Power Apps Code App rather than a native subgrid — which is why it isn't bound by the 5,000-row ceiling or the missing editable-grid support.
Entity-to-library mapping and folder rules are configuration in a model-driven app. A partner consultant sets it up; nobody writes or deploys code to change how it behaves.
The whole product is a single managed solution. Import it, configure it, hand it over — and uninstall it cleanly if you ever want to.
Nothing runs outside the Power Platform. No Azure subscription to stand up, no container to patch, no secret to rotate, no server anyone has to own after go-live.
Documents stay in your Dataverse and your SharePoint, under your retention rules and your DLP policies. SSS DMS reads what's already yours — it doesn't copy it anywhere.
It's a document workspace. It doesn't try to be a records-management suite or a workflow engine, and the feature list is short on purpose — a shorter list is a product that works.
Per production environment, per year. Not per user, not per document, not per gigabyte. Development and test environments are included at no charge. Annual only — this is an operating decision, not a monthly experiment.
| Line | Per year |
|---|---|
| SSS DMS | €8,500 |
| SSS DocGen | €8,500 |
| Both, same environment | €14,500 |
Why the number is on the page. Everything else in this category makes you book a call to find out the price. We don't think a price is a negotiating position that has to be protected until a salesperson has qualified you. It's €8,500 per production environment per year — the same number for a five-person team and a five-thousand-person one, because you aren't buying seats.
Per environment means per environment. No seat counting, no true-ups, no headcount reconciliation at renewal, and no audit clause pointing at your user list. Add a hundred users to the environment and the invoice doesn't move.
Partners are how SSS DMS reaches most of the clients that need it. You deliver it; we build and maintain it. What that's actually like:
No Azure subscription to stand up on the client's behalf, no infrastructure to hand over, and nothing left running that someone has to own after go-live.
Entity-to-library mapping and the folder convention are set up in a model-driven app — the kind of configuration your consultants already do, billable in your engagement.
Per-environment pricing means no seat counts to reconcile and no true-up conversation with your client twelve months after you've left the project.
The licence number is published, so you can put it in a proposal on the same day you're asked for one — without waiting on us to approve a figure.
Updates, compatibility maintenance and support are ours. When Microsoft changes something underneath, fixing it is our problem, not your client's escalation.
We build products. The implementation, the data migration and the client relationship are yours — we're not going to turn up at your account with a services proposal.
Early access opens to a limited number of environments before general release. Tell us about yours and we'll be in touch before it does — whether you're a Dynamics 365 customer with a document problem or a partner who wants to deliver this.
Whether you're a Dynamics 365 customer with a document problem or a partner who wants to deliver this — send us your tenant or environment details and roughly how your documents are split between Dataverse and SharePoint today.
It's in development, so not today. Early access opens to a limited number of environments before general release, and the list on this page is how you get into it. We'd rather tell you a date once we can keep it than publish one now.
Any Dataverse environment where real business documents are managed — typically one per legal entity. Development and test environments are free, however many you run: we don't tax good ALM.
No. SSS DMS covers one SharePoint site with multiple document libraries, and we're saying so up front rather than letting you find out during implementation. If your documents are spread across several sites, tell us — it's useful input, but it isn't what the product does today.
They stay exactly where they are, in your Dataverse and your SharePoint. SSS DMS reads them in place — it doesn't migrate, copy or move anything, so there's no data-migration project hiding inside the install.
Because a document workspace gets more useful the more people use it, and per-seat pricing punishes exactly that. Charging per environment means the finance conversation happens once a year instead of every time somebody joins.
No. Everything runs on the Power Platform you already have. There's no container to host, no function app, no key vault and no cloud bill arriving separately from the licence.
A Dataverse environment, a SharePoint site your users can already reach, and the Power Platform licensing you hold today. Access follows your existing permissions — SSS DMS doesn't grant anyone anything they didn't already have.
That's the intended route. The partner imports the managed solution and configures it in the model-driven app as part of their engagement. If you don't have a partner for it, tell us and we'll help you find one.
SSS DMS is in development and early access opens to a limited number of environments. Join the list and we'll be in touch before it does — or, if you deliver Dynamics 365 for a living, talk to us about reselling it.