Introduction
This document provides a detailed overview of the integration between Legora and NetDocuments. Additionally, it includes a Q&A section to address common questions.
Legora is an approved technology partner with NetDocuments, allowing us to fully utilize their work API, uploading and syncing documents with matter ID attached, facilitating audits.
For more information on security, please review the NetDocuments Security White Paper.
Notes
There is no per-user OAuth connection or redirect URI in this integration.
Do not enter OAuth client IDs, secrets, or base URLs in Legora—the backend reads a single API key from Azure Key Vault.
If you change the API key, update
netdocs-api-keyin Key Vault; no UI change is needed in Legora beyond ensuring the connector remains active.
Add the NetDocuments connector in Legora
Request your Legora Representative enable the NetDocuments Integration for you.
Let users pick and sync documents
Once the connector is active, users can open the NetDocuments (NDConnect) picker in Legora to browse and select documents to sync.
The NetDocuments connector is active.
Users can open the NDConnect picker, select documents, and see them synced into Legora.
Downloads complete successfully (including bulk operations with concurrency control).
Technical note (UI):
NDConnect loader (current setting): The script currently points to the NDConnect US component
Troubleshooting
I can't find the NetDocuments integration
This means the connector was not added or user lacks access. Ask your Legora representative to add the NetDocuments connector in Organisation Admin and ensure the user has permission to use it.
NetDocuments access key is empty
The Key Vault secret exists but has no value. Set netdocs-api-key in Azure Key Vault to the correct APkey; verify backend Key Vault read access
Failed to initialize NetDocuments integration
NDConnect environmnet or network issue; invalid access key. Check the network connectivity to the configured NDConnect endpoint and verify the API key is valid