Schlage PIB300 User Manual page 940

Users Tab
Table 5.3: Authority Levels
Authority Level Description
(0) None: • Allows user to gain access through the reader, but not use the command menus in the reader to change
the reader's settings.
• This choice is appropriate for most users.
(1) Service: • Allows the master reader to display the status of all readers on the network.
• Not relevant on readers that are not configured as a master.
(2) Setup: • Allows user to control reader setup
• See reader's manual for more information.
(3) Management: • Allows user to list all of the users in the reader
• Allows master reader to send/acquire user databases to/from readers in a network.
(4) Enrollment: • Allows user to add or remove users.
(5) Security: • Allows user to modify security settings
• See reader's manual for more information.
See the reader's manual for information on directly changing settings through the reader.
Process Deletes Button
When the Process Deletes button
is pressed, HandNet-Lite looks for a
RemoveUserXML.Xml file in the root
directory of the C: Drive. If this file is
found, any users listed in that file will be
removed from Handnet-lite. Figure 3.1
provides a sample C:\RemoveUserXML.
Xml file which would remove users with
UserIDs of 1000, 1001, 1002, 1003, and
1004 when the Process Deletes button
is pressed.
<?xml version="1.0" standalone="yes"?>
<RemoveUser xmlns="http://tempuri.org/RemoveUser.xsd">
<CRsiRemoveUser>
<UserID>1000</UserID>
</CRsiRemoveUser>
<CRsiRemoveUser>
<UserID>1001</UserID>
</CRsiRemoveUser>
<CRsiRemoveUser>
<UserID>1002</UserID>
</CRsiRemoveUser>
<CRsiRemoveUser>
<UserID>1003</UserID>
</CRsiRemoveUser>
<CRsiRemoveUser>
<UserID>1004</UserID>
</CRsiRemoveUser>
<CRsiRemoveUser>
<UserID>1005</UserID>
</CRsiRemoveUser>
</RemoveUser>
Figure 5.3: Example of RemoveUserXML.xml
Schlage • HandNet Lite Terminal User's Guide • 11