Event tickets are the key to event registrations. Without tickets, an event is simply a date and time on the calendar. For registration to take place, at least one ticket must be created, even if it's only to collect RSVPs.
Create a New Ticket
Tickets are created directly on an event. To create a ticket, navigate to the event and do one of the following:
Click on the New button in the upper right & select Ticket
Navigate to the Tickets tab and press the "+" button
Creating Tickets in Novi (Video)
Ticket Details
Name: Name the ticket in a way that makes sense for your members as well as your staff, since it will display on your website and in the admin.
Seats per Ticket: In most circumstances, this should be set to "1." When selling multi-seat tickets (like golf tournament foursomes or a table of 8), set this to the number of people covered by a single ticket purchase.
Details: Ticket details are displayed on the event registration page and are a great way to describe who the ticket is for and what the attendee will receive. You can use HTML formatting, including bold or italicized text, line breaks, and links. Ticket details must be fewer than 500 characters, including any HTML formatting tags.
Backend
Frontend
📌 Important note: If your event has only one ticket type, attendees who click to register will see that their ticket has been automatically selected. The default quantity is one, but purchasers can edit it. For logged-in users, attendee info will pre-populate from their member record.
Continuing Education Information
If you offer credits for a particular ticket, toggle Continuing Education on. You'll then see the following fields:
Credit Notes: A description of what credits will be earned and under what conditions.
Credit Amount & Credit Type: The credit type and number of credits a person will receive for attending with this ticket. (See: Adding Custom Credit Types)
Instructor(s): Optional. Identify the instructor leading the event or session.
If a member has earned credits but the event is not set up in Novi, you can manually add credits to their record.
Ticket Pricing
Every event that requires registration needs at least one ticket. When setting up a ticket, choose one of the following pricing options.
Paid
Most tickets will be set to Paid, which requires a set price to be entered.
Disable Invoicing: Prevents members from requesting an invoice for this ticket type, so payment must be made to complete registration on the frontend. Staff will still have the option to issue an invoice through the admin.
Taxable: Ensures your tax rate is added to transactions for this ticket.
Dynamic Ticket Pricing
There are two additional options for ticket pricing that provide more dynamic options – Dynamic Pricing by Date and Dynamic Pricing by Quantity. These must be toggled on to use. Only one of these pricing options may be used per ticket setup.
Learn more: Dynamic Ticket Pricing for Events
Free
Free tickets require no payment. If you're collecting RSVPs only, set your tickets to free. Combined with the visibility settings described below, free tickets can also be used for staff, speaker, or complimentary registrations.
Donation
Members can name their price when a Ticket is set to Donation pricing.
Suggested Donation: Admins can suggest a price point to give members a sense of what they might want to pay for a ticket, but this only serves as a starting point. During the registration process, members determine what price they will pay and enter that amount.
Disable Invoicing: This will disable a member's ability to request an invoice for this ticket type, so a payment must be made to complete registration on the frontend. To give your team flexibility, staff will still have the option to issue an invoice through the admin.
Availability
For larger or more complex events, the availability settings in tickets can help eliminate manual work. The goal is to set up your tickets once and let the technology run the event.
Limited quantity
Enable Limited Quantity if only a certain number of tickets are available for this ticket type. This is separate from the overall event capacity set on the event's Settings tab.
Enter the maximum number of tickets available in the Tickets Available field. If tickets have already been sold, Novi will show how many have been taken so you can adjust accordingly.
You can control if and when attendees see a "# Remaining" message by choosing the percentage of tickets sold at which the count should appear.
To never show the remaining count, select 100%.
Frontend view when quantity is limited:
When a ticket type is sold out, a lock icon displays on the frontend. Hovering over it shows a "Sold Out" message.
Set Date & Time
Use Set Date & Time to limit the registration window for a specific ticket. To apply date rules across all available ticket types, use the event-level settings instead.
Registration Starts: Members cannot register before this date. Leave blank to make the ticket available immediately.
Registration Ends: Creates a cut-off date and time for registrations. Not needed if you want registration to close when the event ends.
Visible only within registration window: Hides the ticket from members (but not admins) outside of the registration dates.
If all the other settings of your ticket will remain the same and only the pricing will change, consider using Dynamic Pricing by Date. (For example, dynamic pricing is often a better option than separate tickets when setting up early bird vs. standard registration rates.)
💡Tip: Consider setting ticket availability by date and time if you have additional event activities that need to be closed before the overall registration ends.
Requires Purchase of Another Ticket Type
Conditional tickets allow you to require that attendees purchase one ticket before unlocking another – ideal for conferences where a session or activity ticket should only be available to full-conference registrants.
To set this up, navigate to the dependent ticket and specify which ticket(s) must be selected first. If more than one is listed, the attendee can select any one of them to unlock the dependent ticket – they do not need to select all.
On the frontend, attendees select the required ticket first. If they attempt to select a dependent ticket without it, they'll see a lock icon with an explanatory message. Once the required ticket is selected, the lock becomes a quantity selector.
📌 Important notes:
Admins can override this dependency when registering someone on the backend.
An attendee can return later to purchase a dependent ticket if they previously purchased the required ticket. They must be logged in and their original purchase must be linked to their record. Learn more about updating attendee information.
You can create a hierarchy of tickets (Ticket A unlocks Ticket B, which unlocks Ticket C).
There is no quantity-match limit. Selecting one main ticket does not restrict how many dependent tickets can be selected.
Other restrictions still apply. Dependent tickets can still be limited to members, specific groups, or capacity limits.
Visibility
Customize a ticket's visibility on your website. The ability to purchase the ticket is a separate setting, described in the next section.
Open: Anyone with a browser can see the ticket.
Logged-In Users: Anyone with a record in the system who is logged in, regardless of member status, can see the ticket.
Logged-In Users Without Member Benefits: Logged-in people without benefits (non-member, expired, prospect, applicant, or pending status) can see the ticket.
Logged-In Users With Member Benefits: Logged-in people with benefits (current or inheriting status) can see the ticket.
Specific Group: Limits visibility to one or more specific groups. The group must already exist. Members must be logged in.
Member Type: Limits visibility to one or more member types. The member type must already exist. Members must be logged in. Limited to current, grace, and inheriting members – not expired members or prospects.
Admin Only: Removes the ticket from the website entirely. Only association admins can register attendees for it.
💡 Tip: Many associations use the Admin Only visibility to hide staff or speaker tickets – registrations that need to be tracked but shouldn't be visible on the website.
Viewing Ticket Visibility from the Tickets List
When setting up an event with multiple tickets, it can be time-consuming to click into each ticket individually to check its visibility settings. The Tickets tab includes an optional Visible By column so you can see each ticket's visibility at a glance – without opening the ticket.
The Visible By column is on by default. If a ticket's visibility is restricted to a specific group or member type, the group or member type name will display as a clickable link that opens the record in a new tab.
The Purchasable By column works the same way and also displays secondary restrictions with clickable links where applicable. Both columns can be found in the gear icon column picker.
💡 Tip: When building out an event with many tickets, use this list view to quickly audit your visibility settings across all ticket types before going live.
Ability to Purchase/Attend
The ability to purchase a ticket can be restricted to any of the options below. To limit a ticket to admins only, set the ticket's Visibility to Admin Only (see above).
Open: Anyone can purchase the ticket.
Logged-In Users: Anyone with a record in the system, regardless of member status.
Logged-In Users Without Member Benefits: Logged-in people without benefits (non-member, expired, prospect, applicant, or pending status).
Logged-In Users With Member Benefits: Logged-in people with member benefits (current or inheriting status).
Specific Group: One or more specific groups. The group must already exist. Members must be logged in.
Learn more about groups: Create a Group in Novi
Member Type: One or more member types. The member type must already exist. Members must be logged in. Limited to current members only – not expired members or prospects.
When purchasability is restricted, a second Restriction Level becomes available:
Restrict Purchaser Only: The ability to purchase is locked to the selection above, but the purchaser can still add any attendee to the registration.
Example: A ticket is locked to logged in-users with benefits. The person creating the registration must be a logged in member, but they can select an attendee from their family tree who is not a member.
Restrict Attendee Only: Any logged-in individual can purchase, but attendees must be selected from a list of eligible colleagues.
Example: A ticket is locked to logged in-users with benefits. The person creating the registration does not need to be a member, but they can only select an attendee from their family tree who is a member.
Restrict Purchaser and Attendee: Both the purchaser and attendee must meet the restriction qualifications.
Example: A ticket is locked to logged in-users with benefits. The person creating the registration must be a logged in member, and they can only select an attendee from their family tree who is a member.
When the ability to attend is restricted, ineligible attendees are shown as Not Eligible. Members with management access will see a prompt to add staff. Those without management access will be prompted to reach out to the association.
Frontend View (Ticket-Based Event)
Frontend View (Attendee-Based Event)
💡 Tip: Purchase and attendance restrictions apply to the website only. Admins can manually register any member for any ticket on the backend – make sure your team understands your association's policies. Note that Novi Guest cannot be used for restricted tickets.
Confirmation Email Information
When a member registers for an event, a standard confirmation email is sent. If a specific ticket should include a custom message, enter it in the Confirmation Email Information within each ticket's settings. If multiple tickets share the same message, the confirmation email will display it only once.
The confirmation email editor supports headers, buttons, images, videos, and links to pages on your website or external destinations.
Learn more: Event Email Examples
Payment Plans
Toggle this on if you want to enable a payment plan on an event ticket. Within the ticket edit modal, choose the applicable payment plans. Then, save the ticket settings. If a registration includes a mix of tickets that are and are not eligible for a payment plan, only the eligible items will be a part of the plan and the remainder will be due up front.
Learn more: Enable and Manage Payment Plans
Accounting
When a member registers for an event, Novi uses the ticket to create the accounting transaction. Each ticket type purchased will have its own line item on the invoice or sales receipt.
Item
If an event is Inactive and its tickets have not been assigned prices, linking tickets to QuickBooks Online items is not required. Once an event is Active, each ticket must map to a QuickBooks Online item. The item should already exist in the Products and Services list in QuickBooks Online and be synced to Novi.
Class
Each ticket can be linked to a QuickBooks Online class. This may be required based on your Association Settings. Learn more about using Classes in QuickBooks Online and Novi AMS.
Registration Fields
The registration form (the "Attendee Form") can be customized per ticket type. Drag and drop the custom fields you want to collect to build the form.
Attendee Form (right column)
The built-in attendee fields – Name, Phone, Email, and Company – are automatically set as Required.
When deciding whether to require the Name field:
If required: TBD is not allowed.
If not required: TBD is allowed. A checkbox for "I'm not sure who is coming yet" will appear. Attendees with this box checked will show as "TBD" in the attendee list, checkout, and confirmation emails.
If at least one of the fields is filled out (i.e. Email), but the checkbox is not checked, then the system will leave the name blank (instead of TBD).
If a multi-seat ticket is purchased with unfilled seats, they will be treated as "TBD" attendees.
Each "TBD" attendee record will be counted as a unique attendee.
Available Fields (left column)
Custom fields in the available list are identified by two icons:
The handshake icon indicates a field shown on both the member record and event registration. If a purchaser selects an existing record, values from the member record will pre-populate – but edits made during registration do not update the member record.
The calendar icon indicates event-only fields that do not appear on member records.
If a custom field isn't showing in the available list, confirm it's set to display for Events. Learn more: Adding Custom Fields to Your Event Tickets
💡 Tip: When setting up custom fields for event registration, consider also checking the Attendee List box – this will display the field on the event's attendee list view.
Active and Draft Ticket Status
A new ticket defaults to Draft status. Draft tickets are not visible or purchasable on the website.
To make a ticket available, open it and toggle the status to Active.
📌 Important Notes:
Copying a ticket (active or draft) creates the new copy in Draft status.
Draft tickets do not require accounting fields to be filled in. Active tickets require all applicable accounting fields.
A ticket must be in Active status before registrations can be added to it.
An event can be marked as active even if some of its tickets are still in Draft status.