Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Self Mod/Self Service

Tip

Introduced July 2026

Intro

Self Mod is what we call the ability for an event participant (the primary registrant) to alter their party’s registration directly.

Self mod supports:

  • off/add only/add+remove mode selection per event
  • magic link-based access control for registrants (no password, no login)
  • activity add (and remove) as well as update
  • guest cancellation
  • registrant dietary + accessibility updates
  • primary registrant contact information updates
  • resend confirmation email
  • direct link to pay any open balances

Self mod does not support:

  • swap guest (near-term plans to ship access controlled programming put the brakes on this)
  • add a gift (pending implementation of multi-event-gift capability first)
  • add guest (they can simply register separately)

We’ll be adding all three of these before the year is over.

What control do I have over self mod?

You can set self mod on a per event basis.

  • Off - registrants can’t modify anything and the “Update my Registration” button is hidden from the confirmation
  • Add Only - recommended once you get close to your event so your numbers can’t go down without direct staff intervention
  • Add+Remove - all the features listed above (“supports”) are available
FeatureOffAdd OnlyAdd+Remove
Update my Registration buttonHiddenVisibleVisible
Magic link accessNoYesYes
Add activitiesNoYesYes
Update dietary/accessibility needsNoYesYes
Update primary registrant contact informationNoYesYes
Resend confirmation emailNoYesYes
Pay open balancesNoYesYes
Change existing activity selectionsNoNoYes
Cancel activitiesNoNoYes
Remove guestsNoNoYes

You set this on the Edit Event screen. Look for a heading called Self Mod.

The default is OFF. That seemed safest.

You can also specify:

  • an email address to notify when participants are removed via self mod. This includes guest removals and cases where cancelling a participant’s final activity also cancels that participant from the event. The use case for this is a very invested event manager who needs realtime updates on melt.

  • an intro blurb for the top (inside) screen of self mod. What you’ll use this for will vary from event to event. It is not required.

How do primary registrants access self mod?

  • the confirmation screen has a link to initiate the process (if active)
  • the confirmation email has an “Update my Registration” button (if active)
  • the customer service screen for a registration record contains a button to send the magic link email to the primary registrant (also only if active)

Self mod access is solely available via magic link. We’ll evaluate the value of folding access into the AlumnIQ Profile once we see what kind of utilization this function acquires.

What is being monitored?

  • access requests
  • accesses
  • updates to contact information
  • updates to dietary restrictions/accessibility needs
  • activity adds, updates, and removes
  • guest removes
  • self-triggered confirmation resends

We’re considering how best to include this in customer service screens both in aggregate and individual form. It all informs how we prioritize future enhancements to self mod.

Miscellaneous Notes

  1. When adding an activity in self mod, the then current pricing is what is presented to the participant. We do not grandfather rates as of the party’s creation date for late additions.

  2. Capacities are maintained just as strictly as they are for mainline registration.

  3. Cancellation of the only/final activity under a participant will also automatically trigger cancellation of the participant from the event. This was deemed logically consistent and easier to explain.

  4. If payment is due we will direct the participant to pay via the existing confirmation page.

  5. Guests DO NOT have access to self mod - only the primary. Keep that in mind.