User guide

8 Visitor Administration User Guide
Prerequisites
The Web Application Server is installed through a custom installation of the access control software.
For more information, refer to the Installation Guide.
Other considerations:
• Your server must be a member of a domain. Workgroups are not supported.
• You should be logged into the computer as a domain user.
• Use the fully qualified name of the computer for the URL. This is important when typing the
computer name in the configuration file.
• The LS Application Server service’s “Log On” user should be a domain user.
• Be sure the LS Application Server service is running.
• Be sure that the user has access to B.A.S.I.S., permissions assigned, and linked to a directory
account.
• When making changes, restart IIS when you are done.
• Sign-in locations should be configured in Visitor Administration before using Visitor
Management Front Desk or Host.
Licensing
Visitor Management is a licensed module. To use these applications, the license must be set to a
number greater than zero. The Visitor Management section of the license indicates the number of
concurrent licenses being used and the number purchased. The maximum number of visits indicates
the number of visits you are allowed to have stored in the system.
Note: For group visits, each invited visitor is counted as a single visit event. For example, if a
group visit contains 10 visitors, this uses 10 visits of the license.
Visitor Management Version Compatibility
There are two options for Visitor Management.
• The existing Visitor Management application can be accessed through System Administration, ID
CredentialCenter, or Visitor Management.
• The B.A.S.I.S. ET693 Visitor Management is comprised of the new smart client Front Desk
application, the browser-based Host application, browser-based Administration application, and
the Kiosk. Visits scheduled in System Administration, ID CredentialCenter, or Visitor
Management can be viewed and modified in these other applications.
However, when group visits are scheduled using the Front Desk or Host, they cannot be changed
in System Administration, ID Credential Center, or Visitor Management. Group visits are not
supported through these user interfaces.
For visits scheduled in System Administration, ID CredentialCenter, or Visitor Management, the
sign-in location does not exist. When these visits are seen in Visitor Management Host, this field
will be blank. In Front Desk, these visits will only be seen when All is selected for the sign-in
location, and will not show up in any other location selected.
When an event has been created in System Administration, ID CredentialCenter, or Visitor
Management, the notification e-mail does not have the scheduled time or visit key. Visit events
should be scheduled in Visitor Management Host or Front Desk.