This is an archived version. It is published so that customers who ordered while it was in force can read the text that applied to them. It is not the current version — see the current documents.
1. What you are buying
A subscription to use the Products, for as long as fees are paid. You are not buying the software itself, and you are not buying seats in the case of DocGen and SSS DMS. The unit of licensing differs by Product, deliberately:
| Product | Licensed by | List price |
|---|---|---|
| SSS DocGen | Production Environment | $8,500 / year |
| SSS DMS | Production Environment | $8,500 / year |
| DocGen + SSS DMS, same environment | Production Environment | $14,500 / year |
| PSA Hub — Core | User | $35 / user / month |
| PSA Hub — Pro | User | $55 / user / month |
PSA Hub is billed annually and has a minimum of 15 Users. All prices are exclusive of VAT — see section 5.1 of the Terms of Service. The published price list on the product pages is the list price; an Order may say something different, and if it does, the Order wins.
2. What counts as a Production Environment
A Production Environment is any Microsoft Dataverse environment in which you generate or manage real business records — typically one per legal entity.
Development, test, training and staging environments are free, however many you run. We do not tax good ALM, and there is no count to report at renewal. If an environment is not producing documents or managing documents that a real person or a real counterparty relies on, it is not a Production Environment.
Each additional Production Environment is licensed at the same rate. Two Production Environments running DocGen is $17,000 a year.
The number of templates does not change the price. One Production Environment is one fee whether it runs three templates or fifty. There are no bands, no volume table, and no per-document meter — the infrastructure is yours, so a document costs us nothing and metering it would only be a tax on using what you bought.
3. What counts as a User
A User is a named individual you authorise to access PSA Hub. Users are named, not concurrent. A login may not be shared between people, and a generic or role account used by more than one person counts as one User per person using it.
You may reassign a User licence to a different individual when someone leaves or changes role. You may not rotate a licence between people to cover more of them than you have licensed.
Service accounts and integration principals that access data without a human sitting behind them do not need a User licence.
4. The licence we grant
For the Subscription Term, and while fees are paid, we grant you a non-exclusive, non-transferable, non-sublicensable right to install and use the Products, in your own Microsoft tenant, for your own internal business purposes, within the quantities on your Order.
That licence extends to your Affiliates — entities you control, are controlled by, or are under common control with — provided their use counts towards your quantities and you remain responsible for their compliance.
It also extends to contractors and implementation partners acting on your behalf, for your benefit, on the same terms. Their access is your responsibility.
5. What you may not do
- Sublicense, resell, rent, lease or otherwise make a Product available to a third party as a service, except as expressly permitted in section 8.
- Use a Product to provide a bureau, outsourcing or managed service to parties who are not you or your Affiliates.
- Reverse engineer, decompile or disassemble the compiled components, except to the extent that right cannot lawfully be excluded — and in that case only after asking us first, because we will usually just tell you.
- Fork, modify or create derivative works of the Product source, or attempt to extract it from the managed solution.
- Remove or obscure proprietary notices.
- Exceed the licensed quantities, or use a Production Environment licence to cover more than one Production Environment.
- Benchmark a Product and publish the results without our written consent — which we will give if the methodology is disclosed and the comparison is fair.
6. Extending the Products
Extension is expected, and there are sanctioned ways to do it: configuration data, custom Dataverse columns, navigation slots, and documented Custom API hooks. Anything built that way survives an update.
What is not sanctioned is forking the source. That constraint is the product: it is what lets one fix reach every customer instead of N drifted copies. If the extension point you need does not exist, tell us — adding one is usually a better outcome for both of us than a fork we cannot support.
We do not support, and give no warranty for, behaviour caused by unsanctioned modification.
7. Ownership
7.1 Ours
We own the Products, their source code, the managed solutions, and every improvement or derivative work we make, including any we make in the course of delivering Services to you.
For PSA Hub specifically: you receive a managed solution containing the compiled application, the tables, the security roles and the plugins — the standard Power Platform deliverable. We hold the TypeScript source.
7.2 Yours
You own your Customer Data, and that expressly includes templates and configuration.
A DocGen template is configuration, not compiled code: Handlebars markup and FetchXML rows living in your Dataverse. It is readable and exportable at any time, during the term and after it, and it does not stop being yours when the subscription ends. The same is true of SSS DMS entity-to-library mappings and folder conventions, and of PSA Hub configuration data: all of it is Dataverse data in your tenant, and it exports with your ALM pipeline like anything else.
Custom columns, option sets and plugins you add on the Dataverse side are yours and survive, because the Products read the same schema.
8. Implementation partners and resellers
A Microsoft implementation partner may deploy and configure the Products for a client under that client's licence, as part of the partner's own engagement. No separate licence from us is needed to do that, and the configuration work is the partner's to bill.
Reselling — where the partner contracts with the end client for the Product itself — needs a separate written channel agreement with us. Channel terms are discussed directly and are not published.
9. Licence verification
We do not audit your user list, and there is no clause here pointing at it. Where a Product reports its own usage, that telemetry covers licensed quantities only — environment count, User count — and never document contents, record contents or personal data of your users or customers.
If usage exceeds the licensed quantities, we will raise it with your billing contact and invoice the difference from the date it started, pro rata to your renewal date. We will not disable anything to make that conversation happen.
Enforcement is deliberately soft. Documents and document access are business-critical. Past renewal, whatever the state of the paperwork, the software keeps working and the discrepancy is flagged to us and to your billing contact — not to your users. A licensing dispute should never stop a firm invoicing.
10. Updates
Managed-solution updates, and the compatibility maintenance that keeps the Products working as Microsoft changes the platform underneath them, are included for the life of the subscription. They are not an optional maintenance contract sold separately.
You are responsible for applying updates within a reasonable period. We support the current release and the one before it.
11. When the licence ends
On expiry or termination the licence ends and you will stop using the Products and remove the managed solutions from your environments. Your data, templates and configuration stay in your tenant — they are yours and they were always there. See Cancellation & Refunds.
12. This document is not the whole agreement
It attaches to the Terms of Service, which carries the warranty, liability, confidentiality and governing-law provisions. Read them together.