Page History

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SecuTix may be used by distributors that are selling tickets for a very large number of events or exhibitions. These events and exhibitions are under the responsibility of different promoters or producers. From Gabelhorn V1, SecuTix provides a data access scheme allowing the promoters to work directly in the SecuTix back-end, having only access to their own data. By this way, the distributor can delegate to the promoters or producers an important part of the set-up work. The distributor has still an unlimited access to the data. He can therefore check the data created by the promoters or producers or help them for more advanced features.

However, letting promoter/producer performing the set-up will reduce the reusability of some data. For example, SecuTix allows to create a single price grid and assign it to many events. With the promoter/producer model, a price grid cannot be shared anymore between events (or other products) managed by different promoters because this would allow one promoter to know the price details of another promoter, even before the product is on sale. SecuTix gives you the choice between two strategies:

  • Perform the setup yourself and share (if desired) a maximum data among several events and other products
  • Let the producers/promoters do the set-up (as described in more detail below)

Set-up process

Initial set-up by distributor

...

The main or additional promoter can access to the products assigned to themhim. However, a promoter (even the main promoter) cannot assign or reassign a ticket template to his products. Having the right to access an event allows to access to its performances.

...

The additional promoter has only read access to the price grid or the logical configuration. The main promoter has also a write access if the price grid or the logical configuration is used by a single performance or , in case of price grids concerning other product families, to if the price grid is used by a single product .other than an event. This restriction (forbidding the modification of price grid or logical configuration used by several performances) is intended to avoid unexpected side effects caused by unexperienced operators.

...