How to prevent event registrations

Event creators usually want event attendees to register for their events as much as possible. However, there are unique event cases where an event creator would like to prevent people from having the ability to submit a registration or more than one registration for the events they offer.

For example, you may want to restrict registrations:

  • To prevent scheduling conflicts
  • To prevent duplicate registrations
  • To prevent any kind of malicious activity

Whatever it may be, this help doc will explain what is possible and what is not for these kinds of situations.

In this article

Is it possible to restrict people from registering more than once for the same event?

Yes. Corsizio always prevents duplicate registrations to the same event by default based on the combination of the same exact name and email address.

See Step 5 — Filters & Settings when creating or editing an event. You will see the option to "Allow duplicate registrations with the same name and email address" turned off by default.

If, on the other hand, you would like people to have the ability to submit duplicate registrations to the same event for any reason, then you can turn this option on in Step 5 — Filters & Settings when creating or editing your event.

When it is left off, if a person tries to submit a registration with the same exact name and email address to the same event, the system will not permit them to do so. They will be alerted that this is a duplicate registration and not accepted.

While this will greatly reduce your chances of receiving duplicate registrations to the same event, it is not possible to eliminate this from happening entirely because people can abuse the system by creating different variations of their name or using a different name or a different email address.

It is always important to monitor your event registrations to be aware of who is registering for any of your events and to promptly catch and deal with any problematic activity.

NOTE — In cases where parents are trying to register several of their children for the same event, duplicate registrations should never be created because, as the Corsizio registration form clearly says, it is the name of the "attendee" or "participant" that is to be entered in the first field visible on the registration form. You can create a custom field to capture the parent's name later down on the registration form if needed, but the attendee's name must always be the name of the person attending the event and for whom the event is created.

Is it possible to restrict people from registering for more than one event?

No. There is no way to prevent people from registering for more than one event that you offer using Corsizio.

When using a public registration system like Corsizio, published events are visible to the public, and event registrants do not create login accounts to register for an event through which you could control or limit their registration access. This means anyone can register for any of the events you offer unless you restrict registrations based on an email domain or passcode.

To restrict people from registering for more than one of the events you offer, registrants would need to have a login to the portal where your events are offered, within which you would create a restriction based on some parameter.

For example, within a login-protected, private platform, the attendee may be granted a token or credit to register for only one event, or the other events may have prerequisites that must be fulfilled before registration is allowed.

Such cases are only possible in private registration systems or on private internal networks, such as those found within higher education institutions or large organizations.

When you publish events on Corsizio, interested people can register for as many events as you offer; there is no easy or foolproof way to restrict them from doing so.

  • You cannot restrict people from registering multiple times by email address because many people today have more than one email address and can easily create new ones.
  • You cannot restrict people from registering multiple times based on their name because people can easily provide a variation of their name or a fake name altogether.

Any information registrants are asked to submit on public forms can be manipulated in ways that prevent platforms from being able to enforce any kind of restriction on registrations. Hence, as shared above, the only effective restriction can only be accomplished on private registration systems where the registrant has to create an account where their activity can be limited or controlled.

How to minimize or deal with unwanted registrations

TAKE ACTION: Communicate your registration policy to your audience

To do this, apply any or all of the following:

  • State your event registration policy in the event description that will show up on your event page as part of Step 3 — Description & Content when creating your event.
  • State your event registration policy using a custom field on the registration form and use a heading for more emphasis as part of Step 4 — Custom Form Fields when creating your event.
  • State your event registration policy in a custom message that can be part of the registration and/or event reminder email as part of Step 5 — Filters & Settings when creating your event.
  • Share your event registration policy in other applicable ways, such as through social media, printed formats at your event location, or in person.

For example, you can inform your audience that your policy for duplicate registrations to more than one event will result in cancellations. You will only honor their first registration, and all subsequent ones will be canceled. This will require you to closely monitor your event registration activity to catch and cancel the registration(s) of anyone who registers for more than one of your events.

TAKE ACTION: Monitor your incoming event registrations

Stay up-to-date with who is registering for your events to catch any problematic registrations and deal with them promptly as required, such as by cancelling or transferring them.

TAKE ACTION: Restrict who can register for your events

If your event registration is only open to a specific group or select individuals, you can use the restrict who can register feature on Corsizio. As part of Step 5 — Filters & Settings, when creating or editing an event, enable the "Restrict who can register to this event" option that allows you to restrict who can register for your event by "Organization's email domain" or by "Passcode".

You would then inform your target audience how they can register — using the email associated with the specific email domain or the passcode you give them. If you are using the passcode restriction, please keep in mind that there is no guarantee that someone will not share the passcode they were given with someone else or leak it publicly. Hence, the passcode option typically works best amongst a trusted audience.

Is it possible to restrict people from registering for another event taking place at the same time?

No. If someone has already registered for an event you offer and you have other events taking place at or around the same time, there is no way to prevent the people from registering for them. The reasons are the same as explained earlier above. Attendees do not have their own accounts on Corsizio with private portals and schedules that would control their event activity.

Therefore, it is up to each registrant to be responsible for the times and dates of any events they are interested in or register for so that their event schedules do not conflict.

Is it possible to restrict an event to only accept registrations from select people?

Yes. As part of Step 5 — Filters & Settings, when creating or editing an event, enable the "Restrict who can register to this event" option that allows you to restrict who can register for your event by "Organization's email domain" or by "Passcode".

For more information, please refer to the help doc: Events with restricted or private registrations.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Related Articles