Definitions:
FE User → stands for Front End User; refers to those that are using the website & app
CTA → stands for Call to Action; in our platform, typically refers to a clickable button
Description: Adds a ticket approval flow where users can purchase tickets that require admin review; tickets remain in a pending state until hub admins confirm or reject. Includes hub-side “Ticket Approval” queueing and user email communications for payment confirmation and final status; also notes that waitlist should default to enabled when ticket approval is enabled. Allows communities to gate event attendance through an approval process while still collecting payment upfront, with clear communication and operational tooling for admins to process pending purchases.
Key Users: Hub Admins (approval/rejection workflow); FE Users (ticket purchasers awaiting confirmation)
Use Case: A community is hosting an end of year celebration, where residents must be in good standing with the community in order to attend. When residents purchase tickets to this event, hub admin will be able to check their records to make sure they are up-to-date on dues and have no outstanding violations before approving the resident to attend the event.
How to Access:
Admin | To Set Up: Log into the Hub → Events → + New Event → Tickets Tab → Require admin approval for ticket purchases checkbox
Admin | To Review Ticket Purchase: 1) Log into the Hub → Events → Ticket Approval tab → Click on the event → Attendees ‘See List’ → Use Manage options 2) Log into the Hub → Events → Find & Access the Event with the Ticket Approval Enabled → Attendees ‘See List’ → Use Manage options 3) Receive an email from the system informing you that a ticket purchase is ready to review → Click on the CTA in the email → Attendees ‘See List’ → Use Manage options
Associated Notifications:
Receiver of Notification | Trigger | Meaning |
FE User | Purchase Ticket that Requires Approval | User receives an email with payment confirmation, that also informs the user that their attendance status is Pending |
FE User | Admin Approves or Denies Tickets | User receives a status update email. If rejected, they will also receive a refund email. |
Hub Admin | FE User purchases a ticket for an event that requires approval | An email will be sent to inform hub admin of a new ticket needing review |
Important Notes:
The resident is charged at the time of ticket purchase. If the ticket purchase is rejected, they will be refunded the full amount automatically.
Enabling ticket approval enables the waitlist by default. This creates a list of additional interested users in the instance of needing to confirm any of the ticket purchases and the event is sold out. If you do not want a waitlist for the event, when you get to the Waitlist Tab, you can uncheck the Waitlist box.
When you confirm or reject, you are confirming or rejecting the entire ticket purchase for that user. This means if a user purchases 5 tickets, you cannot approve only 3 of them. All 5 would either need to be confirmed or rejected.
Visual Reference: