Buckets have the following properties:<\/p>\n
I<\/b>dentifier<\/b> : contingent identifier (its name).<\/p>\n<\/li>\n C<\/b>apacity<\/b> : number of places available in this buckets.<\/p>\n<\/li>\n V<\/b>endors <\/b>: indicate here a list of user roles that have the right to access this buckets. The default roles available are as follows : eligible ticket types<\/b> :Ticketack identifiers of the ticket types (one-way tickets, subscriptions) that can access this buckets<\/p>\n<\/li>\n available since<\/b> : date and time from which this buckets is open.<\/p>\n<\/li>\n available until<\/b> : date and time after which this buckets is no longer available.<\/p>\n<\/li>\n can fly from<\/b> : when this buckets has no more space available, it is allowed to steal places from the buckets indicated here, in the order indicated.Note : the rules of the quota from which the seats are “stolen” are not evaluated in case of theft.<\/b><\/p>\n<\/li>\n<\/ul>\n In addition to your specific buckets, we set up the following system buckets for you, the purpose of which is described below.<\/span><\/span><\/span><\/p>\n The functionality overbooking<\/var> allows users with the role overbooking<\/u><\/span> (c.f. user management described in the documentTicketack – Administration, user management and statistics.pdf<\/i><\/a>) to sell or make reservations beyond the capacity of the room. In doing so the bucket<\/var> overbooking<\/u><\/span> is increased by the chosen number of places, thus increasing the capacity of the room in the system.<\/p>\n The functionality \u00ab book-on-check \u00bb allows, for as much that the bucket<\/var> book-on-check<\/u><\/span> has been defined as such – which is its default function – to people who have a subscription<\/var> eligible for an event<\/var> but who have not made a prior reservation, to enter the room. In doing so, the system creates a reservation at the time of entry control for the event<\/var> in a way transparent way for the input controller and the client and thi, for all that long as there are still places available accessibles in the contingents since which the bucket<\/var> book-on-check<\/u><\/span> can take places.<\/p>\n For more information on the application dedicated to entry control, please refer to the documentTicketack – Entry control.pdf<\/i><\/a>.<\/p>\n The “no-show” feature allows room managers to free up reserved to help of events<\/var> of people who did not present themselves at the entry control at a given time. Additional places are thus made available in the contingent no-show<\/u><\/span> for of other clients who are on place (depending on the rules linked to this bucket<\/var>). Note : Place taken with a ticket for a single session and seats reserved less than 15 minutes ago are not released when this function is activated from the room management application.<\/p>\n
\nadmin <\/u><\/span>: the whole of directors
\neshop<\/u><\/span> : your website, ticketing site and mobile application if available
\non-site<\/u><\/span> : your employees at the points of sale during the event
\npartner<\/u><\/span> : external partners (tourist office, partner stores, etc.)
\naccred <\/u><\/span>: the whole of users who have this role (usually the accreditation office).<\/p>\n<\/li>\nSystem buckets<\/h2>\n
Overbooking<\/h3>\n
Book-on-check<\/h3>\n
No show<\/h3>\n