User's Guide

Forced-Open Detection –if enabled, an Entry opening without first unlocking through
Openpath or triggering the REX will generate an event.
Contact sensor events can trigger alerts. See ALERT SETTINGS. They can also be used to trigger
custom integrations. See OUTBOUND WEBHOOKS.
WIEGAND DEVICE
Openpath is compatible with legacy Wiegand Devices.
Port – select the port for the Wiegand Device to which this Entry is wired.
Mode – select the Mode to set which direction the card credential data is sent:
Use Input to receive data from devices such as an RFID reader or PIN code keypad.
Use Output (Gateway) to send credential data to a third–party control panel. See
CONFIGURING OPENPATH WITH LEGACY SYSTEMS for more information.
ADD CONTROL
If an Entry has more than one of any controls (Openpath Readers, Entry/Exit Hardware, Contact
Sensor, Request to Exit, or Wiegand Device) installed, you can select which additional
control(s) you would like to associate with the Entry.
Once you add an additional control, it will appear in the relevant section on this page.
ENTRY SCHEDULES
After creating an Entry, click the Entry to manage Entry Schedules. Scheduling allows for Entries to
be in a specific state (e.g. locked, unlocked, etc) based on date and time. For example, an Entry
Version 1.9
©
Openpath 2019
Page 26