- 26 Mar 2026
- Print
- DarkLight
- PDF
Event Registration Forms
- Updated 26 Mar 2026
- Print
- DarkLight
- PDF
You can create registration forms for the events you host with Slate.
Creating an event registration form
To create an event registration form:
Go to Events.
Select an event template, or create a new one.
Select Edit Form.
Configure form fields as necessary. The remainder of this article discusses the form fields you can add to event registration forms and other configurations.
⭐ Best practice
Always create a registration form from the event template, rather than individual events. If you decide, for example, that you want to add more fields to your campus tour registration form, updating the form associated with the template cascades these updates to the registration forms for all individual campus tour events.
Guests vs attendees
If the registration limit should apply to guests as well, include a form field that is mapped to either Special Form Fields → Guests or Special Form Fields → Attendees.
Guests represents the number of people, not including the registrant, that will attend the event with the registrant. If the registrant brings 2 guests, guests would be 2.
Attendees is the number of people, including the registrant, that will attend. If the registrant brings 2 guests, attendees would be 3.
Type: Both Guests and Attendees are prompt-driven fields, so use the Form Builder Palette to add a form field that is compatible with prompt lists.
System Field: Select Special Form Fields and then select either Guests or Attendees
Prompts: By default, the prompt options for both Guests and Attendees go up to 5. Override system prompts to reduce this number, or even increase it.
Guests count toward the registration limit set for an event if "Include guests in registrant limit" is selected for the Include Guests setting under the Limits tab of the event settings. For example, the event may have a limit of 10 people. If 5 registrants each bring 1 guest, the limit would be met and the event would be marked as Full.
If the registrant limit is exceeded when guests are added, the registration limit default message or (or custom message if it has been configured) will appear in a pop-up window. The default message is: "Registration is no longer available because the registration capacity has been exceeded."
At the template or individual event level, Slate can count guests against the Registrant Limit using the Include Guests setting in the event/event template "Limits" tab:
Here is a truth table for the different setting combinations for the Include Guests setting:
Template Setting | ||||
|---|---|---|---|---|
Inherit from template | Include guests in registrant limit | Do not include guests in registrant limit | ||
Event Setting | Inherit from template | |||
Include guests in registrant limit | ||||
Do not include guests in registrant limit | ||||
The Include Guests setting will be factored into the Slate waitlist transfer functionality, meaning that guests will be included when a registration is transferred from the waitlist. The status of a related event shown on the related events selector will not reflect if there are waitlist spots available.
Ensure Slate collects the correct number of guests for the total registration amount by mapping only one form field to either Guests or Attendees under the Special Form Fields category.
Payment form widget
You can use the payment form widget on an event form to:
Calculate payment-due amounts and create person-scoped Payment Due interactions on the user’s timeline.
Collect payments as a part of form submission (Slate Payments only).
Email confirmation
The Email Confirmation system field can be used to ensure accurate email address entry.
System Field: Special Form Fields → Email Confirmation
The second email address entry is unique in that the value will not be stored in any other field other than the form field. This mapping is used only to prevent form submission if the Email Confirmation value does not exactly match the Email Address form field that is mapped to the Email system field under the Student Record.
Internal-only fields
Sometimes events require additional administrative processing steps once a student has registered. For example, a registrant for a campus tour may need to be assigned to a student guide.
A useful way to manage post-registration work is to add fields to the registration form that are configured as Internal Only. An Internal Only field will not display on the public registration page, but it will display on the administrative registration page. For example, a form field for Tour Guide may be created:
Type: Be sure to select a compatible format type for your question.
Label: This text will only display for your Slate administrators.
System Field: Internal Only fields can be mapped or unmapped.
Export Key: Provide an export key if you choose to keep your field unmapped.
Prompts: In this example, the prompts would be the names of the student guides.
Options: Be sure to check the Internal Only box.
After a student registers for the event, the processing team may open and edit the registration. When editing the event registration, the Internal Only fields will be visible to the processing team.
Hidden or internal?
Hidden fields never display on the registration page, even if the registration page is being viewed administratively. If you need to be able to enter data into a field that should only display administratively, configure the field as Internal Only.
Collecting group registrations
You can collect more than one registrant in a single form submission with group registrations.
Edit Mobile Pass
You can create mobile passes and badges for your events.
Select Edit Mobile Pass to configure its appearance.
