NetDocuments, connected to the rest of your firm.
We open workspaces when matters open, file documents into the right folder with the right profile, and keep NetDocuments in step with your practice management, docketing and Microsoft 365.
NetDocuments integration, built around your firm
For many firms, NetDocuments holds the matter file: workspaces built from client and matter lookups, profiled documents and filed email, and access controls that decide who can see what. It is often the most carefully governed system in the firm.
The trouble starts at the edges. A matter is opened in the practice management system, but the workspace is created by hand days later, sometimes with the wrong matter number. Signed engagement letters, call notes and court orders sit in inboxes and download folders instead of the workspace. Team changes in one system never reach the access list in the other. NetDocuments has no deadlines or tasks of its own, so a filed document that starts a clock only counts if someone notices it.
We connect NetDocuments to the systems around it through its REST API. A matter opened elsewhere creates the client and matter entries and the workspace, with your folder template applied. Documents from other systems are filed and profiled by rule. New documents of the types you choose, such as orders or notices, are picked up and routed to the right person for review. Everything runs in your firm's Microsoft 365 / Azure tenant, under a NetDocuments account your administrator controls.
The NetDocuments data we work with
Clients and matters
Read and create the client and matter lookup entries that define your workspaces, including the closed flag when a matter ends.
Workspaces and folders
Open the workspace for a matter, read its contents, create folders and apply your folder template.
Documents and versions
Upload, download, add versions, check out and check in, and file into folders, with profile attributes such as client, matter, document type and author.
Filed email
Save messages as .msg or .eml documents, with sender, recipients and dates captured in the profile.
Access and ethical walls
Read workspace access lists and Workspace Security Manager policies, so other systems respect who is and isn't allowed into a matter.
Users, groups and history
Map NetDocuments users and groups to Microsoft 365 accounts, read document history, and add an audit entry for each automated action.
How the NetDocuments integration works
- OAuth, approved by your administrator. NetDocuments issues API client IDs through its developer support process, and your repository administrator must authorize the client ID before it can reach your repository. For scheduled jobs, the administrator marks a user as a non-interactive service account and links it to the client ID, so the automation never runs as a person.
- Polling, because there is no push. NetDocuments does not send change events to other systems. We read its change feed for each cabinet on a schedule agreed with you, so new and changed documents are picked up within minutes rather than instantly.
- Paced to your allowance. Every NetDocuments API response reports how much of the usage allowance has been spent. We read it on each call and slow down before NetDocuments has to refuse a request.
- Runs in your tenant. The code, its credentials and its logs live in your firm's Azure subscription. Documents are passed between systems, not copied into a second store.
- Power Automate where it fits. NetDocuments publishes a Power Automate connector. If a simple flow built on it covers what you need, we'll tell you and build it that way.
Where NetDocuments fits
Email and documents filed by rule
Complete matter files without anyone dragging and dropping.
Signed client → matter open everywhere at once
Matter opening goes from days of handoffs to minutes, and every system starts with the same data.
Client call → transcript in the DMS → summary, follow-ups and calendar
The call is documented, filed and on the calendar before the attorney has hung up the headset.
Often connected with
Questions about connecting NetDocuments
Our other systems already say they integrate with NetDocuments. Why would we need you?
If one of those integrations does what you need, use it, and we'll say so. Vendor integrations connect two products in a standard way. We build the workflow that spans several systems and follows your firm's rules, such as intake to matter to workspace to docketing.
Why isn't it instant?
NetDocuments has no webhooks, so every integration has to check for changes. We read the change feed on a schedule agreed with you, usually every few minutes, and pace calls to the allowance NetDocuments reports. For filing and review work, that delay is rarely noticeable.
What does our NetDocuments administrator need to do?
Authorize the integration's client ID for your repository, set up a non-interactive service account for scheduled jobs, and give it access to the cabinets in scope. We provide a checklist with the exact access requested and why.
We still use Worldox. Does this apply to us?
Not directly. Worldox and eDOCS are separate on-premises products that do not use the NetDocuments cloud API. If you are moving to NetDocuments, we can plan the migration so your integrations work on day one.
Running NetDocuments with other systems?
Tell us what you use and where your staff re-key data. We’ll tell you honestly what’s possible, and what your vendors already cover.