Principle

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 dada 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.

Set-up process

Set-up by distributor

• The distributor creates the base data. In this context, the base data represents all the data configured in the institution context as well as the data configured in the initialisation menu of the organisation context.
• The distributor creates a contact of type Producer for each promoter/producer
• The distributor decides which SecuTix menus the promoter/producer should be granted access to and creates the appropriate profile. He can of course define several profiles if needed. These profiles haven't changed in Gabelhorn V1. They define the operations that may be performed by the operators, but not the data they may access. The promoter/producer profile must not grant access to the operator menu because this would allow them to grant additional access rights, thus destroying the whole access right scheme.
• The distributor creates operators and link them to the appropriate promoter/producer (contact) created before and assigns them the appropriate profile.

Event or competition creation

• If the distributor uses tours, he may create the Tour and let the promoter/producer create the event and link it to a Tour. The event will inherit the ticket template linked to the tour. The promoter/producer cannot modify this template.
• If the distributor doesn't use tours, he must create the event. Indeed, since the promoter/producer cannot assign a template to an event, he won't be able to save the event. The distributor only needs to create the event itself, without any related information like price grids or performances.

Other product creation

• Products that don't require a ticket template (ticket template is possible but not mandatory) may be created directly by the promoter/producer.

Set-up by promoter/distributor

The promoter distributor may set.-up all event (or other product) related data, for example:

• Price grids, including possible price breakdown
• Logical configurations
• Performances

Access rights

Different kinds of producers

To be more precise, up to 3 promoters/producers may be linked to a product:

• The main promoter is in charge of the set-up described above. He has read and write access on the data defined below
• The additional promoter is defined by the main promoter or the distributor. He has read-only access to the data defined below
• The invoice promoter has no dedicated access rights. He may be defined for accounting purposes. The SecuTix reporting tool allows to display all the revenue due to a given invoice promoter

Assigning a promoter to a product

When an operator working for a promoter/producer creates a product (event, pass, etc.), this promoter/producer is automatically considered as the main promoter of that product. If he wants, he can assign an additional and/or invoice promoter to his product.

When an operator working for the distributor creates a product, he may assign a main promoter, additional promoter, invoice promoter to the product but doesn't have to. If he doesn't assign a promoter/producer, the product is considered to be owned and managed directly by the distributor. This case happens when the distributor produces himself a subset of the products he's

Data that may be accessed by the main or additional promoter