The participant area & sign-in

Customize “My participation” and check the path from sign-in to the ticket.

Before you start

You need editing access to event pages. Use a test event for a complete registration test.

Customize the attendee area

1. Open Web Builder → Landing Pages and choose My participation among the built-in pages.
2. Keep its fixed functional block. For example, add a short travel note after the registration form using the insertion slots.
3. Use the editor’s example data to check that the note, form and ticket are readable.
4. Open the attendee page in a separate browser window. Sign in with email and code and check where you are taken next.

Check your result

Your note supplements the attendee area without replacing its functions. After sign-in, the previously requested page should open. Test new registration and paid bookings separately and deliberately.

The built-in pages

All pages except Sign in and Program need a signed-in visitor. Anyone else is sent to sign in first and then comes straight back to the page they wanted.

Program is open to everyone by default: guests see the public event calendar (without slots), titled with the event name, and signed-in visitors see their own program including the slots they chose. To make it members-only, open the page in the editor and turn on Authentication required in the page settings.

Signing in with just an email

Participants never have to decide between "register" and "sign in". They enter their email and get a 6-digit code (or a link) by email. After that, FireVue works out the rest:

• Already registered? They continue where they left off.
• Someone registered them (for example a colleague or a parent, using this email)? That registration becomes theirs automatically.
• New? They register for the whole event and are only asked for their name, if it is missing.

Someone who only wants a single option (a slot open to guests, like a gala dinner) uses that slot's guest link or the Book only this option button on its details page. They are registered for that option alone, with it already chosen.

Password, Google and Apple sign-in remain available as alternatives. Someone who prefers a password simply enters an email and a password: if the sign-in fails (wrong password, or no account yet), they can continue with an email code. Once the code is confirmed, a new account is created with the password they typed.

Several people in one account

When your event allows registering multiple people, participants switch between them with Switch person in the header menu or the small arrow next to the name in the page title. Every page then shows that person's registration, slots and ticket.

Choosing slots and paying

On My participation, the registration form comes first; once it is saved, it folds away and the slots follow below. Every pick is saved immediately.

• A free slot is booked right away.
• A paid slot shows Not reserved yet until it is paid. The place is only held once the payment has started.

On the payment page, participants pay for one or several people of their account together. An online payment holds the places for 30 minutes; a bank transfer holds them until you confirm the payment in your participant list.

Designing the pages

Open Web Builder → Landing pages. The built-in pages are listed at the top, above your own pages. Each holds one fixed block that does the actual work. You can't delete or duplicate this block, but you can:

• change its texts, ticket design and status steps in the block's settings (under Ticket → Advanced you can also round the ticket background's corners and add space around it, so the page background shows),
• add anything you like above and below it – images, text, FAQs – like on any other page,
• place content between its sections, using the insertion points listed in the block's settings (for example After the registration form on My participation, or Before the calendar on Program),
• change the page's address and title in its page settings.

The fixed sections themselves always stay in place – insertion points only add to them. Some plugins put their block into an insertion point when you install them; you can move or remove it like any other block.

The event header and footer are shown on these pages too. The AI assistant can change the fixed block's settings, but never removes it.

💡 Tip: Open a built-in page in the editor to see exactly what participants will see – the editor shows sample data, so you can design it before anyone has registered.