Support
Access Control Backup, Handover and Administrator Checklist
System Handover
Summary
Follow the four stages below to diagnose an access-control system is being commissioned, transferred or prepared for support without losing evidence, configuration or device ownership.
Applies to
- New and existing access-control systems
- Installer-to-owner or manager handover
Difficulty and time
Difficulty: Advanced
Estimated time: 45 to 120 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 access-control system is being commissioned, transferred or prepared for support. 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: ownership, admin access, backups or door documentation is incomplete.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Keep the previous known-good backup and never include passwords in an unprotected handover document.
A backup is only useful if ownership and recovery are clear
Protect personal access records and administrator credentials. Use secure storage and the site retention/privacy policy.
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
- Only installer has administrator access
- No current backup exists
- Door/controller names are unclear
- Licences or cloud ownership are undocumented
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: ownership, admin access, backups or door documentation is incomplete.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Keep the previous known-good backup and never include passwords in an unprotected handover document.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management. Do not change anything until the displayed state is recorded.
- Open Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management. Menu wording can vary by model and firmware; use the nearest equivalent label.
- List every controller, door, reader, lock, PSU and network identity.
- Identify owner administrator accounts and remove shared/default credentials.
- Review current people, access levels, schedules, licences and integrations.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Export a dated configuration/database backup using the supported method.
- Create named owner administrators and store recovery details securely.
- Produce a door schedule/permissions matrix and label controller/door mappings.
- Document fire/egress interfaces, battery service dates and support escalation contacts.
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.
- Restore-test or validate the backup according to vendor guidance.
- Have the owner perform login, user change and transaction-search tasks.
- Test representative doors, REX and event reporting.
- Sign off known limitations, outstanding works and offboarding procedure.
Controlled support test
Situation: The reported symptom was: ownership, admin access, backups or door documentation is incomplete.
Solution used: The current state was recorded in Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management, 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 Access Control Terminal 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 |
|---|---|---|
| ownership, admin access, backups or door documentation is incomplete | installer-only admin, missing database backup, undocumented doors/schedules or licences tied to an unknown account | 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 supported backup cannot be verified, ownership/licensing is unclear or emergency interfaces need specialist sign-off.
Send the order number if available, exact model, firmware or app version, screenshot of Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management, the failure time, and the result of the local proof test.
Related support guides
- Access Control Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- Access Control Buying Guide - Door hardware, credentials and system-planning guide.
Relevant product categories
- Access Control Products - Controllers, readers, locks and credentials.
- Door Strikes - Electric strike hardware.
- Maglocks - Electromagnetic locking hardware.
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 access control handover checklist?
Start at Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management. 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 backup/export status, named administrator accounts, device/door inventory, licence owner and last successful synchronisation.
-
What must I avoid changing during the first check?
Protect personal access records and administrator credentials. Use secure storage and the site retention/privacy policy.
-
How do I prove the correction worked?
The owner should log in, locate a door/event, add and revoke a test user, and identify the recoverable backup and support record.
-
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 Access-control client > System/Tool > Backup or Export, then User/Account Management and Device Management, 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.