With Local Edit, you can open documents from Web Access directly in your favorite local editor or viewer.
Local Edit functionality is available only to customers with an Advanced Web Access license.
This document provides guidance for IT administrators on deploying, configuring, and managing Nasuni’s Local Edit application. It includes installation instructions, update management, file lifecycle details, and troubleshooting references.
For the User Guide, see Local Edit.
Supported Document Types
Local Edit supports the following document types for viewing and editing.
Microsoft Formats
Word (.docx)
Excel (.xlsx)
PowerPoint (.pptx)
Text Formats
Plain text (.txt)
Portable Document Formats
PDF (.pdf)
Files up to 250MB can be viewed and edited.
The Local Edit Workflow
Users can view or edit supported documents locally using the following workflow:
The user selects a document in one of the supported formats.
From the right-click menu or the top toolbar, the user selects Edit Locally.
The selected document is downloaded to the user’s local machine.
The document automatically opens in the user’s default viewer or editor.
The user can view or make changes to the document as needed.
Any edits made can be saved directly within the local application.
The updated document is automatically uploaded.
When finished, the user closes the document.
Installing Local Edit
To enable the local editing experience, users must install an application called Local Edit on their computer. Local Edit is developed and maintained by Nasuni.
Local Edit can be downloaded directly from your Nasuni Portal account and is available for both Windows and macOS platforms.
The following subsections provide installation instructions for:
Individual installation: Suitable for testing or for small team environments.
Organizational rollout: Recommended for larger or centrally managed deployments.
Individual Installation
There are two ways for individual users to install Local Edit:
From a colleague: Obtain the relevant installer from a colleague who has access to the Nasuni Portal.
From the download link: When attempting to Edit Locally for the first time, the user is prompted with a download link for the installer.
After the user has obtained the Local Edit installer for Windows or macOS, installation can begin.
Note: Administrative privileges are required during installation. The installer automatically requests privilege escalation through the standard system prompt on both Windows and macOS. Ensure that the user account performing the installation has administrative rights.
The Local Edit installers (.msi for Windows and .pkg for macOS) guide users through the installation process with an intuitive setup wizard.
After installation is complete, no system restart is required.
Organizational Rollout
Local Edit can be deployed across multiple systems using standard enterprise deployment management tools such as JAMF (for macOS) and Microsoft Intune (for Windows). These tools enable centralized installation, version management, and configuration for large-scale environments.
Windows Deployment
To install the application on Windows using administrative privileges, run the following command:
msiexec.exe /i “u:\path\to\LocalEdit.msi” /qn /norestart
where:
/i — Installs the specified MSI package.
/qn — Performs a silent installation with no user interface.
/norestart — Prevents automatic system restart after installation.
This command can be used directly in scripts, Group Policy Objects (GPO), or within deployment tools such as Intune.
macOS Deployment
To install Local Edit on macOS, use the following command with administrative privileges:
sudo installer -pkg /path/to/LocalEdit.pkg -target /
This command can be incorporated into JAMF policies, Apple Remote Desktop scripts, or other MDM deployment workflows.
Updating Local Edit
New versions of Local Edit are released periodically. Customers are notified of these updates through Nasuni’s standard release communication channels.
When a new version becomes available, users can update Local Edit using one of the following methods:
Manual or corporate installation: Users can install the latest version themselves, or IT administrators can deploy it through the organization’s standard rollout process.
Automatic update: Local Edit supports auto-updating, allowing the application to download and install newer versions automatically when enabled.
Keeping Local Edit up to date ensures compatibility with the latest Nasuni features and provides access to performance improvements and security enhancements.
Manual or Corporate Installation
To update Local Edit using the installer, follow the same steps as a standard installation.
If you are deploying updates through a corporate rollout process, you might wish to disable the Automatic Updates. See Configuration for more details.
Automatic Update
The Local Edit application automatically checks for updates every 3 hours while it is running. If a newer version is available, users receive a prompt to install the update.
An example of the automatic update prompt is shown below.
If you are deploying updates through a corporate rollout process, you might wish to disable the Automatic Updates. See Configuration for more details.
Configuration
This section outlines the controls available to manage Local Edit.
Disabling Auto Update
Disabling automatic updates might be required in corporate environments where software installations are centrally controlled or subject to strict change management policies.
Automatic update behavior can be managed through the operating system’s configuration settings:
macOS: Controlled via PList or UserDefaults configuration.
Windows: Controlled via the Registry or Group Policy (GPO).
Windows Configuration
To manage the automatic update setting on Windows, configure the following registry key:
Path:
HKCU\Software\Nasuni\Nasuni Local Edit\Settings\CanUpdate
Possible values:
0: Disables automatic updates.
Any other value, or if unset: Enables automatic updates (default behavior).
macOS Configuration
To manage the automatic update setting on macOS, set the PList option DisableAutoUpdates in com.nasuni.LocalEdit.plist.
For example:
defaults write ~/Library/Containers/com.nasuni.LocalEdit/Data/Library/
Preferences/com.nasuni.LocalEdit.plist DisableAutoUpdates true
Possible Values:
true: Disables automatic updates.
false: Enables automatic updates (default behaviour)
Disabling Local Edit
In environments where the Local Edit feature is not desired, it can be disabled within the Nasuni Web Access interface.
To request that Local Edit be disabled for your organization, contact Nasuni Support for assistance.
Restricting Local Edit Sources (Security Best Practice)
When deploying Nasuni Local Edit to endpoint devices, it is recommended to restrict the sources from which the application can open files.
By defining an explicit list of allowed hostnames or IP addresses, administrators can ensure that users only open documents from trusted Nasuni Web Access servers or other approved sources.
The Local Edit applications allow configuration of a comma-separated list of hostnames or IP addresses.
Note: Wildcards are not permitted.
Windows Configuration
To restrict the allowed sources on Windows, configure the following registry key:
Registry Path:
HKCU\Software\Nasuni\Nasuni Local Edit\Settings\AllowedHostnames
Accepted Values: Provide one or more hostnames or IP addresses, separated by commas.
Examples:
webaccess.example.com
→ Allows documents to be opened from webaccess.example.com.webaccess-eu.example.com,webaccess-us.example.com
→ Allows documents to be opened from either webaccess-eu.example.com or webaccess-us.example.com.10.1.2.3
→ Allows documents to be opened directly from the IP address 10.1.2.3.
Default Behavior:
If this registry key is not set or the value is blank, there are no hostname restrictions, and Local Edit opens files from any source.
macOS Configuration
To restrict allowed sources on macOS, set the AllowedHostnames key in the Local Edit preferences file.
Command Example:
defaults write ~/Library/Containers/com.nasuni.LocalEdit/Data/Library/Preferences/com.nasuni.LocalEdit.plist AllowedHostnames "[insert value]"
Accepted Values:
Provide one or more hostnames or IP addresses, separated by commas.
Examples:
webaccess.example.com
→ Allows documents to be opened from webaccess.example.com.webaccess-eu.example.com,webaccess-us.example.com
→ Allows documents to be opened from either webaccess-eu.example.com or webaccess-us.example.com.10.1.2.3
→ Allows documents to be opened directly from the IP address 10.1.2.3.
Default Behavior:
If this key is not set or the value is blank, there are no hostname restrictions, and Local Edit opens files from any source.
Customizing Installation Instructions
If your organization has specific requirements regarding the installation process or the download information displayed to users when opening files with Local Edit, these settings can be customized.
To request changes, such as disabling the download option or modifying the messaging presented to end users, contact Nasuni Support for assistance.
Uninstalling Local Edit
Local Edit can be uninstalled using the standard tools available on each supported operating system.
Windows
Manual Removal
To manually uninstall Nasuni Local Edit, open the Add or Remove Programs window in Windows and select Uninstall.
Scripted Uninstallation
For automated removal, run the following command with administrative privileges:
msiexec.exe /x "U:\path\to\LocalEdit.msi" /qn /norestart
where:
/x — Uninstalls the specified MSI package.
/qn — Runs the process silently, with no user interface.
/norestart — Prevents the system from restarting automatically after uninstall.
This method can be used in scripts, Group Policy Objects (GPO), or deployment tools such as Microsoft Intune.
macOS
To uninstall Local Edit on macOS, simply remove the application from the Applications folder.
This completely removes the application from the user’s device.
File Life Cycle And Management
When users open files locally, Local Edit downloads the files to their device. These files are stored in a hidden folder named .localedit.
Default folder locations:
Windows: %USERPROFILE%\.localedit\
macOS: $HOME/.localedit/ (this location is recommended, but users can override it when editing their first document)
File Lifecycle
Files downloaded through Local Edit follow a managed lifecycle:
Time Since Download | File Behavior |
0 to 36 hours | Documents can be actively edited and saved. |
36 hours to 5 days | Documents remain stored locally and are eligible for automatic cleanup. Changes can no longer be saved. |
5 days to 2 weeks | Documents containing unsaved changes (for example, edits that could not be uploaded back to Nasuni Web Access) are retained. After 2 weeks, they are removed from disk. |
Local Edit automatically manages the retention and removal of local files. No manual cleanup or user action is required.
Local Edit must be running to manage the files lifecycle.
Detecting Changes To Files
Local Edit automatically monitors files that users open for editing. When changes are detected, the application waits five seconds after the most recent save before beginning the upload process. This delay helps ensure that the user has completed their save operation before synchronization begins.
To maintain data integrity, Local Edit creates a temporary copy of the file before uploading it. This approach ensures that the version being uploaded is consistent and not affected by any additional edits made during the upload process.
Best Practices
The following best practices are recommended to ensure a secure, consistent, and manageable deployment of Nasuni Local Edit across your organization. Implementing these measures helps maintain data protection, streamline administration, and optimize end-user experience.
Endpoint Management
To simplify administration across a large user base, we recommend deploying Nasuni Local Edit in advance using your organization’s endpoint management platform (such as Microsoft Intune, Jamf, or SCCM).
This approach ensures consistent configuration, streamlined updates, and reduced manual intervention.
Disk-Level Encryption
To protect sensitive data stored on endpoint devices, ensure that full disk encryption is enabled.
For example, macOS systems should have FileVault activated, and Windows systems should use BitLocker or an equivalent encryption solution.
Restricted Sources
As part of your deployment, configure Local Edit to open documents only from trusted, approved sources.
This restriction helps prevent unauthorized access and mitigates the risk of data exposure.
For detailed configuration instructions, refer to Configuration.
Troubleshooting
No option to Edit locally
If you do not see any “Edit locally” icon, even one that is disabled (light-grey) check with your IT administrator that your organization has access to the Local Edit feature.
If the icon is present for the supported formats but disabled, check with your IT administrator.
Installation Problems
If the Local Edit helper application does not install reach out to your IT administrator. There may be security policies or anti-virus programs that are preventing installation. Administrator privileges are required to install and uninstall the application.
Local Edit Not Running
If the application starts successfully it will be seen in the Windows System Tray or Mac Menu Bar.
Windows:
When the application is running, you’ll see a notification icon with Nasuni’s ‘N’ logo in the Taskbar system tray. If you don’t see it, it may be hidden — click the small upward arrow (caret) in the Taskbar corner to show hidden icons.
If the icon is not there either, the application may not be currently running.
Mac:
If the application is running, a notification icon featuring Nasuni’s “N” logo should appear in the Menu Bar.
Local Edit Not Opening
If the Local Edit application fails to download the file and launch the local desktop application the user may see a prompt to download the Local Edit application again. They may also see an error that the localedit: protocol is not configured.
If the application is running this may indicate an installation problem. You could retry installing the application or contact your IT Administrator.
Desktop Notifications
Desktop notifications provide insight into what steps are successful and which are failing. Nasuni strongly recommends users do not disable notifications as users will not see upload errors.
Check Local Edit Logs
There are application logs on the desktop that can provide more information about problems Local Edit encounters on the desktop and with communication with the server. This may assist a technical user, your IT administrator or Nasuni support with resolution.
To export the logs to your desktop click the application icon from the Windows Notification Bar or Mac Menu Bar. Chose Export logs.
Files Not Uploaded
Files are uploaded when the Local Edit application is running and the desktop is connected to the network.
When files are saved they Local Edit schedules that version for upload within a few seconds. If an upload fails it will be retried up to 4 times. Check the desktop notifications for errors. If a file is saved again the upload process restarts.
Refresh the Web Access file browser to see updated modification time of uploaded files. If the original file was updated by another user or process the new update is saved as a conflict file.
Files will only be uploaded with 36 hours of opening from the web app. After this time the file needs to be reopened through Local Edit.
Recover Files that Didn’t Upload
Files are uploaded when the desktop is connected to the network. If an upload fails it is retried up to 4 times.
Files that fail to upload can be recovered via the Recent Files option of the application since they remain in the desktop cache for 14 days. (Files that are uploaded successfully remain for 5 days). Once the file is open save it in another location, such as the desktop, and upload to the target folder manually through the web application.
These recovered files can also be accessed from a user’s home folder under the hidden folder .localedit. (Enable view hidden files in order to see these hidden directories).
File and Data Locations
Windows
Files are downloaded to %UserProfile%\\.localedit (the folder is hidden)
Application data folder: %LocalAppData%\\Nasuni\\Local Edit
Database tracking files downloaded: %LocalAppData%\\Nasuni\\Local Edit\\trackedfiles.db
Logs: %LocalAppData%\\Nasuni\\Local Edit\\Logs
Temporary folder used to upload modified files: %LocalAppData%\\Nasuni\\Local Edit\\Temp