# Event registration and payments (/en/businesses/events/registration-and-payments) Limits, quotas and the queue payment are set on each event. The switches for paying, leaving, selling a spot and blocking are venue settings under **Settings** → **Events and classes**, and a change reaches every event and class, existing ones included. Tournament brackets follow the same rules, apart from their [own queue rules](/businesses/events/tournaments/formats-and-brackets#limits-caps-and-queues). --- ## Participant limits [#participant-limits] An event can take any number of people or limit them in three ways: | Mode | How it counts | Good for | | ----------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------- | | **Overall limits** | One minimum and maximum for the whole event | Classes, socials, workshops | | **Limits per resource** | A minimum and maximum on each resource | Open play that runs per court or per simulator | | **Split into quotas** | Named quotas, each with its own maximum, queue and, if you like, price | Equal numbers of women and men, juniors and adults, tennis and dinner | The minimum decides whether the event runs. If fewer people have signed up when registration closes, Thril cancels the event, tells the participants and releases its resources. With **Limits per resource**, Thril keeps as many resources as the sign-ups fill when registration closes and releases the rest for booking. You can also require a minimum number of resources for the event to run. A quota's gender and minimum are shown to customers for information. The event confirms on its total. ### Prices per quota and shared limits [#prices-per-quota-and-shared-limits] **Prices per quota** gives a quota its own price. A quota without one uses the price per participant. This way even a free event can sell paid quotas. Membership discounts apply to the quota price. A participant you move to another quota keeps the price they paid. **Shared limits** cap several quotas together when their spots come from the same place. A quota is full when its own maximum or any of its shared limits is reached, and customers see how many spots each quota has left. A Christmas party where guests play tennis, have dinner or both: | Quota | Price | Maximum | Shared limits | | --------------- | ----- | ------- | --------------------------- | | Tennis only | €35 | 32 | Tennis courts | | Tennis & dinner | €69 | 32 | Tennis courts, Dinner seats | | Dinner only | €45 | 50 | Dinner seats | The courts take 32 players and the restaurant 50 diners, which caps the party at 82 people. Once 32 people play tennis, both tennis quotas are full, and Dinner only stays open until all 50 seats are taken. A spot freed under a shared limit goes to the person who has queued longest and fits every limit of their quota. A session card pays for a quota whose price is within the card's price range. --- ## The queue [#the-queue] When a full event has queuing on, customers can join the queue. When a spot opens, Thril moves the first person in and notifies them, also after registration has closed. With **Require payment to join the queue**, customers pay or use a session card to queue, and the first in line moves in already paid. The venue setting is the default, and each event can require or skip the payment under **Payment to join the queue**. Course classes and tournaments never take a queue payment. A paid queue place is refunded in full if the customer leaves the queue or no spot opens before the event starts. A session card gets its session back. --- ## When customers pay [#when-customers-pay] | Setting | When the customer pays | A spot without payment? | | -------------------------------------------- | ------------------------------------------ | ------------------------- | | Neither switch on (default) | After the event confirms, before it starts | Yes, until the event ends | | **Allow event payments before confirmation** | Any time after signing up | Yes | | **Require payment to confirm participation** | When signing up | No | Requiring payment suits a popular class, where an unpaid sign-up would take the spot of someone ready to pay. Staff can still confirm someone with **Confirm participation** and take the payment on site or later. Read more in [Managing participants](/businesses/events/participants). Customers pay with a card or another payment method you accept, with credits, with employee benefits such as Epassi, or with a [session card](/businesses/shop/session-cards). Each session card and [promo code](/businesses/marketing/promo-codes) chooses the events it covers. A [membership](/businesses/shop/memberships/benefits) can lower the price or cap how many events a member joins at the member price. --- ## Leaving and selling a spot [#leaving-and-selling-a-spot] The registration close you set on each event is also the customer's cancellation deadline. Close registration 12 hours before each class, and customers can leave and get their money back until then. A refund to a card may carry a [refund fee](/businesses/payments). After registration closes, a customer who can't make it can put their spot up for sale. When someone else takes the spot, the seller gets their money back. Until then the spot and the payment are still theirs. | Setting | What it does | | ------------------------------------ | -------------------------------------------------------------------------------- | | **Disable participant cancellation** | Confirmed spots are binding and paid for, for events, classes and tournaments | | **Disable participation selling** | Customers can leave until registration closes. After that, the spot stays theirs | --- ## Blocking customers who don't pay [#blocking-customers-who-dont-pay] **Block customers with unpaid participations** blocks a customer who has too many events left unpaid after they ended. You set the number. A blocked customer cannot make reservations or join events, classes, tournaments or leagues anywhere in your company. Thril tells them, and they can pay what they owe from the app's home screen. The block lifts as soon as they pay or staff mark the participations paid. Each venue counts its own events, and the block covers the whole company. Members who owe a membership fee are blocked with a [membership setting](/businesses/shop/memberships), and customers who keep missing events can be [banned for absences](/businesses/events/attendance#banning-customers-who-dont-show-up). --- ## Who can sign up [#who-can-sign-up] **Allow child accounts** lets parents add their children to Thril, sign them up for your events and classes, and buy memberships and session cards in a child's name. The parent pays and manages everything. With child accounts on, **Who can sign up** on an event is **Anyone**, **Only children added by a guardian** or **Only people signing in with their own account**. A [participation form](/businesses/customers/participation-forms) on the event, or on one of its quotas, asks your questions before a customer joins or queues. A parent answers for their child. Staff can add anyone, also to a members-only or private event. Read more in [Managing participants](/businesses/events/participants#adding-someone-at-the-desk-or-by-phone).