Ticket restrictions

Campus Events(Backend) > Events > Ticket restrictions
This is the area for managing ticket restrictions:

All important information and administration elements can be seen at a glance in the ticket restrictions list.

Column: Decisions
Shows the number of decisions that are still open.
The pill turns green if there are no open decisions, otherwise it turns red.
Clicking on the pill opens a list of pending decisions, this is where the participant restriction decisions are managed.

The event and the associated user account are displayed. Column: Decisions Colour coding indicates whether the decision has been "Accepted" (green), "Pending" (orange) or "Rejected" (red). The action buttons can be used to accept, reject, edit or delete a decision.

Filter options Illustration in list view
Filters that begin with "Event:" do not target the ticket restriction itself.

Example:

"Event: contact person" filter is active.

In the list view, those entries are displayed whose selected event has the corresponding contact person.

Manage restriction decisions

Ticket restrictions > Decisions
This is the area for managing restriction decisions:

Actions > View
View information on a participant restriction decision.
The participant details and order details are displayed here.
If a decision has already been made, the "Decided by" field shows who made the decision.

Actions > Edit
Correct participant details.

Actions > Delete If a ticket number has already been generated for a booking, deleting a restriction decision has no effect on such registrations/orders that have already been completed.
The participant is not notified when a restriction decision is deleted.

Actions > Accept/Reject
A restriction decision is made via Accept/Reject.
In both cases, Accept and Reject, the participant is notified via e-mail.
The ticket restriction e-mail templates for the notifications can be customised on client and event level.

There are 2 ways to set up ticket restrictions for an event.

Via the event overview

1. Actions > Show
2. Click on the Events tab
3. Click on the Create button
   • Ticket restrictions form is displayed
4. Set method
5. Add

Via the ticket restriction overview

1. Click on the New button at the top right
   • Ticket restrictions form is displayed
2. Select event
3. Set method
4. Add

When creating or editing ticket restrictions, the form for specifying the settings for the approval process is displayed:

Event
Select the event for which the participant restrictions are to be set up.

Note

This field is only displayed if the setup takes place via Ticket Restriction Overview.
When setting up via Ticket Restriction Overview, the assignment is made automatically in the background.

Which method is the right one for me?

• See method (manual).
• See with shopping basket/moderated registration.
• See Programme event

Manual method

The "Manual" ticket restriction is activated before the actual ordering process. The user can first request authorisation and enter the relevant participant details. If they are approved, they can then go back to the event in the system and register for the event using the normal ordering process (shopping basket/quick registration/...). In other words, the participant first requests authorisation to register for the event.

Configuration
To add details, select the "Manual" method, then click on (+) under the Details field to specify the required details

Request approval

1. A Campus Events account is required to apply for authorisation to register for an event.
2. It is first necessary to log in with a Campus Events account
3. After logging in with a Campus Events account, you can apply for authorisation.
   To do this, click on the APPLY FOR AUTHORISATION button:
4. Fill in the ticket restrictions and then click on the button APPLY FOR RELEASE WITHOUT OBLIGATION:
5. If the request for activation is successful, the following information will be displayed:
6. An admin then checks the request for approval and decides whether the requirements have been met.
   A restriction decision Accept or Reject is made.
   See Manage restriction decisions for more information.
7. Effects of the restriction decision
   1. "Accept" case: The participant can now log in with their Campus Events account and register for the event or make a booking.
      The participant is notified of the activation by email. The e-mail contains a link to the event.
   2. Reject case: The participant cannot register for the event with their Campus Events account.
      The participant is notified of the rejection by email.

The complete ordering process is run through. The information required in the ordering process is requested in the form of the participant details defined at the event. After the binding order/registration, the organiser must approve the order again.

Configuration
The "Shopping basket/moderated registration" method must be selected

Register for the event (approval required)

1. Authorisation can be granted both with a Campus Events account and with a guest account.
2. Register for the event: The entire order process is completed "as usual".
   The required participant details in the order process are requested in the form of the participant details defined at the event.
   A message about the required approval is displayed throughout the entire order process:
3. An admin then checks the order and decides whether the requirements for approval have been met.
   A restriction decision Accept or Reject is made.
   See Manage restriction decisions for more information.
4. Effects of the restriction decision
   1. "Accept" case: The order/registration is approved and a ticket number is generated by the system.
      The participant is then notified by email.
   2. "Reject" case: The participant is notified of the rejection by email.

Approval and decision based on the affiliation of a participant

It is possible to automatically assign users, including front-end users, to corresponding clients. You can configure whether the decision depends on the client of the event or the registering user. Participants are automatically assigned to the correct client and only authorised persons can see and decide on registrations for their client. Assignment is based on any user attribute, for example the suffix of an e-mail address, the Shibboleth identifier or another transferred attribute. This can be configured by BrainAppeal in the system settings and requires the delivery of a corresponding attribute list. The moderated release process is used to configure such a release process in the system. Either a participant/user or an event can be selected in the dropdown as part of the "with shopping basket/moderated registration" method. The participant/user option is selected here as the decision is to be made based on a participant characteristic. Possible participant characteristics are

• User name
• e-mail address
• Organisation (affiliation)
• University
• Shibboleth identifier

It is also possible to specify several decision criteria. In this case, they are checked from top to bottom depending on the data input. The first matching feature is used for the decision, the other features are then skipped in the following. The user group required to approve participants is the "Events-participant-restriction-decision maker" group.

Only programme participants may register for events with this restriction method. There is also the option of allowing "non-programme participants" to register. Programme participants are then automatically "accepted" by the restriction at this point. Non-programme participants are then available for manual approval or rejection in the participant restriction.

The illustration of the note in the frontend for events with ticket restriction "Programme event"

Email templates for the ticket restrictions can be overwritten at client and event level.
See also the documentation on Email templates event form > Emails.

Customise e-mail templates in the event or event form

[Standard text: Event participant: Restriction decision positive]

Hello {{ U_FIRSTNAME }} {{ U_LASTNAME }},

The registration for the event "{{ E_EVENTNAME }}" has just been released for you.

You can register for the event using the following link:
{{ E_URL }}

[Standard text: Event participant: Restriction decision negative]

Hello {{ U_FIRSTNAME }} {{ U_LASTNAME }},

Your request for activation for the event "{{ E_EVENTNAME }}" has been rejected.

For further information, please contact the contact person of the event.

Set default e-mail templates at client level
This configuration area is only available to admins.
Campus Events (Backend) > System > Users > Clients