The document aims to define in a precise way the processes related to programming and the application of the rules of ticketing in relationship with Kronos and Ticketack This one will be updated regularly according to the requests and the evolutions. If you use Eventival to manage your programming, refer to the ad-hoc document : [...]

Buckets have the following properties: Identifier : contingent identifier (its name). Capacity : number of places available in this buckets. Vendors : indicate here a list of user roles that have the right to access this buckets. The default roles available are as follows : admin : the whole of directors eshop : your website, [...]

The price listsand ticket types are managed through the management interface Kronos. If additional rules need to be implemented on your events, you can let us know so that we can take them into account when importing the events. These price lists and the events to which thetypes of tickets give access depends on the [...]

The tariff grids are managed through the management interface Kronos. If additional rules need to be implemented on your events, you can let us know so that we can take them into account when importing the events. These price lists and the events to which thetypes of tickets give access depends on the programming tool [...]

Film and event data is entered into Eventival by your programming and ticketing teams and then imported into the Ticketack box office as many times as you like. The ticketing options (choice of price range, access rules, etc.) are selected for each session or event from Eventival using a custom form set up by us. [...]

The purpose of this document is to precisely define the processes involved in programming and applying ticketing rules in the context of Kronos and Ticketack. If there is anything you feel is unclear or not sufficiently covered in this document, please let us know so we can improve it.