AllBox entry experience¶
Use Entry Experience to decide which actions appear on the public device menu, what each action is called, and where it appears. Most actions have an Enabled checkbox, Menu label, and Menu order from 1 through 9.
Tip
Give each enabled action a distinct order. The editor does not prevent duplicate menu positions, and duplicate values can produce a confusing or implementation-dependent order on the device.
Directory and access actions¶
- Directory enables host or resident search. Show Address can expose address details in results; enable it only when site privacy policy permits.
- Directory code enables the host-PIN or code-based directory action.
- Access PIN enables PIN-based access and supports a secondary message shown after verification.
- Visitor scan enables the scan-first visitor pass or barcode workflow.
Directory code and Access PIN are separate actions. Label them so users understand whether they are finding a host or presenting an access credential.
Visitor and checkout actions¶
- New visitor exposes the ad hoc or first-time visitor workflow.
- Checkout confirmation exposes the visitor checkout confirmation action.
- Quick entry exposes a reduced-friction entry workflow. Show quick entry text fields controls whether its additional text inputs appear.
Enabling an action does not replace site visitor policy, required fields, screening, or downstream access rules. Test an end-to-end check-in, approval, admit, and checkout flow after changing these settings.
Additional relay actions¶
Two additional relay actions can be enabled independently. Each has a menu label, relay address, and order.
Relay configuration can operate physical equipment. Obtain the exact address format from the installed relay/gateway configuration, verify the target output, and test with on-site personnel. Do not copy a relay address from another AllBox unless both devices are intentionally controlling the same physical output.
Primary menu consistency¶
Return to Overview after configuring the entry actions. If one of these actions is selected as Primary menu option, make sure it is enabled and completely configured here. The editor explicitly prevents a disabled Virtual Agent from being primary, but it does not apply the same cross-check to every other action.