The ndOffice ndMail integration is the pair of NetDocuments desktop tools that connects Microsoft Office and Outlook to the NetDocuments repository: ndOffice handles documents opened and saved from Word, Excel, and PowerPoint, and ndMail files email and attachments into client and matter workspaces. Your users live in Outlook and Word, so the settings behind these two tools shape adoption more than almost any other configuration decision.
What is the ndOffice ndMail integration in NetDocuments?
The ndOffice ndMail integration is the desktop layer that lets users save, open, version, and file NetDocuments content without leaving Microsoft Office and Outlook. Email is also a fraud channel, and business email compromise caused close to $2.8 billion in losses reported to the FBI in 2024, so filed mail needs the same controls as documents. ndOffice manages documents and ndMail manages email, and both write to the same cabinets, workspaces, and profile attributes.
A workspace profiled correctly for documents is the same container ndMail files into, so a gap in your profile design shows up in both tools at once. Keep in mind that a NetDocuments rollout depends on cabinet, workspace, and security design being settled before any desktop tool reaches users.
How does ndMail file email into NetDocuments workspaces?
ndMail files email by saving a message, and optionally its attachments, to a selected NetDocuments workspace or folder and applying profile values to it. Users choose the destination from predicted locations, from recent workspaces, or through a browse dialog.
Out of the box, a standard ndMail filing fills in only the Client, Matter, and Document Type fields, which catches firms that require more. The practical filing paths look like this:
- Predicted locations. ndMail proposes likely workspaces for a message, which covers most repeat correspondence on active matters.
- Browse. Users navigate the cabinet to pick a workspace or folder when the destination is new or unusual.
- Filing on send. Outgoing messages can prompt the user to file as they are sent, which keeps the sent side of every conversation in the matter record.
Which ndMail settings should NetDocuments administrators configure first?
NetDocuments administrators should configure the ndMail Browse profile option, the default profile values for filed email, and the required fields on each cabinet before rollout. These three decisions determine whether filed email arrives complete or arrives missing the attributes your searches and retention rules depend on.
The Browse profile option arrived with ndMail 1.12, so every user needs that version or later before it works. Cabinet Admins then choose Off, On, or On and Force for applying profile attributes in the Browse dialog. Each mode fits a different operating model:
- Off. This is the default. Filing stays fast, and email carries only the core profile values.
- On. Users can add profile attributes when they choose to, which suits firms with optional fields such as author or practice area.
- On and Force. Users must complete profile attributes on every filing, which suits cabinets where a required field drives security, retention, or reporting.
Pick the mode per cabinet with your records team. Forcing extra fields on a high-volume litigation cabinet adds a click to each of hundreds of daily filings.
How do ndOffice echoing and the Activity Center work?
ndOffice echoing keeps a local copy of documents a user opens or saves, and the ndOffice Activity Center is the desktop panel where those documents are listed, reopened, and managed. Together they give users one place to find recent work without opening a browser.
The Activity Center, redesigned in ndOffice 2.9, lists up to 100 recent documents, grouped into day and week sections. Two settings deserve an explicit decision. Optional local file sync keeps the latest version of frequently used documents on the device for offline work, and an administrator has to enable it through a registry setting on each computer. Echo scope is the second: decide which workstations and cabinets allow local copies at all, since a shared or kiosk machine holding echoed client files is a confidentiality exposure.
What security controls protect ndOffice and ndMail on the desktop?
ndOffice and ndMail inherit NetDocuments cabinet security, so a user can only file to or open from the workspaces their access rights allow. The desktop tools add controls on top of that model, and the most useful is the Activity Threshold alert.
The Activity Threshold emails a Repository Administrator when one user acts on more documents than a set limit in a single login session. It counts five actions: downloading, opening through the web interface, printing through NetDocuments, attaching a document to an email, and moving documents to a cabinet in another repository.
- Threshold level. Set the limit above the busiest legitimate day for a heavy user, so alerts point to real anomalies such as ransomware activity.
- Response owner. Name who investigates each alert as part of your NetDocuments governance framework, and log every outcome.
- Access testing. Confirm that a user walled off from a matter cannot file to it from ndMail, because access rules never tested by role surface as failures on go-live day.
How should ndOffice and ndMail be deployed to user desktops?
ndOffice and ndMail should be deployed as packaged, version-controlled installs pushed through your endpoint management tool, starting with a pilot group. A staged deployment catches add-in conflicts and profile gaps with 10 to 20 users before 500 users find them on the same morning.
Both tools share space with every other Office add-in you run. Plan the deployment in three parts:
- Pilot. Deploy to 10 to 20 users across practice groups, including at least one heavy email filer and one assistant who files for several lawyers, and run it for two weeks.
- Version pinning. Package one approved version of each tool and record it, so support can reproduce a problem on the exact build a user has.
- Phased waves. Roll out by practice group or office, a few hundred users at a time, with floor support on the first day of each wave.
Firms arriving from another system should note that moving from iManage to NetDocuments changes the tools lawyers file email with, so filing habits need retraining along with the data.
How do you test the ndOffice ndMail integration before go-live?
You test the ndOffice ndMail integration by running scripted filing and saving scenarios for every cabinet, role, and profile rule in a test environment, then repeating the critical ones in production after deployment.
Build the scripts around real work:
- Required fields. File email to a cabinet set to On and Force, and confirm the filing cannot complete until the required attributes are filled.
- Attachments and threads. File a message with several attachments and a long reply chain, then confirm that what landed in the workspace matches your filing standard.
- Offline saving. Save a document from Word with the network disconnected, reconnect, and confirm the version reaches NetDocuments intact.
Rerun the priority scenarios after cutover.
Why does email filing adoption stall after an ndMail rollout?
Email filing adoption stalls after an ndMail rollout when filing takes more effort than leaving the message in the inbox, and when nobody measures whether email reaches the matter record. Lawyers file what is easy and postpone what is slow.
Email volume makes that choice constant. One 2023 workplace study of 31,000 people in 31 countries found that the heaviest email users (the top 25 percent) spend 8.8 hours a week on email. At that volume, one extra required field or one slow browse dialog repeats dozens of times a day. That is why change management has to start at project kickoff, well before go-live.
Track the share of email filed per practice group every week for the first 90 days, and fix the settings behind the lowest numbers first.
What should hypercare cover after an ndOffice and ndMail go-live?
Hypercare after an ndOffice and ndMail go-live should cover add-in stability, filing errors, echo and sync issues, and user questions for the first 30 days, all through one triage desk. Most desktop tickets cluster in the first two weeks.
Sort issues by cause:
- Configuration defects. A missing default, a wrong required field, or a cabinet permission error affects every user in that cabinet, so it gets fixed once, centrally.
- Desktop defects. Add-in load failures, version mismatches, or echo problems affect one machine at a time and go to the endpoint team.
- User questions. How-to questions point to gaps in training or guides, so log them by topic and update the role guides every week.
Route everything through one queue, since hypercare defects resolve faster through a single triage path with agreed severity levels.
Conclusion
The ndOffice ndMail integration decides how most of your users experience NetDocuments, since they touch it dozens of times a day. Settle the cabinet profile settings first, choose echo and sync behavior deliberately, pilot the desktop install, script the filing tests, and staff a triage desk for the first month.
How Basla can help
Basla provides certified delivery team members for NetDocuments implementation, including business analysts who turn each practice group’s filing habits into ndMail and cabinet profile settings, and QA specialists who script filing and security scenarios across every role before go-live. Basla’s documentation writers produce the role-specific guides that carry ndOffice and ndMail adoption past hypercare.
Basla works through staff augmentation or Basla-managed delivery. On other legal platform programs, Basla has supported legal technology services across more than 100 jurisdictions for a global organization and doubled delivery team capacity to meet compressed implementation timelines.
Frequently asked questions
What is the ndOffice ndMail integration?
The ndOffice ndMail integration is the set of NetDocuments desktop tools that connects Microsoft Office and Outlook to the NetDocuments repository. ndOffice handles saving, opening, and versioning documents, and ndMail files email and attachments into client and matter workspaces.
Which ndMail version supports the Browse profile feature?
ndMail 1.12 and later support the Browse dialog profile feature. A Cabinet Admin must also switch the setting on for each cabinet, choosing Off, On, or On and Force.
Why are filed emails missing required profile fields?
Filed emails miss required profile fields because a standard ndMail filing completes only the Client, Matter, and Document Type values. Setting the Browse option to On and Force makes users complete profile attributes before the filing finishes.
Can ndOffice work offline?
ndOffice supports offline work when an administrator enables Local File Sync, which keeps the latest version of frequently used documents on the device. The feature is turned on per computer through a registry setting, so offline access is an administrator decision.
How many documents does the ndOffice Activity Center show?
The ndOffice Activity Center shows up to 100 recent documents, grouped into day and week sections. The same panel also opens the NetDocuments Home Page.
How long should hypercare last after an ndOffice and ndMail rollout?
Hypercare after an ndOffice and ndMail rollout should run for at least 30 days, with the heaviest staffing in the first two weeks. Extend it for any practice group whose email filing rate is still climbing at the 30-day mark.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*