Settings and default templates

Settings is where you set the emails, registration form, event website designs and attendee app theme that new events start from. Organisation admins set defaults for their own organisation, and HAPR staff set the defaults every organisation starts from. Each default is saved on the platform and picked up by events that have not made their own version.

Open Settings#

1. 1
   Press Settings in the menu on the left. It is not shown on a phone, so use a computer.
2. 2
   Look for the sections you can see.

   • Your organisation defaults is for organisation admins. It sets the starting point for all of your events.
   • Platform defaults is for HAPR staff only. Support staff can read it but not change it.
3. 3
   Press a card to open it. There is one card each for Website, Email, Registration and App, with the number of templates inside.

If you have neither section, Settings shows a placeholder page. Ask an organisation admin or your HAPR contact. See Roles and access.

app.thehapr.com/settings

1. 1The event website look and sections.
2. 2The emails sent to attendees.
3. 3The registration form and its landing page.
4. 4The attendee app's logo, colours and welcome.

Change your organisation's defaults#

1. 1
   Open Settings and press the card you want under Your organisation defaults.
2. 2
   For Email, choose the email at the top of the page, such as Registration link or Reminder.
3. 3
   Make your changes. The editor is the same as the one inside an event, with a live preview.
4. 4
   Press Save your copy.

The first save makes your organisation's own copy. After that, the button reads Save changes. A Saved message appears next to the button.

Each template shows its state.

• Inherited from HAPR means you have not changed it. You see the HAPR version, and saving forks your own copy.
• Customised means you have your own copy. HAPR's later updates to that template no longer reach your organisation.
• Built-in default means HAPR has not saved a default for it yet, so you start from the standard design.

On the Email page, a small dot on a tab means that email is customised.

Go back to the HAPR default#

1. 1
   Open the template you customised.
2. 2
   Press Reset to HAPR default.

Your copy is deleted. The template shows the current HAPR version again and follows later HAPR updates. The button appears only on a customised template. Reset appears next to the button when it works.

What you can set#

• Email. The subject line, greeting and body of each email. The body is built from blocks such as text, bullets, a button, a closing line, contact details and a code, and you can insert personalisation such as the attendee's first name. There is one template each for Registration link, Access code, Registration invite, Reminder, Registration confirmation, Team acknowledgement, Registration updated (team), Voucher delivery and Rooming list share. See Email templates.
• Registration. One Default registration form. It holds the branding, a Privacy consent statement with links, and sections you can hide, show and reorder. It also holds an optional first question (the Travel admin support gate) whose answers show or hide the Travel, Visa and Document sections. A live preview shows the Landing, Dashboard and Form views. See Registration form setup.
• Website. One default for each website design. Each design card shows whether it is Customised, Inherited or Built-in, with what the design suits best. See Event website.
• App. One App theme. It sets the app name (up to 30 characters), accent colour, background colour, top bar colour, logo and logo size, welcome message (up to 240 characters) and cover image, with a live phone preview. Press Crop to fill, Fit whole or Stretch to choose how the cover scales. See Designing the attendee app.

Good to know#

• A new event starts from your organisation's default. If you have not set one, it starts from the HAPR default.
• Changing a default reaches every event that still uses it, straight away. It never overwrites an event that has already saved or published its own version.
• Defaults are kept per template. Customising one email leaves every other email inheriting.
• Only the look and wording are saved. Each event keeps its own content, such as its name, dates and venue.
• Organisation admins edit only their own organisation's defaults.
• To fix one event, change the event, not the default. See Event templates for how an event uses and resets its templates.

If something looks wrong#

• Not permitted. Your role cannot change this default. Ask an organisation admin or HAPR.
• Save failed. The save did not go through. Try again, and contact support if it keeps happening. See Help chat and support.
• Reset failed. The reset did not go through. Try again.
• This form holds an image from before uploads became files. Reload the page to get the current form, then try again. Reload the page, then make your change again.