Authorized, then refused
How you'll know: Users sign in fine, and every repository call returns an access error.
Fix: The firm's administrator hasn't approved the app for that repository yet. Send them the client ID and app name.
You've been handed a ticket: when a matter opens in practice management, its NetDocuments workspace should exist with the right client, matter and profile values. NetDocuments has a REST API for exactly that, covering workspaces, documents, versions and the metadata on each. Before the first call works, three things have to be in place: a portal account from NetDocuments, a registered app, and the firm's approval for its repository.
The API: REST, authenticated with OAuth 2.0. It reads and writes workspaces, documents, versions and profile attributes.
Where apps are registered: NetDocuments' developer or partner portal, which uses its own sign-in. Accounts aren't self-serve: you request one from NetDocuments.
What you get: a client ID and client secret for your application, with the redirect URIs you list.
Which host: the API address follows the firm's NetDocuments data center, so a US app and an EU firm don't mix. An EU example is api.eu.netdocuments.com.
Ask NetDocuments for access through its support channel. The portal account is separate from a normal NetDocuments login, even when the email address is the same.
Create the app in the portal and set its redirect URIs. A server-side integration that keeps its secret private is registered as a confidential client.
Watch for: the redirect URI. It has to match what your code sends exactly, protocol and trailing slash included.
Ask for what the job needs. Lookup, read and edit cover most document and workspace work. Others exist, such as organize, full and admin, and admin is the one that reads repository user and group lists.
A NetDocuments administrator at the firm has to allow the application for their repository. Until they do, sign-in can succeed and calls still get refused.
Use the API host for the firm's data center, then read something you already know, such as one workspace and its profile values, before writing anything.
How you'll know: Users sign in fine, and every repository call returns an access error.
Fix: The firm's administrator hasn't approved the app for that repository yet. Send them the client ID and app name.
How you'll know: The same code works against one firm and fails against another.
Fix: Check which data center each firm is on. An app registered for one region's host won't sign in against another's.
How you'll know: A new feature needs a scope the app didn't ask for, and people have to authorize again.
Fix: List every scope the roadmap needs up front, including admin if you'll read user or group lists.
How you'll know: Workspaces get created, then records staff rename them and refill profile fields by hand.
Fix: Map the firm's client and matter numbers, practice area and responsible lawyer fields before writing the create call, and test against the firm's real profile setup.
Yes, a connector links NetDocuments workspaces to their matching Salesforce records. It handles the general link well. A firm with its own field mapping, or rules about what a closed opportunity should create, needs custom work on the API next to it.
Yes. People open, edit and save NetDocuments files from inside Word, Excel, Outlook and PowerPoint without a separate NetDocuments window, and Power Automate flows can reach NetDocuments through its connector.
Yes, the NetDocuments App Directory lists partner apps and integrations, including e-signature, PDF and practice management links. Look there first. A workflow built around your firm's own matter rules usually isn't something a listed app was made for.
Mostly. You'll need NetDocuments to open a developer portal account, and the firm's administrator to approve the app for its repository. After that, the code is yours to write against the REST API, and that's the layer n-frames builds its NetDocuments integrations on.