Kaba ILCO FDU - PIN Usage as an Alternative to Authorization Keycards

Keycards
Kaba Ilco Lodging Access Control System 79
4.2.6 PIN Usage as an Alternative to Authorization Keycards
For certain authorization levels, the FDU can be configured to allow the usage of a PIN
as an easier method to access the FDU. Instead of swiping a keycard, the PIN is entered
using the FDU keypad. If the entered PIN matches one defined in the FDU memory,
access is granted as if the authorization keycard was swiped. If the system is configured
to not accept PINs, or the PIN is invalid, a message indicating “Invalid PIN” will be
displayed and access to the FDU denied.
Existing and new employees may receive a PIN if the administrator agrees to supply
them with one and the system is configured for PIN usage.
Even when an authorization level has a PIN assigned and the FDU is configured to accept
PINs, the user’s authorization keycard will always be able to log into the FDU if desired.
The usage of a PIN is recorded in the FDU audit as per the usage of an authorization
keycard.
NOTES: In order to create a PIN with an FDU, the system must be
configured to allow this function. Refer to Section 3.6 part 19 –
Create PIN for further details.
In order to accept the usage of PINs on an FDU, the system must
be configured to allow this function. Refer to Section 3.6 part 18 –
Accept PIN for further details.
IMPORTANT: With the exception of doing a FDU-FDU synchronization (see
Section 3.5.4 – Transferring Data to Another FDU) there is no direct
communication between FDUs. As such, for sites that have more
than one FDU it is strongly recommended to only use one FDU as
a “Master FDU” for the creation of PINs. If more than one FDU is
used for PIN creation there is a risk that 2 users with differing
authorization levels could create the same PIN in 2 different units.
This would pose the risk of each user being able to log into the
other FDU with the other user’s authorization level.
The following table shows the different authorization levels that can create and manage
PINs. For example, a Master can create a PIN for a Front Desk but cannot manage one
for a Bellman.
Type of privilege Authorization levels allowed to have a PIN
General Manager Authorization Programming, Bellman, Front Desk, POS
Master Authorization Front Desk, POS
Table 4.2.6: PIN management access table