Skip to main content
All CollectionsEventsEvent Registration
How to Require Users to Login for Event Registrations
How to Require Users to Login for Event Registrations

Learn how to configure event tickets to require login for registration, whether for all users, members only, specific member types, or designated groups.

Melanie Dupont avatar
Written by Melanie Dupont
Updated over 3 weeks ago

Why Require Users to Log In?

To Track CEUs for Attendees

CEUs can only be assigned to individual records when users are logged in. If a registrant is not logged in, their registration is stored under the generic "Novi Guest" record, preventing CEU tracking.

To Collect Complete Registration Data

If a user is not logged in, their registration is assigned to "Novi Guest," regardless of membership status. Requiring login ensures accurate data collection and prevents "Novi Guest" registrations. More info on Novi Guest.

To Allow Non-Members to Pay by Invoice

Only logged-in users can choose the Invoice payment option. If invoicing is an option for non-members, requiring login ensures they have the option to be invoiced.


Event Setting: Ability to Purchase/Attend

If you want to have the best data possible for your event registration lists and do not want to see any Novi Guest purchasers or registrants, then you'll want to consider setting the Ability to Purchase/Attend setting on an event ticket to one of the following options:

  • Logged-In Users

  • Logged-In Users Without Member Benefits

  • Logged-In Users With Member Benefits

  • Specific Group/Committee

  • Member Type


Logged-In Users

There are three main options for requiring users to be logged in:

  • Logged-In Users – Anyone who has a user account with your organization. Whether or not they hold membership is irrelevant as long as they have an account.

  • Logged-In Users Without Member Benefits – Anyone who has an account with your organization and is not a member or inheriting benefits.

  • Logged-In Users With Member Benefits – Anyone who has an account with your organization and is a member or inheriting benefits.

If a user is not logged in and the purchaser is restricted, they'll see the following prompt for locked-down tickets:

If a user is logged in but their membership isn't current, they'll see the following verbiage for locked-down member tickets:

Items of Note for Requiring Non-Members to Login:

  • Don't forget to restrictions as needed to all applicable tickets.


Specific Group/Committee

You can limit the ability to purchase a ticket to any of your Novi Groups, or even multiple groups on the same ticket. Note that the group must be created before it can be added to a ticket. In addition to the members & non-members scenarios above, some other examples include:

  • Retired Members – If you have a custom field that tracks members' retirement status, you can create a group and then offer a discounted ticket that only they can purchase.

  • Board Members – You probably already have a group of your board members, but if not, you can manually add them to a new group. In this example, maybe you don't want everyone to see that the board is receiving a discount. If so, just set the Visibility setting to the same group.

  • Staff – This could be a free "RSVP" ticket (with hidden visibility), even if it's just so association staff are included in food counts and name badge prep.


Member Type

If the ability to purchase a ticket is set by Member Type, users will be required to log in so the system can check the member type on their record. 

  • A ticket with this setting will only be available to individuals who are logged in and are either a current member or are inheriting benefits from a current member - within the member type(s) selected

  • Multiple member types can be applied to the same ticket.

Restriction Level

Once you make any selection that requires logging in, you'll be prompted to select a Restriction Level for the setting.

  • Restrict Purchaser Only – The purchaser must meet the qualifications of the selected restriction, but may register any attendee from a drop-down list of

    colleagues or type in a name.

  • Restrict Attendee Only – Any logged-in individual may choose attendees only from a drop-down list of colleagues who meet the restriction qualifications. If you need to track purchasers but still allow guests to attend the event, you may not want to restrict the ability to attend.

  • Restrict Purchaser and Attendee – Both the purchaser and registering attendees must meet the qualifications of the selected restriction. The purchaser will only be able to choose attendees from a drop-down list of qualified colleagues.


Additional Resources:

Did this answer your question?