---
url: /kb/show-self-service/event-setup/access-types-and-registration.md
---

# Access types and registration

Each event uses **exactly one** access type. You cannot combine types — for example, you cannot keep a registration page in force and also use **Login with Name** for the same event.

## The four access types

These are the options on the event **Access** tab:

* **open** — Anyone with the event link can join. No name, email, or password is collected at login.
* **Login with Name** — Participants enter a name to join. This is not a pre-event registration.
* **Registration** — Participants sign up on the public registration page before the event. Registration **requires a password** and **double opt-in** (for GDPR). The password field is a standard field and cannot be removed.
* **Login with Name and Custom Fields** — Participants enter a name plus any additional fields you configure, at the moment they join. This login is effectively anonymous in advance: there are **no pre-event participant emails**. Confirmation, marketing, and reminder emails are sent only to people who registered through **Registration** with double opt-in. This access type does not provide the same email flow as Registration.

The English UI labels the first option **open** (lowercase).

## Registration fields

On the registration page, these standard fields are always present and required: first name, last name, email, and password. You can add optional or required **Custom Fields**, but you cannot turn off the password field or have the platform generate a password automatically.

## Changing the access type

The public registration page and registration path exist **only** while the access type is **Registration**. If you change the access type to anything else, that public registration page and path are **disabled**. The registration link no longer works as a registration page.

## When to use which type

Use **Registration** when you need a confirmed participant list and the double opt-in email flow before the event. Use **Login with Name** or **Login with Name and Custom Fields** when you only need details at join time and do not need the registration email flow. Use **open** when no identification is required.

## Related

* [Event links and Q\&A-only access](/event-setup/event-links)

## Configure in ContentHub Admin

1. Open the event in Content Hub Admin.
2. Open the **Access** tab.
3. Select exactly one access type:
   * **open**
   * **Login with Name**
   * **Registration**
   * **Login with Name and Custom Fields**
4. Save your changes. \[verify] the exact save control label.

If you switch away from **Registration**, the public registration page and registration path are disabled. Do not expect an already sent registration link to keep working as a registration page.

## If you choose Registration

The public registration page is available only when the event access type is **Registration**.

1. With **Registration** selected on the **Access** tab, review the standard fields. First name, last name, email, and password are required and cannot be removed. \[verify] exact field labels in English.
2. Open **Custom Fields** if you need extra questions. Add or edit those fields there. Do not try to replace the password field.
3. Optionally adjust registration page texts, **Design**, language, and timezone under **Access**.
4. Copy the **Registration Page** link from **Links & Experiences** when you are ready to share it.

The platform cannot generate a password and send it automatically. Participants must set a password themselves during registration, then complete double opt-in.

## See also

* [Event links and Q\&A-only access](/event-setup/event-links)
