Product: Mingcedar Share SHARE

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

Mingcedar Share exposes one selected folder to the local network for temporary or long-running exchange of delivery packages, logs, screenshots, reports, and field materials.

Published 2026-10-25T12:48:42.537770011Z Updated 2026-10-25T12:48:42.53776919Z

<div class="manual-doc-article"><h1 id="share-a-lan-folder-with-role-based-access">Share a LAN folder with role-based access</h1>

<p>Share a folder with LAN users for browser previews, downloads, uploads, and file management by role.</p>

<p>Mingcedar Share file sharing guide for shared folders, web login, document previews, file actions, user permissions, and Windows / macOS / Linux deployment.</p>

</blockquote>

<h2 id="manual-snapshot">Manual Snapshot</h2>

<ul>

<li>File sharing</li>

<li>Windows / macOS / Linux</li>

<li>Web login</li>

<li>Document preview</li>

<li>User permissions</li>

</ul>

<h2 id="key-facts">Key Facts</h2>

<ul>

<li><strong>Runs on:</strong> Windows / macOS desktop · Linux service</li>

<li><strong>Three roles:</strong> Viewer · Operator · Manager</li>

<li><strong>Material review:</strong> Preview before download</li>

</ul>

<h2 id="choose-by-goal">Choose by Goal</h2>

<p>Choose a goal to find its settings.</p>

<h3>I want the field to download installers and patches</h3>

<div><dt>Recommended feature</dt><dd>Web login and file list</dd></div>

<div><dt>Why</dt><dd>Users can download shared files after login.</dd></div>

<div><dt>How</dt><dd>Drop files into the shared folder and have them log in from a browser.</dd></div>

</dl>

</article>

<h3>I want to inspect a file before downloading it</h3>

<span class="doc-goal-cat">Preview</span>

<div><dt>Recommended feature</dt><dd>Browser file preview</dd></div>

<div><dt>Why</dt><dd>Images, PDFs, text, Markdown, CSV, and media can be checked directly in the browser.</dd></div>

<div><dt>How</dt><dd>Sign in with an account that has download permission and select Preview on a supported file.</dd></div>

</dl>

</article>

<h3>I want the field to upload logs and reports</h3>

<span class="doc-goal-cat">Actions</span>

<div><dt>Recommended feature</dt><dd>Preview, download, and upload files</dd></div>

<div><dt>Why</dt><dd>Accounts with upload permission can submit materials to one shared folder.</dd></div>

<div><dt>How</dt><dd>Give field staff the operator role and they will see the upload action.</dd></div>

</dl>

</article>

<h3>I want customers to view and download only, not delete</h3>

<span class="doc-goal-cat">Permissions</span>

<div><dt>Recommended feature</dt><dd>How to split users</dd></div>

<div><dt>Why</dt><dd>Built-in Viewer, Operator, and Manager roles provide three permission groups.</dd></div>

<div><dt>How</dt><dd>Create a viewer account for the customer, opening only list and download.</dd></div>

</dl>

</article>

<h3>I want a quick share on an engineering PC</h3>

<span class="doc-goal-cat">Service</span>

<div><dt>Recommended feature</dt><dd>Windows / macOS desktop and Linux systemd</dd></div>

<div><dt>Why</dt><dd>Select the folder and configure accounts before starting sharing. Windows supports the system tray; macOS supports the menu bar and launch at login.</dd></div>

<div><dt>How</dt><dd>Use the Windows or macOS desktop app to set the shared folder, port, and bind address, then start.</dd></div>

</dl>

</article>

<h3>I want it running long-term on a Linux server</h3>

<span class="doc-goal-cat">Service</span>

<div><dt>Recommended feature</dt><dd>Windows / macOS desktop and Linux systemd</dd></div>

<div><dt>Why</dt><dd>Linux runs it as a systemd service with a fixed folder, port, and service account.</dd></div>

<div><dt>How</dt><dd>Install from the Linux service package and run under a dedicated hqshare user, not root.</dd></div>

</dl>

</article>

<h3>I want to check who can access the share</h3>

<span class="doc-goal-cat">Security</span>

<div><dt>Recommended feature</dt><dd>Access protection and deployment boundaries</dd></div>

<div><dt>Why</dt><dd>The shared folder, account roles, and allowed network sources must be planned together.</dd></div>

<div><dt>How</dt><dd>Share a dedicated folder, keep access on the LAN, change the initial manager password, and disable unused accounts.</dd></div>

</dl>

</article>

</div>

<h2 id="before-you-start">Before You Start</h2>

<p>Mingcedar Share exposes one selected folder to the local network for temporary or long-running exchange of delivery packages, logs, screenshots, reports, and field materials.</p>

<h3 id="preface-item-1">Sharing and file actions</h3>

<p>Select one host folder and configure accounts. Authorized users can get installers, patches, and manuals or upload logs and reports through a browser on the local network.</p>

</article>

<h3 id="preface-item-2">Folder and network scope</h3>

<p>Mingcedar Share serves one host folder on the local network. It has no built-in public sharing links or cloud sync. Restrict network access, avoid sharing system roots, and keep production secrets outside the shared folder.</p>

</article>

<h3 id="preface-item-3">Change before production</h3>

<p>Change the initial manager password, create role-based accounts, and check the folder, bind address, port, and firewall.</p>

</article>

</div>

<h2 id="tutorial">Recommended setup order</h2>

Prepare a dedicated folder and start with local access. Then change the manager password, assign accounts, choose the LAN access scope, and verify file actions and permissions.

<h3>Step 1: Prepare a dedicated shared folder</h3>

<p>Use a folder such as <code>D:\HQShare\Public</code> or <code>/srv/hqshare/public</code>. Avoid sharing the desktop, a system drive root, or real customer data roots.</p>

</article>

<h3>Step 2: Choose a port and bind address</h3>

<p>The default port is 5995. For initial setup, bind to <code>127.0.0.1</code>. Change the manager password before selecting an internal IP and allowing the required source networks through the firewall.</p>

</article>

<h3>Step 3: Start and verify web login</h3>

<p>During initial setup, open <code>http://127.0.0.1:5995/</code> locally and sign in. After configuring accounts, use the actual bound LAN address and port for access.</p>

</article>

<h3>Step 4: Configure users and roles</h3>

<p>Change the initial manager password on the host desktop or CLI, then create Viewer, Operator, or Manager accounts. Viewer can browse, preview, and download; Operator adds upload, folder creation, and rename; Manager adds deletion.</p>

</article>

<h3>Step 5: Confirm the runtime mode</h3>

<p>Use desktop mode on Windows or macOS computers and Linux systemd service on IPCs, gateways, or servers. Fix the folder, port, and bind address before production use.</p>

</article>

</div></div>