QMSdesk

CompareFrom SharePoint or a file server

Moving from a SharePoint QMS to QMSdesk

A SharePoint QMS keeps your documents organized and versioned. QMSdesk™ keeps the quality process around them: who signed, what each signature meant, who needed training, and proof that none of it has changed since.

What you gain moving to QMSdesk

Signatures that say what they mean

Every signature re-authenticates the signer, with multi-factor authentication where your tenant requires it. QMSdesk records what the signature means from a controlled vocabulary of signature meanings, and the signature commits in one transaction with the change it approves.

The right person at every signature

An author, a reviewer and an approver are always different people, checked as each signature is applied. The author never sees the option to approve their own document, and high-criticality documents need two independent approvers.

Training that follows approval

When a document is approved, training is assigned to the people it affects. The document takes effect after a grace period, 14 days by default, so your team is trained before the new version applies. Quizzes are graded against a frozen snapshot of the questions.

A trail that proves itself

Every audit-trail entry is SHA-256 hash-chained to the one before it, and the database keeps the log insert-only. Each day, QMSdesk re-verifies every chain and confirms every signature still points to its record.

Your existing SOPs, migrated honestly

Bring your current SOPs in batches, each under one signed migration attestation. Every migrated document carries a permanent "Migrated" badge, and QMSdesk never presents it as approved inside the system. From its next revision, it follows your full signed lifecycle.

How a SharePoint QMS moves into QMSdesk

  1. Step 1 of 5

    Build your regulatory profile

    Tell QMSdesk what you do, and it sets your document types, signing roles, deadlines and retention floor.

  2. Step 2 of 5

    Export and import your documents

    Export the current versions from SharePoint or your file server, then import them in batches through the import wizard, each batch signed.

  3. Step 3 of 5

    Invite your people

    Give each person their roles in the Access Control stage of the Configuration Runway. Sign-in can use SAML single sign-on with Microsoft Entra.

  4. Step 4 of 5

    Test in your real tenant

    Run a real review and approval end to end. The test records are kept as evidence.

  5. Step 5 of 5

    Go live

    Evidence-based readiness checks, then separately signed technical and quality attestations.

SharePoint Part 11 questions, answered by the workflow

When your document control runs in QMSdesk, the electronic-record and electronic-signature controls are part of every step. QMSdesk is designed to support 21 CFR Part 11 and EU GMP Annex 11 controls:

  • a hash-chained audit trail, with audit-log immutability enforced by the database;
  • re-authentication at every signature, with multi-factor authentication where you require it;
  • recorded signature meaning, with the signature and the change it approves committed together;
  • segregation of duties checked when each signature is applied;
  • a signed periodic audit-trail review over a risk-focused view.

What stays familiar

Author in the editor, or upload a source file

Keep writing your SOPs the way your team already does.

Controlled copies

A controlled-copy PDF carries a "CONTROLLED COPY" banner and a signature log, and every download is logged.

Cross-references

Typed links between documents, a "Referenced by" view, and flags when a reference goes stale.

Search

Global search across documents and every other record, respecting permissions and site scope.

External documents

Standards, guidance and quality agreements sit alongside your SOPs as reference documents, with their provenance and a "not internally approved" banner.

Questions buyers ask

Can we import our documents from SharePoint?

Yes, as files. Export the current versions, then import them in batches through the import wizard. Each batch is signed under one migration attestation.

Will our migrated SOPs show as approved in QMSdesk?

No. They carry a permanent "Migrated" badge, and QMSdesk never creates approvals that didn't happen in the platform. Their history stays honest, and their next revision runs through your signed lifecycle.

Can our team keep signing in with Microsoft?

Yes. QMSdesk supports SAML 2.0 single sign-on with Microsoft Entra, as well as Okta, Google Workspace and custom SAML.

Does QMSdesk support 21 CFR Part 11?

QMSdesk is designed to support electronic-record and electronic-signature controls relevant to regulated use, including the hash-chained audit trail, re-authentication at every signature and recorded signature meaning. The certification under Part 11 §11.100(c) is yours to file with the FDA.

How long does the move take?

The target for a first working workflow is 8–12 weeks, depending on scope, data readiness and your team's availability.

Bring one SOP. We'll show you its whole life in QMSdesk.

Bring a document your team revises often, and we'll take it from draft to approval, training and a controlled copy.