Integrations
DocumentMS integration directory
This directory lists every system DocumentMS connects to, what the connection actually does, and what you need on the other side to set it up. Where no packaged integration exists, the REST API and webhooks cover the same ground with a documented contract.
How DocumentMS connects to everything else
A document management system that does not reach the tools people already have open becomes a second place to look, and a second place to look is a place that stops being current. The integrations below exist to remove that failure: documents open in the applications people already use, records arrive from the mailboxes they already arrive in, and identity is governed where the rest of your identity governance already lives.
Where no packaged connector exists, the REST API and signed webhooks cover the same ground with a documented contract. Most bespoke connections we see are a few hundred lines of code, because the model — documents, folders, metadata, versions, permissions, workflows, events — maps cleanly onto how other systems think about content.
Connector directory
Microsoft 365
Open and edit in Word, Excel and PowerPoint with the version returned to DocumentMS
Outlook add-in
File an email and its attachments into a folder without leaving the mailbox
DocuSign
Send for signature through DocuSign and store the completed envelope
Amazon S3
Use an S3 bucket in your own account and region as the storage backend
Azure Blob Storage
Store documents in Azure with your own keys and region selection
Microsoft Entra ID
OIDC single sign-on with group-to-role mapping
Okta
OIDC single sign-on and SCIM-style user provisioning
Google Workspace
Sign in with Google and import from Drive
REST API
Documented endpoints for documents, metadata, workflows and audit events
Webhooks
Push document, approval and signature events to your own systems
What each connector is for
| Purpose | Connectors | Typical driver |
|---|---|---|
| Authoring without a download cycle | Microsoft 365 | Local copies are where the current version stops being current |
| Getting documents in | Outlook add-in, email-to-folder import, REST API | Email is where most documents arrive and where most of them stay |
| Identity and access lifecycle | Microsoft Entra ID, Okta, Google Workspace | Leavers should lose access through the directory, not a second admin console |
| Signature | Built-in signing, DocuSign | Keeping the signed output as a version of the same record |
| Data residency and key custody | Amazon S3, Azure Blob Storage | Converting a vendor commitment into something you can verify yourself |
| Driving your own systems | REST API, webhooks | An approval here should advance a case there, without either side polling |
FAQ
Integration questions
What if there is no connector for our system?
The REST API and webhooks cover the same ground with a documented contract: read and write documents, metadata, versions and permissions, start workflows, and receive events as they happen. Most bespoke connections we see are a few hundred lines rather than a project.
Do integrations cost extra?
Microsoft 365, Outlook, DocuSign, single sign-on, the REST API and webhooks are included from the Business tier. Customer-provided storage backends are an Enterprise capability. Nothing on this page is licensed separately from the tier it appears in.
Which connectors touch document content?
Microsoft 365 and DocuSign transmit document content by necessity; the storage backends hold it. Single sign-on connectors handle identity only and never see document content. That distinction matters for a security review, so it is stated on each connector page.
Can we restrict which integrations are enabled?
Yes — each is configured per tenant and enabled deliberately rather than by default. Connectors can also be scoped below tenant level, so a branch or department can have an integration the rest of the organisation does not, and an administrator can see which are active where without opening each one.
Última revisión: 2026-09-01