Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Face Capture Configuration

Purpose

Face Capture Configuration is a security enhancement feature that enables lockers to capture a user’s facial image during request access (pickup or drop).

It strengthens:

  • Identity verification for future security purpose
  • Audit traceability
  • Operational accountability

This feature is optional and can be enabled or disabled at the tenant level.

Flow

Why Face Capture Exists

In environments where devices or assets are high value or sensitive, authentication alone may not be sufficient.

Face capture provides:

  • Visual proof of who accessed the locker
  • A deterrent against misuse or impersonation
  • A stronger audit trail for investigations

It acts as a secondary validation layer on top of standard authentication methods.


System Behavior

When Enabled

When Face Capture is turned ON:

  1. A request is created (e.g., pickup or drop).
  2. The user authenticates at the locker.
  3. After successful authentication, the kiosk camera detects and captures the user’s face.
  4. The captured image is:
    • Linked to the corresponding request.
    • Stored as part of the request history for future reference.
  5. The user is allowed to proceed.
  6. The locker completes the requested operation.

Result

  • Access events are traceable with image evidence.
  • Administrative visibility into locker usage increases.

When Disabled

When Face Capture is turned OFF:

  1. A request is created.
  2. The user authenticates.
  3. The locker operates normally.
  4. No facial image is captured or stored.

The system functions without visual audit tracking.


Activation & Control Flow

Face Capture follows a controlled toggle model:

  1. Authorized users enables or disables the feature.
  2. A confirmation popup appears.
  3. On confirmation:
    • The system updates the configuration.
    • The change is logged in activity records.
  4. The new behavior applies immediately to all relevant lockers.

This ensures:

  • Intentional configuration changes
  • Administrative accountability
  • Immediate system-wide enforcement

Architectural Role

Face Capture acts as:

  • A security enforcement layer
  • An audit enhancement mechanism
  • A compliance-support feature

It does not alter request workflows, but it enhances how locker access events are recorded and verified.


Key Considerations

  • Should align with organizational privacy policies.
  • Image storage and retention rules must be defined.
  • Recommended for high-security or enterprise environments.

Summary

Face Capture Configuration controls whether lockers record visual evidence during access events.

It transforms locker interactions from simple authenticated actions into fully traceable, security-audited transactions.