Follow

Configuration Guide - Reception module

Configuration of Reception Module

General Setup

This is the overall configuration of Pronestor Visitor.

In some versions it is possible to lock down the configuration of system specific settings, thus restricting the access to admin personnel only.

Lock/Unlock configuration

By default the configuration will be locked. How to unlock:

  • Open Setup
  • Click the “Enable administration access” button in the bottom of the form
  • Enter your admin password (default: 123456)
  • Click “Unlock

How to change the administrator password

  • Open Setup
  • Go to New password 
  • Enter a New password
  • Confirm Password
  • Click Change

How to remove the requirement for administrator password

  • Open Setup
  • Go to New password 
  • Make a “space
  • Remove the “space”
  • Click Save

Printing

Selection of which Windows printer that is going to be used for printing labels. By enabling “Print Preview” a print preview for every print should be shown prior to printing.

Before a printer is selectable in the Reception module  it must be installed and configured like any other Windows printer. Please consult the installation/setup guide of the printer.

General

Location and language

The application language and the default location for the current installation

Update frequency

How often do you like the lists updated – only useful if multiple Reception Modules installed.

Note! Setting the update too low will have a major impact on the database and can slow down the application. Set it to 120 seconds for optimal update frequency

Barcode scanner

Enable barcode scanner for check in and check out of badges

Safety procedure

Require that visitors from a specific category or all categories needs to be submitted to a safety procedure. If a visitor has been submitted to such one, then it will be valid for a given period.

New visitors that haven’t been submitted to the safety procedure will not be allowed to receive a badge.

Pronestor Room and Catering integration

Enable Pronestor Room and Catering integration (referred to in app as Pronestor Booking)– thus showing all visitors that have been invited as participants to a meeting. Information on which room etc. will also be visible.

Field Settings

Auto capitalize name

Enabling auto capitalize will ensure that all visitors names have the first letter in the first and last name in capitalized letter.

Ex. upon entering “homer simpson” – the visitor’s name will be auto capitalized as “Homer Simpson”. 

Auto capitalize  company

Enabling auto capitalize on company name will capitalize the first letter in the company name.

Preregistration

Show recurrent visitors as preregistered each day in the period they are expected.

LCD Integration

Show checkbox for enabling LCD integration tag for each visitor

Pop-up

When check in of visitor – show host’s contact information

Field 1 - Host

Custom field name for a host

Field 2 -  Host

Custom field name for a host

Field 1 - Badge

Custom field name for a badge.

If enabled, and a value is entered for a visitor – then an additional badge can be printed (badge_5.xml). 

Ex. If “Field 1 – badge” is labeled as “Parking” – then a “Parking” inputbox will be shown for a visit. If a value is entered in the “Parking” for visitor, then a badge is printed.  

Notification

Upon arrival and check-in of a new visitor, Pronestor Visitor can be configured to notify the host. Notification can be an e-mail, SMS or both.

E-mail notification

Server (URL)
Name of the mail server (SMTP)

Server port
Mail server port (usually port 25)

Sender (email)
Name of the sender of the e-mail

Subject
Subject text for the e-mail

Body
Body text for the e-mail

SMS notification

Sender
Name to be shown as the sender of the SMS

Body
Body text for the SMS

Test phone
A test phone number to send a test SMS

You can use the following tags in the subject and body text:

++checkintime++
actual check in time

++hostname++
full name of host

++visitorname++
visitor’s full name

++visitorphone++
visitor’s mobile phone

++location++
location name

++company++
visitor’s company name

Ex. of a body text:

Hi ++hostname++ \n\nYour guest ++visitorname++ has arrived and is awaiting you in the reception ++location++.\n\nYour guest arrived at ++checkintime++ 

License

License key which you have received from Pronestor.

If you change the license key – it will automatically be pushed to all other Pronestor installations on your network.

Database

Information on database type and location of database

Visitors

Visitors is a complete list of all visitors that have been registered for a visit.

You can edit the information for a visitor – setting their first and last name and setting the company.

Deleting a visitor will remove the visitor from the list, but all historic data on the visitor will be saved. It can be useful to delete old visitors, since a large list visitors can result in a slow system.

For Enterprise versions you can also edit an “alert” text for a visitor. Upon check-in of the guest an alert box will pop-up at the Reception Module showing the alert text. This can be used for alerting the reception of special care to be taken for the current visitor, or information to call security to help the visitor leave the building.

Hosts

Hosts is a complete list of all hosts that can receive visitors – usually the list of hosts is equal to the names of the employees in the company.

A host can be edited with:

  • First and full name
  • Initials
  • E-mail
  • Phone
  • Mobile phone
  • Company (useful when running a multi-tenant setup)
  • Notification enabling – receive e-mail or SMS or both upon arrival of visitor for host

Deleting a host will remove the host from the list, but preserve all historic registrations where the host has been involved.

Visitor Categories

A visitor category is a categorization of the visitor. Printing of badges will include this category for the badge – so it is visible what kind of visitor it is. For reporting and data mining is will also be useful to see how many visitors has been visiting within the different types of visitor categories

You can specify which printer will be used for printing badges with a specific visitor category. You might have to printers with two different badges – one in green and one in red – so visitors of one visitor category will be printed to the printer with green badges and another printed to the red badges.

Companies

List of companies used. If you are running Pronestor Visitor in a multi-tenant house, Pronestor Visitor can handle registration of visitors to a specific company.

Badge Layout

A badge lay-out is a related to the different print layouts defined. You can edit the name of the badge layouts if you have changed the underlying badge layouts.

Name

Badge layout

Default

Badge_1.xml

Period

Badge_2.xml

Default+time

Badge_3.xml

Anonymous

Badge_4.xml

Resources

Pronestor Visitor can also keep track of which key cards, parking-slots etc. that a specific visitor has been allowed to use during the visit. You can add the resources here and upon registration of a visit, the reception can choose a resource for the visit.

Note! The dropdown of resources in the registration view will only show the resources that aren’t connected to badge that is checked in. So a resource will released upon check out of the visit for which it has been used.

Locations

Pronestor Visitor supports multi locations.

A location is a reception where guests arrives or leaves. It can be a specific gate, building or even a country, where you have Pronestor Visitor installed and would like to control and ensure correct visitor management.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Support

    Windows authentication can be enabled on the Reception module:
    A match on the user’s windows login and a pronestor appuser (login) must match.

    Create a row in the ”configuration”-tabellen:

    Fieldname: PNG_RequireWindowsAuthentication
    Fieldvalue: true
    Description: pvm

  • Avatar
    Lars Bork

     

    If Pronestor Visitor fails to connect to the MSSQL, but it seems to work well using a test ODBC, please add the port (1433) to the server name.
    Ex.  Database_server_name,1433

     

    Edited by Lars Bork
  • Avatar
    Support

    Add "notification_frequency" to the configuration table, and set fieldvalue to the number of minutes - in which case no immediate notification should be send if one notification has already been sent

Powered by Zendesk