Getting started / hosted and local paths reviewed in UI22

Get started: hosted demo or local hub

Choose the right entry route without switching projects or overwriting saved work.

Wavelink can be opened from the existing hosted demonstration or from a separately installed local Windows hub. These are different deployments. Opening the hosted demo does not require installing a second Windows hub, and a separately installed hub does not automatically share the hosted project's accounts or records.

Open the public demonstration

For the configured AJ demonstration, open https://demo.mywavelink.com/. When Gateway G01 has DEMO_PUBLIC_ENTRY=YES, a fresh browser enters using the configured non-administrator demo guest. This is the visitor route, not an administrator-account selector. JavaScript and browser storage must be available. Public entry does not turn the guest into a read-only account: visitors share its existing permissions and can change fictional records where permitted.

The public handoff does not overwrite an existing saved workspace. An existing signed-in account may be retained. A signed-out, different-project or unrecognised saved workspace can require normal sign-in instead. Use a separate private/incognito window to check a new visitor's experience, not browser-storage clearing.

Sign in as administrator or named staff

Open Normal staff entry: /__demo/login on the hosted demo. This is the outer access-password screen; use the configured demonstration access password there, not your personal Wavelink account password. Successful entry admits the browser to Wavelink. Sign in inside Wavelink using your own User ID and password. The gate password alone does not choose your Administrator account or grant that role.

If the workspace is already signed in as the guest, finish or preserve its unsent work, close any open handover or other operational form, then choose Workspace menu → Sign out. Sign in on the displayed Wavelink account form using your named administrator credentials. Merely reopening the staff URL does not replace a saved guest session. A separate browser profile or fresh private window can keep administrator work separate from public-demo testing.

Sign out is deliberately blocked while recognised drafts, pending changes or active saves need attention. Resolve those items using their normal save/synchronisation controls. Do not clear site data, delete local records or reset the project to switch accounts. Do not put any passwords into a bookmark, GitHub file or support screenshot.

Public entry deliberately refuses an Administrator guest. Keep a separate working named administrator account, and use Technician or Supervisor for the public guest with explicitly reviewed module/department access. Changing DEMO_GUEST_PASSWORD in hosting settings does not change that guest's actual account password: the values must match. Do not re-enable demo initialization to repair sign-in.

Use the local Windows hub instead

This section applies only to the separately installed local hub, not the hosted demo. Use the approved Windows installer on the hub PC. The shipped installer path requires an internet connection for setup; it is not the planned self-contained offline installer. Open Wavelink Admin, select the intended project and use its existing administrator account. Create a first administrator only for a genuinely new project.

In Settings, review the hub name and defaults. Under Users & access, add each team member's named account. In Hub & phones, select the team-facing PC address, use Save address, then Start server. Share the saved address or QR on the approved local network. Keep that PC running and connected while the team needs to share or synchronise work. An IP address shown by the app is not proof a phone can reach it; verify the actual network.

Team members join the same existing hub rather than installing another one. Connect to the approved network, open the administrator-provided address and sign in with the account belonging to that project. An offline browser cache is not vessel/cloud synchronisation or a complete project backup.

Check your account and work before operations

Check the signed-in name, project and permissions in Workspace menu. Administrator, Supervisor and Technician roles are distinct from selected module capabilities, departments and particular review assignments. A missing workspace or action is not permission to use a colleague's login. Ask a named administrator to review effective access; assigned checklist review is separate from the person's general role.

Use fictional practice records to verify sign-in, saving, synchronisation and any required approvals. Home provides Saved local work and, for eligible accounts, separate-log-window review. Server-saved handover drafts are distinct from unsaved in-tab wording. Save them deliberately before leaving. Opening Help, joining a project or using a shared demo account does not approve procedures, authorise equipment operation or provide independent-person attribution.

This browser Help update changes neither the working gateway nor its configuration. Preserve the current domain, persistent disk, required access password, matching guest credentials and INITIALISE_FICTIONAL_DEMO=NO on the existing demo. Deployment, security, device and recovery acceptance remain separate checks.