In development · An add-on to DocGen
DMS: one document workspace for Dataverse and SharePoint
One workspace for the documents attached to your Dataverse records. Keep files organised across Dataverse and SharePoint.
€4,500 per production environment per yearOn top of the DocGen licence (€7,500 a year). €375 a month equivalent, billed annually. Excl. VAT.
An add-on to DocGen, not sold on its own, and not yet generally available. DMS is bought on a DocGen licence in the same production environment. Register your interest to hear when early access opens.
Where the product is
DMS is in development.
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.
Compare storage costs
The number this is compared against
One figure decides whether DMS is worth anything to you, and it isn't a feature list. It's what the files sitting in Dataverse cost you every year above the file capacity you already have. You don't have to take our word for any of it — both figures are in your own tenant, and they take a few minutes to read.
// Power Platform admin center → Licensing → Dataverse ▸ Read the tenant's file usage and its file entitlement // tenant default + each user licence + storage you bought ▸ Subtract the entitlement, then any spare log and database capacity // Microsoft uses it to cover file use first ▸ Multiply what is left by roughly €24 per GB per year = what you are paying, annually, to hold those files in Dataverse // that is the number on the other side of this decision ✕ Not a feature comparison // we don't win one and aren't trying to ✕ Not a per-seat calculation // see pricing
Set that annual figure next to €4,500 for the add-on and €7,500 for the DocGen licence underneath it. If the capacity number is small, the arithmetic answers itself and the answer is no. If it's large, the question becomes governance: which files are attached to which records, in which library, under which folder convention, and who is accountable for the ones that keep arriving. That is the part DMS is for.
Below 250 GB, don't buy this
We would rather publish the disqualifier than discover it with you in month two. Under roughly 250 GB of file capacity, the out-of-the-box SharePoint integration that ships with Dynamics 365 is the right choice. It's included, it's supported by Microsoft, and it will cost you nothing on top of what you already pay. Use it.
- The out-of-the-box SharePoint integration is included in what you already own
- Your annual capacity cost is smaller than the licence you'd be adding to it
- There is no governance problem at that size that a convention and a bit of discipline won't solve
- Buying this would be a worse decision than doing nothing, and we'll say so on a call
- Capacity is now a line somebody in finance has noticed
- Files arrive faster than anyone is deciding where they should go
- Nobody can say what the capacity is actually being spent on
- You are already running DocGen, or willing to — it's the prerequisite
The current document grid: limitations
The document grid you have today
- Capped at 5,000 rows, and the cap isn't a setting you can raise
- No editable-grid support — open each record to change anything
- No enforced folder structure, so every user invents their own
- Nothing tells you which copy of a document is the current one
- Nothing tells you what your file capacity is being spent on either
- Built as a Power Apps Code App — a real grid, not a subgrid
- Folder structure defined once and enforced on every record
- Configured in a model-driven app, by a consultant, not in code
- One managed solution to import — nothing to provision
- Files stay where they already are — nothing is migrated or copied
Technical details: how DMS works
How it's put together
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 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 // the files attached to that record, where they live ▸ 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 // what it requires ▸ SSS DocGen // the prerequisite licence — this is an add-on
Planned capabilities
What's in it
Every file the workspace shows is attached to a record, in a library you mapped, under a folder convention you defined. When somebody in finance asks what the file capacity is being spent on, there is an answer.
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. 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.
Pricing
DMS is an add-on, so it has a price but not a basket of its own: the licence you buy is DocGen, and the add-on goes on top of it in the same production environment. €4,500 per environment per year (€375 a month equivalent), billed annually — not per user, not per document, and not per gigabyte, which is rather the point of the section above. Development and test environments are included at no charge. Annual only — this is an operating decision, not a monthly experiment.
Licence
per production environment · billed annually| Line | Per month |
|---|---|
| SSS DocGen — the prerequisite | €625 / month €7,500 / year, billed annually |
| SSS DMS — add-on, not sold on its own | €375 / month €4,500 / year, billed annually |
| Both, same environment | €1,000 / month €12,000 / year, billed annually |
- Development and test environments at no charge, however many you run
- Managed-solution updates for the life of the subscription
- Dataverse and SharePoint API compatibility maintenance
- Business-hours support, next-business-day response
Both numbers are on the page. No call to book before you see a price, and no add-on price that only appears after the prerequisite is signed. The same figures 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.
No platform fees of its own. Dataverse capacity, SharePoint storage and Power Platform licensing stay between you and Microsoft — and what you already spend on Dataverse file capacity is the figure to set beside these ones. How to read it.
For implementation partners
For Microsoft implementation partners
There is nothing partner-specific about DMS, because it isn't a product a partner delivers on its own — it's an add-on inside a DocGen engagement. The partner imports the same managed solution and configures the entity-to-library mapping and folder convention in the model-driven app, billable in the engagement they're already running. Everything else — channel terms, rates, what we do and don't do to your accounts — is published in one place, and it isn't this one.
Join the early access list
Early access opens to a limited number of environments before general release. This is a list, not an order form — the add-on is bought on a DocGen licence, so if you want to move now, DocGen is where to start. Tell us your capacity figure and we'll tell you honestly whether the add-on is worth adding when it ships.
Send us your tenant or environment details and the GB of file capacity you read in the admin center. That figure is enough for us to tell you which side of the threshold you're on — including when the answer is that you should keep the out-of-the-box integration.
Prefer the form? It is hosted by Microsoft Forms, which sets its own cookies, so it loads only if you choose it. What you send through it is covered by section 1.3 of the Privacy Policy, but the policy does not yet cover the cookies Microsoft Forms sets. Emailing us sets no cookies.
Runs in your tenantData Processing AgreementSecurity overview
- Controller. Simple Smooth Safe, Unipessoal Lda., Rua Retiro dos Pacatos 50, Ed. Startup, Sala 9, 2635-224 Rio de Mouro, Portugal. NIF/VAT PT518264742. Questions or requests: info@simplesmoothsafe.com.
- What we hold. Your name, email address, whatever you chose to tell us about your organisation, and the correspondence itself.
- Purpose. To answer you, and to follow up on the specific thing you asked about.
- Legal basis. Legitimate interest (Art. 6(1)(f)) in responding to an enquiry you initiated, or steps prior to entering a contract (Art. 6(1)(b)) where you are asking to buy.
- Retention. Up to 24 months after our last exchange, then deleted — unless you become a customer, in which case section 1.4 applies.
- Your rights. Ask for access, correction or deletion, or object, at any time by emailing us. Full detail in the Privacy Policy, section 1.2.
- Controller. Simple Smooth Safe, Unipessoal Lda., Rua Retiro dos Pacatos 50, Ed. Startup, Sala 9, 2635-224 Rio de Mouro, Portugal. NIF/VAT PT518264742. Questions or requests: info@simplesmoothsafe.com.
- Where it goes. The form is hosted on Microsoft Forms. It collects your name, work email, company, tenant or environment details, and whether you are a partner or an end client.
- Purpose. To contact you about the product you asked about — early access, availability, or a demo. That is the only thing it is used for.
- Legal basis. Consent (Art. 6(1)(a)), given by ticking the box on the form.
- Retention. Until you withdraw consent, or until the programme you signed up for closes, whichever is first.
- Withdrawing. Email us. No reason needed, no effect on anything else, and no retention "for our records". Full detail in the Privacy Policy, section 1.3.
Prefer email? info@simplesmoothsafe.com reaches the same place, under section 1.2 of the Privacy Policy.
Questions buyers actually ask
When can I actually use it?
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.
What counts as a production environment?
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.
Does it work across multiple SharePoint sites?
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.
What happens to documents we already have?
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.
Can we buy SSS DMS on its own?
No. SSS DMS is an add-on to SSS DocGen and there is no standalone licence for it. DocGen is €7,500 per production environment per year, the add-on is €4,500 on top of it, and both in the same environment are €12,000. If you aren't running DocGen, there is nothing here for you to buy yet.
How do we know we're big enough for it?
Open the Power Platform admin center, go to Capacity, then File, and read the GB your environment is using. Below roughly 250 GB the out-of-the-box SharePoint integration is the right answer and we would rather you used it. Above that, multiply the GB by roughly €24 per GB per year — that figure is what this is compared against, and Microsoft list pricing varies with your own licensing agreement, so check yours.
Do we need an Azure subscription?
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.
What does it need from our tenant?
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.
Can our implementation partner deliver it?
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.