Configure event questions, gifts, emails, and sharing

In GiveCampus Events, available controls depend on your assigned administrator role(s), access to the event, and the interface used by your institution.

Rules and troubleshooting

The event settings allow up to three suggested giving amounts. Event-invitation/reminder sequences must be considered separately from transactional confirmation emails. The email send validator requires an event sequence’s origin event to be active or complete before scheduling.

If a message or field is missing, check the event’s exact configuration and whether the question belongs to the registrant, guest, or another registration step. Do not assume every change applies retroactively to completed registrations.

How to use

Open Events → Events → select the event → Edit Event → Guest Information to manage registration fields and their order. Reusable event fields are available in event settings. Configure the registrant-affiliation requirement only with compatible affiliation settings.

Use Gifts settings to configure the giving experience offered alongside registration. Use Edit Event → Email Settings to edit and test the available transactional email templates. The event also has sequences, capabilities, sharing, waitlist settings, name-tag settings, and unique tracking links.

Edit an event confirmation or other transactional email

1. Open Events → Events → select the event → Edit Event → Email Settings.
2. Scroll to Email Template Name at the bottom. Select the template name or its pencil icon, such as Registration Confirmation or Registration Summary.
3. Edit the subject and body using the controls shown. Use that template's merge-token picker for registration details, event details and registration-management links.
4. Save, then send a test and check the received email, including images, buttons and merge-token examples.

Other available templates can include Registration Reminder, RSVP No Confirmation, Waitlist Confirmation and Waitlist Invitation. Reminder, RSVP No and waitlist templates appear when the corresponding event option is configured. The reminder's edit action is no longer offered after that reminder has been sent.

This area edits transactional event emails. Outreach emails and event Sequences are separate workflows, even if both use an editor called Composer. Do not paste Outreach-only personalization or advocate-link tokens into a transactional event template; use the tokens offered by that editor.

New events, existing events and cloned events

The new email editor, Composer, is available for Events transactional emails as of November 6, 2026. New events automatically use it for Registration Confirmation, Registration Summary, Registration Reminder, RSVP No Confirmation, Waitlist Confirmation and Waitlist Invitation. Individual templates still appear according to the event's reminder, RSVP No and waitlist settings.

Existing and cloned emails are not automatically migrated. A cloned event retains the source templates' format and content. A legacy template continues sending in its current form until you choose to convert that individual email and save it.

To convert a legacy template, open Events → Events → select the event → Edit Event → Email Settings and click that template's name or pencil icon. The Email conversion prompt offers Convert or Use legacy editor. Choose Convert, review the imported content and image blocks, make any adjustments, and click Save. Opening the converted preview and leaving without saving does not persist the conversion.

Conversion applies to one template at a time; there is no bulk-convert action. You can keep an unconverted template in the legacy editor. Once a template is converted and saved, there is no supported option to convert it back to the legacy editor. Review carefully before saving.

Subject lines, saving and testing

The subject line has an emoji picker and its own merge-token menu. Use the tokens offered for that email; body and subject token lists differ. Registration and waitlist emails also have different applicable body tokens. Do not paste an Outreach-only token into these transactional messages.

Edits are not automatically saved. Click Save to apply the subject and body changes. When leaving with unsaved edits, choose Save and continue or Continue without saving according to your intent. Use Send Test Email to inspect the received message; in Composer, sending the test saves the edits first. Test emails use example registration data. Saving a template does not resend previously delivered confirmations or change another template.

School logos and event-email images

The school logo is an editable image block. Select it to resize, replace or remove it. Add other images directly to each template. Converting a legacy template brings its school logo and existing email Event Image into image blocks; check for duplicate images if you had also pasted a logo into the original body.

The old shared Email Settings → Image control is absent for new Composer events. For an existing event with legacy templates, it remains until all editable templates use Composer. That control is separate from the public event page's Event Image setting.

School-logo changes do not automatically update already-created or edited email templates. Update the image in each affected template, save and test. There is no single image change that updates all Composer event emails.

Administrator roles

Superadmin, Events Superadmin, Advanced Events Admin, Basic Events Admin, Events Content Manager and Events Communication Admin include event editing within their assigned event access. An administrator with access to the event can edit its available email templates. Partners assign predefined roles; they do not toggle a separate email-editor permission within a role.