Skip to main content


Eptura Knowledge Center

Add or Edit Custom fields

Proxyclick provides specific default fields that can be used during the check-in process on the kiosk. These default fields include first and last name, email, company, mobile number, and more.

Custom fields can be set up and used during the registration process on the kiosk. Some examples of custom fields include the following:

  • Free text - Provide a blank field that can be filled in with letters or numbers.
  • Multiple-choice - You can list different custom options.
  • Yes/No - Specially designed for simple visitor or host questions.
  • Date

Custom fields can be:

  • Mandatory or optional.
  • Saved in the visitor profile to facilitate future visits.
  • Easily activated and deactivated without losing your historical data.
  • Only shown to users belonging to the Reception and Admin user group.


  • Only showing the custom fields to reception and admins is useful if the questions are to be answered by the visitor on the day of their visit. Imagine you are asking your visitors which transport they used to reach your building. When you enable this option, it makes sure it is hidden from the host inviting that person and avoids confusion when creating a visit. It also allows the reception team to create a visit on the go and fill in the custom fields from the dashboard.

  • You can make the visitor check-in faster by skipping pre-filled custom fields.

A step-by-step guide to setting up your own Custom fields

Logbook Custom Fields

The custom fields and the information that is saved from those entries will be saved in the Logbook and will be visible to your company users only. The two conditions for them to appear on the visitor creation page are that this custom field is Active and displayed to.

  1. Navigate to Settings > General Settings > Custom Fields.


  1. Click on the New custom field button.


Custom fields do not have to be displayed to guests; they can be strictly for internal use by selecting the option Only show this field to receptionists and admins, which is at the bottom of the window.


The Data Retention period provides 3 options.

  • Do not save any data that is entered.
  • Save the data that is entered for a specific number of days.
    • The data is saved for the # of days that is entered in the field. Be sure to click the Save button at the bottom of the screen.
    • The data retention begins when the data is entered, not from the start time of a particular visit, scheduled or unscheduled.
  • Keep that data forever.

Edit Custom Fields in your Account Settings

Custom Fields can be managed in three locations depending on where they will appear during the check-in process:

  • Custom screens for the Kiosk
  • Custom Fields to set up to appear on the Kiosk
  • Texts and translations so the text in the Custom Fields appears correctly for the region
  1. Settings > Visitors > Configure Kiosk > Custom Screens

  2. Settings > General Settings > Custom Fields
    image 3.png

  3. Settings > Visitors > Configure Kiosk > Text & Translations

Here is an overview of how they interact:

  • Adding a custom field in the Custom Fields makes this field available in the Custom Screens manager.

  • Only when you add this specific custom field in the Check-in flow or create a question will the custom field show in the Text & Translations.

  • Editing the title of a question in the Custom Screens Manager will edit the field in the Text & Translations and the Custom Field in the Logbook.

  • However, the contrary isn't true: editing a custom field in the Text & Translations isn't reflected in the Custom Screens Manager or Custom Fields in the Logbook. The reasoning behind it? The translation will only apply to the specific language you provide the translation for.

Note on translations:

  • Automatic translations

    • Common terms (Proxyclick immediately translates those that are part of the default Proxyclick setup).

    • Custom terms are pre-filled by the translation entered for the location's default language.

  • The user can request a machine-generated translation to a specific language for each custom term.

    • The machine-generated translation replaces the current translation for that language.