Answers to the questions that come up most

DocuSign is included in Premium and Diamond plans. On Business and Enterprise plans it's available as a paid add-on at €2,150/year. Customers without DocuSign obligations can skip it entirely.

Four plans from €4,450/year (Business) to €18,450/year (Diamond), priced per-plan with unlimited documents. DocuSign is included on Premium and Diamond; €2,150/year add-on on Business/Enterprise.

Yes. Upgrades take effect immediately, pro-rated for the remainder of the year. Downgrades take effect at the next renewal. No long-term contract required for the upgrade path.

Per-plan. Every plan covers unlimited workforce members inside your Microsoft 365 tenant. No seat licenses, no per-user overages, no counting approvers or authors.

No. Documents, metadata, and audit logs all live inside your SharePoint libraries, which are inside your M365 tenant. The only exception is when DocuSign is enabled — documents transit DocuSign for the signing ceremony and return immediately.

Our service accounts have scoped access to the libraries under governance — necessary for the integration to function. Our engineering team does not have unilateral content access; support-session access is logged when customers explicitly request troubleshooting.

We don't position the product itself as HIPAA-certified. Microsoft signs a HIPAA BAA covering M365 tenants, and our layer inherits that posture. ISO 27001 certification at the vendor level is in progress; in the meantime, Microsoft's ISO 27001 covers the substrate.

Microsoft (M365 as the primary substrate, covered by your existing relationship with Microsoft) and DocuSign when customers enable the integration. We maintain the current list as part of our DPA.

Typically 8–12 weeks from kickoff to first-wave go-live. Month 1 is design workshops, month 2 is configuration and pilot, month 3 is cutover and remediation. Larger scopes take longer; smaller ones can complete in 6 weeks.

Yes. Three strategies — new-only, bulk, hybrid. Most customers pick hybrid: bulk-migrate high-criticality document types at cutover, use new-only for lower-criticality types that onboard gradually.

End users: 30 minutes or less, because the tools they use (Word, Outlook, Teams) don't change. Document owners: 2 hours. Approvers: 1 hour. Compliance admins: 3-4 hours. Train-the-trainer works well for larger organizations.

Your documents stay in your SharePoint libraries — they never left. Versioning, audit logs, and metadata remain accessible via SharePoint native tooling. The governance layer turns off; the library itself is unaffected.

No — and intentionally so. Part 11 validation sits with the customer's QA team as part of their compliance program. We provide the capabilities Part 11 audits reference (audit log, signatures, access control); your QA team runs IQ/OQ/PQ on the deployed instance.

The audit log provides the capabilities §11.10(e) explicitly requires: secure, computer-generated, time-stamped, append-only, named-user attributed, captures create/modify/delete events. Whether your program meets Part 11 depends on the validation work your QA team does around it.

Yes — customers use the capabilities in their Part 11 and GxP compliance programs. We're not positioned as a validated QMS platform (MasterControl and equivalents fill that slot). For SOPs and documented information in GxP scope where the customer's QA team runs validation, we fit well.

Two different layers that interoperate. Purview handles tenant-level records retention, legal hold, eDiscovery, and DLP. We handle active document governance on top — templates, approvals, review cadence, audit-log evidence. Customers run both together without conflict.

Yes, within the sequential-execution model. You configure the number of steps, which role sits at each step, fixed vs variable approvers, and whether any step requires PAdES signing. We don't support parallel, state-based, or conditional-skip workflows — by design, for compliance defensibility.

Word (primary authoring + automatic PDF at publication), PowerPoint, Excel, and PDF — all supported end-to-end. Legacy binary formats (.doc, .xls, .ppt) convert during migration. CAD, engineering, and specialized formats live in systems designed for them with cross-references from the DMS.

Yes. The active-lifecycle layer deploys on top of SharePoint libraries you already have — existing libraries become governed libraries. You don't migrate to a new storage location; the governance layer attaches to where your documents already live.

PAdES simple and advanced via DocuSign. Both cryptographically bind the signature to the PDF. Advanced adds identity verification (SMS, ID check, or knowledge-based auth). Simple is sufficient for most regulated workflows; advanced is for high-assurance contexts.

No. Qualified e-signatures require a Qualified Trust Service Provider and a qualified signature-creation device. Our DocuSign integration provides PAdES advanced, not qualified. Customers needing qualified signatures run a specialized tool alongside the DMS.

Yes. Customers with existing DocuSign agreements can connect their own tenant to the integration rather than using ours. This preserves your DocuSign branding, admin console, and billing relationship. For customers without DocuSign, we provision it as part of the Premium/Diamond onboarding.