Document management integrations and API

A stored document opens directly in Word, Excel or PowerPoint, and saving returns it to DocumentMS as a new version. The document stays checked out while it is open, so two people cannot produce conflicting edits. Removing the download-edit-reupload cycle matters disproportionately: that cycle is where local copies are created, and local copies are where the current version stops being current.

The Outlook add-in files a message and its attachments into a folder from the reading pane. Email is where most documents arrive and where most of them stay, so intake that requires leaving the mailbox is intake that does not happen.

Single sign-on runs over OIDC with Microsoft Entra ID, Okta and Google Workspace, with directory groups mapped to DocumentMS roles. The convenience is secondary; the control is primary. When a leaver is disabled in the directory they cannot authenticate here, which closes the gap between an offboarding process and a document system nobody remembered to update.

Group-to-role mapping also means access reviews happen where the rest of your identity governance already happens, rather than in a separate console with its own review cycle.

The storage backend is configurable at runtime between local disk, Amazon S3 and Azure Blob Storage. Pointing DocumentMS at a bucket or container in your own account means document bytes sit in a region you chose, under your bucket policy, your lifecycle rules, your keys and your logging.

For organisations with data residency obligations this is usually the deciding capability, because it converts a vendor commitment into something you can verify yourself.

Where an organisation has standardised on DocuSign, documents can be sent into it for signature and the completed envelope, certificate of completion and signing history filed back against the original record. The choice is per workflow, so high-value agreements can route through DocuSign while internal acknowledgements use built-in capture.

The API covers documents, folders, metadata, versions, permissions, workflow instances, signature requests and audit events. It authenticates with scoped API keys, paginates consistently, and returns a documented error contract rather than a bare status code and an empty body.

The contract matters more than the coverage. An API that changes shape between releases costs more to depend on than one with fewer endpoints and a stable interface, so breaking changes are versioned rather than shipped.

Webhooks push events outward as they happen: a document uploaded, a version created, an approval granted, a signature completed, a permission changed, a record deleted. Payloads are signed so the receiver can verify they came from us and were not replayed.

Webhooks are what make DocumentMS usable as a component rather than a destination — an approval in DocumentMS can advance a case in another system without either side polling the other.

There is a desktop application, and the web interface works on mobile and tablet. Mobile matters most for capture rather than reading: a signed delivery note or a site inspection photographed on a phone reaches the repository, gets OCR-processed and becomes searchable, which is a different proposition from browsing folders on a small screen.