Support
How to Share HiLook App Access Without Sharing the Owner Password
Safe App Sharing
Summary
Follow the four stages below to diagnose another person needs HiLookVision or Hik-Connect access without receiving the owner login without losing evidence, configuration or device ownership.
Applies to
- HiLookVision and compatible Hik-Connect sharing workflows
- Owner and recipient with separate accounts
Difficulty and time
Difficulty: Easy
Estimated time: 10 to 25 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when another person needs HiLookVision or Hik-Connect access without receiving the owner login. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: a family member or staff user needs access, or a previous share is pending or missing permissions.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Confirm the true device owner account before deleting, unbinding or attempting a new claim.
Do not give every user the owner password
Shared owner credentials prevent clean offboarding and expose account-wide control. Use individual recipient accounts and least-privilege permissions.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Invitation is still pending
- Recipient used a different account or region
- Playback permission was not granted
- Installer account still owns the device
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: a family member or staff user needs access, or a previous share is pending or missing permissions.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Confirm the true device owner account before deleting, unbinding or attempting a new claim.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device. Do not change anything until the displayed state is recorded.
- Open HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm the device is bound to the real owner account and shows Online.
- Confirm the recipient has their own account in the same app/region.
- Review live view, playback, alarm and intercom permissions separately.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- From the owner account, select the recorder/device and open Share Device.
- Enter the recipient account, email, mobile or scan its supported QR path.
- Grant only required channels and permissions, then send the invitation.
- On the recipient phone, accept the invitation and refresh the device list.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Test the recipient can open only intended live channels.
- Test playback separately if it was granted.
- Confirm owner credentials were never entered on the recipient phone.
- Remove the share and confirm access stops as part of handover/offboarding planning.
Controlled support test
Situation: The reported symptom was: a family member or staff user needs access, or a previous share is pending or missing permissions.
Solution used: The current state was recorded in HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Hikvision NVR User Manual before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| a family member or staff user needs access, or a previous share is pending or missing permissions | share invitation not accepted, wrong recipient region/account, insufficient permissions or device bound to another owner | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when the owner can see the online device but a correctly identified recipient cannot receive or accept a share.
Send the order number if available, exact model, firmware or app version, screenshot of HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device, the failure time, and the result of the local proof test.
Related support guides
- HiLook Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- HiLook Buying Guide - Broader HiLook planning guide.
- NVR Buying Guide - Recorder planning guide.
Relevant product categories
- HiLook CCTV Products - HiLook products.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for share HiLook app access?
Start at HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for the device owner, recipient identity, Pending/Accepted state, selected channels and each permission toggle.
-
What must I avoid changing during the first check?
Shared owner credentials prevent clean offboarding and expose account-wide control. Use individual recipient accounts and least-privilege permissions.
-
How do I prove the correction worked?
Have the recipient sign in with their own account and test live view and any granted playback, then verify an ungranted function remains unavailable.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of HiLookVision/Hik-Connect app > device card > Share, Share Device or More > Share Device, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.