Office & remote access

One office workspace.
The right people connected.

Run the business workspace on the office PC. Add optional HTTPS access for authorised staff on the office network, with company VPN access where your network is configured for it.

Optional setup · Local-only by default

Office PC

VELQRA host & business records

Trusted HTTPSOwner pairing + staff login
Office staffBrowser or remote desktop mode
Home or another locationCompany VPN & office address

Local PC

Use VELQRA directly on the computer where it is installed. Business records stay in that local workspace.

Default

Office sharing

A separate HTTPS gateway exposes the workspace at your configured office address. The private app backend remains on loopback.

Requires setup

Remote desktop mode

A second VELQRA desktop window can point at the office HTTPS origin rather than starting another independent business database.

Requires office gateway

What needs to be ready

Connect the office deliberately.

The app does not automatically create DNS, certificates, firewall rules or a VPN. The office computer and network need to be prepared.

  1. Prepare the host PC

    Complete company/owner setup. Choose the PC that owns the business workspace and keep its records backed up.

  2. Choose the office address

    Use a stable office DNS name, a specific network-interface IP and the chosen HTTPS sharing port.

  3. Provide trusted HTTPS

    Configure a valid certificate and private key for the office hostname. Client Windows devices and browsers must trust the issuing authority.

  4. Configure office sharing

    Set the host profile’s office connection mode, bind address, port, office URL and certificate paths, then restart the app.

  5. Allow the intended network

    Restrict the selected inbound TCP port to the intended office/VPN network. Do not expose the private loopback backend port.

  6. Pair and sign in

    Open the office HTTPS address on the other device. The owner authorises that browser, then the staff member signs in with their own account.

How access behaves

People, sessions
and the office PC.

Does pairing give access to every business record?

No. Pairing allows the browser to reach the office workspace. The person still signs in, and the backend applies their staff and company permissions.

How long does pairing last?

Browser pairing lasts up to 12 hours. Stopping and restarting the office host revokes pairings, so users need to pair and sign in again. Saved business records remain.

Can staff connect from home?

Use a managed company VPN with working routing, DNS, firewall policy and trusted HTTPS. The implementation does not provide an automatic internet relay or certify your home/office network.

Can I close the office app window?

Enable the owner’s Keep the office host running after closing the window option. The host remains in the system tray. Use Stop office host and exit to stop it explicitly.

Does it start automatically after a restart?

The installed edition has an opt-in start-at-Windows-sign-in path. It is not a boot service and does not host before Windows sign-in. Sleep, shutdown and sign-out interrupt access.

Can clients use the same office workspace?

Eligible trade presets include a client portal for linked records made available to that client. This is distinct from unrestricted staff access. Portal availability depends on the selected trade and configuration.

What has been tested?

Local integration tests passed real HTTPS pairing, login, save/read, staff/company isolation, expiry and restart invalidation. A second physical office PC, trusted production certificate and home VPN still need testing on the actual deployment.