Categories can be {{categoryTypes[0].name}} (that is, visible to everybody) or {{categoryTypes[1].name}} (visible after inserting an access code)
Everyone can buy/get a ticket for this category. This is the default option.
Some examples:
Only a restricted group of people can access and get tickets for this category. Once you create a {{categoryTypes[1].name}} category, the system will generate a set of unique codes (one code per seat) that can be used to reserve a ticket for this category.
{{categoryTypes[1].name}} categories need to allocate a fixed number of tickets to work, and therefore they are only compatible with "{{allocationStrategies[1].name}}" ticket allocation strategy
Some examples:
You must decide how to distribute available seats between categories.
The recommended option for most use cases is: "{{allocationStrategies[0].name}}"
This category doesn't allocate tickets exclusively, instead it shares them with other dynamic categories, if any. This is useful if you have only one category or if you have different ways to sell the same seat.
Some examples:
Select this option if you want to allocate exclusively a fixed number of tickets for this category.
Some examples:
-:_@!$*,;
. Spaces are not allowed.
{{baseUrl}}/e/{{event.shortName}}/c/{{ticketCategory.code}}
Attendees must do the first check-in by using their ticket. Then, if you print their badge using Alf.io, you can request them to repeat the check-in every morning, by using their badge
Make this category stand out at check-in. If set, the color will be used from our mobile app and check-in stations to match the color of the badge upon successful scan. This will help your crew to handle this category properly.