Support

AX PRO User, Installer and New-Owner Handover Checklist

This guide addresses an AX PRO alarm is being handed from installer to owner or site manager in the order technical support would test it: preserve what matters, open the correct screen, correct the proven cause and verify the result.

Alarm Handover

Summary

Follow the four stages below to diagnose an AX PRO alarm is being handed from installer to owner or site manager without losing evidence, configuration or device ownership.

Applies to

  • New and existing AX PRO systems
  • Installer-to-owner and tenancy handovers

Difficulty and time

Difficulty: Advanced

Estimated time: 45 to 90 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 an AX PRO alarm is being handed from installer to owner or site manager. 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: the owner lacks clear app ownership, user roles, recovery details or a tested operating procedure.
  • Photograph the current status, error text, wiring or timeline as applicable.
  • Record the last known working time and anything changed immediately before the fault.
  • Export or record current system configuration and ownership before changing roles.
Important

Do not leave the owner dependent on an unknown installer account

Ownership, monitoring and emergency contacts must be explicit. Never publish user codes or recovery credentials in an unsecured document.

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

  • Installer account still owns the system
  • Users share one code/account
  • Zone labels are unclear
  • Alarm communications were never acceptance-tested

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: the owner lacks clear app ownership, user roles, recovery details or a tested operating procedure.
  • Note whether every device or user is affected, or only one.
  • Compare one working path with the failing path if a comparison exists.
  • Export or record current system configuration and ownership before changing roles.

Step 2: Open the correct screen and inspect the evidence

The primary diagnostic location is Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History. Do not change anything until the displayed state is recorded.

  • Open Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History. Menu wording can vary by model and firmware; use the nearest equivalent label.
  • Identify the bound owner, installer/admin and every daily user.
  • Review zones, areas, entry/exit delays, communications and current bypasses/faults.
  • Confirm monitoring details and testing/maintenance contacts where applicable.

Step 3: Correct only the cause you proved

Use the matching correction below. Make one change, save it, then repeat the same test.

  • Move daily users to individual accounts/codes with least required rights.
  • Securely document owner recovery, installer access and offboarding steps.
  • Label zones clearly and record batteries, communications and service dates.
  • Remove obsolete users and resolve unintended bypasses before sign-off.

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.

  • Have the owner arm/disarm and interpret one fault.
  • Run an authorised walk test and confirm zone labels.
  • Confirm intended alarm/fault pushes and any monitoring response.
  • Provide a dated handover record without exposing passwords in plain text.
Worked example

Controlled support test

Situation: The reported symptom was: the owner lacks clear app ownership, user roles, recovery details or a tested operating procedure.

Solution used: The current state was recorded in Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History, 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 AX PRO 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
the owner lacks clear app ownership, user roles, recovery details or a tested operating procedure installer-only ownership, shared user codes, unclear zones, untested notifications or undocumented monitoring 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 ownership cannot be transferred cleanly, monitoring details conflict or unexplained faults/bypasses remain.

Send the order number if available, exact model, firmware or app version, screenshot of Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History, the failure time, and the result of the local proof test.

Related support guides

Related buying guides

Relevant product categories

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 AX PRO handover checklist?

    Start at Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History. 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 bound owner, user roles/codes, named zones/areas, current faults/bypasses and communications status.

  • What must I avoid changing during the first check?

    Ownership, monitoring and emergency contacts must be explicit. Never publish user codes or recovery credentials in an unsecured document.

  • How do I prove the correction worked?

    The owner should independently arm/disarm, identify a zone fault, receive a test notification and explain who to contact.

  • 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 Hik-Connect > AX PRO > Settings > User/Share, plus panel User Management and Fault/Event History, 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.

Further Reading
Guide Page Hikvision AX PRO Alarm Support Overview Overview Guide Page Hikvision Support Guides Guide Page HiLook Support 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.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

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.
Send Cart Email
Your cart email sent successfully :)