HQShare Manual | Share a LAN folder with role-based access
HQShare exposes one selected folder to the local network for temporary or long-running exchange of delivery packages, logs, screenshots, reports, and field materials.
Share a LAN folder with role-based access
Select a shared folder and account permissions so LAN users can preview common materials in the browser before downloading, uploading, or organizing files.
HQShare file sharing guide for shared folders, web login, document previews, file actions, user permissions, and Windows / Linux deployment.
Manual Snapshot
File sharing
Windows / Linux
Web login
Document preview
User permissions
Key Facts
Runs on: Windows desktop / Linux service
Three roles: Viewer · Operator · Manager
Material review: Preview before download
Choose by Goal
Choose the current goal to find the matching feature and configuration step.
I want the field to download installers and patches
Web
Recommended feature
Web login and file list
Why
After login, users can download files from the file list without moving packages through USB drives.
How
Drop files into the shared folder and have them log in from a browser.
I want to inspect a file before downloading it
Preview
Recommended feature
Browser file preview
Why
Images, PDFs, text, Markdown, CSV, and media can be checked directly in the browser.
How
Sign in with an account that has download permission and select Preview on a supported file.
I want the field to upload logs and reports
Actions
Recommended feature
File downloads, uploads, and package access
Why
Accounts with upload permission can send files in directly, so you don't chase materials.
How
Give field staff the operator role and they will see the upload action.
I want customers to view and download only, not delete
Permissions
Recommended feature
How to split users
Why
Built-in viewer, operator, and manager roles let you grant exactly what's needed.
How
Create a viewer account for the customer, opening only list and download.
I want a quick share on an engineering PC
Service
Recommended feature
Windows desktop operation and Linux systemd
Why
The desktop build runs as soon as you pick a folder, and can sit in the tray or auto-start.
How
Use the Windows desktop app to set the shared folder, port, and bind address, then start.
I want it running long-term on a Linux server
Service
Recommended feature
Windows desktop operation and Linux systemd
Why
Linux runs it as a systemd service with a fixed folder, port, and service account.
How
Install from the Linux service package and run under a dedicated hqshare user, not root.
I want to make sure the share is secure
Security
Recommended feature
Security hardening and vulnerability boundaries
Why
Path limits, filename checks, and password protection are built in, but still need a network boundary.
How
Share a dedicated folder, keep it on the LAN, change the initial manager password, and disable unused accounts.
Before You Start
HQShare exposes one selected folder to the local network for temporary or long-running exchange of delivery packages, logs, screenshots, reports, and field materials.
What it solves
Use HQShare when the site needs a controlled LAN entry for installers, patches, manuals, logs, screenshots, or reports. It is clearer than repeated removable-media transfer and better aligned with local-network delivery than public cloud drives.
What it should not replace
HQShare is not public cloud storage or object storage. Do not expose it directly to the Internet, do not share system roots, and do not place production secrets or long-term archives in a temporary shared folder.
Change before production
After first deployment, change the initial manager password, create role-based users, and confirm the shared folder, bind address, firewall, and port match the site network boundary.
Recommended setup order
Prepare the folder, choose the port and bind address, start the service, create users, then verify preview, download, upload, and permission boundaries.
Step 1: Prepare a dedicated shared folder
Use a folder such as D:\HQShare\Public or /srv/hqshare/public. Avoid sharing the desktop, a system drive root, or real customer data roots.
Step 2: Choose a port and bind address
The default port is 5995. Desktop sharing may bind to 0.0.0.0; production deployments should bind to a fixed internal IP and firewall the allowed source segments.
Step 3: Start and verify web login
Open http://server-ip:5995/ in a browser. Web access starts from login, and the file list appears only after authentication.
Step 4: Configure users and roles
Split users into read-only visitors, operators, and managers. Give upload only to users who need it, and keep delete/user-management permissions for maintainers.
Step 5: Confirm the runtime mode
Use desktop mode on Windows engineering workstations and Linux systemd service on IPCs, gateways, or servers. Fix the folder, port, and bind address before production use.
