You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>BrickSuite Server lets another BrickSuite installation establish a secure connection to the computer that owns the authoritative workshop database. A connected Client can browse Host Workspaces, Storage used by Inventory, My Inventory, and Inventory History. Remote Inventory is read-only at this stage; adding, editing, moving, correcting, losing, or removing Inventory still requires using the Host computer.</p>
4
+
<p>BrickSuite Server lets another BrickSuite installation establish a secure connection to the computer that owns the authoritative workshop database. A connected Client can browse Host Workspaces, Storage used by Inventory, My Inventory, Inventory History, and Builds. Remote shared data is read-only at this stage; changes still require using the Host computer.</p>
5
5
<p>The Client chooses its Host Workspace independently. This does not change the Workspace selected in the Host computer's UI. The selection is remembered on the Client for that Host identity and validated again after reconnecting.</p>
6
-
<divclass="note"><b>Hybrid data:</b> operational Workspace, Storage, Inventory, and History data comes from the Host. Part and Color names and images continue to use the Client device's local Rebrickable catalog and image cache. Unknown local catalog items remain visible using Host fallback text.</div>
7
-
<p>Remote Builds and Collection workflows are not yet enabled in the application UI.</p>
6
+
<divclass="note"><b>Hybrid data:</b> operational Workspace, Storage, Inventory, History, Build requirements, allocations, Missing Parts, and Pulling state come from the Host. Part and Color names and images continue to use the Client device's local Rebrickable catalog and image cache. Unknown local catalog items remain visible using Host fallback text.</div>
7
+
<p>In <b>Builds</b>, a Client can view the Host Build list, immutable requirement snapshots, Host-calculated Missing Parts, and the current Pulling projection. Pulling is read-only: creating or editing Builds, allocating Inventory, recording pulls, reconciling pull lists, completing, cancelling, archiving, or disassembling a Build is not available remotely yet.</p>
8
+
<p>Remote Collection workflows are not yet enabled in the application UI.</p>
8
9
<h2>Security model</h2>
9
10
<p>Connections use <b>WSS/TLS</b>. Each Host generates its own persistent certificate and private key. The Client verifies its SHA-256 fingerprint. A separate access token authorizes the Client through a nonce-based HMAC-SHA-256 challenge response and is stored through the operating-system credential service.</p>
10
11
<divclass="note"><b>Verify before trusting.</b> Compare the Client fingerprint with the fingerprint shown directly in Server Settings on the Host computer. First-use acceptance without that comparison can trust the wrong computer.</div>
0 commit comments