Event details
Event details are used to add additional, predefined fields to the event description. This makes the description and organisation of an event more structured and clearer. Defined event details appear in the event form, where they can be populated with information. Depending on the settings for each event detail, the information can be displayed on the front end for everyone to see, or only internally for administrators on the back end.
Individual details do not follow any specific logic. Your Campus Events systems contain demo data by default during setup, so there is an example for each field type.
Name (mandatory field): Enter a unique and clear name for the entry. This is used to identify the entry within the system.This is the name under which the event detail will be displayed in the event form and, when shown on the front end, in the event description.
Enabled: Controls whether this event detail can be displayed on the front end. If ‘Enabled’ is not selected, the event detail remains visible in the backend for editing, but is not displayed on the frontend, regardless of whether the list or detail view is selected. If ‘Enabled’ is not selected, the event detail is only visible to administrators in the backend event form.
Visible in list view: If an eventcontains values maintained here and appears in an event list on the website, these details will also be displayed in the event overview list (short description).
Visible in detail view: If an eventcontains values maintained here and its detail view is opened on the website, this information will also be displayed on the event details page (description).
Editing in: Controls the area in which this event detail can be edited: directly on the event and/or on additional items.
Field type: A field type determines the format in which values for this event detail can be entered in the event form, for example as an input field, text field, drop-down list or multiple selection.
- Input field: A field for free text entry. Any characters or words can be entered here (e.g. names, descriptions or comments)
- Free-form input fields: Field type for the flexible entry of event details
- Text field: A field in which more than one line is available for free-form text entry
- Drop-down menu: A drop-down menu allows multiple options to be stored for selection. When used, a value can be selected in the event form for display. To do this, a new data record must be created, which lists the possible options as ‘values’. The selection items can be sorted using drag-and-drop.
- Checkbox: A selection field that can be ticked or unticked. Multiple checkboxes can be selected independently of one another, allowing several options to be selected simultaneously. If this option is selected, “Yes” is displayed on the website.
- Multiple selection: A field in which several options can be selected at the same time. When used, unlike the ‘Dropdown’ option, multiple values can be selected in the event form. To do this, a new data record must be created, listing the possible options as ‘Values’. The selection items can be sorted using drag-and-drop.
Validations: Validations can be defined for the various field types. A validation checks whether an entry meets specified requirements. For example, it is possible to check whether a mandatory field has been completed, whether an email address is in a valid format, or whether an entered value falls within a specific range. If the entry does not meet the selected condition, it will not be accepted and the person concerned will receive a corresponding notification. Validations help to prevent incorrect or incomplete entries and ensure consistent data quality.
Note: Configuration can be complex and should only be carried out by experienced users.
- Condition: Select which validation rule should be applied to the input
- Mandatory field: The input must not be empty.
- Length: The entry must comply with a specified minimum or maximum length.
- Email: The input must be a valid email address.
- Regular expression: The input must match a specified pattern.
- Value range: Numeric values must fall within a minimum and maximum range.
- IBAN: The input must be a valid IBAN.
- BIC: The input must be a valid BIC.
- Date: The input must be a valid date.
- File: An uploaded file must meet the specified requirements.
- Image: An uploaded image file must meet the specified requirements.
- URL: The input must be a valid URL.
- Options: Specify additional settings for the selected condition in YAML format. The available options are pre-populated with default values after saving and can then be adjusted.
- If you have any questions about configuring validations, please feel free to contact our service desk at any time.
Which user groups are relevant? Master Data > Event Details Editor > Authorises the user to edit ‘Event Details’ master data records.
Event lists
Event lists can be used to control which list an event is accessible via and whether it is displayed in the public event overview.
By default, events are assigned to the default list. Only events on the default list are displayed in the regular events overview on the website.
In addition, further event lists can be created, such as a ‘Non-public events’ list. Events assigned exclusively to such an additional list do not appear on the website.
A separate URL is available for each event list. This URL can, for example, be shared via email with selected individuals. The events on the respective list can be accessed via this link.
Important: The link does not constitute secure or personalised access. Anyone who receives the link can, in principle, pass it on to others. Such a list should therefore not be used to restrict access to confidential events.
Publishing events
Assigning an event to a non-public event list does not replace the publication of that event.
For an event to be visible to others and accessible via the link in an event list, the event must be published.
The following applies:
- Published + standard list: The event is displayed in the public event overview on the website.
- Published + other event list: The event is not displayed in the public event overview, but can be accessed via the URL of the relevant event list.
- Unpublished: The event is not visible to external users – regardless of which event list it is assigned to.
Description: Enter a unique and clear description for the entry. This is used to identify the entry within the system.
Preselected (checkbox): The ‘Preselected’ option affects the creation of new events.
- ‘Preselected’: In the ‘Classification’ section of the event form, the event list is preselected by default when creating new events.
- ‘Preselected’ disabled (default setting): The event list is available in the event form when creating new events, but must be explicitly selected.
Allow additional use after approval (checkbox): If the checkbox is ticked, other clients in Campus Events can request approval of the event list for individual events in order to display their event on that list. A request for approval of an event list is made within the event form, under Classification > Event lists > Approvals. Once the approval request has been submitted, an administrator from the client to which the event list belongs can accept or reject the request under Approvals > for event lists.
Notify about pending approvals: Here , you can select users who should be notified of the approval request.
Which user groups are relevant? Only users who have the ‘Approval Administrator’ rightcan be selected.
Venues
Venues store key location data which can be reused in events and displayed in the front end along with the address. A properly maintained address enables automatic linking to Google Maps, provided that a valid address or valid longitude/latitude coordinates have been entered. Changes to the venue record affect all events that use this venue. A venue is displayed in the list view of events.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system. The venue is visible in the event description on the front end.
Visible: Tick this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is unticked, the entry remains saved but is not offered as a selection.
Name (List view): Unlike the venue name, an alternative name can be specified here for the event’s display in the list view on the front end. If no name is specified, the name entered above will be displayed.
Street: Enter the street name and, if applicable, the house number of the event venue.
Postcode: Enter the postcode of the venue.
Town/City: Enter the town or city where the venue is located.
Building: Enter the name or number of the building in which the event is taking place.
Room: Enter the name or number of the event room.
Geo-coordinates: There are fields for geo-coordinates (longitude and latitude)
- The geo-coordinates are automatically updated based on the address entered
Internal note: This note is only visible in the backend.
Event categories
Categories provide subject-specific descriptions of events and make them easier to find, for example in the advanced search on the home page. Categories are defined centrally and can be applied to as many events as required. Changes to a category’s details affect all events that have been assigned that category. Examples include ‘webinar’, ‘conference’ or ‘lecture’. The detailed view of an event lists the categories that apply to that event. On the Campus Events homepage, you can filter the event search by category.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system.
Visible: Select this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is deselected, the entry remains saved but is not offered as a selection option.
Participant list templates
These templates save the layout and column selections for participant lists and signature lists. In the participant management module, lists can be generated directly using the saved settings. The templates are maintained centrally and are then available in the participant management module for PDF and list printing. This allows recurring column and layout combinations to be used without having to reconfigure them.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system.
Internal description: This note is only displayed in the backend.
Page orientation: Select the desired page orientation for the document:
- Portrait: vertical orientation (taller than it is wide)
- Landscape: horizontal orientation (wider than tall)
Columns: In this section, you define which fields are to be displayed in the document and how wide each column should be.
Field: Select the desired data field to be displayed as a column (e.g. title, first name, surname, email). You can select fields relevant to tickets and orders.
Relative column width: Specify how wide the respective column should be in relation to the other columns. Higher values result in wider columns. The column width determines the spacing within the row.
Certificates
Certificate templates define the layout and content of attendance certificates. They are selected for each event and can be issued to participants after the event. A template describes the reusable basic layout. Event-specific content such as the dates, title or other placeholders is only populated with the specific event details when the certificates are generated.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system. The name of the certificate should be defined using the translation control above the table. Within participant management, in the event-specific participant overview, you can specify the language in which the certificates are to be issued. The certificates can then be viewed in the profile and in the participant overview in the specified language. If the language is changed at a later date, the certificate must first be reset in the participant overview so that it can be saved again in the relevant language.
Active: Select this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is deselected, the entry remains saved but is not offered as a selection.
Prerequisites for issuance
Dependencies can be defined to specify when a particular certificate is issued or becomes available.
Passed: The certificate can be issued if the participant has passed the event or examination. Note: This refers to the “Overall Pass Status”
Attended: The certificate can be issued if the participant has been marked as having attended. Note: This refers to the ‘Overall Attended Status’
Paid (Outstanding payment = no): The certificate can be issued once all payments for the order have been settled. This refers to the column content “Outstanding payment = no” in the event-specific participant overview
Certificate background: Select a file from the media library or upload a new file. The selected background forms the design basis of the certificate. The following PDF versions are supported for uploading: 1.0, 1.1, 1.2, 1.3 and 1.4
Signature
In the ‘Signature’ section, you can add and position one or more signatures on the certificate.
Position X: Sets the horizontal position of the signature on the certificate.
Position Y: Sets the vertical position of the signature on the certificate.
Text: Enter and format the text to be displayed in the signature area. The built-in editor offers various formatting options. Placeholders can be used to insert dynamic content. These are automatically replaced with the relevant information when the certificate is created.
Signatures: Add further signatures using the plus icon.
Text blocks
In the Text blocks section, you can define additional content and your own placeholders for the certificate.
Custom placeholders: Create custom placeholders whose content can be entered manually when the certificate is issued or selected. You can add further placeholders using the plus icon.
Newly created placeholders will only be available in the text blocks once the certificate has been saved. The following rules apply to the name:
- The placeholder must begin with a letter.
- Only lower-case letters, numbers and underscores may be used.
- Spaces and special characters are not permitted.
Participant details
This section is used to create and manage input fields for participant details for an event. In Campus Events, ‘participant details’ refers to the information provided by the respective participant during the registration process for an event. It is often desirable and necessary for participants to provide certain details when registering for an event. You can decide whether each piece of participant information is optional or mandatory. Using participant details, the registration process for an event can be expanded to include any number of input fields. The details can be displayed in participant lists and PDFs. The definition here merely specifies the available fields. Whether a field is requested for a specific event is only determined in the relevant event configuration.
The following participant details are predefined and required for every event; however, from the perspective of further processing within Campus Events, only the email address is strictly mandatory:
- Title
- First name
- Surname
- Email (mandatory field)
Under Configuration -> Master Data, a system administrator can add new options for the otherwise fixed values (such as for title or gender). If you have any questions regarding this configuration, please feel free to contact our service desk.
Description: Enter a unique and clear description for the entry. This is used to identify the entry within the system (e.g. ‘Dietary requirements’ or ‘Comment’). This will be displayed to participants in the event registration process under the specified description in the form.
Active: Tick this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is unticked, the entry remains saved but is not offered as a selection option. Only active fields are displayed during participant registration.
Field type: A field type determines the format in which values for this event detail can be entered in the event form, for example as an input field, text field, single selection or multiple selection.
- Input field: A field for free text entry. Any characters or words can be entered here (e.g. names, descriptions or comments) (participants enter individual words and a short sentence here)
- Free-form input fields: Field type for the flexible entry of participant details
- Text box: A field in which more than one line is available for free-form text entry (e.g. comments (continuous text))
- Drop-down menu: A drop-down menu allows multiple options to be stored for selection. When used, a value can be selected in the event form for display. To do this, a new data record must be created, listing the possible options as ‘values’ (e.g. T-shirt size). The selection items can be sorted using drag-and-drop.
- Checkbox: A selection field that can be ticked or unticked. Multiple checkboxes can be selected independently of one another, allowing several options to be chosen at the same time. If this option is selected, “Yes” is displayed on the website. (e.g. “I require a certificate”). For checkbox fields, the “Label (HTML)” field is displayed. If filled in, the content will be displayed in the registration form instead of the text label.
- Multiple selection: A field in which several options can be selected at the same time. When used, unlike the “Selection” option, multiple values can be selected in the event form. To do this, a new data record must be created, listing the possible options as “Values”. If a multiple-selection participant field is required in the event form, at least one option must be selected when registering for the event. If, on the other hand, it is to be possible to select nothing in the multiple selection, the participant field must be configured as optional by ensuring the ‘Required’ box is not ticked in the event form. The selection items can be sorted using drag-and-drop.
- File upload: Uploading files (e.g. supporting evidence or documents)
Description: If completed, the content will be displayed in the registration form beneath the relevant field.
- This is displayed to the participant and serves as:
- Guidance for data entry
- An explanation of the field’s purpose
- Additional information (e.g. notes on permitted file formats)
Validations: Validations can be defined for the various field types. A validation checks whether an entry meets specified requirements. For example, it is possible to check whether a mandatory field has been completed, whether an email address is in a valid format, or whether an entered value falls within a specific range. If the entry does not meet the selected condition, it will not be accepted and the person concerned will receive a corresponding notification. Validations help to prevent incorrect or incomplete entries and ensure consistent data quality.
Note: Configuration can be complex and should only be carried out by experienced users.
- Condition: Select which validation rule should be applied to the input
- Mandatory field: The input must not be empty.
- Length: The input must comply with a specified minimum or maximum length.
- Email: The input must be a valid email address.
- Regular expression: The input must match a specified pattern.
- Value range: Numeric values must fall within a minimum and maximum range.
- IBAN: The input must be a valid IBAN.
- BIC: The input must be a valid BIC.
- Date: The input must be a valid date.
- File: An uploaded file must meet the specified requirements.
- Image: An uploaded image file must meet the specified requirements.
- URL: The input must be a valid URL.
- Options: Specify additional settings for the selected condition in YAML format. The available options are pre-populated with default values after saving and can then be adjusted.
- If you have any questions about configuring validations, please feel free to contact our service desk at any time.
Email address validity check
By default, email fields in the frontend for orders and quick registration are duplicated and checked for consistency.
If a typo is made in the ‘Repeat’ field, the field is cleared to ensure that the user enters the email address entered above exactly as it is. If you enter the string ### in the ‘Repeat’ field, the email address entered above is automatically copied exactly as it is. This setting must be configured in the backend. Please contact support if you wish to configure this setting.
Validation: In this section, you can define rules to ensure that participant details are entered correctly and in full. Validation, or input validation, means checking whether the data entered is correct. This involves checking whether the value entered matches the expected value, i.e. whether the input complies with the rules.
- Entries are automatically checked upon saving, as soon as a participant enters or saves their details
- If any details are invalid or missing, the participant receives an error message
- The ticket booking is blocked until the requirements are met
The following conditions can be set:
- Mandatory field
- Length
- Regular expression
- Value range
- IBAN
- BIC
- Date
- File
- Image
- URL
Once selected from the drop-down menu, the available options will only become active after you have saved your changes. If you have any questions about configuring validations, please feel free to contact our service desk at any time.
Which user groups are relevant? Master Data > Event Details Editor > Authorises the user to edit ‘Event Details’ master data records.
Digital signatures
Digital signatures (from users) are managed centrally and used as facsimiles in certificates or documents. The signature is uploaded as an image file and assigned to a user. Changes to the data record affect all certificates that incorporate this signature.
User: Select the user to whom the signature is to be assigned. The signature can then be used automatically in this user’s documents.
Signature: Upload the selected user’s signature as an image file. JPG and PNG file formats are supported.
Please note the following when uploading:
- Create the required image crop before uploading.
- The file is not automatically cropped or resized during upload.
- Any adjustments to the size or cropping will only take place when the signature is applied to documents or pages.
- Ensure the image is of good quality for optimal display
Target groups
Target groups describe the groups of people an event is aimed at, for example students or staff. They appear on events and can also be used for search and filter functions in the front end. The relevant target groups are visible in both the list view and the detail view of an event.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system. The target group is visible in the event description on the front end.
Visible: Select this option so that the entry can be displayed and used in the relevant overviews and selection lists. If the option is deselected, the entry remains saved but is not offered as a selection option.
Grading categories
Grading categories define selectable marks or assessment entries for courses with graded learning content. They are assigned to a course in the "Learning content (certificate)" section of the course form and are subsequently used in the participant management system for successful completions. The optional assignment of marks then takes place when maintaining the ‘Passed’ status of participants in the participant management section of a course.
Name: Enter a unique name for the grading scale.
Sort order: Determines the order in which the marks are displayed. Entries with a lower number are displayed before those with a higher number.
Value: Enter the name or value of the mark, for example 1.0, Very Good, Pass or Fail.
Ticket categories
If events are subject to a fee (i.e. events with shopping basket orders) and different terms and conditions apply, ticket categories can be used to charge different prices depending on the applicable terms. This makes it possible, for example, to offer early bookers lower prices or to grant students a reduced rate.
Note: Ticket categories are linked to events and can therefore only be deleted if they are no longer in use.
It is possible to restrict participant details to a specific ticket category.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system.
Visible: Select this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is deselected, the entry remains saved but is not offered for selection.
Ticket category references: If you click ‘Display’ in the ticket category overview, you will see a view containing the ‘References’ section. This contains a list of the events in which these ticket categories are used.
Required authorisation: Master Data > Ticket Categories Editor.
Organiser
Organisers indicate which organisation, department or unit is responsible for an event. In the front end, you can filter by organiser using the advanced search.
Name: Enter a unique and clear name for the entry. This is used to identify the entry within the system.
Visible: Tick this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If this option is unticked, the entry remains saved but is not offered as a selection option.
Filter categories
Filter categories flag events with technical or editorial characteristics for interfaces and display on other systems. They remain hidden in the front end, but are delivered via interfaces and can be used there for assignments or filtering.
How can the display of events on other systems be controlled?
First of all: ‘Other systems’, ‘receiving systems’ or ‘third-party systems’ are systems that are not Campus Events. Examples of these include
- our own websites (main site, satellite site, microsites, landing pages)
- external websites (website of the city/municipality, the association, or the parent organisation)
- monitors/displays on-site (information systems for visitors, customers and staff)
- Smartphone apps (in-house apps and third-party apps)
- Third-party software
Filter categories can be used to assign a characteristic to events. Similar to tagging on social media, this characteristic is a word. Any number of words – and thus filter categories – can be set for each event. The filter categories are always hidden and are not displayed to website visitors.
However, the filter categories for each event are delivered via the interface. The receiving system connected via the interfaces can use these words for filtering. In practical terms, for example, one event can be assigned to the system’s home page using the filter category ‘Home page’, whilst another event can be assigned to ‘Area 1’ using the filter category ‘Area 1’.
Description: Enter a unique and clear name for the entry. This is used to identify the entry within the system.
Visible: Tick this box so that the entry can be displayed and used in the relevant overviews and selection lists. If this option is unticked, the entry remains saved but is not offered for selection.
Allow additional use after approval (checkbox): If this checkbox is ticked, other clients in Campus Events can request approval of the event list for individual events in order to display their event on that list. A request for approval of an event list is made within the event form, under Classification > Event Lists > Approvals. Once the approval request has been submitted, an administrator from the client to which the event list belongs can accept or reject the approval under Approvals > for Event Lists.
Notify about pending approvals: Here , you can select users who should be notified of the approval request.
Which user groups are relevant? Only users who have the ‘Approval Administrator’ rightcan be selected.
Sponsors
Sponsors add logos, names and links to supporting organisations to events.
Name (internal label): Enter a unique and clear name for the entry. This is used to identify the entry within the system. It will not be displayed on the website.
Visible: Tick this option so that the entry can be displayed and used in the relevant overviews and drop-down lists. If the option is unticked, the entry remains saved but is not offered as a selection.
Display name (shown on the website): Enter a unique and clear name for the entry. This will be displayed to visitors on the website.
Logo: Upload an image file to be used as the logo for the entry.
Alternative text: Provide a brief description of the logo’s content. The alternative text supports the accessible use of the website and is read aloud by screen readers, for example.
URL: Enter the web address to which users should be redirected when they click on the entry or logo.
Presenters
In this section, you can record and manage the people who host or support events. In addition to profile information visible to the public, you can store internal contact details, billing information, documents and professional details.
The data is divided into the sections General, Public, Billing and Internal.
Moderator references: If you click on ‘Show’ in the moderator overview, you will see a view containing the ‘References’ section. This contains a list of the events in which these moderators are assigned.
General
Visible: Tick this option so that the entry can be displayed and used in the relevant overviews and selection lists. If the option is unticked, the entry remains saved but is not offered for selection.
Internal/External: Specifies whether the moderator is an internal staff member or an external person. This setting has no effect on how the moderator’s details are displayed on the website.
User: Links the moderator entry to an existing user account in the system, if required.
Public
The details in this section can be displayed in the moderator’s public profile. These are displayed on the front end of the website.
Title: Enter how the person should be addressed. This custom entry overrides the standardised options, such as ‘Ms’, ‘Mr’ or ‘Diverse’.
Surname: The moderator’s surname.
First name: The moderator’s first name.
Date of birth: The person’s date of birth in the format DD.MM.YYYY.
Academic title: The person’s academic title or qualification, for example ‘Dr’, ‘Prof’ or ‘BA’.
Institution: University, company, organisation or other institution to which the presenter belongs.
Link to profile: Web address leading to a more detailed profile page for the person.
Public description: A description of the presenter for public display. This may include, for example, their professional background, presenting experience, specialist expertise or particular areas of focus.
Invoicing
In this section, you enter the bank and tax details required for the presenter’s remuneration and invoicing. This information is not displayed on the website’s front end.
IBAN: International Bank Account Number of the presenter or the payee.
BIC: International Bank Identifier Code of the relevant bank.
Bank name: Name of the bank.
Tax number: Tax identification number or tax reference, if required for the moderator’s billing.
Internal
The details in this section are intended solely for the internal organisation and administration of presenters. They are not displayed on the website’s front end.
Internal notes: Enter any internal notes, agreements or additional information regarding collaboration with the presenter.
Telephone: The telephone number on which the person can be contacted.
Email: The presenter’s email address.
Business address: The person’s business or work postal address.
CV: Upload the presenter’s CV or a brief profile as a file. Files already saved can be accessed via the ‘Download’ link. Use the plus icon to add further files.
Quotations: Upload quotations, fee agreements or other documents relevant to invoicing. Documents already saved can be downloaded. Use the plus icon to add further upload fields.
Publications: Enter the presenter’s publications, books, specialist articles or other publications.
Areas of expertise: Describe the presenter’s specialist areas, subject areas and particular skills.
Event formats: Specify the types of events for which the person can be booked as a presenter, such as panel discussions, workshops, conferences, and in-person, online or hybrid events.
References: Provide details of previous moderating experience, reference events, recommendations or any other information that may assist in the selection process.
Contact persons
Contact persons provide key contact details for events so that participants can direct any enquiries to the correct people.
Title: Enter the person’s academic or professional title, for example ‘Dr’ or ‘Prof’.
First name: Enter the contact person’s first name.
Surname: Enter the contact person’s surname.
Role: Enter the person’s professional role or position, for example ‘Project Manager’ or ‘Event Coordinator’.
Department: Specify the department or organisational unit to which the person belongs.
Institution: Enter the name of the university, organisation, institution or company.
Visible: Tick this box so that the entry can be displayed and used in the relevant overviews and drop-down lists. If this option is unticked, the entry remains saved but is not offered as a selection option.
Telephone number: Enter a telephone number where the contact person can be reached.
Email address: Enter the contact person’s email address.
References for contact persons: If you click on ‘Show’ in the contact persons overview, you will see a view containing the ‘References’ section. This contains a list of the events in which these contact persons are used.