Skip to content
VoidSenses

Set up, understand access, and find the right next step.

Start with the exact product and approved configuration. An organization owner or administrator creates the site, enrolls supported nodes or devices, assigns camera groups and invites members. A member sees only assigned cameras and explicitly opens an authorized view.

Use an up-to-date desktop Chromium browser for the currently exercised workflow; a broad browser and mobile support matrix is not yet qualified. Allow requested private-network access only on the intended trusted network. Do not bypass certificate warnings. A VPN or private route can affect Local reachability; Local is not a physical-location guarantee.

Install and enroll VoidBridge

Who can help: Account owner or organization administrator, with the computer owner

  1. Confirm the exact RTSP camera stream and desktop are in the agreed scope. The desktop must stay powered and connected. Bridge does not record or supply playback or AI.
  2. Open the console download page with an eligible account. Choose Windows x64, Linux AppImage or Linux Debian; verify the filename, version and SHA-256 below before installation. There is no qualified public Mac package.
  3. Install on the chosen computer and sign in. Add a camera manually or with the supplied import template; enter camera credentials only in the trusted desktop app. Prefer a dedicated camera account with only the required permissions.
  4. If needed, explicitly select Prepare secure background startup at sign-in, add a camera, then enable Launch VoidBridge automatically without opening the app window. Windows uses your login item; Linux requires a graphical user session and an unlocked supported secure credential store.
  5. Assign the Bridge to the intended site, give the camera a useful name, and grant the team the right group and live access. Open one authorized view deliberately to verify the setup. Upgrades require installing the new package; there is no automatic updater.

Prepare and enroll VoidEdge

Who can help: Organization administrator and the agreed installation operator

  1. Arrange an exact-camera, Linux computer and storage review first. There is no general customer installer or customer-qualified appliance announced. Keep the existing recorder in service during evaluation.
  2. The approved operator installs the reviewed package on its own computer and disk, configures qualified H.264 RTSP streams and recording limits, and verifies local recording and storage health. Do not install the Edge package on a camera or assume an arbitrary NVR can host it.
  3. The operator creates the recorder identity and public certificate request locally. In the console VoidEdge page, an authorized administrator opens Authorize a new recorder and supplies the public request and intended camera identities.
  4. Transfer the one-time enrollment grant to the approved operator through the agreed private channel. The private key and camera passwords stay on the appliance. Never paste them into a public inquiry.
  5. Confirm the recorder and intended cameras appear, assign group access, check health, and open a permitted live view and finalized recording. Person search needs separate configuration, an explicit grant and a retained index; a subscription alone does not enable it.

Plan resident Connector installation

Who can help: Organization administrator and a qualified camera installer

  1. Record the manufacturer, exact model, firmware and camera application platform. The current evaluated resident route is Hanwha QNV-C8011R. A vendor name, ONVIF label or another model is not proof of support; VIVOTEK resident installation remains pending qualification.
  2. Agree the package, vendor installation rights and supported features before installation. There is no universal public Connector installer. Use the approved vendor workflow only for the reviewed configuration.
  3. The installer enrolls the camera installation through its scoped workflow and names the camera in the intended account. Keep installation grants, certificates and camera credentials out of public forms.
  4. Confirm camera permissions and supported capabilities before opening a view. SD playback needs a suitable card, camera recording configuration and available recordings. Activity search needs collected metadata; it cannot search events that were never indexed.

Invite a team member or join a team

Who can help: Organization administrator sends; the intended recipient accepts

  1. In Account settings, an administrator creates or reviews the organization, camera groups and member permissions. Invite the intended email with its role, groups and LAN-only or LAN-and-Cloud live access.
  2. An invitation link is sensitive. Share it privately with its intended recipient. Delivery status describes the attempt; it does not establish inbox receipt. Ask the administrator for a replacement if the link expires or is revoked.
  3. Open the invitation, sign in or create the intended account, then choose Join organization. Signing up by itself neither accepts the invitation nor starts a camera stream.
  4. Viewers see only assigned cameras and do not administer billing or members. Power users have permitted device actions; administrators manage team permissions. If no cameras appear, ask the organization administrator to check membership and group assignment.

Understand Local, Cloud and Unavailable

Who can help: Viewer checks the connection; administrator checks grants; network operator checks reachability

  1. Local means authorized media takes a direct private-network route where the product supports it. This can include a routed network or VPN and does not prove the viewer is in the same building. Cloud authentication still applies.
  2. Cloud means an authorized remote media route is in use. The account needs cloud live permission. A viewer with LAN-only permission cannot use cloud fallback.
  3. Unavailable is a state to investigate, not proof the camera or recordings have failed. Check sign-in, selected camera, group assignment, device status and connectivity. The displayed reason determines the next step.
  4. If the browser requests local-network permission, grant it only for your trusted VoidSenses site when you intend local viewing. If previously denied, review that site permission in the browser. The network operator can check private-network/VPN reachability; the administrator can check LAN/cloud grants.
  5. Do not expose a camera port to the internet to clear an error. If local viewing fails, permitted cloud fallback may be available; LAN-only users need the local route restored or an explicit administrator permission change.

Find a missing camera or unavailable feature

Who can help: Organization administrator; installer for camera configuration

  1. Confirm you are signed into the intended account and organization. Ask an administrator to confirm the camera belongs to the organization and is assigned to your group. A camera label does not grant access.
  2. For an offline device, the installation owner checks power, the camera network, the desktop or recorder process and its cloud connection. Health observations are not proof that video was recorded and are not emergency monitoring.
  3. For playback, select the correct camera and time interval. Bridge has no recording. Edge needs finalized retained segments. Resident Connector needs supported camera storage and recorded material; expired or absent video cannot be recovered by changing a website filter.
  4. For search, confirm the selected product actually supports it, the required grant is current and metadata was collected for the chosen interval. Human review is needed; detection may miss events.
  5. After a role or group change, refresh the console. If access remains denied, ask the administrator to review the current grant instead of repeatedly retrying the stream.

Choose a browser and recover interrupted updates

Who can help: Viewer; desktop administrator when browser policies are managed

  1. Use an up-to-date desktop Chromium browser for the currently exercised web workflow. A broad Chrome, Edge, Firefox, Safari or mobile device support matrix is not yet qualified; verify the exact browser and OS during the scoped setup.
  2. Media support also depends on the camera codec and product. H.265 / HEVC playback is conditional on browser capability and the selected integration. A browser that opens the console may still reject a particular stream format.
  3. When a page or update fails to load, use Try again, then Reload page if needed. Check your connection first. Keep a private invitation link available before deliberately clearing site data; do not clear it as the first troubleshooting step.
  4. Use browser zoom, keyboard Tab and Shift+Tab, and labeled buttons. On narrow screens use the navigation menu. If an action is inaccessible or a managed permission is blocked, record the browser version and non-sensitive error wording for support.

Review billing and cancellation

Who can help: Account owner or organization administrator with billing access

  1. Open Subscription in the console to review the account’s current plan and billing state. Organization viewers and power users ask an administrator to handle billing.
  2. Use the displayed billing portal or cancellation action to manage the active subscription. Read and confirm the effective date shown for your subscription. A public product comparison does not create a subscription or purchase a hardware configuration.
  3. Live-view subscriptions do not automatically grant Edge AI, hardware, installation or a business pilot. Those depend on the separate agreed scope.
  4. Standard website subscription charges have a 15-calendar-day full-refund request window. Email the business contact with your account email and invoice reference; refunds are handled manually. Manage billing cancels renewal at period end without automatically prorating a refund. Read the complete Terms for the policy and applicable-law rights. Cancellation does not itself delete account data or local recordings.

Prepare a safe support request

Who can help: Your organization administrator or agreed support contact

  1. First route account/group issues to your organization administrator, camera/power/storage issues to the installation owner, and routing or browser policies to the network/desktop operator.
  2. For a product question, use the contact page and its available fallback. Online inquiry delivery can be unavailable; do not interpret a failed or uncertain submission as received. No response-time commitment or emergency response is announced.
  3. Inquiries normally leave the active business mailbox 15 days after resolution, subject to ongoing business, billing, dispute and legal needs. Privacy requests use a 15-day handling target after identity verification. Logs, backups and downloaded/local recordings have distinct limits; read the Privacy Policy before assuming every copy is automatically erased.
  4. Share only the product, installed version, general model/firmware, browser/OS, approximate time with timezone, and a sanitized description. Omit footage, camera URLs, private network details, account passwords, invitation links and enrollment material.
  5. If a screenshot is necessary through an agreed private channel, review it for people, camera labels, location details and tokens first. Public help does not replace your organization’s incident, retention or emergency procedures.

Verified VoidBridge 0.6.2 downloads

Reviewed October 14, 2026. Confirm the current approved version in the official download catalog before installation.

Use the SHA-256 values displayed above. On Linux run sha256sum <downloaded-file>; in Windows PowerShell use Get-FileHash <downloaded-file> -Algorithm SHA256. Compare every character to the checksum for that exact filename before opening the installer. A checksum match confirms the advertised bytes, not camera or site qualification.

Choose your next step