Getting started¶

Midsummer is a multi-tenant platform: each convention (“event”) runs on its own subdomain or custom domain, and you sign in with the email address you registered with — there are no usernames to remember.

Finding your event¶

Every event has its own address. Depending on how your convention is set up, yours will look like one of:

https://yourevent.midsummer.cloud — a Midsummer-hosted subdomain.
https://register.yourcon.org — a custom domain the organizers configured.

If you are not sure which address to use, ask your event organizers. The public schedule, registration form, and shop are linked from the event’s landing page.

Signing in¶

Midsummer authenticates you with your email address, not a username. There are three ways to sign in:

Magic links (passwordless): Enter your email and Midsummer emails you a one-time link. Clicking it signs you in instantly. Magic links expire after a short window and can only be used once.
Password: If your account has a password set, you can sign in with your email and password.
Single sign-on (SSO): Some events are connected to an identity provider (OIDC/OAuth2). For those, a “Sign in with …” button appears on the login page.

Note

After signing in, Midsummer returns you to the page you came from (for example, a checkout or application form) instead of dropping you on a dashboard.

Two-factor authentication (2FA)¶

Accounts can be protected with a second factor. Depending on how your event is configured, 2FA may be optional or required, and may use:

TOTP — an authenticator app such as Google Authenticator, Authy, or 1Password.
Email — a one-time code sent to your address.

If you lose access to your second factor, contact your event organizers; they can reset 2FA on your account.

Your account & personnel file¶

Each account has a personnel file that event staff and organizers can use to manage your relationship to the event (registrations, vendor applications, staff assignments, and so on). You can manage your own contact details, and — where the event allows it — edit your own registration.

Understanding roles¶

What you can see and do depends on your role. There are four effective permission levels, described in detail on the HR & permissions page:

Level	Roughly means
`public`	Not signed in, or no role for this event/module.
`staff`	Assigned to a department that owns the module (e.g. a check-in volunteer).
`admin`	Can configure a module for the event (e.g. create registration forms).
`superadmin`	Full control of a module for the event.

If a page tells you that you do not have permission, you either need to sign in, or you need an organizer to grant you a role. See The four permission levels.

Getting help¶

If you hit an error in the app, it will look like the panel below and include a link back to this site:

┌─────────────────────────────────────────────┐
│ ⚠  E:REG:1 — ConfigError: No Form Available │
│                                             │
│   ▸ For Attendees/Users                     │
│   ▸ For Event Organizers                    │
│   ▸ For Event Technical Staff               │
│   About E:REG:1  ↗                          │
└─────────────────────────────────────────────┘

Click About <code> to jump straight to that error’s page, which explains the problem separately for each of the three audiences above.