---
title: Registration
description: Choose a registration mode and know what you can change later.
sidebar:
  order: 7
---

Every event has a registration app. The **mode** decides which forms you manage and whether money is involved.

## Modes

| Mode | Code | What attendees do |
| --- | --- | --- |
| Registration | `registration` | Fill a registration form |
| RSVP | `rsvp` | Yes / no (and maybe guests) |
| Ticketing | `ticketed` | Buy or claim tickets, then fill the order form |
| Check-in only | `check_in_only` | No public form — you import or add people |
| External | `external` | Register somewhere else; Micepad is used for onsite |

The sidebar label is **Ticketing** when the event is ticketed, otherwise **Registration**.

Check-in only also applies when the registration channel is `no_registration`.

## What you see in the sidebar

When you are allowed to manage forms:

1. **Overview** — counts by status (and orders/tickets if ticketed)
2. **Details** — open/close window, capacity, login options
3. **Forms** or **Order form** — form builder
4. If ticketed: **Tickets**, **Promo codes**, **Orders**, **Waitlist**

If the plan does not include registration forms, the section is locked and links to the feature gate.

## Switching modes

You can change mode until real data exists.

- From **ticketed**: blocked if any non-cart order or any ticket exists
- From **registration** or **rsvp**: blocked if those forms have submissions. Delete attendees first; their responses go with them

Switching does **not** convert existing form records. Old STI form types stay in the database but are hidden from the builder.

## Capacity and windows

Details lets you set an opening and closing datetime. Those values sync onto the forms.

Non-ticketed remaining capacity is the minimum of the plan attendee limit and the event guest cap, minus current participants. Ticketed events use per-ticket capacity instead.

## Login on public forms

Registration can offer email and Google login (`login_with_email`, `login_with_google`). RSVP can restrict who may respond (`rsvp_permission`, default `all_visitors`).