Credential and badge events
AuthDenied access, expired credentials, anti-passback, schedule mismatch, and cardholder state.
Open credential event flowCommand page
Local filter active on this page
Controls active. Showing 10 of 10 guide entries.
Security systems troubleshooting
Security / Access Control / CCTV troubleshooting destination for field diagnostics and controlled escalation.
Route quickly to the right checks for access hardware, cameras, VMS/NVR, PoE, and supporting network faults while keeping secure conditions intact.
Guide index
Filterable entries
- Door won’t unlock: maglock, strike, REX, and controller command path
- Badge denied: cardholder rights, schedules, and anti-passback checks
- Reader offline: reader power, bus, and controller communication checks
- Forced/Held door alarms: contact status, timing profiles, and REX validation
- Camera offline: power, link, IP reachability, and camera service state
- No video: stream negotiation, codec mismatch, and client decode path
- PTZ control issues: command channel, permissions, and control lockouts
- NVR/VMS issues: ingest, recording state, storage, and licensing checks
- PoE/Network faults: switch budgets, VLAN path, and endpoint addressing
- Repeated alarms: event thresholds, debounce windows, and escalation policy
Decision flows
- Access denied path: credential → policy → reader/controller state.
- Door event path: forced/held → contact timing → site escalation.
- Video outage path: camera power/link → VMS ingest → storage/retention.
Access control / CCTV lanes
Choose the correct secure troubleshooting lane before deep triage.
Route issues quickly across credentialing, door hardware, controller, camera, and recording paths without crossing security boundaries.
Reader and REX devices
Field I/OReader power, LED/buzzer behavior, Wiegand/OSDP path, request-to-exit trigger, and tamper status.
Open reader/REX flowDoors plus maglock/strike behavior
HardwareDoor position contact, unlock/lock timing, fail-safe vs fail-secure behavior, and mechanical restore.
Open door hardware flowController or panel connectivity
Core controlPanel heartbeat, bus health, upstream session state, and multi-door impact footprint.
Open controller/panel flowPower and communications path
DependencyPoE budget, PSU/backup state, switch port condition, VLAN/policy path, and link continuity.
Open power/comms flowCameras and live video
Live feedOffline camera state, stream registration, channel mapping, and live-view availability.
Open live video flowImage quality and PTZ behavior
OpticsFocus/exposure drift, IR/night mode state, latency artifacts, and PTZ control response.
Open image/PTZ flowRecording or VMS/NVR history
RetentionTimeline gaps, retention policy effect, storage health, and event-to-video correlation.
Open NVR/VMS recording flowCritical escalation routes
Route nowCredential and badge events troubleshooting flow
Reader and REX troubleshooting flow
Door, maglock, and strike troubleshooting flow
Controller and panel connectivity troubleshooting flow
Power, communications, and PoE/network troubleshooting flow
Cameras and live video troubleshooting flow
Image quality and PTZ troubleshooting flow
NVR/VMS recording history troubleshooting flow
Security guide index
Open the correct Access Control / CCTV troubleshooting workflow fast.
Browse by issue, then jump directly into the detailed decision flow. Entries are operationally scoped for field and NOC use.
-
Door won’t unlock or lock · Maglock or strike faults
Trace credential-to-output behavior when door state does not follow command, including lock release and relock path checks.
door lock strike -
Badge denied
Validate denied-event context against credential status, time policy, and door profile before escalating entitlement changes.
badge reader door -
Reader offline
Follow reader heartbeat and event continuity checks to isolate field wiring, addressing, or upstream path disruption.
reader controller comms -
Forced or held door · Repeated alarms
Correlate door-position signals and alarm cycles to distinguish persistent access risk from sensor-state instability.
door repeated alarm reader -
REX issues
Check request-to-exit trigger path where exit action is delayed, missing, or unexpectedly sustained.
REX door lock -
Controller or panel offline
Use panel health and controller status sequence to confirm whether outage is local device, bus segment, or upstream dependency.
controller panel reader -
Power or communications failure
Validate supply continuity and communications path integrity between field endpoints and supervisory systems.
power controller comms -
Camera offline · Network or PoE faults
Resolve endpoint loss by verifying link state, PoE delivery, and reachable camera services in the expected segment.
camera PoE network -
No video · Poor image · PTZ failure
Run channel, stream, optics, and PTZ command-path checks when visual output is missing, degraded, or unresponsive.
camera PTZ video -
NVR or VMS recording issues
Confirm recording workflow from ingest to retention when clips are missing, delayed, or not searchable as expected.
recording NVR VMS
Tool-guidance quick links
Use these checks alongside the decision flows to validate documented expectations.
Security category operations
Access Control / CCTV: tool guidance with strict authorization boundaries
Use these checks to triage safely, document clearly, and route incidents to the correct security, facilities, network, or authorized vendor path without enabling bypass behavior.
Security and authorization rules
Do not bypass controls
Troubleshoot only within approved scope and role authorization.
- • Do not bypass locks, defeat credentialing, prop or force entry, disable or obscure surveillance, or override secure settings without explicit authorization.
- • Do not perform restricted work outside site policy, permit boundaries, or role authorization.
- • If suspicious activity, life-safety interaction, forced-entry evidence, or unresolved secure-area exposure is present, escalate to site security immediately instead of troubleshooting-only behavior.
Panel and controller status review ▾
Best used for: Initial triage of alarm state, communication state, and obvious fault indicators.
What it can confirm: Whether the controller reports a visible fault, offline condition, tamper/event status, or door state change.
What it cannot confirm alone: Root-cause wiring faults, reader hardware integrity, or whether access should be granted by policy.
Good practice: Record panel text exactly and capture timestamps before any authorized reset/retest steps.
Escalate when: Persistent secure-area exposure, repeated controller instability, or policy-sensitive overrides are involved.
Credential and reader visual inspection ▾
Best used for: Rapid check of obvious badge/read path issues before deeper diagnostics.
What it can confirm: Physical damage, contamination, loose mounting, misalignment, and visible reader feedback behavior.
What it cannot confirm alone: Credential entitlement, backend policy mapping, or cryptographic/authentication processing outcomes.
Good practice: Compare against a known-good authorized credential under site-approved test procedure.
Escalate when: Multiple users fail with authorized credentials or security policy conflicts are suspected.
Lock hardware and door-condition observation ▾
Best used for: Identifying mechanical alignment and door-closure conditions affecting normal secure operation.
What it can confirm: Door/frame misalignment, strike/latch obstruction, damaged closers, or incomplete closure events.
What it cannot confirm alone: Electrical control logic integrity or permission rules in upstream systems.
Good practice: Observe multiple open/close cycles with authorized supervision; document physical symptoms without forcing entry.
Escalate when: Forced-entry signs, life-safety door interaction, or hardware replacement decisions are required.
Camera and image-path visual checks ▾
Best used for: Rapid triage when video is missing, degraded, frozen, or delayed.
What it can confirm: Visible obstruction, lens contamination, framing changes, and obvious stream/path interruption symptoms.
What it cannot confirm alone: Legal retention compliance, full evidentiary integrity, or root-cause encoding/storage behavior.
Good practice: Note scene conditions and compare affected feed with nearby known-good camera views when permitted.
Escalate when: Surveillance coverage gaps impact secure areas or incident-review requirements.
PoE and link-status checks ▾
Best used for: Establishing whether endpoint connectivity and powering path appear healthy.
What it can confirm: Port/link presence, apparent power delivery state, and obvious network path loss patterns.
What it cannot confirm alone: End-to-end service quality, policy segmentation impacts, or upstream controller/app behavior.
Good practice: Correlate physical port observations with approved network monitoring or switch logs from authorized teams.
Escalate when: Link flaps persist, secure devices repeatedly drop offline, or network-core review is required.
VMS/NVR recording and history verification ▾
Best used for: Confirming whether expected events or footage are indexed and retrievable.
What it can confirm: Presence/absence of records in expected windows and obvious timeline discontinuities.
What it cannot confirm alone: Legal retention interpretation, chain-of-custody determinations, or all subsystem dependencies.
Good practice: Capture exact query windows and event IDs; avoid altering retention/export settings without authorization.
Escalate when: Incident evidence may be impacted or deeper storage/forensic interpretation is required.
Documentation and escalation
Operational closeout
Capture facts first, then route to the right authority.
Record in your ticket/log:
- • Event/alarm text exactly as shown
- • Door, camera, reader, and controller identification
- • Timestamp range and timezone context
- • User-reported symptoms and impact scope
- • Physical condition notes (damage, obstruction, forced-entry signs)
- • Network context (link state, affected segment/path)
- • Who was notified and when (security, facilities, network, vendor)
Escalate to:
- • Site security for suspicious activity, secure-area exposure, or evidence handling concerns
- • Facilities / network support for power, link-path, or environmental dependencies
- • Authorized vendor service when deeper device interpretation, repair, or policy-bound reconfiguration is required
For advanced interpretation, follow current manufacturer documentation and site security policy requirements before further action.
Security troubleshooting flows
Access Control / CCTV decision flows
Use these on-site, mobile-first guides to route legitimate diagnostics fast while preserving secure states. Follow site policy, event logs, network records, and manufacturer documentation at every step.
Security boundary
Do not bypass credentialing, defeat locks, force doors, disable surveillance, or expose secure areas during testing. Escalate to authorized security, access-control service personnel, network, facilities/power, or incident-response teams when required.
Legend
- Flow order: Symptom → Safety → Checks → Test → Expected Result → Decision → Action → Resolution
- Decision buttons: tap an outcome to reveal next action on-page (no reload)
- Documentation: record timestamp, device, panel/camera ID, and observed outcome before handoff
- Policy check: compare relay logic, lock timing, PoE class, image settings, and retention rules to site standards
Coming soon (backend only)
Save flow state History timeline Secure share handoff1) Door won’t unlock or lock + maglock/strike faults Includes: door not unlocking, door not locking, maglock not releasing, strike not actuating, inconsistent lock hardware response. Open
Symptom
Door remains locked when valid access is expected, remains unlocked when it should secure, or lock behavior is inconsistent.
Safety
Keep secure perimeters controlled. Do not wedge doors, short lock wiring, or bypass credential/relay control.
Checks
Confirm door status sensor state, lock power path, relay assignment, timer schedule, and event log entries versus site policy and vendor docs.
Test
Use authorized test credential and supervised REX cycle while observing relay LED, lock response, and door contact transitions.
Expected Result
Credential reads, relay state changes per policy timing, and lock hardware follows consistently without unsafe unlock state.
Decision
Credential accepted, lock still fails
Proceed to hardware/power service path with authorized access-control service personnel; attach event and wiring observations.No consistent relay change in log/controller
Route to controller logic path and security administrator review of schedules, access groups, and policy constraints.Action
Document door ID, panel/reader channel, timestamps, observed lock behavior, and who received escalation (security and authorized service team).
Resolution
Flow closes when lock state reliably matches authorized command timing and secure state is restored/verified with security.
2) Badge deniedIncludes: credential read but not accepted, access level mismatch, anti-passback/policy denial, schedule-based denial. Open
Symptom
Reader beeps or reads card, but event shows denied and door does not release.
Safety
Do not tailgate, prop doors, or borrow credentials. Keep identity and authorization controls intact.
Checks
Review denial reason code, badge status, assigned access group, schedule window, and area restrictions against site policy.
Test
Run an authorized known-good credential at the same reader and compare event results in real time.
Expected Result
Known-good credential is accepted while denied badge remains denied for policy reason.
Decision
Denial reason is policy/account related
Route to security administration/account authority for entitlement correction.All credentials deny at one reader
Route to reader/controller communication flow and authorized service diagnostics.Action
Capture denial codes, reader ID, user/credential reference (per policy), and handoff recipient.
Resolution
Resolved when authorized credential acceptance is restored without reducing access-control policy requirements.
3) Reader offlineIncludes: reader offline persists after visual and link review, intermittent online/offline state.Open
Symptom
Reader status offline in system; badge presentations do not generate expected events.
Safety
Maintain entry control with approved security procedures; do not unlock/bridge lines to simulate service.
Checks
Inspect reader power indicator, cabling termination, controller channel status, and recent faults in event logs.
Test
Perform supervised reseat/check per vendor procedure and watch for restored heartbeat or channel recovery.
Expected Result
Reader returns online and resumes event generation, or remains offline with consistent fault indicators.
Decision
Online state restored and stable
Proceed to verification with test credential and close with security sign-off.Offline state persists
Escalate to authorized access-control service and controller communications diagnostics.Action
Log reader ID, panel channel, cable path notes, and escalation destination.
Resolution
Reader remains online through repeated authorized tests and normal alarm/event behavior.
4) Forced/held door + REX issuesIncludes: forced door alarm, door held open alarm, request-to-exit device not triggering correctly.Open
Symptom
Frequent forced/held alerts or REX events missing/constant at one opening.
Safety
Treat as security-significant until validated. Keep area monitored; do not suppress alarms outside authorized process.
Checks
Review contact alignment, hold-open timer settings, REX wiring/sensor behavior, and door closer condition against policy.
Test
Run controlled open/close and authorized exit cycles while observing event sequence timing in logs.
Expected Result
Event sequence aligns: valid exit/open, expected hold duration, secure re-close, no persistent false forced/held state.
Decision
Sequence mismatch remains after physical review
Escalate to authorized service for sensor/REX/door hardware correction and security monitoring continuity.Sequence normal after adjustment/validation
Return to service with incident note and post-check watch period.Action
Record door cycle timings, REX trigger behavior, contact state changes, and who approved return to normal.
Resolution
Alarm pattern clears and door/REX events remain policy-aligned under supervised checks.
5) Controller or panel offlineIncludes: access controller unavailable, panel heartbeat loss, multiple downstream readers/cameras affected.Open
Symptom
Panel/controller shows offline and linked endpoints fail or become unstable.
Safety
Treat as high-impact security condition. Maintain guard/incident process; do not disable secure states for convenience.
Checks
Validate panel power health, network link indicators, communication path status, and controller fault/event records.
Test
Perform authorized diagnostics/restart sequence only per vendor documentation and change-control policy.
Expected Result
Panel returns online with normal heartbeat and downstream endpoint recovery, or remains offline with repeatable comm/power fault signature.
Decision
Online restored and stable across endpoints
Proceed to controlled endpoint validation and close incident with security operations.Offline persists or flaps
Escalate immediately to authorized access-control service + network + facilities/power teams.Action
Capture controller ID, firmware/build reference, affected doors/cameras, test sequence run, and escalation contacts.
Resolution
Controller remains online through observation window; dependent security points operate normally under policy.
6) Power or communications failure + network/PoE faultsIncludes: PSU issues, battery/backup concerns, link down, VLAN/path mismatch, PoE/link not present.Open
Symptom
Devices lose power/comms, links drop, PoE endpoints fail to initialize, or comm failures repeat across one segment.
Safety
Do not repurpose security power feeds or bypass protected circuits. Follow electrical/network authorization paths.
Checks
Compare power status, breaker/UPS state, switch port status, PoE class allocation, and comm errors with facility/network records.
Test
Run approved power and network diagnostics: verify source availability, interface status, and path integrity without changing security policy.
Expected Result
Power/link indicators normalize and endpoint registration returns, or faults isolate to a known infrastructure segment.
Decision
Infrastructure recovers after approved remediation
Validate all affected access/CCTV endpoints and log restoration timeline.PoE/link/comms still absent
Escalate to network team and facilities/power support with port/power evidence set.Action
Document panel/switch IDs, ports, PSU channels, UPS state, and handoff ticket references.
Resolution
Power/comms remain stable through repeat checks and dependent services are confirmed normal.
7) Camera offline + no videoIncludes: camera unreachable, stream unavailable, no live view despite camera endpoint assignment.Open
Symptom
Camera marked offline or channel shows blank/no stream in VMS.
Safety
Treat blind spots as security-impacting. Do not disable other cameras or recording protections during troubleshooting.
Checks
Verify camera power/link indicators, switch port state, addressing/profile assignment, and VMS camera binding.
Test
Execute approved reachability and stream test path from monitoring system; compare with known-good adjacent camera behavior.
Expected Result
Camera stream becomes available, or failure isolates to endpoint hardware, network path, or VMS integration layer.
Decision
Endpoint reachable, stream still unavailable
Escalate to VMS/profile/authentication review with authorized video system personnel.Endpoint unreachable / no link
Route to network/PoE and field hardware path with security incident visibility.Action
Log camera ID, channel, stream profile, switch/port details, and timeline of outage.
Resolution
Live video is restored and verified by authorized monitoring user and security operations.
8) Poor image + PTZ failureIncludes: image present but poor, blur/noise/exposure issues, PTZ command failure or inconsistent movement.Open
Symptom
Video is available but quality is not operationally usable, or PTZ does not respond as expected.
Safety
Do not disable surveillance zones or privacy controls while tuning; keep coverage requirements intact.
Checks
Compare focus/exposure/profile presets, frame/bitrate constraints, PTZ permissions, and mechanical limits with documented site standards.
Test
Run approved image profile swap and controlled PTZ preset call; observe command acknowledgment and returned scene quality.
Expected Result
Image clarity reaches usable baseline and PTZ presets execute consistently, or fault localizes to camera optics/mechanics/control path.
Decision
Settings adjustment resolves issue
Document final approved settings and apply consistency check across similar cameras if authorized.Quality/PTZ fault persists
Escalate to authorized CCTV service/vendor support with sample captures and command logs.Action
Record before/after settings, PTZ command attempts, and quality observations tied to camera ID and timestamp.
Resolution
Camera provides stable, policy-aligned image quality and PTZ control with monitoring team confirmation.
9) NVR or VMS recording issuesIncludes: recording gap observed, retention mismatch, recording policy/schedule conflict, storage/path alert.Open
Symptom
Playback missing for expected interval, retention shorter than policy, or recording service alerts present.
Safety
Do not purge archives or disable recording safeguards. Treat potential evidence impact under incident procedures.
Checks
Review recording mode, schedules, retention policy, storage health, camera assignment, and service logs against official requirements.
Test
Trigger approved short test event and verify ingest, index, and playback path in NVR/VMS with authorized account.
Expected Result
New event records and replays correctly, or gap persists indicating ingest, storage, or policy execution fault.
Decision
Only policy mismatch identified
Escalate to security governance/authorized admin for policy-correct configuration.Ingest/storage faults continue
Escalate to VMS/NVR support and storage/network teams with evidence timeline.Action
Document affected channels, time window, retention targets, and incident/hand-off references.
Resolution
Recording and retrieval match policy and monitoring confirms no unresolved gap pattern.
10) Repeated alarmsIncludes: recurring alarm loop, repeated nuisance alarms, repeated alarm pattern requiring authorized follow-up.Open
Symptom
Same alarm type repeats at short intervals across one point or related points.
Safety
Do not blanket-disable alarm classes. Maintain incident-response readiness until authorized teams classify root cause.
Checks
Correlate alarm timestamps, affected devices, environmental/facility events, and network/power records for recurrence patterns.
Test
Run controlled verification on one representative point per procedure; confirm whether alarm recreates under known conditions.
Expected Result
Pattern either localizes to specific hardware/path or indicates broad systemic condition requiring coordinated response.
Decision
Outcome A: pattern tied to one device/group
Next action: route to authorized service personnel for targeted hardware/path remediation while security keeps coverage controls active.Outcome B: pattern spans multiple systems/sites
Next action: initiate incident-response process and coordinated network/facilities/security investigation; avoid unauthorized suppression.Action
Produce handoff packet: alarm IDs, event export window, affected assets, comparison notes, and owning teams (security/network/facilities/service).
Resolution
Recurrence stops or drops to expected baseline after authorized corrective action; closure approved by security operations.