All Collections
🔐 Access Control
Proxyclick access control: how we manage visitor access
Proxyclick access control: how we manage visitor access
How permissions are applied to visitors and your building is kept secure.
Andy Orwell avatar
Written by Andy Orwell
Updated over a week ago

Our approach to managing access to your premises is based around efficiency and security for both you and anyone visiting. By integrating Proxyclick with your access control system (ACS) you do not need to add visitor details, ensure they have the correct permissions, or take the permissions away to ensure they don't have access when they no longer need it.

ℹ️ - What are access levels?
An access level (AKA access rule, clearance, or template) is a set of permissions in an access control system that will be applied to a user. It defines which doors, parking barriers, gates, turnstiles, etc. a user is allowed to enter through.

How it works

  • When a meeting is created the visitor will receive an invitation email that includes their QR code (the QR can instead be provided in the welcome email after check-in, or on a printed badge)

  • This QR code includes a unique token number

  • When the invitation goes out we also automatically create a profile for the visitor in your access control system that we add the same token number to

  • Using QR code readers as part of your ACS will allow visitors to scan their QR code to gain entry wherever you need them to
    ℹ️ See "Reading QR codes with access control" .

  • You may also make use of physical RFID access cards
    ℹ️ See here for more information on our Access Card Manager.

How we manage access

Each visit in Proxyclick will have a status of:

Expected (visitor is due to arrive)

Checked-in (visitor has arrived and checked-in)

Checked-out (meeting is complete and visitor has checked-out)

We have a staged access approach: our access control integration adds access levels into your ACS that match the above statuses. As you can see below, when the visit has the status on the left we automatically apply the access level on the right:

These access levels are created by Proxyclick and entered into the ACS, but you have full control over the access they provide. For example:

  • The "Proxyclick - expected" access level may offer access to your car park and entrance so visitors may check-in at the kiosk.

  • The "Proxyclick - checked-in" access level can then elevate their permissions to allow access through turnstiles and anywhere else they need access to during their visit.

  • Once they check-out, the "Proxyclick - checked out" access level is applied and you could set this to allow visitors to exit the building and car park or set it to offer no access at all.

The options here are very flexible and can be tailored to the needs of your building.

Tip 💡 An additional Proxyclick status named "On-site" can also be activated in the Proxyclick settings. This status sits between "Expected" and "Checked-in" and an associated "Proxyclick - on-site" access level will automatically be created if this is activated.

Custom access levels

Alongside the above, we have some nice features to take this even further.

Custom access level creation is used to extend the above functionality, when you have more specific needs for managing access, and have a variety of visitor types that will need distinct access permissions.

Custom field to access levels

You may choose to add a custom field in Proxyclick and we can then map this field to create a custom access level in the ACS.


In the image below I have a custom field named "Access Type" set up as part of my visit creation page. When I'm setting up a visit I now have the option to select an access type -

In this example, once we map the custom field to create custom access levels the below access levels would be created in your access control system:

  • Proxyclick expected - Default

  • Proxyclick checked-in - Default

  • Proxyclick checked-out - Default

  • Proxyclick expected - Contractor

  • Proxyclick checked-in - Contractor

  • Proxyclick checked-out - Contractor

  • Proxyclick expected - VIP

  • Proxyclick checked-in - VIP

  • Proxyclick checked-out - VIP

The first three could be configured to offer your default levels of access (whatever you choose) for everyday visitors. The Contractor and VIP access levels can be configured however you decide is suitable for each type of visitor. "Contractor" may be selected when a contractor is invited and will need access to staff-only areas of the building. "VIP" can be selected for important visitors that need access to additional areas that everyday visitors usually do not.

ℹ️ - The above is just to illustrate the flexibility that custom access levels offer. The name of the custom field, as well as the options and therefore access levels, is up to you.

ℹ️ - The custom field must be set up as multiple choice with different options listed.

ℹ️ - This should also be set as a mandatory field, as not making a selection will result in no access level being applied.

Company specific access levels

For systems with multiple tenant companies, we can also configure the integration to create access levels per company instead of having all companies using the same access levels. Once configured the access levels created will automatically use the tenant company name as part of the access level name. Example:

  • Proxyclick expected - Tenant Company Name

  • Proxyclick checked-in - Tenant Company Name

  • Proxyclick checked-out - Tenant Company Name

The company-specific access levels will sit alongside our default access levels. This provides a lot of flexibility and can be set for all tenant companies (each will have their own access levels) or individual companies as required (others will use the defaults).

All of the above options may be used together.

Our staged access approach - applying access at each stage of the visit (Expected, Checked-in, and Checked-out) - is always present, but you can make use of both Custom and Company-based access features to meet the level of complexity you require.

Did this answer your question?