Use an enrolled face credential to request authorised entry on a supported terminal or reader. HJ checks approach, lighting and matching settings, provides a suitable alternative credential and defines enrolment, access and deletion responsibilities; recognition is not an infallible identity check.
Conceptual Face Recognition Access product and system illustration for Authentication. Final device form, model, interfaces and quantities are confirmed from the assessed scope and approved product data. Conceptual identity and permission path for Face Recognition Access, derived from this page's scope, interfaces and acceptance record.
Conceptual planning path — not an as-built drawing or project photograph.
Use an enrolled face credential to request authorised entry on a supported terminal or reader. HJ checks approach, lighting and matching settings, provides a suitable alternative credential and defines enrolment, access and deletion responsibilities; recognition is not an infallible identity check.
It sits in Door Access / Access Control under Authentication. The final deliverable is shaped by the intended outcome, the installed or proposed environment and the interfaces that must be owned, supplied, integrated and tested.
Terminal model, reader/controller role, approach and light, enrolment authority, authorised user groups, alternative credential and biometric-record retention/deletion policy.
From the initial brief to the handover record: what to prepare, check and confirm with HJ.
Use an enrolled face credential to request authorised entry on a supported terminal or reader. HJ checks approach, lighting and matching settings, provides a suitable alternative credential and defines enrolment, access and deletion responsibilities; recognition is not an infallible identity check.
Terminal model, reader/controller role, approach and light, enrolment authority, authorised user groups, alternative credential and biometric-record retention/deletion policy.
Confirm the reader or terminal decision path, controller protocol, lock output, door contact, exit devices, power and supported software. Attendance, intercom or alarm links require a documented interface and responsible owner; a working credential does not prove the complete door is safe.
Test valid and denied entry, ordinary exit and the approved emergency release with responsible parties. Network loss, power loss and backup affect different components; document the actual installed behaviour without assuming fail-safe means every escape requirement is satisfied.
Record opening IDs, device/firmware labels, credentials and user groups, permitted schedules, administrative ownership, power/release dependencies, acceptance results and unresolved limits. Keep personal data, retention, revocation and later changes under the owner policy.
HJ coordinates assessment, engineering, installation, integration, testing and lifecycle support only for the scope recorded in the quotation. ISD handles catalogue, model, datasheet, supply and availability enquiries. Customer, consultant, builder and appointed-specialist responsibilities remain explicit.
Identity, image, credential and movement data require an authorised controller, lawful access, proportionate collection, retention rules and recorded administrator responsibility.
This focused topic remains connected to its complete system owner. Final models, quantities, interfaces and included work are confirmed in the assessed quotation.
See related systems, how HJ installs them, and support for equipment you already have.
Use the answers as a planning boundary; site conditions and written scope remain decisive.
No biometric match is infallible. Confirm supported matching settings, approach and lighting, test authorised users and failed cases, and provide an agreed alternative credential. Enrolment, access and deletion of biometric records need owner governance.
Confirm the reader or terminal decision path, controller protocol, lock output, door contact, exit devices, power and supported software. Attendance, intercom or alarm links require a documented interface and responsible owner; a working credential does not prove the complete door is safe.
Test valid and denied entry, ordinary exit and the approved emergency release with responsible parties. Network loss, power loss and backup affect different components; document the actual installed behaviour without assuming fail-safe means every escape requirement is satisfied. Record opening IDs, device/firmware labels, credentials and user groups, permitted schedules, administrative ownership, power/release dependencies, acceptance results and unresolved limits. Keep personal data, retention, revocation and later changes under the owner policy.
Tell us where it will be used, what it needs to do and what equipment you already have. HJ will recommend the right system, explain who is responsible for what, and agree the next step with you.