Gallagher Command Center Configuration
The Gallagher Command Center integration has the following prerequisites:
Networking
- The Proxyclick access control client reaches out to Proxyclick servers via port 443. For more information on networking refer to the 'Deployment Requirements' section of the Access Control Overview.
- The access control API listens on port 8904 by default, but depending on your setup this can change. Confirm the correct port number with your access control administrator.
- The access control client needs to be able to reach the API.
Licensing
Gallagher offer a variety of licences for the API. You can see which are currently enabled under File > Server Properties > Licensing.
For the Proxyclick integration to function with Gallagher, you will need licences for RESTCardholders and RESTEvents to be enabled.
Enable the REST API
From the Configuration Client go to File > Server Properties then select Web Services The default port is 8904 so the API will be located at https://localhost:8904
Create a REST client
From the Configuration Client go to Configure > Services and Workstations then right click on the page that displays and select New > Rest Client On the REST Client creation window, you can see the API Key which is needed to configure the Proxyclick client software.
Create a Proxyclick Card Type - for QR-based access
A Card Type must be set up (via the Configuration Client select Configure > Card Types) and named exactly as follows:
Proxyclick QR code
Configure the Proxyclick Card Type - for QR-based access
A token range must be set that matches the range you tell us to generate tokens within. See Access Control System Configuration.
The same range must be set under the Proxyclick Card Type in Gallagher. Double click the card type to open the properties page then select Setup.
- Under Card Number set the Format to "Decimal"
- For the Range enter the first and last possible 8-digit token numbers that will be applied. Example: you could enter 10,000,000 to 99,999,999 (our full token range)
This token range must be shared with the access control team in advance.
Configure the Card Format - for QR-based access
From the Configuration Client select Configure > Universal Card Formats
Set up a Wiegand card format to match your reader configuration. Further information on QR code reader setup may be found here.
Below is an example QR Card Format set up for a simple 42bit Wiegand configuration:
When this is set up, you can simply drag and drop the card format to the controller Card Formats tab:
- From the Configuration Client select Configure > Hardware
- Double click the required controller to open the controller properties page
- Select the Card Formats tab
- Drag and drop the card format:
Using Physical Credentials - RFID Cards/Fobs
Our Access Card Manager allows physical credentials to be assigned to a visitor via the Proxyclick dashboard. To configure this, we will need to know the Card Format/Type configured for your RFID readers. See Access Card Manager.
QR code setup steps (create and configure the Proxyclick Card Type) must be completed to enable the use of physical credentials.
Access Group setup
Access groups cannot be created automatically in Gallagher.
You will need to create the three access groups listed below for our standard functionality to be possible. Please create these access groups named exactly as follows:
Proxyclick expected
Proxyclick checked-in
Proxyclick checked-out
- From the Configuration Client select Manage > Access Groups > Right click > New to create these access groups
- Double click the access group name to open the Properties page
- Select Access to configure which Access Zones and Schedules are related to each access group
In addition to the above, if you are using our employee features and require access for employees, you will also need to create an access group as below. This also must be named exactly, minus the quotes and with the company name added:
Proovr - "company name as displayed in Proxyclick account"
If you have more complex requirements for managing access, additional access groups will also need to be entered in advance to achieve this. You can discuss this with the team who will guide you through this setup.
- We can allow for custom access groups to be applied for different visitor types. A custom field in Proxyclick may have the option to specify if the visitor is a ContrExample actor, Visitor, or VIP (just an example, the options you set can be adapted to your needs).
This field can then be mapped to the associated access group in Gallagher. When the option "Contractor" is selected when creating the visit, there needs to be an access group in Gallagher that can be applied to this visitor. In that scenario the access levels would need to be formatted as:
Proxyclick expected - Contractor
Proxyclick checked-in - Contractor
Proxyclick checked-out - Contractor