Manual

HQShare Manual | Share a LAN folder with role-based access

HQShare exposes one selected folder to the local network for temporary or long-running file exchange. It is independent from HQControl and is intended for delivery packages, log collection, screenshots, reports, and field collaboration.

Select a shared directory, configure the port, login accounts, and role permissions, then allow LAN users to download, upload, and organize files within their authorized scope. HQShare is deployed and upgraded independently from HQControl.

HQShare standalone file sharing guide. Configure the shared folder, port, users, web login, file actions, Windows desktop operation, and Linux service deployment in order.

Manual Snapshot

Standalone
Windows / Linux
Web login
User permissions
File actions

Key Facts

Runs on: Windows desktop / Linux service
Three roles: Viewer · Operator · Manager
Access: Visible only after web login

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 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

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, object storage, or an HQControl file module. 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 downloads, uploads, and permissions from a browser.

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.