Using Proxyclick QR codes is an excellent way to provide building access, as this allows visitor credentials to be sent in advance with no front desk process involved. It's a simple and seamless way to allow visitors to gain access.

Sometimes QR codes are not suitable; perhaps due to internal policies, the hardware already in use, or simply due to preference. If that's the case, the Proxyclick Access Card Manager makes managing physical credentials as simple as possible.

The Access Card Manager allows physical credentials to be associated with a visitor via the Proxyclick dashboard. Simply enter a card number when inviting someone or edit the visit once they arrive and enter the card number before handing it to them.

Proxyclick access control integration handles the rest, and will associate the token number from the card with the profile we have created for the visitor in the ACS. Upon checking out, the card is automatically removed from the ACS profile and ready to be associated with another visitor.

💡 This feature allows you to use QR codes and RFID cards simultaneously!
Access using a QR credential could be allowed prior to checking-in, to allow visitors to park their vehicle or enter an external gate. Once checked-in, they can switch to RFID credentials to have access around the site.


Setup and functionality

  1. Proxyclick must already be integrated with your access control system for this feature to work - you can request that we activate the Access Card Manager during the ACS deployment process

  2. You will then need to identify the collection of cards/fobs to keep at the front desk

  3. When a visitor checks-in, simply edit their visit, enter the card number in the "Access card" field, then click "Save".

To enter the card number you can either:

A - Type the token number:
ℹ️ You'll need to know how each card will be interpreted by your access readers: cards can be labelled so the encoded token number may easily be typed in.

B - Scan the card to enter the token number:
ℹ️
This method requires a desktop reader with keyboard output, which means that cards presented to the desktop reader will have the token number sent as if typed on a keyboard. This should be connected to the PC where cards will be managed - typically at the front desk.
ℹ️ The desktop reader will need to be configured to match the output of the access readers on site. This ensures the token number transferred by Proxyclick to the ACS matches the token number sent by the access readers.

See our Access Control Overview documentation for further information.

💡 Configurable third party desktop readers are available from Elatec. Your ACS manufacturer may also offer a native version. We recommend you discuss suitable options with your integrator.

Did this answer your question?