Last updated: December 3, 2020
Security settings give Organizers greater control over registration and attendance for their events, including allowlist/denylist options, limiting the number of registrants, and manual approval.
EventBuilder offers several choices for Organizers to set security for Templates and Events. Located on the Security step, the following options are available:
- Let anyone register and attend - The default setting, allows anyone with the Registration Page URL to attend an Event.
- Manually approve Registrants before they can attend this event - Organizers decide which Registrants can attend the scheduled Event.
- Allowlist or Denylist Registrants using a list - Organizers can automatically screen Registrants by domain and/or email address.
- Allowlist or Denylist Registrants by querying a remote server - This option allows Organizers to automatically screen Registrants by querying a remote server - requires Organizers to have administrator access to the endpoint server.
- Require Registrants to verify via email - Enables two-factor authentication for Event registration.
- Use a validation question for Registrants to enter a custom field/promo code - Screens Registrants by a custom value they enter at time of Registration.
- Limit the number of Registrants - Set a maximum number of registrants and once that number has been reached any additional registrants will be placed on a waiting list. The maximum number can be adjusted at any time.
Organizers can add optional Security settings to their events, including "Limit the maximum number of registrants' and 'Require Attendees to confirm their email address when joining this event.'
Note: The setting shown below, 'Only allow one unique join key use at this time' is available for Enterprise subscribers only.
- Limit the maximum number of registrants - Places a hard registration limit on your Event.
- Require Attendees to confirm their email address when joining this event - Requires attendees to confirm their address when connecting to the Event. Note: this voluntary confirmation, not two-factor authentication.