Configuring Chrome Local Network Access (LNA) for NetDocuments

Overview

Starting with Chrome 142 and Edge 143, browsers require explicit permission for websites to communicate with local applications through Local Network Access (LNA). This affects NetDocuments desktop integrations, specifically:

• ndOffice – Opens documents directly in Microsoft Office applications
• ndClick – Handles document downloads and local file operations

Without proper LNA configuration, users will experience prompts or failures when trying to use these NetDocuments features.

NetDocuments URL Patterns

You’ll need to add both of these URL patterns to cover all NetDocuments deployments:

Deployment Region
URL Pattern

US Deployments
https://[*.]netvoyage.com

International Deployments
https://[*.]netdocuments.com

Recommendation: Always configure both domains to support cross-region workspaces.

Method 1: Google Workspace Admin Console (Cloud-Managed Chrome)

Use this method if you manage Chrome browsers through Google Workspace.

Prerequisites

• Google Workspace administrator access
• Chrome Enterprise Core or Chrome browser management enabled

Step-by-Step Instructions

1. Sign in to the Google Admin Console
   • Go to admin.google.com
   • Sign in with your administrator account
2. Navigate to Chrome Settings
   • Click the menu icon (☰) in the top left
   • Go to Devices → Chrome → Settings
   • Select User & browser settings
3. Select the Organizational Unit
   • On the left side, select the organizational unit (OU) you want to apply the policy to
   • To apply to all users, select the top-level organization
4. Find the Local Network Access Setting
   • Use the search box at the top of the settings page
   • Search for: Local Network Access
   • Or navigate to: Network → Manage website access to local network endpoints
5. Configure the Allowed URLs
   • Click on Allowlist of URL patterns not subject to Local Network Access checks
   • Add the following URLs (one per line):

<?XML:NAMESPACE PREFIX = “[default] http://www.w3.org/2000/svg” NS = “http://www.w3.org/2000/svg” />

     https://[*.]netvoyage.com
     https://[*.]netdocuments.com

6. Save the Configuration
   • Click Save at the bottom of the page
   • Changes typically take effect within minutes, but can take up to 24 hours

Alternative: JSON Policy Method

If your Admin Console supports custom JSON policy configuration:

json

{
  "LocalNetworkAccessAllowedForUrls": [
    "https://[*.]netvoyage.com",
    "https://[*.]netdocuments.com"
  ]
}

Method 3: Windows Group Policy (On-Premise Active Directory)

Use this method if you manage devices through on-premise Active Directory with Group Policy.

Prerequisites

• Domain administrator access
• Chrome ADMX templates installed (download from Google)
• Group Policy Management Console (GPMC)

Step-by-Step Instructions

1. Download and Install Chrome ADMX Templates
   • Download from: Chrome Enterprise Bundle
   • Extract the ADMX files
   • Copy chrome.admx to C:\Windows\PolicyDefinitions\
   • Copy language files (e.g., chrome.adml) to C:\Windows\PolicyDefinitions\en-US\
2. Open Group Policy Management Console
   • Press Win + R, type gpmc.msc, press Enter
   • Or search for “Group Policy Management” in the Start menu
3. Create or Edit a Group Policy Object (GPO)
   • Right-click on your target OU
   • Select Create a GPO in this domain, and Link it here…
   • Name it: Chrome - NetDocuments Local Network Access
   • Or edit an existing Chrome policy GPO
4. Navigate to the Chrome Policy
   • Right-click the GPO → Edit
   • Navigate to:

     Computer Configuration
     └── Administrative Templates
         └── Google
             └── Google Chrome
                 └── Content Settings

5. Configure Local Network Access Allowed URLs
   • Find and double-click: URLs to grant Local Network Access permission
   • Select Enabled
   • Click Show… to add URLs
   • Add each URL on a separate line:

     https://[*.]netvoyage.com
     https://[*.]netdocuments.com

• Click OK twice to save

6. Force Group Policy Update (for testing)
   • On a test workstation, open Command Prompt as Administrator
   • Run: gpupdate /force
   • Restart Chrome browser

Verification Steps

After deploying the policy, verify it’s working correctly:

Check Chrome Policy Status

1. Open Chrome browser on a managed device
2. Navigate to: chrome://policy
3. Click Reload policies to get latest
4. Search for: LocalNetworkAccessAllowedForUrls
5. Verify both NetDocuments URLs appear in the policy value

Test NetDocuments Integration

1. Log in to NetDocuments
2. Select a document
3. Click Edit (should open in native Office application via ndOffice)
4. Verify no browser prompts appear for Local Network Access

Troubleshooting

Policy Not Appearing in chrome://policy

• For Intune: Verify device sync status, check Intune reports for deployment errors
• For Group Policy: Run gpresult /r to verify GPO is applied
• For Google Admin: Check OU targeting, wait up to 24 hours for propagation

ndOffice/ndClick Still Not Working

1. Clear browser cache and restart Chrome
2. Restart the ndOffice/ndClick application on the desktop
3. Verify the desktop application is running (check system tray)
4. Check for conflicting policies that might block local network access

Error: “ERR_BLOCKED_BY_LOCAL_NETWORK_ACCESS”

This indicates the policy hasn’t been applied. Verify:

• The URL patterns match exactly as specified
• The policy is scoped to the correct users/devices
• Sufficient time has passed for policy propagation

Additional Considerations

Embedded Content (iframes)

If your organization embeds NetDocuments in other applications (SharePoint, Salesforce, etc.), each parent iframe must include the allow="local-network-access" attribute:

html

<iframe src="https://vault.netvoyage.com" allow="local-network-access"></iframe>

Salesforce Integration Note

There’s a known Salesforce platform issue where the Visualforce host iframe doesn’t support the allow="local-network-access" attribute. Salesforce has a bug open for this (Reference ID: W-19721422). Monitor for updates via Salesforce Known Issues.

References

• NetDocuments Support Article: Configure Local Network Access permissions
• Chrome Enterprise Policy List
• Microsoft Intune Documentation
• Google Chrome Enterprise Help