Search Visit Create Knowledgebase

Access & Print

This configuration area defines the behaviour of Check-In for specific modes. Although not mandated, typically a Check-in instance will be assigned a location which uniquely identifies it, and optionally that location may belong to an area. For example:

  • an area named ‘registration desk’ with locations named ‘station 1’, ‘station 2’, ‘station 3’
  • an area named ‘hall 1’ with associated locations named ‘entrance 1’, ‘entrance 2’, ‘exit’

When using Check-in certain modes, the conditions defined here are checked to validate if the registrant has access to the associated location. Properties are checked from top to bottom relative to their position on screen. In summary:

  • First, access rules are checked. No further processing will take place unless the registrant get an allow result from these initial checks.
  • Second, if an access product is required, the registrant’s order is checked for one or more compatible products in the context of the current area. When configuring an access product in a Visit shop, the associated area is mandatory. It’s also possible to add one or more exception rules to bypass the access product check.

Access Control Rules

Access control rules are optional, so by default a registrant will be assumed to have access if no conditions have been implemented. To add access control criteria, do the following:

  • Use +Add to create a new access control rule
  • Select from any of the available rules, or define a new rule by adding one or more conditions. Rules are used extensively throughout Visit, and are used to check properties of the registration, event and system properties such as the current time of day
  • Optionally you may associate one or more areas with the rule, to restrict which of the check-in instances the rule applies to.
  • Set whether the behaviour of the configured rule is to allow or deny access
  • Configure a display message to be shown on-screen when the condition is met

You may edit, temporarily disable or delete a rule directly in the rule list:

When processing rules, they are evaluated sequentially from top to bottom. Once a rule matches, no further rules are checked, and the access control result is taken from the matched rule result (allow or deny).

In the case that no rules apply, the default access state is used. Note that this setting is only available once at least one access control rule has been configured.

Following a successful access check (access control result is allow), Visit may also validate for access products.

Access Products

Check this box to require a valid access product. Access product are a specific type of shop item with one or more associated access areas. For example, the below access item is configured to have access to Hall 1:

For a visitor to pass the access product check, the requirements are:

  • one or more of the access product in a completed order
  • the check-in instance must be configured as a location belonging to the product’s area

Access Product Exceptions

Optionally you may add one or more exceptions to bypass the access product check

  • Select an existing rule or add one or more conditions to define a new rule
  • Select the area(s) the exception applies to, or leave empty for the exception to apply to all areas
  • Optionally you may include a custom message to display on screen

Exception rules are processed in order from top to bottom, with the first matching exception only being applied.

  • The order of the exceptions may be modified by dragging their positions in the list
  • You may edit, temporarily disable or delete an exception directly in the rule list

Repeat Scans

This setting is used in conjunction with locations configured as IN or OUT gates, used to identify visitors entering or exiting spaces. With the duplicate scan check enabled, additional validation is run to verify if the registrant is already known to be in the associated area (from a previous scan). The benefits of using this functionality are:

  • accurate reporting of the number of visitors considered to be in a particular area
  • mitigating against badge sharing between different visitors

For this to be effective, it’s critical that every visitor is captured at the configured entry and exit points. Effective management of the scanning process is therefore vital.

  • An attendee may enter/leave an area multiple times in the same event day, provided they have been correctly captured at the IN and OUT locations, and therefore is known to have entered and left the area
  • The area check resets daily, therefore an attendee will be allowed access on a subsequent day if for example their ‘out’ scan was previously missed

Invited Visitors

With reference to registration states, normally only registered or duplicate visitors are eligible for processing by access control rules. An invited visitor is someone whose details are known by the system, however their registration has not been completed and therefore they don’t have a valid registration type.

Use the ‘allow invited’ option to allow scanning and subsequent registration of invited visitors. Visitors admitted using this function will:

  • Have their registration state updated from invited to registered
  • Be assigned the registration type configured for this setting (all ‘registered’ records must have a valid registration type)
  • Have their registration time set to the current date/time. Although this time is timezone-neutral, it may be displayed in the local timezone of the event, according to your account settings in Visit Create

Printing

Use the printing settings to select which document is used on check-in terminals when printing a badge. Select from any of the available documents; however note that you’ll need ensure your chosen document is compatible with the target printer. Since printers are configured locally on Check-In, the choice of printer is unknown within the Access & Print settings. For example, if using a 4″ thermal printer, you’ll want to sure the selected document is based on a compatible template.

Dynamic Document Selection

Optionally you can configure one or more print rules to change the behaviour to a different document. As with all rule definitions, you may pick from an existing rule or define a new one using conditions defined here. Select the print document to apply when the rule applies.

When defining multiple print rules, they may be re-positioned to the required processing order. Rules are processed sequentially from top to bottom, until a matching rule is met. If no rules are met, the default document is used

Local Document Selection

Check-In also features an optional badge document selection, which overrides any chosen settings and rules defined in Visit Create. To use the global print document and rules (if configured) please ensure this setting is left empty on each check-in instance.

The hierarchy of print document selection can therefore be summarised as:

  1. Print document if defined on check-in
  2. Print document if selected by any applicable rules configured in Visit Create
  3. Default print document if defined in Visit Create
  4. No document printed if none of the above apply

Dynamic Printer Selection

Print rules also permit the definition of a target Printer name, enabling print jobs to target one of several printers where rule conditions are met. Typically you may use this when for different pre-printed media to match different registration types (for example loading different printers with different coloured branding), however other workflows are also possible. Note that this functionality is only available for named network printers, which must be accessible to the Check-In instance.

NFC Pairing

This setting configures the global default for NFC pairing, when using Visit smart badges and associated touchpoints. Currently this functionality is only available for Zebra thermal printers fitted with Visit’s optional NFC encoding plate.

Note this setting can also be overridden within an individual Check-In instance’s settings.

  • Default – use the settings as configured in Visit Create
  • None – disable NFC encoding
  • Zebra w / built-in Touchpoint – enable NFC encoding

Badge Collection

By default, any badge can be printed from any Check-In instance at an event. Use this function to define rules that prevent groups of visitors collecting their badge. This function may be used, for example, to direct VIPs to a specific area of the event.

  • Set up one or more rules to identify groups of Visitors for which badge printing should be prevented
  • Optionally include a message for each badge collection rule
  • Optionally add one or more areas to each rule, to limit their scope. Without areas defined, rules apply to all Check-In instances in use at the event.
  • Drag the rules into the required processing order. Rules in the list are processed in order from top to bottom. The first matched rule only is used.

Share this Doc

Access & Print

Or copy link

CONTENTS