Support

How to Share Dahua CCTV in DMSS

Sharing Dahua CCTV access should be deliberate. The owner should keep control of the recorder, while staff, family or managers receive only the live view, playback and notification access they genuinely need.

DMSS sharing

Dahua DMSS sharing concept showing owner phone access, recorder and cameras
Good sharing starts with a clear owner account, then named user access for family, staff or managers. Avoid leaving a whole site dependent on one shared installer login.

Access levels to think about

User type Typical access What to avoid
Business owner Full live view, playback, notification and device management. Losing ownership by letting an installer or staff member control the only account.
Manager Live view, playback and selected alerts. Giving system-level control unless needed.
Staff member Limited live view or selected camera access. Giving access to private areas, all recordings or admin settings.
Family member Live view or playback depending on the home safety purpose. Sharing one password across multiple phones.

Good sharing practice

  • Use named users where possible rather than one shared login.
  • Decide who owns the Dahua account before handover.
  • Give playback access only to people who need it.
  • Review app users when staff leave, property managers change or family roles change.
  • Test live view, playback and notifications on the recipient's phone before considering the job complete.

Handover checklist

  1. Confirm the recorder is online in DMSS.
  2. Confirm the owner account and recovery email/phone are correct.
  3. Add or share access to each user deliberately.
  4. Set camera, playback and notification permissions.
  5. Test access on Wi-Fi and mobile data.
  6. Record who has access and who can remove users later.

FAQ

  • Should every user share one DMSS login?

    No. Shared logins create handover and security problems. Named access is cleaner where the setup allows it.

  • Can I give someone live view but not playback?

    That is usually the better approach for staff or casual users who do not need full recording access.

  • What should I do when staff leave?

    Remove or review their DMSS access immediately and check whether any shared passwords need changing.

  • What should I record before changing any settings?

    For How to Share Dahua CCTV in DMSS, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.

  • Should I factory-reset the equipment while troubleshooting?

    Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.

  • How do I confirm the problem is genuinely fixed?

    Repeat the original test, then check the relevant local and remote paths separately. For an intermittent fault, monitor through the conditions that previously caused it.

  • What details should I send technical support?

    Send the order number if available, exact product models, firmware if known, screenshots or photos, precise error wording, failure times and a short list of completed checks.

  • Should I change several settings at once?

    No. Change one item, repeat the same test and record the result. Multiple simultaneous changes make it difficult to identify the fault or safely reverse the change.

Before you start

Record the exact model, version, error wording, affected item and last known working time. Photograph the current state and protect recordings, configuration and account ownership before making changes.

Step 1: Record the exact starting condition

Before changing How to Share Dahua CCTV in DMSS, reproduce one clear test and write down the affected device, channel or user, the exact error wording, and the last time it worked.

  • Photograph the current status or error.
  • Record the exact model and firmware or app version.
  • Note what changed immediately before the fault.
  • Protect recordings, account ownership and the current configuration.

Step 2: Follow the local path described above

Use the recorder, controller or device screen named in this guide before treating the phone app as the cause. Record the status you find before editing it.

  • Start at the local device where possible.
  • Use the exact channel, door, zone or user involved.
  • Compare it with one working equivalent.
  • Change one setting at a time.

Step 3: Correct the proven layer only

Keep power, cabling, storage, network, account and app checks separate. Correct only the layer that failed the controlled comparison.

  • Resolve physical power or cabling before software.
  • Prove local operation before remote access.
  • Keep owner and shared-user permissions separate.
  • Avoid reset, format or unbind options unless a backup and recovery plan exist.

Step 4: Repeat the original test and document it

Repeat the same test, then verify any local and remote outcomes separately. A saved setting or online icon is not enough on its own.

  • Record the successful test time.
  • Check the expected log, playback or hardware response.
  • Restart only when it is a safe and relevant proof.
  • Save the final screenshot with the site handover record.

Common mistakes

  • Changing several unrelated settings before repeating the original test.
  • Skipping the local device check and relying only on an app symptom.
  • Resetting, formatting or unbinding equipment without a backup and ownership record.
  • Escalating without the exact model, version, error text and test time.
Worked example

Compare one failing path with one working path

Situation: One device, channel or user failed while another comparable item still worked.

Solution used: The two paths were compared at the local device first, one meaningful difference was corrected, and the original test was repeated.

Why this was chosen: The comparison isolated the affected layer without disturbing the rest of the system.

Installation notes: The final status, screenshot and test time were added to the handover record.

Troubleshooting table

Symptom What to check What to do next
The local device also fails Power, cable, storage or local configuration Keep the test local and resolve the first failed layer before changing app or cloud settings.
Local operation works but the app fails Ownership, sharing permission, cloud status or remote network Keep the proven local setup and compare owner versus shared-user access on mobile data.
Only one channel, zone, door or user fails Item-specific schedule, permission, wiring or assignment Compare it side by side with one working item and change only the meaningful difference.
The fault started after another change Router, password, firmware, account, power or configuration change Document the last known working state and reverse only the relevant change where safe.
The fault is intermittent Exact time, logs, signal, load, power and environmental pattern Capture failure times and screenshots so support can correlate the event instead of guessing.

When to contact support

Contact SecurityWholesalers support when the local result, exact model, firmware or app version and one controlled test are documented but the fault remains. Send the order number if available, screenshots, exact failure time and the checks already completed.

Related support guides

Related buying guides

We make product support and ordering easy! Reach out to our help team :)
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Your cart email sent successfully :)