> For the complete documentation index, see [llms.txt](https://eventx-hq.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eventx-hq.gitbook.io/knowledge-base/registration-and-ticketing/registration-form/manage-registration.md).

# Manage Registration

Manage Registration allows attendees to update their own registration details from the event landing page without needing to contact the organizer. Attendees can edit their profile fields, update add-on selections, and pay for newly selected paid add-ons — all through a self-service flow. The feature supports both logged-in and logged-out access via email OTP verification.

## For Organizers

### Enabling Manage Registration

1. Go to **Registration Form** in the portal sidebar.
2. Toggle ON the **Enable Attendee Registration Editing** option.
3. Ensure the event has at least one registration form configured.

![](/files/dywbjqfKsk6rshJe6fdC)

Once enabled, a **Manage Registration** button appears on the event landing page sidebar for all attendees.

![](/files/a09DuOWliJRVHiAUv5E3)

### Viewing Self-Service Activity

All changes attendees make through Manage Registration are recorded in the attendee activity log with the action **Registered Details Updated**. This includes which profile fields were updated and which add-ons were selected.

1. Go to **People List** on the left.
2. Click on the profile icon of the attendee, then click the activity log icon.
3. The activity log shows a history of changes made through Manage Registration, indicating which fields were updated and their new values. Each change shows the field name and what it was set or changed to.

For more details, see [View Attendee Activity Logs](https://eventx-hq.gitbook.io/knowledge-base/attendee-management/managing-attendees/view-attendee-activity-logs).

## How It Works

### Accessing Manage Registration

The entry flow differs depending on whether the attendee is logged in.

#### Logged-out Attendee (OTP Verification)

1. On the event landing page, click **Manage Registration** in the sidebar.
2. A dialog opens. Enter the **Registration email** you used when registering for the event.

   ![](/files/nl9pgCGEgVQJFKAdjAqy)
3. Click **Send verification code**.
4. Check your email for a 5-digit verification code. The email is sent only if your registration is found — if you do not receive a code, it means the email is not associated with any registration for this event.

   **Note:** After sending a code, you must wait 2 minutes before requesting another one. If you request too many codes in a single day (10 within 24 hours), further requests will be silently blocked to protect against abuse.
5. Enter the verification code and click **Verify and continue**.
6. If the email is associated with multiple registrations (e.g., you registered twice using the same email), a selection screen appears. Choose the registration you want to edit. Each row shows the registration name, ticket name, add-on summary, and registration date to help you identify the correct one.
7. After verification (or selection), the managed registration editor opens with your current details loaded.

#### Logged-in Attendee

1. Click **Manage Registration** in the sidebar.
2. The system automatically identifies your registration — no OTP is required. The managed registration editor opens immediately.

### Session Timeout

The manage registration session uses a 15-minute token. Each time you load or reload your registration details, a **fresh token** is issued, extending the session. This ensures long checkout flows (e.g., adding paid add-ons) are not interrupted as long as you remain active. If the session expires, you must re-authenticate via the OTP flow or re-log in.

## Editing Your Registration

The managed registration editor proceeds through a series of steps based on what is available for your specific ticket. Not all steps appear — only the ones relevant to your registration are shown.

### Ticket Step

If your registration has a ticket assigned, the ticket details are shown in read-only mode. You **cannot** switch to a different ticket type through this flow. This step is informational only and is skipped if you do not have a ticket.

### Add-ons Step

If your ticket class has add-ons available, you can manage them here.

![](/files/PThalaaNNdHuOWazJoXH)

**Free add-ons (price = $0):**

* You can select additional free add-ons by checking their checkbox.
* Free, non-compulsory add-ons you already have can be **deselected** by unchecking the checkbox. This removes them from your registration when you save.

**Paid and compulsory add-ons:**

* Paid add-ons you already have are **locked** — they appear as checked and disabled. You cannot remove them.
* Compulsory add-ons are also locked and cannot be removed.
* To add **new** paid add-ons, check their box. These will require payment in a later step.

**Waitlisted add-ons:**

* Add-ons that you are already on the waitlist for have their checkbox hidden while the add-on remains out of stock.
* If you previously joined the waitlist for a free add-on and stock becomes available, the system automatically confirms it when you save.

### Registration Form Step

Edit your profile fields such as name, organization, job title, phone number, city, country, and any custom fields configured by the organizer.

**Note:**

* Some fields may be read-only if the organizer has restricted them from attendee editing.
* The email address used for registration cannot be changed through this flow.
* Secondary email addresses (if configured) can be edited unless restricted by the organizer.

### Review Step

The review step shows your updated registration details before submitting:

![](/files/AG0BISLvz8ENTc3LTqja)

* All form fields are displayed with their current values.
* All selected add-ons are listed in a single summary.
* If only free add-ons were changed, the button reads **Save**. Clicking it saves all changes and shows a success confirmation.
* If paid add-ons were selected, the button reads **Next**. Clicking it proceeds to the payment step.

### Payment Step (Paid Add-ons)

When you select new paid add-ons, they must be paid through a separate amendment order before they are added to your registration:

1. The payment step shows an order summary with the add-ons being purchased, the total amount to pay, and the available payment methods (Stripe, KPay, offline payment, etc., depending on the event's payment settings).
2. Fill in any required billing information and select a payment method.
3. Complete the payment. On successful payment, the paid add-ons are added to your registration and the success dialog appears.

**Note:** If you start a payment but do not complete it, any prior pending amendment orders for the same registration are automatically cancelled. Only the most recent amendment order is valid.

## How Add-on Changes Are Handled

The system handles free and paid add-ons differently to ensure that paid add-ons are only acquired through a completed payment:

| Add-on Type           | Action   | Behavior                                     |
| --------------------- | -------- | -------------------------------------------- |
| Free (not compulsory) | Select   | Added immediately on save, no payment needed |
| Free (not compulsory) | Deselect | Removed immediately on save                  |
| Free (compulsory)     | —        | Cannot be removed (locked)                   |
| Paid (already owned)  | Deselect | Blocked — cannot be removed                  |
| Paid (newly selected) | Select   | Requires payment via amendment order         |

When you save after adding free add-ons and paid add-ons in the same session:

1. The free add-on changes are applied immediately.
2. If paid add-ons need to be purchased, you are routed to the payment step.
3. Only after successful payment are the paid add-ons confirmed.

Behind the scenes, the editor uses an upsert/sync approach: free add-ons you omit from your selections are removed, and paid add-ons you already have are always preserved (even if omitted from the request). This is how the system supports unselecting free add-ons while preventing accidental removal of paid ones.

## Remarks

1. If you share the same email address across multiple registrations, the OTP verification flow will list all matching registrations for you to choose from.
2. The OTP verification process does not reveal whether an email is registered — the response is the same for both found and not-found emails, protecting attendee privacy.
3. A verification code is valid for a limited time. If it expires, you must request a new one (after the 2-minute throttle window).
4. After 5 incorrect code attempts within 10 minutes, the email is temporarily locked from further verification attempts. A new code must be requested (after the 2-minute throttle) to reset this lock.
5. The manage registration session lasts 15 minutes and is refreshed each time you load your details. If it expires mid-flow, you are prompted to re-authenticate.
6. Any prior pending amendment orders for your registration are cancelled when a new payment is initiated, preventing duplicate charges.

## Limitation

1. Ticket type switching is **not supported** — you cannot change to a different ticket class through Manage Registration.
2. Paid add-ons you already own **cannot be removed** through this flow. Contact your organizer if you need to remove a paid add-on.
3. The maximum number of verification code requests is 10 per email per 24 hours. After this limit, further requests are silently blocked (the UI shows a success message but no email is sent).
4. There is a 2-minute cooldown between verification code requests for the same email.
5. Compulsory add-ons assigned by the organizer cannot be removed by the attendee.

## Related Articles

* [Registration Form Setup](/knowledge-base/registration-and-ticketing/registration-form/registration-form-setup.md)
* [Ticketing Setup](/knowledge-base/registration-and-ticketing/ticketing-and-pricing/ticketing-setup.md)
* [Add-on Item](/knowledge-base/registration-and-ticketing/ticketing-and-pricing/add-on-item.md)
* [Attendee Portal](/knowledge-base/attendee-management/managing-attendees/attendee-portal.md)
* [Event Settings - General Settings](/knowledge-base/event-setting/event-configuration/event-settings/general-settings.md)

## Frequently Asked Questions

### Q: How long is the OTP valid?

**A:** The OTP is valid for a limited time (approximately 5 minutes). The Manage Registration session itself has a 15-minute timeout.

### Q: Can attendees change their ticket type through Manage Registration?

**A:** No. Attendees cannot change their ticket type. Only profile fields and add-on selections can be modified.

### Q: What happens if an attendee removes a paid add-on?

**A:** Removing an existing paid add-on is not allowed if the add-on has already been paid for. Only free add-ons can be removed freely. New paid add-ons require payment.

### Q: Where can I see what changes attendees made?

**A:** All changes are recorded in the attendee activity log with the action **Registered Details Updated**. Go to **People List** > attendee profile > activity log icon.