Entry Page (Attendee Form)

The entry page of the registration form is the first page of the form that a registrant sees.

It can be used as the event's entire website (for simple events), or simply as an instructional entry to the online registration process.

It can also be used to limit access to the registration form by requiring attendees to log in using a username and password, for example.

Video: Restricting Access to Forms Using Reg Status and Username + Password (1.5 min)

Entry Section

The instructions appear above the header bar at the top of the section.

Text Above Header appears above the Header Text in the header bar (in a contrast color).

Page HTML appears directly below the header.

Page HTML can include any information desired.

Text entered into the page HTML field converts into HTML.

Carriage returns in the page HTML field convert into HTML BR (break) tags.

This page can also restrict access to the registration form through a variety of permissions.

Form Entry Permissions

Form Entry Permissions determine access to a registration form.

• Open Enrollment or Profile Login is the least secure method of access to a registration form, and it is the default entry permission.
• Open Enrollment allows anyone who has access to the form URL to view the form.
• Open Enrollment includes access via an emailed invitation link from a colleague.
• Open Enrollment includes access via a link to the registration form on a webpage.
• Profile Login applies when Username and Password are set as Required, but a person does not have an existing registration ID in the event.
• In this scenario, information compares to the Profiles database in the account.
• The Profiles database is an address book populated with information from past registrants.
• Reg ID in URL or Integrations Only is an advanced option typically used when an ID value passes to the form via GET or POST methods.
• Certain customers who integrate Certain with back-office systems or internal portals adopt this approach to expedite access to the registration form.
• Forms accessed via a registration link that includes the Dynamic Data Field “Reg ID for URL” appended to the URL string also use this option.
• This option denies access to the form unless a valid ID passes by either GET or POST.
• Valid IDs are:
• Reg_ID (passed in the encoded format PKregID for security)
• Reg Code (the registration code for the attendee)
• Profile External ID (pro_external_frn_key)
• Username and Password, or Email address
• Restrict to Registrations in this event (Existing or Imported) restricts access to the form to only people who have an existing registration in the event.
• Existing registrations can be created through the Import Registration process.
• Existing registrations can already exist as a result of a past registration.
• This option allows existing registrants the ability to return and make modifications.
• Entry into the registration form can restrict access to specific Registration Statuses, including custom statuses.
• A form designed for accepted applicants can restrict registrations to enable registrations with an "Invited" status.
• A form designed for accepted applicants can restrict registrations to prevent registrations with a "Denied" status.
• If no statuses (or all statuses) are selected, registrations do not restrict based upon their registration status.
• Note: This feature works only when used in conjunction with collecting username/password combinations and/or registration codes.
• If a registrant enters a valid username/password combination or registration code, but the registrant does not have an enabled registration status, the form displays the error message in the " Status not allowed " text box.

Waiver Checkbox

To include a waiver checkbox on the entry page, select Require from the Collect? menu.

These extra fields are added:

• Waiver Message is the text shown in the entry section with a check box next to it.
• Registrants must read the waiver and select the check the box before viewing the registration page.
• Box not checked is the text shown to a registrant who does not select the check box and tries to register.
• Default: "Please check the box below to certify that you have read this message."
• The waiver text highlights in the error font color.
• Leave the waiver text field blank if the waiver check box does not require.

Username and Password

Username and Password fields provide the highest level of security.

Each registrant must be pre-assigned a unique username (or Personal Identification Number) and a password prior to invitation.

Registrants may also be asked to select a username and password the first time they log in.

Usernames attach to the registrant's profile record.

Usernames can be reused from event to event.

Certain enables the following options to set for usernames and passwords:

• Collect? selects No, Optional, or Require to determine whether username and password are collected.
• Text Above Header is the text message preceding the fields.
• The HTML Editor edits Text Above Header.
• "Username" Field selects the data field used as the identifier for the attendee upon login.
• Usually Username serves as the "Username" Field.
• Other fields such as Email Address or Last Name may serve as the "Username" Field.
• "Username" Display is the label for the field selected as "Username" Field.
• The "Username" Display usually shows "Username".
• The "Username" Display matches the attendee's understanding.
• "Password" Field authenticates the attendee upon login to the registration form.
• The "Password" Field can set to one of several fields.
• The "Password" Field typically sets to Password.
• Caution: Enabling Enable Forgot Password requires the "Password" Field to be Password.
• Passwords set in the Registrations > Profile area for any registration.
• "Password" Display is the label for the field selected as "Password" Field.
• H ide text? hides the password field as a hidden text field.
• Login fails displays the text if:
• The registrant enters a Username and Password combination that does not match any profile in the account's database.
• No values are entered and Collect? is set to Require.
• Enable Forgot Password includes a link allowing the attendee to reset their password.

> Note: You must designate an email template (Promote > Communication > Email Templates) as your "Forgot Password" template before being able to enable this feature.

Video: Forgot Password Email and Form Setup (2 min)

• Caution: The "Password" Field nominated above must be Password for this option to work because the profile field being reset equals the "Password" Field.
• Enabling Enable Forgot Password adds several extra Forgot Password fields.
• Forgot Password fields configure field labels and messages for:
• The page where the registrant requests a password reset.
• The page where the registrant enters a new password.
• Password reset pages may also show a password-strength indicator.
• This document summarizes and illustrates How to use the Forgot Password feature.
• Note: If the person clicking the Forgot Password link has not already registered for the event but has a Profile record in the account, then the person still receives the Forgot Password email.
• Forgot Password enables the person to reset their password.
• Open Enrolment / Profile Login must set under Form Entry Permissions above.

Passcodes

Collect? determines whether to place a single text box on the entry page to request a passcode from registrants.

Select No, Optional, or Required for access to the form.

If Optional or Required is selected, several fields are added:

• Instructions displays above the Passcode text box.
• Display places text immediately left of the passcode text field.
• Select "Hide Text?" to collect the passcode as a hidden text field.
• Hidden text prevents the registrant from seeing what the registrant types.

Three types of passcodes are used on the entry page:

• Global passcodes: enter a single password in the Passcode field to enable access to the registration form.
• Compare to attendee type: collect passcodes from registrants and compare them to attendee types for an event.
• When a passcode provided matches an attendee type, the system assigns the corresponding attendee type.
• The system shows questions, agenda items, and options accordingly.
• A single (unique) password may provide each attendee type.
• Compare to reg code: ask registrants to enter a passcode compared to pre-assigned registration codes for the event.
• Registration codes can set up for one-time use.
• After one person uses the code to access the form and completes a registration, no one else can use the same code to register online.
• Prevent reg edits? requires selection in the form setup.
• If the form profile sets the registrant's name as read-only, then the registration code becomes non-transferable.
• Non-transferable registration codes allow only the intended recipient to register online using the code.

Passcode error and capacity messages include:

• Passcode omitted: message displays if any of the three passcodes is required and the registrant tries to enter the form without providing one.
• Passcode fails: message displays if a passcode is provided but does not match any of the types it is being compared to.
• Attendee type full: message displays if the passcode matches an attendee type that is full, meaning its capacity limit has been reached.

If more than one passcode is optional or required, the system evaluates and uses the first code that matches in the following order:

1. Registration code 2. Attendee type 3. Global passcode

SSO Login

SSO Login supports SSOs ("Single Sign Ons") such as social logins for LinkedIn or Facebook.

SSO Login uses SSOs configured for the event in Plan > Configure > Single Sign On.

Attendees click the relevant button to pre-populate the form with their details.

Which fields pre-populate depends on the SSO configuration for the account in Account Settings > Management > Single Sign-On.

SSO pre-populated fields always include at least First Name and Last Name.

> Note: Button details including label, color, text, icon, and class derive from the SSO configuration for the account in Account Settings > Management > Single Sign On.

SSO Login includes:

• Required? selects No, Optional, or Require to determine whether login via SSO is required.
• "OR" field provides the text displayed between the Username/Password and SSO sections if both options are available.
• Default: "OR"
• Leave blank if no text should display on the form, for example if only SSO login is available.

(See SSO Configuration and Use for a brief overview of SSOs in Certain.)

Messages for Existing Registrations

Messages for Existing Registrations gives the planner the ability to script messages for existing registrants on the Entry page.

The script messages display depending on whether the registrant has an existing incomplete or completed registration.

Messages for incomplete and completed registrations can use the HTML editor.

Messages can also use event and registration fields.

Messages can insert fields into message content, for example displaying <{First Name}> <{Last Name}> and other registration fields in the message body.

Default messages exist by clicking Default Value below each message entry box.

Defined message types include:

• Incomplete: Some information has already been collected on the registrant.
• Complete: All necessary information has been collected and the registrant is confirmed.

> Note: If an attendee with a " Cancelled " status tries to log back in using their Username & Password, Passcode, or Single Sign-On (SSO), then the attendee sees the "Event Registration Capacity" Message customized on Plan > Forms > Setup > Advanced.

Other Options

Other Options include:

• Registration button: label on the button to submit the entry section.
• If blank, the default text provided in the event setup displays on the Submit button.
• Default: " Continue ".
• Disclaimer: text shown immediately below the Registration button, but above the general Submit button.
• Default: "<BR>NOTE: Your registration is not valid until you have successfully completed the entire process and received a printable confirmation page and an email confirmation."

Since only one button is shown on the form, the planner can decide whether the disclaimer text appears above or below the entry Submit button by using the optional button or general button.