The web app uses images in many places. Respect the following sizes to achieve the best possible result:

1. Cover image (home page) 1000 x 250 px, 72 dpi, max. 1MB file size. Formats: png, jpg
   Upload the image to the Gallery and link it to the event template in the ‘Homepage image’ field
2. Navigation on the left (Rooms + Services) 450 x 200 px, 72 dpi, max. 1 MB file size. Formats: png, jpg
   Upload images relating to the bookable Rooms or Items to these records in the ‘Image 1’ field.
3. Item tiles / Product information dialogue box (services) 450 x 250 px, 72 dpi, max. 1 MB file size. Formats: png, jpg
   Save the images in the relevant record.
4. Icons: Seating arrangements (rooms) 80 x 80 px (optional)* 72 dpi, max. 1 MB file size. Formats: svg, png, jpg
   *Not strictly necessary when using the scalable SVG format
   Upload the images to the Gallery and link them under Room > Seating Plan > Added fields in the “Icon for UI” field. If necessary, link actual seating plans in the “Link to large image” field.

Users and  User groups are imported with the scenario. Check on the  Administration tab under  Users > Usersto ensure that the import was completed successfully and without errors.

1. Link the following users and user groups:
   1. the technical User "Online-Buchung_WebApp" with the User group "Berechtigung Online-Buchung_WebApp": authorises the user to open the WebApp and to create an enquiry or order.
   2. the technical User "Online-Buchung_Backend" with the  User group "Berechtigung Online-Buchung_Backend": authorises the user to import enquiries or orders from the Online Booking web app and to send email confirmations and invoices.
   3. the designated real  Users or Groups in the  User group “Betreuung WebApp Online-Buchung”: authorises the user to manage the Online Booking WebApp (upload new templates, populate the WebApp, receive notifications of new enquiries, receive error messages).
2. Assign email accounts to the User "Online-Buchung_Backend" at (Setting up email accounts):
   1. an email account for sending email confirmations
   2. (optional) an additional email account for sending invoices.

Go to the  Configurations tab and click on   Web >  Web logon tickets >  New to create a new ticket for the user "Online-Buchung_WebApp" with multiple use (only if Web App access is enabled).

Define the individual settings for each company under Configurations > Company Added Fields.

1. By default, all text in the WebApp and text templates is pre-set to use the formal ‘Sie’. Enable the Iinformal address ("Du" if you prefer a more informal form of address for a particular company and there are corresponding text templates available.
   Important: This selection applies to all event templates for this venue that can be booked online.
2. Enable showing the Company logo filed under  Company settings > Images > Logo 1if the WebApp is not integrated into an existing website that already features a logo.
3. If you wish, hide the Captcha , which protects against automated bookings. We strongly advise against using this option.
4. Enter the email addresses for sending Confirmations and Invoices.
   Important: The User ‘Online-Buchung_Backend’ must be authorised to send emails via these accounts (see above)
5. Upload the standard text templates for the Confirmation. The confirmation should include a cover letter and a note regarding the right of withdrawal, such as “There is no right of withdrawal as the service is time-bound (Section 312g(2)(9) of the German Civil Code (BGB)).”
6. Save the standard text template for the Spreadsheet and the Cover letter for the invoice. 
   Important: If other text templates are defined in an event template, these take precedence over the standard templates.
7. Provide the URLs , for your Legal notice, your Terms and Conditions, and your Privacy statement. 
8. 8. Enter the URL of your PHP mailer. If only the ‘Email Enquiries' module is enabled this field is mandatory. If you are using the ‘WebApp Access’ module, this information is only required if you intend to use import via email rather than direct import.

Set up time slots and, where applicable, series to restrict the booking times for your events.

Important: You can select times and days of the week in both  Series and Time slots . To ensure that these two functions work smoothly together:

- ALWAYS define the times in the time range and
- ALWAYS define the weekdays in the series. 

E.g.: If, in a series, weekdays are entered for the available booking times of online bookings, the series of bookable days will be ignored entirely.

Creating time slots

The mapping "WebApp_Nährwerte" (WebApp_Nutritional Values) for online booking is imported using the Scenario . Go to Configurations > Mappings and check whether the field names in your database and the values in the ‘To column match, so that the nutritional values can be read and displayed correctly. Update the mapping if necessary.

The Jobs for Online Bookings are imported using the Scenario . Go to  Configurations >  Jobs to make sure that the import has been completed successfully and without errors.

1. Link the Job “WebApp_Online-Buchung_Import_11_Aktivität” to the user group “Betreuung WebApp Online-Buchung”.
2. Link the Job “WebApp_Online-Buchung_Import_ErrorHandling_Aktivität” either to the “"Betreuung WebApp Online-Buchung” user group or to another group that is to be responsible for handling error messages.